Re: [libreoffice-design] Flying the ship... [please everybody, post a short reply]

Hi Vamsi, Phil, all

sorry for this short reply (and top-posting), but I'm still more than 
busy with the discussion on how our larger community will evolve after 
the OpenOffice.org donation to Apache and the license shift from LGPL to 
Apache V 2.0 where every (free or corporate) entity (including 
Microsoft) can take the code without being obliged to contribute 
anything back.

I marked Phil's mail for replying once I read it first - it is very 
reasonable and leads to more transparency in our team to have such a 
kind of formal guideline.

What I'd like to see is a "how we work" area in the wiki we can point 
new members to - being quite similar to a formal paper, but more 
friendly to new contributors...

Best regards

Bernhard

Vamsi Kodali schrieb:
> +1 to Bernhard.
> Now that that's out of the way, I request you to please consider Phil's
> proposal. I think that almost all (if not all) the steps he mentioned
> are being followed now too, just in a unorganized way. I believe that
> bringing a organized and managed scheme for new ideas and conveying it
> to the people involved in a clear manner will tidy up and improve the
> productivity of the entire process.
>
> Thanks,
> Vamsi.
>
> On 05/25/2011 04:59 PM, Phil Jackson wrote:
> > Hi Bernhard
> >
> > We need some structure and therefore we need someone unofficially or
> > officially to lead it. I'm more than happy for you to take on that role.
> >
> > If possible, I'd like to see a degree of formalisation of how the
> > design team will work together with suggestions of stages for taking
> > an idea and transforming it into a form that we have agreement on for
> > submission to the pool of programmers.
> >
> > This is about building relationships between the design team members
> > but also between the design team and programmers so they feel part of
> > the design team.
> >
> > It's like selling ideas to management - well articulated ideas with
> > supporting evidence should make a difference in getting done what the
> > Design Team thinks by consensus is necessary to improve the product.
> >
> > Here are some suggestions for stages;
> >
> > 1) Someone comes up with an idea
> > 2) Idea is posted on Design/WhiteBoards and emailed to team members
> > 3) Idea is discussed and debated with ample opportunity to test idea
> > and gather arguments for and against
> > 4) Goes to vote stage by design members after member proposes that
> > they do this - if passed goes to Stage 5)
> > 5) A Design/Whiteboards paper for the idea if constructed giving a
> > formalised breakdown of the idea -
> > i.e. Overview, Introduction, Main Body with evidence, conclusions (why
> > idea is a good one) and references/bibliography.
> > 6) Submitted to programmers pool for their feedback.
> > 7) Followup
> >
> > We need to make this reasonably professional without turning it into a
> > Phd. It makes it transparent for all.
> >
> > I know that some of these things are already done, but using a system
> > will make it more likely that progress is seen to be made on some very
> > interesting and beneficial ideas.
> >
> > What does everybody think?
> >
> > Cheers
> >
> > Phil Jackson


--
Unsubscribe instructions: E-mail to design+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/design/
All messages sent to this list will be publicly archived and cannot be deleted