CG: remove information about frogs and frog meister

frogs list is dead, and the frog meister was a good idea
but it gets out of touch from reality (since a few months
previous Frog Meister didn't actually participate in development).

(cherry picked from commit fcad9f183bb05f7206427bf5fc1b95fd8209d26e)

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 8be1d903fa12f1e0c8448005c412e05b1ca9af21..90fe795a0cffa5b3617765afc330674f90225b64 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -126,7 +126,7 @@ on which part of the job, checks to make sure that everything is
 running smoothly, and has final say on our policy for
 Documentation.  Also includes LSR work.
 
 running smoothly, and has final say on our policy for
 Documentation.  Also includes LSR work.
 

-Currently: Graham
+Currently: None

 
 @item
 Translation Meister: trains new translators, updates the
 
 @item
 Translation Meister: trains new translators, updates the


@@ -135,19 +135,6 @@ directions).
 
 Currently: Francisco
 
 
 Currently: Francisco
 

-@item
-Frog Meister: is responsible for code patches from (relatively)
-inexperienced contributors.  Keeps track of patches, does initial
-reviewing of those patches, sends them to @w{@code{-devel}} when
-they've had some initial review on the Frog list, pesters the
-@w{@code{-devel}} community into actually reviewing said patches, and
-finally pushes the patches once they're accepted.  This person is
-@emph{not} responsible for training new programmers, because that
-would be far too much work -- his/her job is @qq{only} to guide
-completed patches through our process.
-
-Currently: Mike Solomon
-

 @end itemize
 
 @node Patchy
 @end itemize
 
 @node Patchy

diff --git a/Documentation/contributor/introduction.itexi b/Documentation/contributor/introduction.itexi
index b6530b4ffdcdfa99a3e5fe2520034a58320e71ae..12c62e5bfaaffc554cace48ef0a9a377af64c814 100644 (file)
--- a/Documentation/contributor/introduction.itexi
+++ b/Documentation/contributor/introduction.itexi
@@ -47,27 +47,24 @@ since the program was born.
 
 The @q{official} LilyPond Git repository is hosted by the GNU
 Savannah software forge at @uref{http://git.sv.gnu.org}.
 
 The @q{official} LilyPond Git repository is hosted by the GNU
 Savannah software forge at @uref{http://git.sv.gnu.org}.

-Although, since Git uses a @emph{distributed} model, technically
-there is no central repository.  Instead, each contributor keeps a
-complete copy of the entire repository (about 116MB).

 
 Changes made within one contributor's copy of the repository can
 be shared with other contributors using @emph{patches}.  A patch
 
 Changes made within one contributor's copy of the repository can
 be shared with other contributors using @emph{patches}.  A patch

-is a simple text file generated by the @command{git} program that
-indicates what changes have been made (using a special format).
+is a text file that indicates what changes have been made.

 If a contributor's patch is approved for inclusion (usually
 through the mailing list), someone on the current development team
 will @emph{push} the patch to the official repository.
 
 The Savannah software forge provides two separate interfaces for
 If a contributor's patch is approved for inclusion (usually
 through the mailing list), someone on the current development team
 will @emph{push} the patch to the official repository.
 
 The Savannah software forge provides two separate interfaces for

-viewing the LilyPond Git repository online: @emph{cgit} and
-@emph{gitweb}.  The cgit interface should work faster than gitweb
+viewing the LilyPond Git repository online:
+@uref{http://git.sv.gnu.org/cgit/lilypond.git/, cgit} and
+@uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git, gitweb}.
+
+@ignore
+The cgit interface should work faster than gitweb

 in most situations, but only gitweb allows you to search through
 the source code using @command{grep}, which you may find useful.
 in most situations, but only gitweb allows you to search through
 the source code using @command{grep}, which you may find useful.

-The cgit interface is at
-@uref{http://git.sv.gnu.org/cgit/lilypond.git/} and the gitweb
-interface is at
-@uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git}.
+@end ignore

 
 Git is a complex and powerful tool, but tends to be confusing at
 first, particularly for users not familiar with the command line
 
 Git is a complex and powerful tool, but tends to be confusing at
 first, particularly for users not familiar with the command line


@@ -283,8 +280,8 @@ switching git branches (not expected, but just in case...)
 @item
 You don't need to be able to completely approve patches.  Make
 sure the patch meets whatever you know of the guidelines (for doc
 @item
 You don't need to be able to completely approve patches.  Make
 sure the patch meets whatever you know of the guidelines (for doc

-style, code indentation, whatever), and then send it on to the
-frog list or -devel for more comments.  If you feel confident
+style, code indentation, whatever), and then send it on to -devel
+for more comments.  If you feel confident

 about the patch, you can push it directly (this is mainly intended
 for docs and translations; code patches should almost always go to
 -devel before being pushed).
 about the patch, you can push it directly (this is mainly intended
 for docs and translations; code patches should almost always go to
 -devel before being pushed).

