The WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL./free software project has contributors worldwide who work on code, provide support, do translations, organize events, write documentation, review plugins and themes, and many other tasks that make the project what it is. These contributors are grouped into project teams, and each team has a site on the make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ network to communicate about the work they’re doing. Each team should elect two team reps to represent the team to the rest of the project, ensure issues are raised and addressed as needed, and coordinate cross-team efforts.
Current Team Reps
Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. Orientation
Since anyone who is an active contributor on a team can be elected as team rep, team reps will often have different levels of familiarity with other areas of the project, communication protocols, and general processes. To get everyone’s expectations in the same place, here’s the “job description” for team reps.
Often, Team Reps are the people who would be labeled Leads if we had that designation, but please avoid calling people Team Lead rather than Team Rep. There are many cases where the team reps will not be the same people that are considered “Leads” (a title we only have on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team right now, but could discuss for others if people think it’s useful), so being careful with language now will prevent confusion later.
Team Rep is a leadership role that is mostly administrative in nature; it is not a Lead role. Letting go of the Team Rep title is not a loss of status, just a handing off of responsibilities. Someone who is a leader in a team can lead whether they are doing the team rep job or not.
- There are at least two Team Reps. The intent is that one can take responsibility for the duties during the first half of the term while the other provides backup, and that in the 2nd half of the term, the backup rep will take the primary responsibility. This means about 3 months learning the ropes, and about 3 months as the primary team rep.
- The primary Team Rep is responsible for posting a weekly update of the team’s activity to the make.wordpress.org/updates blog, as well as raising any issues or red flags that other teams should be aware of or discussing. If the primary Team Rep can’t post the update, the backup rep needs to make it happen. If a team fails to post any updates in a 3 month period, they’ll be asked to recruit new Team Reps who have the availability/dedication to fulfill that duty.
- All teams will be invited to participate in a quarterly progress report. Currently (in late 2020), the reports include information on who was contacted on the team, what is the team’s current top priority, what is the team’s most recent priority, what challenges the team is facing, and what big win(s) the team has enjoyed recently.
All sites on this network are set up to allow anyone to comment. Add people as authors if they are active members of the team and you trust them to respect the responsibility of author status — author privileges are given to enable better communication, not to give anyone and everyone access to post all their opinions and ideas in an official channel. Anyone with posting privileges will be seen by the public as being official, so when someone is given author privileges, make sure to go over what is appropriate to post on a team site vs on a personal one.
Examples of Nomination and Election Posts/Processes
Some example posts from teams that have held team rep elections:
On Being Official
Please be thoughtful about how you communicate in and about the WordPress community and project. As a Team Rep, you have an official role, and while we certainly have no interest in censoring anyone, please remember that when speaking on behalf of your team, you should represent the project in a professional, courteous manner. It should go without saying, but: no swearing, no personal attacks, no discriminatory language, check your facts before making announcements, and most importantly, ALWAYS spell WordPress with a capital P. 😉
You will be added as an author to the make.wordpress.org/updates blog so that you can post your weekly updates. Each Team Rep will be made an admin on their team’s site so that they can update widgets, give people author privileges, etc.
Note that being a Team Rep doesn’t impart unilateral decision-making authority for the WordPress project or the wordpress.org site. Here are some rules of thumb to help in determining what you and your team should just do, what should get feedback from other reps and the executive director (currently Josepha Haden Chomphosy) or Matt first, and what requires permission.
- If it’s something that only affects your team or team site, and your team is agreement, go for it. Include it in your weekly update so everyone else will know what’s up.
- If it’s something that involves another team, changes a policy, or would affect the make.wordpress.org network, put your proposal in writing and post it to the updates blog for feedback before implementing the change (incorporating feedback). You can do this as part of your weekly update or as a standalone post. If there is significant opposition to your proposal, don’t proceed until we get the concerns addressed.
- If you have an idea for improving the wordpress.org site based on your team’s area of expertise, Matt’s approval is required. Write up the suggestion (and/or mockups if applicable) and post it to the updates blog. The other Team Reps will weigh in, but the executive director (currently Josepha Haden Chomphosy) or Matt will make the final decision about changes to the wordpress.org site. Once approved, the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team handles implementation. Please don’t give requests for changes to the wordpress.org site to the Meta team without approval unless it is for small/uncontroversial things like fixing typos, reporting bad css, etc. Also note that there are a number of changes/projects for improving wordpress.org that have been approved but not implemented yet, so your request may already be in the queue.
Team Reps will be added as authors to the Meta team site, so that small fixes and approved proposals can be posted.
Editorial note: @kafleg removed some outdated content and added some more current relevant content to this page on January 02, 2024.