lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: we now have "lilypond" organization on GitHub


From: David Kastrup
Subject: Re: we now have "lilypond" organization on GitHub
Date: Tue, 24 Sep 2013 20:16:29 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Joseph Rushton Wakeling <address@hidden> writes:

> On 24/09/13 18:59, David Kastrup wrote:
>> How about not worrying about the tools then and just doing your
>> contribution any old way you prefer to work?  We have procedures in
>> place for picking up from there.
>
> I can give a detailed response here, but ... it's got a bit heated
> today.  Shall we pick up tomorrow? :-)
>
> Short version: I like working with a project's tools where possible
> (it's the nice and responsible thing to do), and I don't like the idea
> of asking someone else to do manual labour in place of my using those
> tools.

Well, let's just say that our track record with "I'll contribute once
everything is exactly like I want it, I could not expect to bother you
with my help before" is not unlike that spelled out in Wilde's "The
Devoted Friend" <URL:http://www.online-literature.com/wilde/176/>.

If you already find the suggestion offensive of working yourself on your
preferred way of contributing, that does not make for a very encouraging
outlook regarding other contributions.

There is some history to Graham saying "good!" for our current tools
looking discouraging as indeed the complexity of working on LilyPond and
its documentation system itself dwarves that of the contribution
process, and so it's not necessarily ill intent that stops contributors
short after the "VCS tool" hurdle has been placed aside.

So don't worry about contributing only "nice and responsible".  After
enough naughty and irresponsible contributions of code and
documentation, people will be more willing to listen to suggestions how
your contributions could be made involving less manual work by others.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]