Drastic Prelude changes imminent

[Gabriel Gonzalez]

Whether or not we use Github, you have to admit that the development 
process for core libraries is not very transparent in its current form.  
We have evidence for this right now: lots of people have been 
complaining that they never realized that this change got into GHC-7.10.

You don't have to adopt my specific suggestion, but you can't just keep 
doing business as usual either and pretend that there isn't a problem.  
If you reject my Github suggestion then propose a better solution for 
increasing the transparency and visibility of the process.

On 1/27/15, 1:40 PM, David Feuer wrote:
>
> Github is not and has never been a focus for GHC development. It seems 
> a bit odd to separate things into "noise" on Trac and the mailing 
> lists and, theoretically, "signal" on GitHub. I agree that important 
> community discussions should not be happening on Phabricator, but they 
> generally aren't anyway.
>
> On Jan 27, 2015 4:09 PM, "Gabriel Gonzalez" <gabriel439 at gmail.com 
> <mailto:gabriel439 at gmail.com>> wrote:
>
>     I think that all breaking changes that are approved on this
>     mailing list should be migrated to a much more visible Github
>     issue (i.e. https://github.com/ghc/ghc) before final approval. 
>     You can still do all actual pull requests and coding via
>     Phabricator, but the discussion should be on Github, because the
>     barrier for new people to join in on the discussion is lower.  You
>     will get a lot more discussion and visibility into these changes
>     purely by using Github as the central forum.
>
>     This mailing list is not an appropriate forum for discussion for
>     several reasons:
>
>     A) The volume of email is too high.  Only people who are experts
>     at managing their inbox subscribe here.
>     B) There is too little signal to noise (for a beginner). Why would
>     a beginner want to join a mailing list that debates such dry
>     topics as whether or not to add Data.Intersperse.sequence?
>     C) There's no (easy) way to subscribe to (or mute) a particular
>     thread (unlike Github where you can easily watch or mute specific
>     issues)
>
>     Pretty much everybody on this mailing list is a die-hard Haskell
>     expert and that's not representative of the Haskell community at
>     large.  Migrating important topics to Github will give us a more
>     representative sampling of the community and will also help
>     centralize the discussion better.
>
>     On 1/27/15, 12:54 PM, Johan Tibell wrote:
>>     A point about process: I've been aware of this change for quite
>>     some time but I wasn't aware of the details (e.g. the changes to
>>     Data.List). It's easier to judge proposals like this if the
>>     complete list of changes are listed in some proposal page.
>>
>>
>>     _______________________________________________
>>     Libraries mailing list
>>     Libraries at haskell.org  <mailto:Libraries at haskell.org>
>>     http://www.haskell.org/mailman/listinfo/libraries
>
>
>     _______________________________________________
>     Libraries mailing list
>     Libraries at haskell.org <mailto:Libraries at haskell.org>
>     http://www.haskell.org/mailman/listinfo/libraries
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20150127/c6acb64a/attachment-0001.html>