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
You’ll notice in the above screenshot that most of the tickets have tags in separate gray boxes next to the subject line. The first thing you’ll want to do is tag tickets/emails that aren’t tagged. There are a few ways to do this:
If you can tell the context of a ticket by its subject line, you can quickly tag it from this inbox view. Click the checkbox at the far left of the ticket. You’ll notice a menu pop up when you do this.
Click the little “tag icon” (third from the left) and a text field will appear. You can now enter tags by typing them in. You may notice that as you type, that suggestions for your tags will appear. You can select from those suggestions if you’d like, or just type your tags separated by commas. What tags should you use? See the section titled “The TagTagTag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. System” for more guidance.
If there are multiple tickets that you see that you’d want to assign the same tags to, you can click multiple checkboxes to assign the same tags to them in bulk.
If you can’t tell the context of a ticket from its subject line, you’ll want to use this method. Click on the ticket to open the conversation.
The actions you can take with the ticket are in an icon menu at the top: Reply, Note, Assign, Status, Tag, More (which includes Delete, Follow, Forward).
After you quickly scan the email and have determined its context, add tags by clicking the tag icon and typing them in. What tags should you use? See the section below titled “The Tag System” for more guidance.
Keeping our tags consistent is important for keeping searches accurate.
We use a system similar to the way WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. manages tickets. We tag for Component, Keyword, Location, and Priority.
Best practices: hyphenating multiple-word tags, and using singular forms of nouns.
payment contract (signing/reviewing venue or vendor contracts) swag (requests or reminders to send swag to a group) application budget sponsor speaker venue insurance advice (organizer requesting advice on an aspect of the event or group) GPL trademark trouble (organizer is asking for help dealing with conflict or has a big problem that requires the help of someone with experience) camera video contact-form (For use when people fill out the contact form at https://central.wordcamp.org/contact-us/) meta(for emails related to the MetaMetaMeta 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) QBO(for emails related to QuickBooks, our invoicing software) wptv(for WordPress.tv related emails) amazon(for emails from Amazon web services)
Keywords (these relate to an action that needs to be performed by a 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.): needs-vetting needs-interview needs-orientation
needs-agreement needs-site needs-budget-review needs-shipment needs-advice second-opinion (if a deputy would like another deputy to weigh in on a ticket)
Tag with the city name associated with the event. Try to be consistent. 🙂
City names that are multiple words should be hyphenated, e.g., “New Delhi” should be tagged as new-delhi and “St. Louis” should be tagged as st-louis.
Priority: Urgent: This should only be used for a ticket that requires an immediate response. For example: this payment didn’t show up, we discovered a GPLGPLGPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. issue with a speaker/sponsor after announcing them, our lead organizer is stepping down, our registration page is broken.
Unlike SupportPress, we don’t tag/notify for 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., we assign them. For more information on assigning tickets, see the “Assigning tickets” section.
When you have some background or additional information about a ticket that is not contained in that ticket, use the Notes feature to share your notes or background with the rest of the group.
Open the ticket and click the pencil icon, “Note”.
Type in your note! Good examples of things to put in a note: notes from vetting, an interview, orientation, budget review, links to other related tickets, and/or links to public wordpress.slack.com interactions that are relevant to the ticket.
You can now choose a Status (Active, Pending, or Closed). “Active” status will keep the ticket open. If there is no action required of anyone on a ticket, please remember to close it. The ticket will be reopened when a reply comes in. “Pending” status is currently only recommend when you are going to perform some future action on a ticket, within the next few days.
You can also choose to Assign the ticket at this point. A best practice when closing a ticket is to assign the ticket to “Anyone”, so that if/when a reply comes in, any deputy can respond to it.
If a ticket is in a different language, you can use a service or app like Google Translate to try to get the context of the ticket, and answer the ticket in English, prefacing it with something like:
We usually provide support in English, so I’ve entered your message into Google Translate and received the following:
[PASTE TRANSLATED TEXT HERE]
Note: The above is in Help Scout’s Saved Replies as “Translate Text” if you’d like to use it.
Then underneath the translated text box, answer their query in English.
There are also some Deputies that are fluent in different languages, so you may also want to 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.” in the #community-team channel in Slack to see if they can help, and/or answer the ticket.
It’s good practice to sweep the “Spam” folder for legitimate emails and mark them as active. Some of the most common legitimate emails found in the Spam folder are contact form submissions, 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. applications, or responses to invoices. To move them back to the active mailbox, simply select “Active” from the “Status” (flag) drop-down menu.
Don’t forget to triage tag the email properly once it’s been moved back to the mailbox!
Sometimes we’ll receive Spam messages through the contact or application forms on Make/Community or WordCamp CentralWordCamp CentralWebsite for all WordCamp activities globally. https://central.wordcamp.org includes a list of upcoming and past camp with links to each.. Although the messages are technically Spam, they should not be marked as such in Help Scout, since it trains Help Scout to recognize form submission as Spam (and therefore HS would start flagging more legitimate submissions as Spam).
It’s best to mark these messages as Spam in the “Feedback” section of the Dashboard of Make/Community or WordCamp Central.
If you don’t have your permissions set to do this, assign the ticket to a Super DeputySuper deputySuper Deputies are Deputies who can perform extra tasks on WordCamp.org like creating new sites and publishing WordCamps to the schedule. with a note requesting for them to mark the message as Spam in “Feedback”. Then you can either close or delete the message from Help Scout, without flagging it as Spam.
If all the messages in the Spam folder are truly Spam, you can delete them all permanently by clicking on the little trashTrashTrash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. icon, as seen below. It’s very satisfying to do! 🙂
In an effort to ensure that Help Scout tickets are managed properly, its important to update the status of tickets efficiently. This helps to ensure that tickets are actioned appropriately. Below are some best practices to follow when working with tickets.
Please only assign a ticket to yourself when you are either physically performing some task on the ticket (e.g. application vetting) or you plan to perform some future task within the next few days (e.g. updating a meetup in the meetup list after a meetup orientation).
If you need to perform a follow up task on a ticket, leave it assigned to yourself and mark the status as “Pending”.
Once you have completed whatever you are doing on that ticket, please mark the status as “Closed”. Any future reply on the ticket will re open in.
If a ticket requires some future action that you will not be doing (e.g. a meetup orientation is required after you have vetted the application), assign it back to “Anyone” and mark the status as “Active”.