Re: Guide to Writing Orchestral Scores with Lilypond?????

[Urs Liska]

Am 16.01.2013 00:01, schrieb Antonio Gervasoni:
> Joseph wrote:
>
> > You're preaching to the converted here, I fear ... :-)
> Very true!!!! :-P
>
> > Will you be publicly sharing your drafts?  I'm sure people would be happy
> > to
> > give feedback and contributions on the way.
> Urs has almost convinced me about using Git so i't's very likely I will get
> a Github account and start collaborating directly with his project.
> According to him my "source code would be public this way right from the
> beginning. But the tutorial itself (in its PDF representation) would be
> hidden as long as [I] wish."
If you are going to do the switch, you will work on your own 'branch' 
(branching is maybe Git's killer feature I didn't tell you about so far 
...).
That means your source code is somewhat separate from the 'master' 
branch, but anybody who wants can see it.
Well, the PDF wouldn't (couldn't) be _really_ hidden. Anybody can access 
the source code and can therefore compile it to a PDF - provided he/she 
has the appropriate LaTeX infrastructure available. But we just wouldn't 
publish the PDF on our own.
In effect this would mean that your work isn't at a prominent place, but 
visible to anybody who cares.

Best
Urs
> Regards,
>
> Antonio
>
>
>
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/Guide-to-Writing-Orchestral-Scores-with-Lilypond-tp139065p139609.html
> Sent from the User mailing list archive at Nabble.com.
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user