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

[James]

Hello,

On 6 October 2012 09:51, Janek Warchoł <address@hidden> wrote:
> Just a musing....
> I think the case shown below would perfectly qualify for "could you
> write a documentation patch for this? it can be done with a web
> interface, instructions are here" - if we had the web interface.
>
> On Sat, Oct 6, 2012 at 10:44 AM, Janek Warchoł <address@hidden> wrote:
>> On Sat, Oct 6, 2012 at 2:38 AM, Brad Smith <address@hidden> wrote:
>>> When should you
>>> use ly:pitch and when should you use ly:music? (Is there a place in
>>> the documentation that is good for learning these things?)
>>
>> I'm no expert on music functions, but i'd say that ly:music? is used
>> when the argument would be a music expression, e.g. { c8 d-. e-. c-.
>> }, while ly:pitch? is used when the argument is a note name.
>> This /should/ be in the documentation.  Could you make a bug report about it?
>>
>> hope this helps,
>> Janek
>
> I know that everyone can make a simple email with doc suggestion and
> send it to the mailing list, but then someone has to maintain it.
> Also, several times when i asked users for such suggestions they were
> very vague and i couldn't just copy-and-paste them (and i didn't have
> time to do more).  If we presented them with a web interface where
> they could write the actual change, it should work way better.  Just
> look at Wikipedia.

How is a web interface easier than email to enter information?

Also Wikipedia is still maintained (and checked) by someone - who
would that be in this case, oh I know lets get a group of people to
monitor this website and if they find any comprehensible requests then
they can create a tracker so that users don't request the same thing
over and over. This group of people should have a name too.. how about
Bugsquad... oh wait... ;)

The email lists are also archived, while it isn't a perfect system,
Bug squad are great at catching most things, and also clarifying with
the contact if they don't understand it.

I think you have proven your own point when you say

> Also, several times when i asked users for such suggestions they were
> very vague

And being vague in an email vs vague on a website is different how?

> and i couldn't just copy-and-paste them (and i didn't have
> time to do more).

Right, so you fwd to bug list and bugsquad take care of it if they can.

James