Open up the issues tracker on ghc-proposals

David Feuer

1 May 2018 1 May '18

2:24 p.m.

Sometimes, a language extension idea could benefit from some community discussion before it's ready for a formal proposal. I'd like to propose that we open up the GitHub issues tracker for ghc-proposals to serve as a place to discuss pre-proposal ideas. Once those discussions converge on one or a few specific plans, someone can write a proper proposal.

Attachments:

attachment.html (text/html — 385 bytes)

Show replies by date

Richard Eisenberg

1 May 1 May

3:23 p.m.

I like this idea, but I think this can be done as a PR, which seems a better fit for collaborative building. The author can specify that a proposal is a "pre-proposal", with the goal of fleshing it out before committee submission. If it becomes necessary, we can furnish a tag to label these, but I'm honestly not sure we'll need to. Richard

...

On May 1, 2018, at 2:24 PM, David Feuer wrote:

Sometimes, a language extension idea could benefit from some community discussion before it's ready for a formal proposal. I'd like to propose that we open up the GitHub issues tracker for ghc-proposals to serve as a place to discuss pre-proposal ideas. Once those discussions converge on one or a few specific plans, someone can write a proper proposal. _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Joachim Breitner

3:31 p.m.

Hi, the distiction between an issue and a pull request is a rather thin one, and the Github API actually allows you to upgrade an issue to a pull request… So no need to be picky about the precise form: If someone has something interesting to say in an issue without yet having some text to attach to it, by all means go for it! Cheers, Joachim Am Dienstag, den 01.05.2018, 15:23 -0400 schrieb Richard Eisenberg:

...

I like this idea, but I think this can be done as a PR, which seems a better fit for collaborative building. The author can specify that a proposal is a "pre-proposal", with the goal of fleshing it out before committee submission. If it becomes necessary, we can furnish a tag to label these, but I'm honestly not sure we'll need to.

Richard

...
On May 1, 2018, at 2:24 PM, David Feuer wrote:

Sometimes, a language extension idea could benefit from some community discussion before it's ready for a formal proposal. I'd like to propose that we open up the GitHub issues tracker for ghc-proposals to serve as a place to discuss pre-proposal ideas. Once those discussions converge on one or a few specific plans, someone can write a proper proposal. _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/

David Feuer

3:48 p.m.

The ghc-proposals repository does not have the issue tracker enabled, so it's currently impossible to open an issue. On Tuesday, May 1, 2018 3:31:24 PM EDT Joachim Breitner wrote:

...

Hi,

the distiction between an issue and a pull request is a rather thin one, and the Github API actually allows you to upgrade an issue to a pull request…

So no need to be picky about the precise form: If someone has something interesting to say in an issue without yet having some text to attach to it, by all means go for it!

Cheers, Joachim

Am Dienstag, den 01.05.2018, 15:23 -0400 schrieb Richard Eisenberg:

...
I like this idea, but I think this can be done as a PR, which seems a better fit for collaborative building. The author can specify that a proposal is a "pre-proposal", with the goal of fleshing it out before committee submission. If it becomes necessary, we can furnish a tag to label these, but I'm honestly not sure we'll need to.

Richard

...
On May 1, 2018, at 2:24 PM, David Feuer wrote:

Sometimes, a language extension idea could benefit from some community discussion before it's ready for a formal proposal. I'd like to propose that we open up the GitHub issues tracker for ghc-proposals to serve as a place to discuss pre-proposal ideas. Once those discussions converge on one or a few specific plans, someone can write a proper proposal. _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Joachim Breitner

4:09 p.m.

Fixed! Am Dienstag, den 01.05.2018, 15:48 -0400 schrieb David Feuer:

...

The ghc-proposals repository does not have the issue tracker enabled, so it's currently impossible to open an issue.

On Tuesday, May 1, 2018 3:31:24 PM EDT Joachim Breitner wrote:

...
Hi,

the distiction between an issue and a pull request is a rather thin one, and the Github API actually allows you to upgrade an issue to a pull request…

So no need to be picky about the precise form: If someone has something interesting to say in an issue without yet having some text to attach to it, by all means go for it!

Cheers, Joachim

Am Dienstag, den 01.05.2018, 15:23 -0400 schrieb Richard Eisenberg:

...
I like this idea, but I think this can be done as a PR, which seems a better fit for collaborative building. The author can specify that a proposal is a "pre-proposal", with the goal of fleshing it out before committee submission. If it becomes necessary, we can furnish a tag to label these, but I'm honestly not sure we'll need to.

Richard

...
On May 1, 2018, at 2:24 PM, David Feuer wrote:

Sometimes, a language extension idea could benefit from some community discussion before it's ready for a formal proposal. I'd like to propose that we open up the GitHub issues tracker for ghc-proposals to serve as a place to discuss pre-proposal ideas. Once those discussions converge on one or a few specific plans, someone can write a proper proposal. _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/

David Feuer

3:35 p.m.

I suppose that would be a reasonable alternative. But to keep discussion tracking reasonable, I suspect it would be best to close the pre-proposal PR and open a new one (with mutual links) for the actual proposal if and when the time comes. On Tue, May 1, 2018, 3:24 PM Richard Eisenberg wrote:

...

I like this idea, but I think this can be done as a PR, which seems a better fit for collaborative building. The author can specify that a proposal is a "pre-proposal", with the goal of fleshing it out before committee submission. If it becomes necessary, we can furnish a tag to label these, but I'm honestly not sure we'll need to.

Richard

...
On May 1, 2018, at 2:24 PM, David Feuer wrote:

Sometimes, a language extension idea could benefit from some community discussion before it's ready for a formal proposal. I'd like to propose that we open up the GitHub issues tracker for ghc-proposals to serve as a place to discuss pre-proposal ideas. Once those discussions converge on one or a few specific plans, someone can write a proper proposal. _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

2576

Age (days ago)

2576

Last active (days ago)

List overview

Download

5 comments

4 participants

participants (4)

David Feuer
David Feuer
Joachim Breitner
Richard Eisenberg