Claus Agerskov wrote:
On Wed, 21 Dec 2005, Jacqueline McNally wrote:
The OpenOffice.org project guidelines suggest communications of
these types of decisions privately, and I remember you yourself
said praise on-list and critique off-list.
Yes critique - but telling MarCons to leave their position is not
critism but kicking them out.
Ryan started this thread of his own volition. I did not ask him to
resign or kick him out. I sent him a private message revoking his MarCon
role.
I disagree with this approach when it comes down to the situation
we have at hand.
You don't know what the situation will be - some will leave without
saying nothing at all others (like Ryan) will say goodbye in a quiet
way and I would have fought if it was me.
I do not feel that Ryan said goodbye in a quiet or considerate way, and
even if it is considered quiet or some other way, it is his own choice.
OpenOffice.org is an open source project and you cannot use the
usually business or corporate way to manage situations. Kicking
people off the projects without taking an open discussion and hearing
what the rest of the project members have to say is not the open
source way - not if it have to succeed in the long run.
I did not kick Ryan off or from OpenOffice.org. Ryan stated in his
message that he was unsubscribing from the OOo lists.
As to using business or corporate way, you are right. We don't even
employ this method to recruit people to the MarCon role.
If you only criticise off list then only the one who is criticised
will see what is criticizable so the rest of the project members does
not learn from it. And the rest of the project members can't respond
if your critism is wrong.
I agree with you. And I'm in a somewhat of a dilemma. You are saying
that any critique is to be public, whereas others and the OpenOffice.org
guidelines are saying that it is to be private.
I prefer any communication to be public, especially difficult or awkward
situations. For example, there has been some email conversations in
which I have been cc'd in that I would have prefered not to. Statements
about other community members that I consider to be scandalous if not
libelous, but because private messages or marked as in-confidence, I
have no easy way of verifying or doing anything about it. And to be
quite honest would have preferred to be not involved. I quite understand
people stating in their sigs, reply to the list only.
You can view criticizable behavior as a bug - and in open source
projects bugs are discussed openly.
I agree with you, but others state otherwise.
I will only now consider public critique to Ryan at his request.
When you become a member of an open source project you will be a
target of public critic - escpecially from you peers.
And I'm ok with that, but I'm not ok with what people consider all is
wrong with the OOo MP is my problem. I am not the MP.
The Project Leads are responsible for the recruitment of and
liaison with MarCons. Usually, potential candidates contact us, as
two did earlier this week. The "What Do MarCons Do?" is a minimum,
and I'm happy to say that most of the MarCons exceed these
requirements.
And where did Ryan not meet the "What Do MarCons Do?"?
http://ooosmp.homelinux.org/GoalsandObjectives/MarketingProject
The most enjoyable greetings
That is up to Ryan to say if he wishes.
From the posts here and offlist I am beginning to think that perhaps we
need to be more formal. The "What Do MarCons Do" was simply documenting
an existing process, one that works well when things are going well, but
doesn't work so well when it doesn't.
Other OSS projects (Debian, Fedora and Ubuntu come to mind), have a more
formal process as to code of conduct and membership and I think it may
be a good idea to look to them and include some of these processes.
Regards
Jacqueline McNally
Lead, OpenOffice.org Marketing Project
Are you a computer angel? (www.computerangels.org.au)
Linux.conf.au 2006 (www.linux.conf.au)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
