Based on feedback, @devinmaeztri and I have updated and simplified the previous information into this one post. The goals of these changes are:
- change the role names so they are more universally translatable
- simplify the number of applications needed to contribute
- simplify the overall contributor journey
- clarify the tasks and expectations for the various contributor roles
- create support for our mentors so they can be more successful
- create a Help Path to help the work flow more smoothly
- specify the Deputy/Community Admin tasks so their contribution is more evident and the necessary tasks are getting done
To accomplish these goals, we suggest the following changes.
Name Changes
WordCamp Mentor/DoAction Mentor/Meetup Mentor become Event Mentor.
Community Deputy becomes Community Admin.
Super Deputy becomes Community Advisor.
Updated Role Descriptions
Community Team Member: participate in the Make/Community Slack channel or attend WordPress events
Event Organizer: organize local events that promote WordPress and Open Source
Event Mentor: help guide and unstick event organizers
Community Admin: support mentors and help with the technical side of event organizing
Community Advisor: guide all other contributing roles with a particular focus on what’s best for our community now and in the future
Contributor Journey Visuals
This is the current contributor chart. The arrows show the various paths you can take to get from one role to another. As you can see, each area requires the contributor to submit an application to change roles.
The chart below is based on the recommended updates. It allows community team members who want to contribute beyond organizing events to submit one application and be filtered into the supporting role that fits them best or appeals to them most.
It also allows flexibility, so individuals who are ready can move directly into a Community Admin role without being required to first be a mentor.
How We Work
The Community Team is committed to working as publicly as possible for transparency and the education of all. Questions should be asked as publicly as the content allows so that we can learn and grow together. Delicate situations will be managed with caution and respect by more than two people so important information does not become lost while keeping the necessary people informed.
Help Path for the Entire Community Team
- Check the handbook
- Ask a community team member
- Next, ask an Event Mentor
- Ask a Community Admin
- Ask a Community Advisor
- Email [email protected]
Expectations of Event Mentors, Community Admins, and Community Advisors
- Help organizers plan events that align with open source philosophies and promote WordPress
- Help make events easier to organize and improve attendee experience
- Help organizers avoid problems before they become problems
- Help keep organizers accountable to the planning details and financial reports of the event.
Time Commitment
- At least 4 hours a month, depending on your desired level of involvement.
Requirements
- Willing to work and communicate publicly and transparently
- Successful lead or co-organizer of the type of event you want to mentor — both financially and in team management
- Demonstrate understanding of the WordPress community, its values, and both the Event Code of Conduct and Community Code of Conduct
- Demonstrate exemplary behavior that aligns with the WordPress community standards, it’s values, and both code of conducts, including no previous incidents or conflicts with the Community Team
- Successfully finish the required training courses
- Exhibit collaborative, community-minded communication skills
- Be organized and reliable
- Be able to meet with event organizers and other community members when necessary on Slack, Google Meet, and/or Zoom, your choice
Additional requirements specific to becoming a Community Admin
- Consistently supports WordPress communities and organizers with strong understanding of the global program
- Participates regularly in Community Team discussions and decision making
- Successfully complete ALL organizer-related courses
- 3 references from event organizers or current Community Admins
Additional requirements specific to becoming a Community Advisor (in process)
- Consistent participation beyond the basic requirements
- Ability to be consistently available
- 3 references from fellow Community Admins or current Community Advisors
Tasks by Role
| ROLE | TASKS |
| Event Mentors | Monthly – Check in with your event organizers – How’s the budget? – How’s the timeline? – Are they facing any blockers? – Do they have any issues within the organizing team? – Use the Help Path to answer questions for your event organizers – Attend each monthly Community Team meetings, async is fine – Report about your event’s progress in the monthly Community Team meeting – Report about your event’s progress on the monthly Make/Community Post Yearly Note: WordCamps will only be mentored by lead organizers who have successfully led a WordCamp. |
| Community Admins | Monthly – Vet at least 1 event application – Give at least 1 event orientation – Keep the Event Trackers up-to-date based on mentor feedback – Triage HelpScoutAttend each monthly Community Team meetings, async is fine – Help fellow Admins in decision making in #community-Admin – Answer questions in #community-event and #community-team when possible – Update documentation as needed Quarterly Mentor events, as they choose and qualify. If mentoring an event remember to: |
| Community Advisors | As possible – Perform budget reviews – Perform the tasks of Community Admin and Event Mentors Continually |
Invitation to Leave Feedback
Please leave your comments and questions in the comments. You can also join us tomorrow for the live discussion during the Community Team training.