2011/4/16 Graham Percival <[email protected]> > > On Fri, Apr 15, 2011 at 11:17:23PM +0200, Janek Warchoł wrote: > > 2011/4/15 Graham Percival <[email protected]>: > > > Note that both of these points require little or no technical > > > ability. Non-technically-skilled users can help tremendously with > > > these points. And if we can reduce the time it takes to read > > > emails from 5 hours a week to 3 hours a week, that allows > > > programmers to spend more time programming or helping each other. > > > > I have an idea concerning this, should i wait for GOP or start a discussion? > > Send it to me privately, and I'll add it to the GOP list. With > this branching, we have more than enough vague policy discussions > on -devel at the moment.
ok. > > > Right. The main problem for you is: > > > - you need a mentor. Somebody who can guide you through the > > > steps, encourage you, and investigate if you get truly stuck. > > > > > > Unfortunately, Mike Solomon is the only programmer who has offered > > > to mentor people, and IIRC he's paired up with Benko Pal. > > > > Mike is also my mentor, see your mail "contributors / mentors" from 22 > > II. Unfortunately, he has been busy since April 3rd and said he will > > remain busy until next thursday. > > In that case, I think that you're guilty of not following the > contributor's responsibilities: > http://lilypond.org/doc/v2.13/Documentation/contributor/mentors > Namely, points 2 Poor Mike, i'd flood him totally if i obeyed this rule. > and 3. I'm not sure if this would really help. However, i could have tried. > I agree that it's unfortunate that you need to wait until he's not > busy, but those guidelines are there to protect you. At the > moment, you're disappointed, frustrated, and you feel like you've > wasted a lot of time and effort. I would rather have new > contributors feeling impatient to hear back from their mentors, > rather than wasting a lot of effort. > > There are lots of tasks that need to be done, so if you *are* > stuck waiting for a week or two for your mentor, you could try > doing some other task? Like attached one? cheers, Janek
From c868775c7feaddd79a50ba56c3846d9edde51052 Mon Sep 17 00:00:00 2001 From: Janek Warchol <[email protected]> Date: Sat, 16 Apr 2011 21:57:48 +0200 Subject: [PATCH] Doc: issue 1453 - how to create Lilydev iso --- Documentation/contributor/administration.itexi | 81 ++++++++++++++++++++++++ 1 files changed, 81 insertions(+), 0 deletions(-) diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi index e906dc3..85c4c54 100644 --- a/Documentation/contributor/administration.itexi +++ b/Documentation/contributor/administration.itexi @@ -852,3 +852,84 @@ 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 Lilydev iso image + +Here's the short instruction on how to create lilybuntu iso image +(Jonathan Kulp did this on a spare drive, +but he supposes it can be done in a VM too): + + +@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 + +@item +Install git and autoconf: + +@example +sudo apt-get install git-core gitk autoconf +@end example + + +@item +Test to see whether everything works fine now: + +@enumerate + +@item +use @command{lily-git.tcl} to grab source files + +@item +go to source dir and do + +@example +"./autogen.sh" ; make ; make doc +@end example + +@item +if all compiles, move on to iso creation... + +@end enumerate + +@item +Download & install "remastersys": +@uref{http://sourceforge.net/projects/remastersys/, http://sourceforge.net/projects/remastersys/} + +@item +Copy @command{lily-git.tcl} script file into @file{/etc/skel/}. + +@item +Modify @file{/etc/remastersys.conf} as desired (change @code{.iso} name, +default live session username, etc). + +@item +Remove non-essential desktop software as desired. + +@item +Create iso: +@example +sudo remastersys dist +@end example + +New iso is in @file{/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 -- 1.7.0.4
_______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