diff --git a/Documentation/contributor/quick-start.itexi b/Documentation/contributor/quick-start.itexi
index df0b9ed50ae14c0ab9c816ac0c13f20aa1f6e050..22ea0591b10c33022aea51adb0d93b9d956f9cd8 100644 (file)
--- a/Documentation/contributor/quick-start.itexi
+++ b/Documentation/contributor/quick-start.itexi
@@ -35,12 +35,6 @@ it is available for all major operating systems and is easy to install
 If you are not familiar with GNU/Linux, it may be beneficial to read a
 couple of @qq{introduction to Ubuntu} web pages.
 
 If you are not familiar with GNU/Linux, it may be beneficial to read a
 couple of @qq{introduction to Ubuntu} web pages.
 

-Some contributors have recommended a free PDF:
-
-@example
-@uref{http://www.ubuntupocketguide.com/}
-@end example
-

 For those interested, the LilyDev remix is currently based on a 32bit
 version of 10.04 LTS Ubuntu (Lucid Lynx).
 
 For those interested, the LilyDev remix is currently based on a 32bit
 version of 10.04 LTS Ubuntu (Lucid Lynx).
 


@@ -421,11 +415,6 @@ Send patch files to the appropriate place:
 @item
 If you have a mentor, send it to them via email.
 
 @item
 If you have a mentor, send it to them via email.
 

-@item
-New contributors should send the patch attached to an email to
-@email{frogs@@lilynet.net}.  Please add @qq{[PATCH]} to the
-subject line.
-

 @item
 Translators should send patches to
 @email{translations@@lilynet.net}.
 @item
 Translators should send patches to
 @email{translations@@lilynet.net}.


@@ -435,6 +424,10 @@ More experienced contributors should upload the patch for
 web-based review.  This requires additional software and use of
 the command-line; see @ref{Uploading a patch for review}.
 
 web-based review.  This requires additional software and use of
 the command-line; see @ref{Uploading a patch for review}.
 

+@item
+If you have trouble uploading the patch for review,
+ask for help on @email{lilypond-devel@@gnu.org}.
+

 @end itemize
 
 
 @end itemize
 
 

diff --git a/Documentation/included/helpus.itexi b/Documentation/included/helpus.itexi
index 2789f28097841523ad317ea635056a57178b9f90..96f697be4cb95bbf1767356cf3a62ac2fb4ca39f 100644 (file)
--- a/Documentation/included/helpus.itexi
+++ b/Documentation/included/helpus.itexi
@@ -15,9 +15,9 @@ of spending time on those simple tasks.
 
 For a multi-faceted project like LilyPond, sometimes it's tough to know
 where to begin.  In addition to the avenues proposed below, you can send
 
 For a multi-faceted project like LilyPond, sometimes it's tough to know
 where to begin.  In addition to the avenues proposed below, you can send

-an e-mail to the @email{mike@@mikesolomon.org, Frog meister}
-letting him know your skill set and asking how you can help or proposing a
-project.  He'll be able to give you guidance on how to get started.
+an e-mail to the
+@uref{https://lists.gnu.org/mailman/listinfo/lilypond-devel, lilypond-devel@@gnu.org}
+mailing list, and we'll help you to get started.

 
 @end macro
 
 
 @end macro
 


@@ -35,11 +35,6 @@ Mailing list support: answer questions from fellow users.
 Bug reporting: help users create proper @rweb{Bug reports}, and/or
 join the Bug Squad to organize @rcontrib{Issues}.
 
 Bug reporting: help users create proper @rweb{Bug reports}, and/or
 join the Bug Squad to organize @rcontrib{Issues}.
 

-@item
-@rcontrib{Grand Regression Test Checking}: verify that LilyPond works correctly
-by examining output of test snippets.  Checking one snippet takes less
-than a minute!
-

 @item
 Documentation: small changes can be proposed by following the
 guidelines for @rcontrib{Documentation suggestions}.
 @item
 Documentation: small changes can be proposed by following the
 guidelines for @rcontrib{Documentation suggestions}.


@@ -90,8 +85,7 @@ Translations: see @rcontrib{Translating the documentation}, and
 @rcontrib{Translating the website}.
 
 @item
 @rcontrib{Translating the website}.
 
 @item

-Bugfixes or new features: the best way to begin is to join the
-Frogs, and read @rcontrib{Programming work}.
+Bugfixes or new features: read @rcontrib{Programming work}.

 
 @end itemize
 
 
 @end itemize
 


@@ -101,23 +95,6 @@ Frogs, and read @rcontrib{Programming work}.
 @macro helpusProjects
 @subheading Projects
 
 @macro helpusProjects
 @subheading Projects
 

-@subsubheading Frogs
-
-Website and mailing list:
-
-@example
-@uref{http://frogs.lilynet.net}
-@end example
-
-The Frogs are ordinary LilyPond users who have chosen to get
-involved in their favorite software's development.  Fixing bugs,
-implementing new features, documenting the source code: there's a
-lot to be done, but most importantly: this is a chance for
-everyone to learn more about LilyPond, about Free Software, about
-programming@dots{} and to have fun.  If you're curious about any of
-it, then the word is: @emph{Join the Frogs!}
-
-

 
 @subsubheading Grand LilyPond Input Syntax Standardization
 
 
 @subsubheading Grand LilyPond Input Syntax Standardization