Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

Re: [board-discuss] Design team leads

Hi Mirek,

On Thu, Jun 19, 2014 at 05:56:35PM +0200, Mirek M. wrote:
Astron told me that the idea to have positions within the design team was
not well-received and that I should discuss it with you. What do you find
problematic about having positions within the team?

To be clear, leads would be there to make sure that things get done, that
the process by which they get done produces the best results, and to
resolve controversial issues if they arise.

as others have aleady expressed, electing such titles and granting them on
extended timeframes has historically proven to be a hazard.

I believe in "With great power comes great responsibility", or corollary: power
should always be based on current resposibilities.

To give you an example, Ubuntu has the concept of a patch pilot:

whos prime responsibility is to welcome newcomers over a certain timeframe (a
day/a week). There is a natural authority derived from those doing duty on
those, without any need for granting titles or elections. It also usually keeps
those most involved with growing and progressing the team by doing onboarding
work -- which admittedly often is not the most attractive task -- in high
regard and prevents "title-envy" as everyone knows the work attached to the

Now, I dont know if and how that can be translated to the design team. One
(likely stupid) idea would be to have an email alias for onboarding newcomers
and anyone decently skilled(*) can join that alias and help newcomers asking
questions to it. In general, if things are not completely broken in the
project, those who do the most work there in helping others should naturally
grow authority in the design project. Then again, the same thing should work on
a mailing list -- but a onboarding mail alias _might_ make more obvious who is
doing most in onboarding newcomers and who is mostly following his or her own

Just my two eurocents -- I admittedly dont have to deep an insight into the design
team structure.



(*) use common sense here, like for direct commit access for developers
(**) which might be perfectly fine, but isnt the best prerequisite for
     leadership work

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.