@menu
* Help us::
* Overview of work flow::
-* Lilybuntu::
* Mentors::
@end menu
@section Overview of work flow
@cartouche
-@strong{Ultra-short summary for Unix developers}: source code is at
-@code{git://git.sv.gnu.org/lilypond.git}. Documentation is built
+@strong{Short summary for Unix developers}: source code is at
+@uref{git://git.sv.gnu.org/lilypond.git}. Documentation is built
with Texinfo, after pre-processing with @code{lilypond-book}.
Send well-formed patches to @email{lilypond-devel@@gnu.org}.
@end cartouche
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 116M).
+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
Git is a complex and powerful tool, but tends to be confusing at
first, particularly for users not familiar with the command line
-and/or version control systems. Contributors who don't want to
-deal with Git directly are encouraged to use the
-@command{lily-git} graphical user interface instead.
+and/or version control systems. We have created the
+@command{lily-git} graphical user interface to ease this
+difficulty.
@emph{Compiling} (@q{building}) LilyPond allows developers to see
how changes to the source code affect the program itself.
@uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel}.
@warning{Contributors on Windows or MacOS X wishing to compile
-code or documentation are strongly advised to use @ref{Lilybuntu}
-instead of trying to install all software dependencies
-themselves.}
-
-
-@node Lilybuntu
-@section Lilybuntu
-
-It is not possible to compile LilyPond on Windows, and extremely
-difficulty to compile it on MacOS X. We have therefore made a
-@q{remix} of Ubuntu which includes all necessary dependencies to
-compile both LilyPond and the documentation. This can be run
-inside a virtual machine without disturbing your main operating
-system.
-
-@enumerate
-@item
-Install some virtualization software.
-
-Any virtualization tool can be used, but we recommend VirtualBox:
-
-@example
-@uref{http://@/www.virtualbox.org/@/wiki/@/Downloads}
-@end example
-
-In virtualization terminology, your main operating system is the
-@qq{host}.
-
-@item
-Download the @file{lilybuntu.iso} disk image.
-
-@example
-@uref{http://@/files.lilynet.net/@/lilybuntu.iso}
-@end example
-
-@item
-Install @file{lilybuntu.iso} as the @qq{client} operating system
-on your virtualized system.
-
-@itemize
-
-@item
-The latest version of lilybuntu is based on Ubuntu 9.04; if you
-encounter any difficulties installing it, search for one of the
-many tutorials for installing Ubuntu 9.04 as a client operating
-system.
-
-@item
-When @file{lilybuntu.iso} boots, it automatically selects @qq{Try
-Ubuntu without any change to your computer}; instead of this, you
-must select @qq{Install Ubuntu}.
-
-@item
-If possible, use at least 700 MB of RAM (1GB would be better) for
-the virtual machine, and use a dynamically expanding virtual hard
-drive. A complete compile of everything (code, docs, regression
-tests) can reach 10 GB.
-
-@item
-At the partitioning stage, do not be afraid to select @qq{use
-entire disk}, since this refers to your @emph{virtual disk}, not
-your machine's actual hard drive.
-
-@end itemize
-
-@item
-Do any extra configuration for your virtualization software.
-
-VirtualBox has extra @qq{guest additions} which can make the
-virtualization easier to use (full-screen, easy file sharing
-between host and client operating systems, shared clipboards,
-etc).
-
-@enumerate
-
-@item
-From the @code{Devices} menu of VirtualBox, select @code{Install
-Guest Additions...}.
-
-@item
-From the @code{Places} menu of Ubuntu, select
-@code{VBOXADDITIONS_}. A file-system window will open.
-
-@item
-Double-click on the @file{autorun.sh} file, then select @qq{Run in
-Terminal}.
-
-@item
-Once the script is finished, reboot your Virtual Machine to
-complete the installation.
-
-@end enumerate
-
-If you use other virutalization software, then follow the normal
-procedures for your virtualization software with Ubuntu 9.04 as
-the client.
-
-@end enumerate
-
-Follow instructions for Linux when reading instructions about
-@ref{Working with source code}, or @ref{Compiling}.
+code or documentation are strongly advised to use our Ubuntu
+LilyPond Developer Remix, as discussed in @ref{Quick start}.}
@node Mentors
that new contributors often get stuck with something that could be
solved/explained with 2 or 3 sentences from a mentor.
+@item
+If you have been working on a task much longer than was originally
+estimated, stop and ask your mentor. There may have been a
+miscommunication, or there may be some time-saving tips that could
+vastly simply your task.
+
@item
Send patches to your mentor for initial comments.
-devel before being pushed).
@item
-Keep track of patches from your contributor. If you've sent a
-patch to -devel, it's your responsibility to pester people to get
-comments for it, or at very least add it to the google tracker.
+Keep track of patches from your contributor. Either upload them
+to Rietveld yourself, or help+encourage them to upload the patches
+themselves. When a patch is on Rietveld, it's your responbility
+to get comments for it, and to add a link to the patch to the
+google tracker. (tag it @qq{patch-new}, or @qq{patch-review} if
+you feel very confident in it)
+
+@item
+Encourage your contributor to review patches, particularly your
+own! It doesn't matter if they're not familiar with C++ / scheme
+/ build system / doc stuff -- simply going through the process is
+valuable. Besides, anybody can find a typo!
+
+@item
+Contact your contributor at least once a week. The goal is just
+to get a conversation started -- there's nothing wrong with simply
+copy&pasting this into an email:
+
+@example
+Hey there,
+
+How are things going? If you sent a patch and got a review, do
+you know what you need to fix? If you sent a patch but have no
+reviews yet, do you know when you will get reviews? If you are
+working on a patch, what step(s) are you working on?
+@end example
+
@end enumerate