Great! Install git, and then follow the instructions here: http://lists.gnu.org/archive/html/lilypond-devel/2009-06/msg00348.html
More git instructions here (just follow the above email for the "getting the source code") http://lilypond.org/doc/v2.13/Documentation/devel/contrib-guide/index Once you have the source, look in texinfo/*.texi and texinfo/css/lilypond-general.css Find some typo, or misspelling, or rewrite some sentence or whatever, then send me a patch. (instructions in the CG) (an absolutely trivial patch is fine; the important thing right now is just to get used to git and sending patches) Cheers, - Graham On Fri, Jul 10, 2009 at 12:49:01PM -0700, Patrick Horgan wrote: > Graham Percival wrote: > > I'll volunteer for css and/or proofreading. I also don't have a job or > girlfriend;) I'll be in Peru much of August though and looking for a > job after that. Put me to work. (Although I'll have to confess, as far > as css goes, the current new stuff is looking great already!) > > Patrick >> http://percival-music.ca/blogfiles/out/lilypond-general_1.html >> >> There's now an Examples section, thanks to Jonathan Kulp. >> - currently, most examples have a "click-to-expand" thing. Some >> of them don't work expanded, others don't work non-expanded. >> But there's enough working stuff for you to get the idea. >> >> IS THIS WORTH IT? Making it work nicely in small+expanded >> versions is turning out to be a pain. I'm wondering if we >> should just stick to small examples, which are approximately >> infinitely times easier to create/modify/regenerate. >> >> >> More importantly, we need help. I recently re-iterated my claim >> that the lilypond community should have the >> program/bugs/documentation/website they deserve, but currently >> this isn't happening -- Patrick and I have spent a ton of time and >> effort on this website. >> >> - Patrick wants to spend time programming lilypond. I also want >> him to spend time programming. He's doing nifty stuff like >> fixing the SVG output, fixing misc bugs, and cleaning up a ton >> of advanced documentation. >> >> WE NEED A NEW CSS PERSON. >> >> - I'm wasting a lot of time on mundane jobs. For example, the old >> news page needs to be put into the new website source. This >> means going through a bunch of things like >> <h2>New German translaton! Aug 07, 2006</h2> >> <p>Ich nein katza, <a href="http://blah";>auf blitzen</a> drie.</p> >> and turning it into >> @subheading New German Translation! 2006 Aug 07 >> >> Ich nein katza, @uref{http://blah, auf blitzen} drie. >> Not hard. I could even train an undergraduate to do this job! >> >> WE NEED SOMEBODY TO WRITE TEXT. >> >> - I tend to rewrite / reword sentences as I work on them, but I >> have a nasty habit of not reading the once I erase stuff and >> write new material. The result is by native English speakers, >> although it may slightly confusing. Not what we in a shiny >> new website, that's for certain! >> >> (also, many sentences on the website could be rewritten to >> reduce the words, reduce the complexity -- remember, we have >> a fair chunk of non-native English readers, so let's not >> elaborate our missives with loquatious (sp) verbitage) >> >> WE NEED SOMEBODY TO PROOFREAD TEXT. >> >> - Some of the examples could be improved... fancier formatting, >> adding more text to the theory example, etc. >> >> WE NEED SOMEBODY TO WORK ON .LY FILES. >> >> >> Now, I'm *completely* capable of doing any of those tasks (even >> self-proofreading, once I get into the mood)... but >> a) I don't think I should be doing so much work on this, and >> b) if somebody does those jobs, I can tackle harder stuff. >> >> I'm *really* not doing much this summer other than lilypond -- I >> have no job, no studies, no girlfriend -- so it's mainly a >> question of "what parts of lilypond do I work on", not "will I >> work on something". So, just like we all benefit from having >> Patrick *not* working on CSS stuff, I think we would all benefit >> from me *not* working on the website so much. >> >> Cheers, >> -Graham >> >> >> _______________________________________________ >> lilypond-user mailing list >> lilypond-user@gnu.org >> http://lists.gnu.org/mailman/listinfo/lilypond-user >> >> > _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
