Welcome! This is the home of the Make Community Team for the WordPress open sourceOpen SourceOpen 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. project!
This team helps the community with official events like:
Discuss: Here we have policy debates, project announcements and status reports. Everyone is welcome to comment on posts and join the discussion.
Plan: Want to organize a meetupMeetupMeetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. in your community? Excited to host a WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.? Check out one of our handbooks to get started.
Assist: Participate in the Meetup Reactivation project, apply to be a Community DeputyDeputyCommunity Deputies are a team of people all over the world who review WordCamp and Meetup applications, interview lead organizers, and generally keep things moving at WordCamp Central. Find more about deputies in our Community Deputy Handbook., or help out as a WordCamp MentorMentorSomeone who has already organised a WordCamp and has time to meet with their assigned mentee every 2 weeks, they talk over where they should be in their timeline, help them to identify their issues, and also identify solutions for their issues..
Discover: Any skill level can find a way to be involved in our Team Projects.
Office HoursOffice HoursDefined times when the Global Community Team are in the #community-events Slack channel. If there is anything you would like to discuss – you do not need to inform them in advance.You are very welcome to drop into any of the Community Team Slack channels at any time. are held on Slack in #community-events
Kicking off the Community Documentation/Translation Sprint from September 20 to 24
As announced previously, the Community Team is launching a week-long documentation sprint (focussed on translations), as part of the International WordPress Translation Day celebrations! From today (September 20) through September 24, community contributors and deputiesDeputyCommunity Deputies are a team of people all over the world who review WordCamp and Meetup applications, interview lead organizers, and generally keep things moving at WordCamp Central. Find more about deputies in our Community Deputy Handbook. will work together to update Community team handbooks, with a focus on translating them (and related Community Team documentation pages) to local languages! The sprint is open to all, and we warmly welcome everyone to participate!
Want to find out more about the event and learn how to participate? Check out the announcement post for more context and details:
We also have an excellent Tuesday Training which will guide you on how to translate community team documents:
How do I participate in the translation sprint?
Anyone can participate in this initiative! The team will keep track of edits in a Google Sheet. Please log all the changes you make in that sheet. The team will also coordinate together in the #community-team channel. You can also share your updates in the #polyglots-events channel to connect with fellow Polyglots.
If you are new to translating handbooks, check out this Tuesday Training that will answer all your questions. Anyhow, here is a suggested workflow for contributors:
Check the tracking sheet if anyone else is working on it for your locale. If your locale has already translated handbook pages, check your locale’s Rosetta site to see if anyone has already translated the page – you might also want to check with other community members to see if anyone is working on the docs. If no one is working on the doc and it has not been translated, log it in the sheet. Don’t forget to add the handbook and page names, and your WordPress.orgWordPress.orgThe 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/ username!
Copy the contents of the page over to a new Google doc. Ensure that its sharing permissions are set to: “Anyone with the link can comment”. If you already have access to your Rosetta site, you can copy the contents over to your locale’s handbook and make changes over there. Feel free to ask in #community-team if you have any questions about any contents in the documentation.
Once you have finished translating the document, you can optionally pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” one or more of your team members to ask for review. Once the document is finalized, you can go ahead and publish the same in the handbook. If you prepared the translations in a Google Doc, don’t forget to share the same with your Locale Manager(s) or GTEGeneral Translation EditorGeneral Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor.(s) so that they can update the same on your behalf.
Fill up the spreadsheet to record the changes that you have made and update the field if the translated page was merged.
That’s it, you have successfully made your first contribution to the Docs translation sprint! You can now proceed to work on the next document!
Remember: Every contribution, however small, is valuable!
But… I’m not a Polyglot and I would like to participate! What do I do?
We are glad you asked! While the focus of this sprint is translation, we need your help in reviewing our existing documentation, suggesting changes, and even creating new documentation pages. Even though the tracking Google sheet is aimed at translations, you can use the same to track your documentation updates too.
Check out the announcement post of the original docs sprint to learn more about how to update Community Team documentation:
I warmly welcome you all once again to join us in this initiative and to help us update our documentation and translate it into as many languages as possible. It will go a long way in supporting the WordPress community!