[Haskell-cafe] Guidelines for proposing library changes

Donald Bruce Stewart dons at cse.unsw.edu.au
Tue Oct 31 03:58:26 EST 2006


ross:
> On Wed, Oct 25, 2006 at 11:58:59AM +1000, Donald Bruce Stewart wrote:
> > After some discussion on the libraries list, I've put up the suggested
> > 'best practice' for proposing library changes, here:
> > 
> >     http://haskell.org/haskellwiki/Library_submissions 
> > 
> > The idea is to reduce the number of 'bikeshed' discussions we're having, 
> > ensure that submissions are not dropped, and generally improve
> > productivity.
> > 
> > People should refer to this when proposing new functions for the core
> > libraries, at risk of not having the suggestion adopted or considered ;)
> 
> Perhaps it would be kinder to the mail system to suggest attaching the
> patch to the ticket instead of mailing it.  These patches to base are
> quite big, and are causing trouble. 

Good idea. 

So instead of 'darcs send', we'd use the Trac system to send a combined
proposal and patch?

>                        And if we could get the ticket mail
> sent to libraries instead of ghc-users, that would make the procedure
> simpler, too.

Ah yes. Igloo or SimonM, do you admin trac?

For the time being I've increased the libraries@ limit to 250k, inline
with that for ghc-cvs and cvs-all at .

-- Don


More information about the Libraries mailing list