Page Comparison

...

The current proposed definition for Core Contributors work is "any scope of work described by an open ticket or pull request on the Open edX github organization, or is listed below in Core contributor work that doesn’t require a ticket.".

Reasoning

The intent of this approach is to maximize the proportion of cases where the default situation doesn’t require any work/overhead to get a decision. When 100% of contributors think something is core contributor work, we don't need to discuss it. That should likely be the most frequent case with the tickets and pull requests created on the Open edX github organization - most of them would be an obvious match for core contributor work. 

...

When an Open edX ticket or pull request describes scope which a core contributor or their organization doesn’t think should be counted as core contributor time, they can tag these tickets – a bit like Wikipedia page creation & flagging. 

Searching existing tickets

• Search all issues/PRs

• Search only issues, excluding PRs

• To list your issues, you can add assignee:[your-github-username] to the previous searches queries

• To get a list of issues to mention in your end of sprint update in Listaflow, you can add updated:>2023-01-09 to the previous query, and it will give you the list of your issues/PRs that have been updated during the sprint.

Creating a ticket

• Go to one of the openedx org’s repositories, then

• => “Issues” tab (top left)

• => “New issue” green button (top right)

• => “Blank issue” → “Get started” green button

Core contributor work that doesn’t require a ticket

...