VOTING: Code of Conduct Revision
Ruth Cheesley
Voting procedure
Valid votes contain one of the following options:
+1 (in favor of the motion)
-1 (against the motion)
Abstain or blank vote (reply to the email thread with the word “Abstain”)
Please make sure to use the terms provided above in order to cast a valid vote. Anything else will cause your vote to be considered a non valid vote.
The voting basis:
To have a quorum, a majority of the current 28 members in leadership need to cast a valid vote.
To adopt the motion, the votes in favor need to be 50% + 1 of the votes casted, ignoring the blank votes.
Voting will take place by responding to this email thread with your vote.
CLT:
Guillermo Bravo
Peter Bui
Ruth Cheesley
Alice Grevet
David Jardin
Dianne Henning
Sander Potjer
PLT:
Roland Dalmulder
Chris Davenport
Robert Deutz
Marco Dings
Jessica Dunbar
Javier Gomez
Thomas Hunziker
Tom Hutchison
Tessa Mero
Viktor Vogel
George Wilson
OSM:
Martijn Boomsma
Ronni Christiansen
Victor Drover
Jorge Lopez-Bachiller Fernandez
Rod Martin
Ryan Ozimek
Saurabh Shah
Joe Sonne
Marijke Stuivenberg
Sarah Watz
Proxies
If, for any reason, a member is unable to vote within the given time frame, he or she can authorize another person to cast the vote by proxy.
Timeline
Voting on revised Code of Conduct 15-29th July 2015
Publication of revised Code of Conduct 30th July 2015
Jessica Dunbar
+1 on Joomla code of conduct v3
-1 Conflict resolultion team operating procedures
+1 on COI
+1 on the 1 pager
I really appreciate everything that went into this. I have an issue with the operating procedures others everything looks good.
After dealing with my own COC drama, it's completely unnecessary to start a discussion with the entire leadership team. I don't know who is experienced in human resources or discipline on leadership. it's certainly not going to be added onto my already full plate.
using PLT as an example. PLT members need to make our code and releases a priority. Not politicking and group discussion on people's behavior on other teams. Unless it deals directly with us. I understand if someone gets banned we should be notified, but there needs to be a level of trust and privacy for other issues duties. I don't understand how involving all of leadership will help these situations.
As leaders we need to be trusted to do what's best for the team you are leading or involved with, without an oversight committee. Getting the CRT involved should be a last resort.
nominations and voting for the actual committee needs to be completed. The team should be expanded for diversity purposes. Also I work with half of the CRT team on a daily basis a bigger team is needed.
--
You received this message because you are subscribed to the Google Groups "Joomla Leadership Team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-leaders...@googlegroups.com.
To post to this group, send email to joomla-l...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-leadership.
For more options, visit https://groups.google.com/d/optout.
Ryan Ozimek
Sent from my mobile device.
Ronni Christiansen
The only reason why the vote is valid is because we accept it - and once its passed it needs to be ratified on a OSM board meeting in an official vote to implement it into the bylaws of the organization, or it has no legal value.
So we can continue voting.
I would like to know what has been updated in the COI - i was not aware it was a part of the documents being updated by this working group and i am not sure why its a part of this vote.
As for the CoC and CRT i vote +1 for both.
It is extremely important that this is clearly documented so that any future leadership members are fully aware whats expected from them from day 1 so we can avoid those kind of situations in the future.
Tessa Mero
Martijn Boomsma
It seems to me that it's unclear what vote is requested exactly. Your
statement is "we propose the following for adoption by vote" but then
there are four documents. Do we have to vote on them separately or all
in one go? Maybe because of their nature they should be separate, so
we would have two ot three rounds of voting?
So to start with (keep it simple;)):
we hereby propose to adopt the Revised Joomla! Code of Conduct:
https://docs.google.com/document/d/12L3604QBuM_vSgud8vsbEHJhbI-mHz26QCanUB_R4jU/edit?usp=sharing
Then:
we hereby propose to adopt the Conflict Resolution Team Operating Procedures:
https://docs.google.com/document/d/16Avdx_ioQhH2zjJoPRl3Ac8pbpa_3nYE2XBo_yknRlU/edit?usp=sharing
Or can these not be dealed with separately?
Thank you!
Warm Regards,
Martijn Boomsma
Open Source Matters Inc.
http://www.opensourcematters.org/
Joomla! http://www.joomla.org/
Ruth Cheesley
- The Leadership Team would only be involved in the CRT process if a sanction is being proposed.
We discussed several different options which included having the CRT decide and impose sanctions without involving the leadership.
Based on the experience of other projects and the fact that this is a new process, it was decided that when a sanction is being proposed it should be (at least until these processes are tried and tested) discussed and accepted by the Leadership Team by a majority vote, having heard the recommendations from the CRT.
The way this has worked for example in the KDE community is that the whole board discussed and implemented any sanctions for the first few years, and then they devolved that responsibility entirely to the working group (equivalent of our CRT) at a later date, who now manage the process internally and report to the board monthly with any sanctions that have been imposed or lifted that month.
I hope that explains why we chose to adopt this route in the initial stages of rolling out a new process where there hasn't been one before.
If the Leadership Teams feel that the CRT should be able to make those sanctions without the consultation and voting of the rest of the Leadership at this early stage then absolutely, that can be discussed as part of the CRT's operating procedures, but this should not hold up the voting on the new Code of Conduct. Please post comments/thoughts on the operating procedures document - request access if you need it. - The reason we are asking for a vote from the Leadership Teams is to officially update the Code of Conduct with the one we have proposed. This is the process we were asked to follow at Cancun in the LT summit (to open for feedback then prepare a proposal to be voted by the Leadership Teams).
- The Conflict of Interest policy has been updated to include leadership team members, whereas in the past it was only used for OSM board members.
The current document is here: https://docs.google.com/document/d/1wK8DIojOiZGLLVNTYlgxDbKaF-sVyeHP74lVvO1uD4s/edit?usp=sharing - Thank you for the suggestions Tessa, at this point we've already been through four weeks of leadership and community feedback so this is the version we were proposing for adoption.
I'm not sure that as we've already requested the voting to start, that we can now make substantial changes to the document without re-starting the process again.
I've incorporated the grammatical issues you raised and pointed you at the forum where some of the other issues you raise have already been discussed. - Martijn, we updated the Code of Conduct but in doing so it was suggested we create a one-page document and operating procedures for the conflict resolution team (which we had originally included in the Code of Conduct itself).
It was also identified that there is currently no Conflict of Interest policy in use for the leadership in general, only OSM.
If there are any issues with a specific document then people could raise those issues, and/or give a +1/-1 for each of the documents if there are any issues with specific documents.
If the Leadership Teams feel that any or all of those documents need to go through a separate approval process then by all means I'll send three separate vote requests in addition to this one. Please let me know if that is the route people would prefer us to take.
I hope that answers some of the questions, thank you for taking the time to review this in detail and voice the issues that have been raised.
Kind regards,
Ruth Cheesley
Alice Grevet
--
You received this message because you are subscribed to the Google Groups "Joomla Leadership Team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-leaders...@googlegroups.com.
To post to this group, send email to joomla-l...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-leadership.
For more options, visit https://groups.google.com/d/optout.
Dianne Henning
Robert Deutz
Guillermo Willin Bravo
Dianne Henning
--
David Jardin
Cheers,
--
Roland Dalmulder
Martijn Boomsma
Martijn Boomsma
Open Source Matters Inc.
http://www.opensourcematters.org/
Joomla! http://www.joomla.org/
Saurabh Shah
http://opensourcematters.org/
Phone: +91 - 9561160006
Chris Davenport
Joomla Production Leadership Team
Rod Martin
OSM Joe Sonne
Javier Gomez
Viktor Vogel
Sander Potjer
Sarah Watz
Jorge Lopez-Bachiller
http://opensourcematters.org/
Tessa Mero
Jessica Dunbar
Emotional deceit is a great weapon that many use in this community. And we've seen many great leaders subject to it and eventually leave. The ability to recognize understand the nature of conflict, and to be able to bring a QUICK and just resolution to conflict is needed to prevent escalation and resentment.
@jessicadunbar on Twitter
Tessa Mero
Robert Deutz
Jessica Dunbar
David Jardin
Jessica Dunbar
Dianne Henning
Jessica Dunbar
Was Tessa's bcc concern over spelling and grammar errors? Or was it changed?
Grammar and spelling can completely change the context of a sentence.
Can we all have access to versioning again to see the minor changes you speak of?
This thread proves how poor the communication is within the CoC team. This is exactly what I personally experienced. Never ending changes, poor response time and made up processes all resulting in resentment, misunderstanding and humiliation.
Here's my -1 to all 4 docs
Thomas Hunziker
George Wilson
Dianne Henning
--