Doc: CG - replace references of Google Code with Sourceforge Allura

Issue 4672

Replaced all @urefs and
@examples with URLs from
Allura/Sourceforge.

Also modified some of the
notes in the Bug Squad
section to bring the
instructions up to date
with regard to how to
get an Allura account etc.

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index dfd5a72fa452a5fedf0a7086f3a73d6d94039250..a317a3a3bf9a432f8ca5da6cb59219b0438bc0ae 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -216,8 +216,7 @@ Currently: Francisco Vila @email{translations@@lilynet.net}
 @section Managing Staging and Master branches with Patchy
 
 @ignore
 @section Managing Staging and Master branches with Patchy
 
 @ignore

-The script 'test-patches.py' no longer works with code.google.com since
-Google changed their authentication method.
+The script 'test-patches.py' does not currently works with Allura.

 @end ignore
 
 @menu
 @end ignore
 
 @menu


@@ -269,7 +268,7 @@ commits.  See @ref{Compiling}.
 
 @item
 Commit access @emph{is} required to test and push new commits, but a
 
 @item
 Commit access @emph{is} required to test and push new commits, but a

-valid login to @uref{http://code.google.com/} is @emph{not}.  See
+valid login to @uref{https://sourceforge.net} is @emph{not}.  See

 @ref{Commit access}.
 
 @end itemize
 @ref{Commit access}.
 
 @end itemize


@@ -792,7 +791,7 @@ savannah bug tracker?
 Reitveld is inconvenient in some respects: it requires a google
 account, and there's no way to see all patches relating to
 lilypond. Should we switch to something like gerritt?
 Reitveld is inconvenient in some respects: it requires a google
 account, and there's no way to see all patches relating to
 lilypond. Should we switch to something like gerritt?

-@uref{http://code.google.com/p/lilypond/issues/detail?id=1184}
+@uref{https://sourceforge.net/p/testlilyissues/issues/1184/}

 
 (prep: 5 hours.  discuss: 15 hours)
 
 
 (prep: 5 hours.  discuss: 15 hours)
 


@@ -1749,13 +1748,13 @@ sequential-statement to the score."
 
 @item
 Discussion on
 
 @item
 Discussion on

-@uref{http://code.google.com/p/lilypond/issues/detail?id=1322}
+@uref{https://sourceforge.net/p/testlilyissues/issues/1322/}

 about \new vs. \context.
 
 
 @item
 Let users add their own items to the parser?  comment 11 on:
 about \new vs. \context.
 
 
 @item
 Let users add their own items to the parser?  comment 11 on:

-@uref{http://code.google.com/p/lilypond/issues/detail?id=1322}
+@uref{https://sourceforge.net/p/testlilyissues/issues/1322/}

 
 @item
 should engravers be pluralized (note_heads_engraver) or not
 
 @item
 should engravers be pluralized (note_heads_engraver) or not


@@ -1763,7 +1762,7 @@ should engravers be pluralized (note_heads_engraver) or not
 
 @item
 should we allow numbers in identifier names?  Issue:
 
 @item
 should we allow numbers in identifier names?  Issue:

-@uref{http://code.google.com/p/lilypond/issues/detail?id=1670}
+@uref{https://sourceforge.net/p/testlilyissues/issues/1670/}

 
 @item
 should we officially allow accented characters?  in general, how
 
 @item
 should we officially allow accented characters?  in general, how

diff --git a/Documentation/contributor/doc-work.itexi b/Documentation/contributor/doc-work.itexi
index 0435b96265dadd300670a75d02989b799c728feb..b9f1c7a77e149b7c4bdb6a648affef6ab77ad731 100644 (file)
--- a/Documentation/contributor/doc-work.itexi
+++ b/Documentation/contributor/doc-work.itexi
@@ -1544,7 +1544,7 @@ build/tempdocs/pitches/out/pitches.html
 @end example
 
 According to
 @end example
 
 According to

-@uref{http://code.google.com/p/lilypond/issues/detail?id=1236,LilyPond issue 1236},
+@uref{https://sourceforge.net/p/testlilyissues/issues/1236/,LilyPond issue 1236},

 the location of the LilyPond Git tree is taken from @code{$LILYPOND_GIT}
 if specified, otherwise it is auto-detected.
 
 the location of the LilyPond Git tree is taken from @code{$LILYPOND_GIT}
 if specified, otherwise it is auto-detected.
 

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index 782d84d155056ec20e54c2a3e5dacec5fb53587f..434ead511a139e1181b417f0cfb7997e4da18ae6 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -69,93 +69,80 @@ If you would like to be part of the Bug Squad, please contact the
 @node Bug Squad setup
 @subsection Bug Squad setup
 
 @node Bug Squad setup
 @subsection Bug Squad setup
 

-We highly recommend that you configure your email to use effective
-sorting; this can reduce your workload @emph{immensely}.  The
-email folders names were chosen specifically to make them work if
-you sort your folders alphabetically.
+We highly recommend that you configure your email client to use some
+kind of sorting and filtering as this will significantly reduce and
+simplify your workload.  Suggested email folder names are mentioned
+below to work when sorted alphabetically.

 
 @enumerate
 
 @item
 
 @enumerate
 
 @item

-Read every section of this chapter, @ref{Issues}.
+Read every section of the @ref{Issues} chapter in this guide.

 
 @item
 
 @item

-If you do not have one already, create a gmail account and send
-the email address to the @ref{Meisters, Bug Meister}.
+Subscribe your email account to @code{bug-lilypond}.  See
+@uref{https://lists.gnu.org/mailman/listinfo/bug-lilypond}.

 
 @item
 
 @item

-Subscribe your gmail account to @code{bug-lilypond}.
+Send your email address to the @ref{Meisters, Bug Meister}.

 
 @item
 
 @item

-Configure your google code account:
+Create your own Sourceforge login (required for the Allura issue
+tracker):

 
 

-@enumerate
+@itemize

 
 @item
 
 @item

-Wait until your gmail account is listed in:
-
-@example
-@uref{http://code.google.com/p/lilypond/people/list}
-@end example
+Go to @uref{https://sourceforge.net/p/testlilyissues/issues/}

 
 @item
 
 @item

-Sign in to google code by clicking in the top-right corner of:
-
-@example
-@uref{http://code.google.com/p/lilypond/issues/list}
-@end example
-
-You cannot log on if you have Google Sharing enabled
-@uref{http://www.googlesharing.net/}.
+Click on 'Join' in the top-right corner.

 
 @item
 
 @item

-Go to your @qq{Profile}, and select @qq{Settings}.
+Fill in your details as required and click the @emph{Register} button to
+complete the registration.

 
 

-@item
-Scroll down to @qq{Issue change notification}, and make sure that
-you have @emph{selected} @qq{If I starred the issue}.
+@end itemize

 
 

-@end enumerate
+@item
+Send your Sourceforge @emph{username} (not your email address) to
+@email{bug-lilypond@@gnu.org} asking to be given appropriate permissions
+to either create, edit and comment on tracker issues.

 
 @item
 Configure your email client:
 
 
 @item
 Configure your email client:
 

-@enumerate
+@itemize

 
 @item
 
 @item

-Any email sent with your gmail address in the @code{To:} or
-@code{CC:} fields should go to a @code{bug-answers} folder.
-
-When setting up your filtering rules, be aware that Google Code
-might use different versions of your email address, such as ones
-ending in @code{@@googlemail.com} or @code{@@gmail.com}.
+Any email sent with your address in the @code{To:} or @code{CC:} fields
+should be configured to go into a @code{bug-answers} folder.

 
 @item
 
 @item

-Any other email either from, or CC'd to,
+Any email either @code{From:} or @code{CC:} to,

 
 @example
 
 @example

-lilypond@@googlecode.com
+testlilyissues-auto@@lists.sourceforge.net

 @end example
 
 @noindent
 @end example
 
 @noindent

-should go into a separate @code{bug-ignore} folder.  Alternately,
-you may automatically delete these emails.
-
-You will @strong{not read} these emails as part of your Bug Squad
-duties.  If you are curious, go ahead and read them later, but it
-does @strong{not} count as Bug Squad work.
+should be configured to go into a @code{bug-ignore} folder or,
+alternately, configure your email client to delete these automatically.
+You do @emph{not} need to read mails in the @code{bug-ignore} folder.
+If you are curious (and have time) then read them, but they are not
+necessary for Bug Squad work.

 
 @item
 
 @item

-Any other email sent to (or CC'd to):
+Any email sent @code{To:} or @code{CC:} to,

 
 @example
 bug-lilypond
 @end example
 
 @noindent
 
 @example
 bug-lilypond
 @end example
 
 @noindent

-should go into a separate @code{bug-current} folder.
+should be configured to go into a @code{bug-current} folder.

 
 

-@end enumerate
+@end itemize

 
 @end enumerate
 
 
 @end enumerate
 


@@ -187,7 +174,7 @@ Monday: Federico Bruni
 Tuesday: Simon Albrecht
 Wednesday: Simon Albrecht
 Thursday: Colin Campbell
 Tuesday: Simon Albrecht
 Wednesday: Simon Albrecht
 Thursday: Colin Campbell

-Friday:
+Friday: Ralph Palmer

 Saturday: Colin Campbell
 Sunday:
 @end example
 Saturday: Colin Campbell
 Sunday:
 @end example


@@ -341,21 +328,26 @@ After @strong{every release} (both stable and unstable):
 @item
 Issues to verify: go to
 
 @item
 Issues to verify: go to
 

-@example
-@uref{http://code.google.com/p/lilypond/issues/list?can=7}
-@end example
+@smallexample
+@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AFixed}
+@end smallexample

 
 

-(You can also generate this list by selecting
-@qq{Issues to verify} from the drop-down list next to the search
-box.)
+(You can also generate this list by selecting the @qq{Open (Fixed)}
+button down the left-hand frame)

 
 

-You should see a list of Issues that have been claimed fixed by a
+You should see a list of Issues that have been marked as 'Fixed' by a

 developer.  If the developer has done their job properly, the
 developer.  If the developer has done their job properly, the

-Issue should have a tag @qq{Fixed_mm_MM_ss}, where mm is
-the major version, MM the minor version and ss the current
-release.  This will help you work out which you can verify - do
-not verify any Issues where the claimed fixed build is not yet
-released.  Work your way through these as follows:
+Issue should have the @qq{Labels} field filled in with @qq{Fixed_x_y_z},
+where X is the major version, y the minor version and z the current
+release.
+
+@example
+Fixed_2_19_39
+@end example
+
+This will help you work out which you can verify - do not verify any
+Issues where the claimed fixed build is not yet released.  Work your
+way through these as follows:

 
 If the Issue refers to a bug, try to reproduce the bug with the latest
 officially released version (not one you've built yourself from
 
 If the Issue refers to a bug, try to reproduce the bug with the latest
 officially released version (not one you've built yourself from


@@ -839,10 +831,10 @@ available to do this task if required).
 
 @subsubheading Project overview
 
 
 @subsubheading Project overview
 

-Grid view provides the best overview:
+Project activity

 
 @smallexample
 
 @smallexample

-@uref{http://code.google.com/p/lilypond/issues/list?mode=grid&y=Priority&x=Type&cells=ids}
+@uref{https://sourceforge.net/projects/testlilyissues/}

 @end smallexample
 
 @subsubheading Hindering development
 @end smallexample
 
 @subsubheading Hindering development


@@ -850,28 +842,61 @@ Grid view provides the best overview:
 These issues stop or slow development work:
 
 @smallexample
 These issues stop or slow development work:
 
 @smallexample

-@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:Maintainability}
+@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status:Accepted%20AND%20_type:Maintainability}

 @end smallexample
 
 @subsubheading Easy tasks
 
 Issues tagged with @code{Frog} indicates a task suitable for a
 @end smallexample
 
 @subsubheading Easy tasks
 
 Issues tagged with @code{Frog} indicates a task suitable for a

-relatively new contributor.  The time given is a quick
-(inaccurate) estimate of the time required for somebody who is
-familiar with material in this manual, but does not know anything
-else about LilyPond development.
+relatively new contributor.  The time given is a quick (and probably
+inaccurate) estimate of the time required for somebody who is familiar
+with material in this manual, but does not know anything else about
+LilyPond development.

 
 @smallexample
 
 @smallexample

-@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:Frog}
+@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status:Accepted%20AND%20labels:Frog}

 @end smallexample
 
 @end smallexample
 

-@subsubheading Patches to review
+@subsubheading Patches currently in the Patch Review cycle
+
+Overview

 
 

-Patches which have no @qq{obvious} problems:
+@c The following URL is provided by one of the Developers giving a much
+@c easier way to see all patches at all stages of the Review cycle in a
+@c single place.

 
 @example
 
 @example

-@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:patch-review}
+http://philholmes.net/lilypond/allura/

 @end example
 
 
 @end example
 
 

+@noindent
+New patches

 
 

+@smallexample
+@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Anew}
+@end smallexample
+
+
+@noindent
+Patches under Review
+
+@smallexample
+@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Areview}
+@end smallexample
+
+
+@noindent
+Patches on final Countdown
+
+@smallexample
+@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Acountdown}
+@end smallexample
+
+
+@noindent
+Patches that can be pushed
+
+@smallexample
+@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Apush}
+@end smallexample

diff --git a/Documentation/contributor/source-code.itexi b/Documentation/contributor/source-code.itexi
index b43b3f348261813f30f0240c7667214867cc7ccb..19b835a0ef959caac542cedae29d10b82cfa88cb 100644 (file)
--- a/Documentation/contributor/source-code.itexi
+++ b/Documentation/contributor/source-code.itexi
@@ -45,7 +45,7 @@ If you haven't already, download and install Git.
 @qq{Full installer for official Git} from:
 
 @example
 @qq{Full installer for official Git} from:
 
 @example

-@uref{http://code.google.com/p/msysgit/downloads/list}
+@uref{https://git-for-windows.github.io/}

 @end example
 
 @item Other operating systems: either install @command{git} with
 @end example
 
 @item Other operating systems: either install @command{git} with


@@ -2356,9 +2356,7 @@ has, either as a complete file or as a @q{diff} or @q{patch}
 @subsection Installing git
 
 Obtain Git from
 @subsection Installing git
 
 Obtain Git from

-@uref{http://code.google.com/p/msysgit/downloads/list} (note, not
-msysGit, which is for Git developers and not PortableGit, which is
-not a full git installation) and install it.
+@uref{https://git-for-windows.github.io/}.

 
 Note that most users will not need to install SSH.  That is not
 required until you have been granted direct push permissions to
 
 Note that most users will not need to install SSH.  That is not
 required until you have been granted direct push permissions to