From: Graham Percival Date: Wed, 7 Sep 2011 23:03:05 +0000 (+0100) Subject: Doc: CG: remove more GOP material X-Git-Tag: release/2.15.11-1~9 X-Git-Url: https://git.donarmstrong.com/lilypond.git?a=commitdiff_plain;h=bf643d01ad9b911d590a456dace574685dd1664d;p=lilypond.git Doc: CG: remove more GOP material --- diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi index b9dcbecd88..515763c352 100644 --- a/Documentation/contributor/administration.itexi +++ b/Documentation/contributor/administration.itexi @@ -385,14 +385,6 @@ lilypond. Should we switch to something like gerritt? (prep: 5 hours. discuss: 15 hours) -@item @strong{Subdomains of *.lilypond.org}: -Unless Jan has a really weird DNS hosting setup, there are no -technical barriers to having names like lsr.lilypond.org, -frog.lilypond.org, or news.lilypond.org. Is this something that we -want to do? - -(prep: 1 hours+2 weeks. discuss: 5 hours) - @item @strong{Clarity for sponsorships}: We currently do not advertize bounties and sponsorships on the webpage. How much advertising do we want, and what type? @@ -400,27 +392,6 @@ Should we change the "structure" / "framework" for bounties? (prep: 2 hours. discuss: 10 hours) -@item @strong{Separate branches for active development}: -it might be good to have @emph{everybody} working on separate -branches. This complicates the git setup, but with sufficient -logic in lily-git.tcl, we can probably make it transparent to -newbies. However, we'd need a reliable person to handle all the -required merging and stuff. - -(prep: 2 hours. discuss: 10 hours) - -@item @strong{When do we add regtests?}: -There is a discrepancy between our stated policy on adding -regtests, and our actual practice in handling bugs and patches. -Clarify. - -There is also a wider question how to organize the regtests, such -as where to put interesting-console-output regtests, including -stuff like lilypond-book and midi2ly in a sensible manner, and -possibly including regtests for currently-broken functionality. - -(prep: 2 hours. discuss: 5 hours) - @item @strong{code readability}: "Our aim when producing source code for Lilypond in whatever language is that it should be totally comprehensible to a