Skip to content

Latest commit

 

History

History
84 lines (48 loc) · 3.96 KB

CONTRIBUTING.md

File metadata and controls

84 lines (48 loc) · 3.96 KB
Raw

Contributing

Start at GitHub - WordPress/Community-Team

Event Issue Creator - Bookmarklet

Install the bookmarklet here:

https://wordpress.github.io/Community-Team/

Installation:

Drag the issue creator button to your bookmarks bar to install.

Usage

  1. Open the event tracker to a specific event needing vetting.
  2. Click on the issue creator button link in your bookmarks bar and confirm.
  3. A new tab open with the new issue already on GitHub and the right name and labels already added, you just have to leave it unassigned or assign it to yourself if you are going to vet it, and then you click on the green button (Submit new issue) at the bottom.

Github Event Issue Creator | Bookmarklet

Create new Event Tracking issue

Requirements

If you do not have access to any one of these, you will not be able to vet applications. Please ask someone for access #community-team

Creating an issue

Click on the New Issue button

step-1

step-2

Select Event Application Vetting - 'Get started'

step-3

Click on the button Submit new issue

  • In the Title field, add: event type (Meetup, for example), city/event name, and link to the tracker
  • Add the labels for event type (meetups or WordCamp)

step-4

Click on the button Todo / Ready

  • There is no need at this stage to assign the issue to someone, team leads will do it later
  • Neither is it necessary to select the project, it will be automatically assigned to the Community Team 2024 Project Board
  • If everything looks good, scroll the page and click on "Submit New Issue".

step-5

Issue assignment

Once the issue is created, you can assign it to yourself or to a teammate

step-6

You can comment /claim to self-assign an issue.

You can also assign to teammates in the dropdown

Make sure to set the status as Todo/Ready

Application Review Process on GitHub

Once you’ve received the issue assigned to yourself, you’ll use GitHub just to track the progress, but the whole process will be carried out using the event tracker and HelpScout as usual. Please never share your vetting notes on GitHub, only in the event tracker as we always do.

  • Update the status to In Progress
  • If you need a second opinion or help from teammates, while you wait for their feedback please update the status to In Review
  • If you need, you can leave a comment on the issue:

Once you’ve completed the entire application review process: tracker updated and email sent to organizer for inviting to orientation or reject the application, please update the status to Complete, scroll the page until the bottom, and close the issue.