The GHC Proposals Process

[Eric Seidel]

I've thought about this a little. The only advantage I can think of is that moving to GitLab would make it easier to cross-reference other GHC issues. 

For example, in the record-set-field proposal[1] people have referenced a few different Trac tickets. Sometimes the reference includes a link to the ticket and sometimes it's just "#1234". GitHub (and I hope GitLab) has a nice feature that automatically renders references to other issues as links. It works across projects too, and the comment editor helps you search for the correct issue while typing.

This would be a nice convenience, but I'm not sure if it pulls its weight in comparison to the greater visibility of GitHub.

Eric

[1]: https://github.com/ghc-proposals/ghc-proposals/pull/158

On Fri, Jan 4, 2019, at 13:56, Ben Gamari wrote:
> On January 4, 2019 12:56:58 PM EST, Ara Adkins <me at ara.io> wrote:
> >Hey All,
> >
> >Now we have our own git instance in GitLab, are there any plans to move
> >the
> >proposals process from GitHub?
> >
> >_ara
> 
> I haven't considered the possibility of moving the proposal process and 
> I'm not sure I see a compelling reason to do so. I would be happy to 
> consider arguments otherwise but it seems to me that the process is 
> running reasonably well on GitHub and benefits from the broad reach that 
> GitHub provides.
> 
> Cheers,
> 
> - Ben 
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs