lilypond-devel
[Top][All Lists]
Advanced

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

Re: [talk] why it'd be great to have web interface for submitting simple


From: James
Subject: Re: [talk] why it'd be great to have web interface for submitting simple doc patches
Date: Sat, 6 Oct 2012 15:46:26 +0100

Hello,

On 6 October 2012 15:23, Joseph Rushton Wakeling
<address@hidden> wrote:
> On 10/06/2012 11:34 AM, James wrote:
>>
>> How is a web interface easier than email to enter information?
>
>
> Well, the problem with simple doc patches is that to submit them to Lilypond
> you have to go through the same procedure as if you were submitting a code
> patch, which means uploading to Riedveld etc., which in turn means
> installing some custom code on your machine -- see:
> http://www.lilypond.org/doc/v2.17/Documentation/contributor/commits-and-patches#uploading-a-patch-for-review

That;s not technically true. Git-cl is supposedly to ease updating the
tracker and posting to reitveld at the same time.

You can upload your patch manually if you so wish, we just ask that we
have Rietveld for code review and the tracker to keep.. err track of
what is what and where etc.

>
>  ... and as it's a doc patch, there's not really any reason to do this,
> because it's not going to break any unittests.

Pardon?

Says someone who evidently has never built, submitted or tested 'doc'
patches for LP.

I think you perception of what we do and why is skewed.

>
> Yes, you can wait for some other dev team member to pick up your small patch
> and submit it, but that puts the onus on them to do the work.

So does poorly submitted documentation suggestions, but hey.. *anyone*
can write documentation right? With clear understanding, good syntax,
spelling, sentence structure and oh and good lilypond examples.
Easy-peasy.

James



reply via email to

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