Re: developer newsletter

[John Mandereau]

Le mercredi 13 janvier 2010 à 15:15 +0100, John Mandereau a écrit :
> Another thing that we could do instead of creating another list is
> writing down as a specification (even written quite informally) the
> important changes already started i.e. the i18n of Texinfo, stuff
> specific to building the website on lilypond.org (all details that are
> independent of the build system), and switching the build system.  In
> each specification we should at least explain the desired goal, and we
> may specify the expected amount of work and the tools to be used.
> 
> Draft specifications could be developed on the wiki or on the list; I'd
> prefer mainly on the wiki, discussion pages on the wiki being definitely
> usable for discussion, so this would not overload the list traffic.
> Specifications which are finalized and approved by all interested
> developers may then be added in the CG.
> 
> Of course, all this may not be worth the extra work, but looking back at
> my very little development experience (especially LilyPond-related), I
> believe it's worth trying it.  If there are no objections or better
> suggestions, I'm gonna start doing this for the translation
> infrastructure.

Sorry for not having completed enough my initial reply: having these
kinds of specifications would allow us discover problems before
implementation, tests and committing to Git, that's why I proposed this,
to hopefully help solving the development organization issues you
pointed out.

Best,
John

signature.asc
Description: Ceci est une partie de message numériquement signée