To help our core contributors plan their work better, we’re changing how we plan Core Contributor work in Jira. I have already updated the handbook to reflect these changes.
The old process involved the “Core Contributor” field in Jira and/or recurring tickets in the sprint.
The new process: For any Core Contributor work (e.g. answering a question on the community forum, reviewing a team member’s upstream PR, reviewing a community PR, improving the devstack, helping with the Maple release, etc.), create a dedicated Jira ticket.
For each ticket:
- The epic for the ticket should always be MNG-2649 Core Contributors
- The account should be the client’s account (for team member upstream PRs), the accelerated epic’s account (if it’s an accelerated epic), or “Contributions” (for anything else).
For upstream PR reviews, the goal is still to review them in the same sprint as the work is done. There will just be a separate ticket to track the Core Contributor review.
Core Contributors: please start using this process next sprint. And in particular, please create tickets to plan 10 hours of work for Sprint 262 now, during Sprint 261.
- Q: Does this mean that we won’t use the “Core Contributor 1” field(s) in Jira anymore?
- Right, we don’t need those anymore.
- Q: For an upstream PR review, who creates the ticket - the Core Contributor or the original author?
- It’s probably easier if the Core Contributor creates their own tickets. Ping them in a comment on the original ticket to ask if they can review, and if they are available they can create their own ticket for it, which will be linked to the original ticket.
- Q: Won’t it be a hassle? Creating tickets in Jira is a bit of a pain compared to just setting the “Core Contributor” field
- That’s why I created a bookmarklet so that as a Core Contributor, you can create a review ticket in just one click
Ticket for this post: MNG-2500