Open up the issues tracker on ghc-proposals

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Open up the issues tracker on ghc-proposals

David Feuer
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
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: Open up the issues tracker on ghc-proposals

Richard Eisenberg-4
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 <[hidden email]> 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
> [hidden email]
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: Open up the issues tracker on ghc-proposals

Joachim Breitner-2
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 <[hidden email]> 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
> > [hidden email]
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
> _______________________________________________
> ghc-devs mailing list
> [hidden email]
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
--
Joachim Breitner
  [hidden email]
  http://www.joachim-breitner.de/

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Open up the issues tracker on ghc-proposals

David Feuer
In reply to this post by Richard Eisenberg-4
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 <[hidden email]> 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 <[hidden email]> 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
> [hidden email]
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: Open up the issues tracker on ghc-proposals

David Feuer-2
In reply to this post by Joachim Breitner-2
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 <[hidden email]> 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
> > > [hidden email]
> > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> >
> > _______________________________________________
> > ghc-devs mailing list
> > [hidden email]
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>


_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: Open up the issues tracker on ghc-proposals

Joachim Breitner-2
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 <[hidden email]> 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
> > > > [hidden email]
> > > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> > >
> > > _______________________________________________
> > > ghc-devs mailing list
> > > [hidden email]
> > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
>
>
--
Joachim Breitner
  [hidden email]
  http://www.joachim-breitner.de/

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Open up the issues tracker on ghc-proposals

GHC - devs mailing list
In reply to this post by David Feuer
|  > Sometimes, a language extension idea could benefit from
|  some community discussion before it's ready for a formal proposal.
|  
|  Can I point out it's not only ghc developers who make proposals. I'd
|  rather you post this idea more widely.

The Right Thing is surely for the main GHC proposals pave
        https://github.com/ghc-proposals/ghc-proposals
to describe how you can up a "pre-proposal".  That is, document
the entire process in one, easy to find, place.

Mind you, I'm unclear about the distinction between a pre-proposal
and a proposal.  Both are drafts that invite community discussion,
prior to submitting to the committee for decision.

Simon

|  -----Original Message-----
|  From: Glasgow-haskell-users <glasgow-haskell-users-
|  [hidden email]> On Behalf Of Anthony Clayden
|  Sent: 02 May 2018 02:34
|  To: [hidden email]; [hidden email]
|  Subject: Re: Open up the issues tracker on ghc-proposals
|  
|  > On May 1, 2018, at 2:24 PM, David Feuer <david.feuer at
|  gmail.com> wrote:
|  >
|  > Sometimes, a language extension idea could benefit from
|  some community discussion before it's ready for a formal proposal.
|  
|  Can I point out it's not only ghc developers who make proposals. I'd
|  rather you post this idea more widely.
|  
|  As a datapoint, I found ghc-users and the café just fine for those
|  discussions.
|  Ghc-users seems to have very low traffic/is rather wasted currently.
|  And I believe a lot of people pre-discuss on reddit.
|  For ideas that have been on the back burner for a long time, there's
|  often wiki pages. (For example re Quantified
|  Constraints.)
|  
|  > 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.
|  
|  I'm not against that. There gets to be a lot of cruft on some
|  discussions about proposals, so I'd expect we could archive it all
|  once a proposal is more formalised.
|  
|  AntC
|  
|  _______________________________________________
|  Glasgow-haskell-users mailing list
|  [hidden email]
|  http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs