Re: Fwd: [board-discuss] Design team leads

2014-06-19 Thread Sophie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le 19/06/2014 18:38, Cor Nouws a écrit :
 Mirek M. wrote (19-06-14 18:18)
 What if we called them experts instead?
 
 Moderator / key-contact / coordinator / ..

I think coordinator gives a good pictures of what you described of the
roles on the Design list.
 
 It needs to be clear to newcomers that they're the go-to people
 for certain tasks within the design team, and that requires a
 semi-formal mention on e.g. the wiki.
 
 Yep!
+ 1 :)
Cheers
Sophie

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJToxktAAoJEPL4wtZQX4TTPmAH/i0HhvuoT/ZcErEGhaW/zoxZ
pMttvxRUE4DICs6LR/bn0wTpDdZG7D5yC45P0z1e2qV7Q8C3bzSe+PTePqD421oZ
6Soi6pFP8ZiwcrfMbIP5n4WDF76Kp6dTd8822oTJOJLmRT3X4hlpdwnpY/bzs7DK
LYrrOgZ9NG2ScHPAg8GCuXWeSbMZ2t9x57sunGiPmhMv5Ld35SxotWR7Mapi0ft2
nIHH+lwG7ZzSkFWmJJJx9po5SFGPnhrVyG/FT6RRldXfLMPbALUbK9FkOLTAHqpd
xdlHgLCQr/8I1oLeo9LtAwfx0maBAIjxMQI5ge+XuiSK5wHVnUAwQi2094P7ZoA=
=5LyL
-END PGP SIGNATURE-

-- 
To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/board-discuss/
All messages sent to this list will be publicly archived and cannot be deleted



Re: [board-discuss] Design team leads

2014-06-19 Thread Norbert Thiebaud
On Thu, Jun 19, 2014 at 10:56 AM, Mirek M. maz...@gmail.com wrote:
 Hi,
 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.

Just to pile up on what has already said:
'lead' has a loaded history in the project
so is the bestowing of 'title'.

That being said, as a team, the notion of coordinator is not offensive
per se, and as long as it is a de facto acknowledgement of a actual
function and not a de jure title it is perfectly fine imo.
But one is such coordinator because he/she is actually 'coordinating'
with the approval and agreement of the people being coordinated (no,
no need for an election or such.. if you need a formal election it is
already a 'fail')
This is a natural extension of the meritocratic principle at the core of TDF.

Norbert

-- 
To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/board-discuss/
All messages sent to this list will be publicly archived and cannot be deleted



Re: [board-discuss] Design team leads

2014-06-19 Thread Bjoern Michaelsen
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:

 https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews#Patch_Pilots

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
authority.

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
agenda(**).

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

Best,

Bjoern

(*) 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: board-discuss+unsubscr...@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/board-discuss/
All messages sent to this list will be publicly archived and cannot be deleted