Re: Bootstraping LSR: search for volunteers

[Erik Sandberg]

On Sunday 13 February 2005 11.47, Sebastiano Vigna wrote:
> On Sun, 2005-02-13 at 11:46 +0100, Erik Sandberg wrote:
> > Would it be possible to write a simple script to automate this task? It
> > could save a lot of work.
> >
> > (Also, this could be a way of including the bug repository in LSR in the
> > future; just checkout CVS now and then, and run a similar script to
> > update the bug section of the LSR)
> >
> > It's just an idea, I know nothing about the infrastructure of LSR so I
> > don't know if it's feasible.
>
> It is not difficult if it is "already snippetised", that is, if we
> already have a clear source for the text, the snippet title, and the
> snippet body. The manual needs, unfortunately, manual tweaking, but I'm
> rather sure that bugs could be put in directly. Say, if in the header
> section two title/text variables are defined... I think nothing is
> impossible 8^).

You could always create drafts for everything automatically using the texidoc 
fields, e.g. convert e.g. test/mensural-note-heads.ly into an item with title 
like "[todo] Ancient Mensural Note Heads" and text
"Mensural notes may also have note heads.", and do this preliminary conversion 
for test/*ly. This could simplify a lot for those who are going to work with 
the transition.

Also, bug reports are a bit different from other snippets: 
1. They should somehow be separated from the others (in general they show you 
what not to do, rather than what to do, so usually you don't want to find 
them).
2. They need some additional fields: Which version it was reported in, the 
bug's current status, etc.
3. They are in general not editable, instead they are re-generated sometimes 
from the bug cvs.

From my point of view, (3) is most important: It shouldn't be possible to post 
bug reports to LSR, if this could mean that some reports wouldn't reach me. 
Instead everything should go through the mailing lists.

Erik