Re: LilyPond Grand Organization Project: ongoing jobs

[Jonathan Kulp]

Wow, Graham, you were really ringing in the new year.  All four of your 
emails were after 3 a.m. :)

[Comments inline below...]

Graham Percival wrote:
> Project website: http://percival-music.ca/gop/
> (includes these emails)
>
>      LilyPond GOP - Ongoing jobs
>
> Although GOP is a short-term project, the main goal is to train
> more people to handle ongoing jobs. The more people doing these
> jobs, the ligher the work will be, and the more we can get done
> with lilypond!
>
> Jobs for normal users
> ---------------------
>
> *Consultant
>     LilyPond is sometimes critized for not listening to users, but
> whenever we ask for opinions about specific issues, we never get
> enough feedback.
>     I propose to create a lilypond-consultants mailist. This will
> be a relatively low-volume list for developers to ask for feedback
> about proposed changes (names for new commands, new doc pages,
> etc). 

I'll join this.


> *lilypond-user support
>     I think it would be nice if we had an official team of users
> helping other users. Some people think it would be nice if I
> stopped being sarcastic to newbies.
>     This strikes me as the ideal opportunity for a trade. If we
> get six or more non-developers signing up to be official
> lilypond-user helpers, I'll stop answering newbie emails. Sounds
> like a win-win-win situation! 
I'll commit to this, too, especially for anything related to guitar 
notation, for which there seems to be a lot of questions.

> *LilyPond Report (run by Valentin Villenave)
>     The LilyPond Report, our newsletter, will return in a weekly
> format. Of course, producing a weekly newsletter takes a lot of
> work; Valentin could use all the help he can get for this task.
>
> *Regression test checker
>     Every time there is a new release, the regression tests need
> to be checked to see if anything broke. 
>
> *Translations
>     Keeping the documentation translations is a monumental task;
> we need all the help we can get! 
>
> Jobs for advanced users or developers
> -------------------------------------
>
> *Git help for writers
>     We often receive reports of typos and minor text updates to
> the documentation. It would be great if somebody could create
> properly-formatted patches for these corrections.
>     Technical requirements: knowledge of git, or at least
> willingness to learn git. Git is available on windows as well as
> OSX and Linux. 

I already know the texinfo formatting so I could help with this once I 
learn Git.  Right now I only know how to download the whole source-code 
tree and build the program and docs.  I don't know how to submit patches.

> *LSR editor
>     LSR contains many useful examples of lilypond, but some
> snippets are out of date and need updating. Other snippets need to
> be advertized, and new snippets need to be sorted. We could use
> another person to handle LSR.
>     Technical requirements: use of a web browser. LilyPond
> requirements: you should be familiar with most of NR 1+2 (or be
> willing to read the docs to find out). 
I could probably help with some of this, too.  I've just recently 
figured out how to upload snippets and have submitted 3 or 4 now.

Best,

Jon
--
Jonathan Kulp
http://www.jonathankulp.com