Interested in joining the leadership team that supports and helps build the WPSeattle community?
Here’s what you need to know:
- You’ll be asked to serve a two-year term
- You’ll be part of a team that always includes at least two other co-leads
- Your responsibilities will include providing support to meetup hosts, promoting the community, and administering resources like our Meetup site, community portal, and PayPal account. Read more about community leader responsibilities.
Prerequisites: To become a community leader, you must have at least one year of experience hosting a WordPress meetup in the Seattle area or have served as a co-organizer for WordCamp Seattle at least once. If you’ve done both, that’s even better.
The first step in the process is letting the current leadership team know of your interest. We’ll be happy to help you gain the requisite experience you’ll need if you’re not already an experienced host or veteran WordCamp co-organizer. If you meet the criteria, you’ll be asked to shadow one or more leaders for a trial period, during which time you’ll learn about the duties of the role. If there’s mutual agreement that you’d be a good fit following the trial period, you’ll be added to the leadership team for a two-year term.
Community leadership continuity and succession
To ensure the WPSeattle community is well supported, there shall always be at least three active co-leads, but no more than five. A co-lead may step down at any time and for any reason by providing written notice to the other co-leads. The notice must specify the effective date that the leader intends to resign from their role and turn over their duties to a successor. Leaders are asked to provide at least a few weeks’ notice if at all possible.
Upon completion of a term, a co-lead may serve a second term by mutual agreement between themselves and the other co-leads then in office. Upon completing a second consecutive term, a co-lead shall rotate off the leadership team.
Terms ordinarily begin on February 1st and end on January 31st, with the month of January serving as a “transition period” between outgoing and incoming co-leads.
Retired co-leads may continue to assist the organizing team on an as-needed basis as advisors. A retired co-lead may also be temporarily called back into service by the leadership team in the event of an emergency or contingency, such as an unexpected resignation or departure that leaves the leadership team with fewer than three members.
Community leaders are expected to:
- Abide by the WordPress community Code of Conduct
- Complete tasks they’ve agreed to take on in a timely manner
- Advise their co-leads if they are unable to complete a task by an agreed-upon deadline
- Monitor communications on Slack except during times of unavailability
- Show up at organizing meetings except when a conflict exists
When a community leader cannot make a meeting or complete a task for any reason, it is their responsibility to notify their fellow co-leads that they will be absent or unable to follow through so that their co-leads can adjust accordingly.
Co-leads are expected to work cooperatively and hold each other accountable for meeting the expectations defined herein. When a member falls short of the expectations, the other co-leads shall consider the magnitude of the violation prior to responding. Co-leads shall make every effort to treat each other with respect, especially when holding each other accountable.
A co-lead may be removed from the leadership team by their fellow co-leads prior to the expiration of their term when any of the following conditions are met:
- The co-lead has been absent from three consecutive meetings (or three of the past four meetings) of the leadership team without having given 24+ hour notification of an absence;
- The co-lead has become unresponsive to emails, phone calls, and Slack messages for at least two weeks without having given notice of unavailability;
- The co-lead has consistently failed to complete more than three of five recently agreed-upon tasks by the agreed upon deadline.
When a member of the leadership team is believed to be derelict in their duties by a colleague, that colleague shall call for an open meeting of the entire leadership team – including the member who is not meeting expectations – to discuss the potential removal of that member. At least forty-eight hours’ notice must be given for this meeting via email and Slack. In the event said member decides not to resign of their own will, the member may be removed by unanimous agreement of the remaining members.