Merge branch 'lilypond/translation' of ssh://git.sv.gnu.org/srv/git/lilypond into...

[lilypond.git] / Documentation / contributor / administration.itexi

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 1208b4beaebc328bdf1bde33ad66edbd06e489f4..4f98519e91191757dba9c87f569da249fd632e37 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -277,7 +277,7 @@ We often receive reports of typos and minor text updates to the
 documentation. It would be great if somebody could create
 properly-formatted patches for these corrections.
 
-Technical requirements: ability to run @ref{Lilybuntu}.
+Technical requirements: ability to run @ref{Lilydev}.
 
 @item LSR editor:
 LSR contains many useful examples of lilypond, but some snippets
@@ -294,7 +294,7 @@ chapters 1 and 2 (or be willing to read the docs to find out).
 often find them in Ponds of Lilies) and new feature implementors.
 
 Technical requirements: development environment (such as
-@ref{Lilybuntu}), ability to read+write scheme and/or C++ code.
+@ref{Lilydev}), ability to read+write scheme and/or C++ code.
 
 @end itemize
 
@@ -485,6 +485,16 @@ required merging and stuff.
 
 (prep: 2 hours.  discuss: 10 hours)
 
+@item @strong{Precise definition of Critical issues}:
+at the moment, a stable release is entirely dependent on the
+number of Critical issues, but there's some questions about
+precisely what a "Critical issue" should be.  We should clarify
+this, in conjunction with a general discussion about how often we
+want to have stable releases, how permissive we want to be about
+patches, etc etc.
+
+(prep: 1 hour.  discuss: 5 hours)
+
 @end itemize
 
 
@@ -788,6 +798,9 @@ about \new vs. \context.
 Let users add their own items to the parser?  comment 11 on:
 http://code.google.com/p/lilypond/issues/detail?id=1322
 
+@item
+should engravers be pluralized (note_heads_engraver) or not
+(note_head_engraver) ?
 
 @end itemize
 
@@ -827,62 +840,3 @@ developers are tired of pushing patches for a contributor, we'll
 discuss giving them push access.  Unsolicited requests from
 contributors for access will almost always be turned down.
 
-
-@subsubheading Creating the @strong{Lilybuntu} respin
-
-@enumerate
-
-@item Install ubuntu, reboot
-
-@item Run all updates, reboot if asked
-
-@item Enable src repos, refresh package lists
-
-@item install LP build deps:
-
-@example
-sudo apt-get build-dep lilypond
-@end example
-
-@ install git and other stray build dependencies:
-
-@example
-sudo apt-get install git-core gitk autoconf dblatex
-@end example
-
-@item TEST TO SEE WHETHER EVERYTHING WORKS NOW:
-
-@itemize
-
-@item use @code{lily-git.tcl} to grab source files
-@item go to source directory and do @code{./autogen.sh ;
-make all ; make doc}
-
-@item if all compiles, move on to iso creation...
-
-@end itemize
-
-@item Download & install "remastersys" package:
-
-@example
-@uref{http://sourceforge.net/projects/remastersys/}
-@end example
-
-@item copy @code{lily-git.tcl} script file into @code{/etc/skel/}
-
-@item modify @code{/etc/remastersys.conf} as desired
-(change .iso name, default live session username, etc)
-
-@item Remove non-essential desktop software as desired
-@item create iso:
-
-@example
-sudo remastersys dist
-@end example
-
-@item new iso is in @code{/home/remastersys/remastersys/}
-
-@item test iso by installing in VM and repeating steps above for
-getting source files and building lp and docs
-
-@end enumerate