lilypond-devel
[Top][All Lists]
Advanced

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

Re: GOP-PROP 7: Developers as resources


From: Jan Warchoł
Subject: Re: GOP-PROP 7: Developers as resources
Date: Fri, 29 Jul 2011 09:56:38 +0200

2011/7/28 Graham Percival <address@hidden>
> ** Amateur orchestra
>
> I shall describe the workings of the (Vancouver) “West
> Coast Symphony Orchestra” (at least when I was playing with them,
> back in 2002-2006).
>
>    There is no discouragement from missing a concert – members
> know that they all have busy lives, and if there is a big deadline
> at work or a family vacation during a rehearsal period, they
> simply do not sign up for that concert. However, if you do sign up
> for a concert, then you are normally only allowed to miss one
> rehearsal.

And what happens if they miss more?  What will happen if we sign up to
a team and not do our "homework"?

> If we had a central authority leading a team (or teams) of
> developers – or at least, leading developers for X hours a week –

The question is, who will it be.

> then we could “enforce” reviews. Maybe July-August would be
> directed towards the graphical display of rhythms. That team would
> dissect any patch for beaming, drawing longas, etc; any patch to
> the parser would be ignored (at least, ignored during the X hours
> of team work).

What about new contributors?  It would be bad to tell them "you want
get much help on this during next 5 months, come back again in
December when we'll discuss fonts."

In general, count me in (i don't know for how many hours yet).

Additional idea: when there are teams, work can be split.  One person
can research proper notation, another write the code, another prepare
some regtests, another write docs.  Not everyone is good with all
these.

cheers,
Janek



reply via email to

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