Triage Novice issues and tasks

Before you start

1. Log in to Drupal.org.
2. Find out from the event organizers what the projects and priorities for the contribution event are (for example, particular Drupal Strategic initiatives, Drupal core, the User Guide, particular contributed modules, etc.).
3. Locate the issue queue for the project.

For each potential novice issue

1. Locate an issue that might include tasks that would be appropriate for new contributors.
   • Category to search for: Start with Task issues. Then continue with Bug report issues.
   • Tags that could be useful to search for: Start with issues that are already tagged Novice, and see if they still should be and have proper task documentation (see below). Then search for new issues to add the Novice tag to, which could have one of these tags: Needs change record, Needs documentation, Needs issue summary update, Needs manual testing, Needs reroll, Needs screenshots.
2. Verify that the issue has at least one task that would be appropriate for new contributors. See the "What makes a good novice task" in Setting up for new contributors for guidance.
    
3. If the issue has no good novice tasks in it and it was previously tagged as Novice, remove the Novice tag and add a comment like this:
   

   I am removing the Novice tag from this issue because [why]
   
   I’m using this documentation as a source: https://www.drupal.org/community/contributor-guide/task/triage-novice-issues-and-tasks 
   
   

   Start over to continue searching.

4. If the issue has good novice tags in it, add the "Novice" tag to the issue, and any other special "Needs..." tags as appropriate. Also review the existing "Needs..." tags and remove any that no longer apply. If the contribution event has its own issue tag, add that as well.

5. Add the "Remaining tasks" section to the issue summary.
    
6. Indicate if a remaining task is novice by putting "(Novice)" at the beginning of the list item, and link any available contributor task documentation.
    
7. If the issue summary is unclear and a novice might be able to update it, tag the issue "Needs issue summary update". Otherwise, update the issue summary yourself.
    
8. Add a comment like this to the issue, and save the issue.
   

   I performed Novice Triage on this issue. I am leaving the Novice tag on this issue because [why]
   
   

9. If this issue is for a specific event, add the event tag, and add this snippet as part of the comment:
   

   <table class="views-view-grid" width="100%" bgcolor="#d4efcc">
   <tbody>
   <tr>
   <td width="48"><img src="/files/webform-hello-32x32.png" width="32" height="32" alt=""></td>
   <td>
   
   The Drupal Contribution Mentoring team is triaging issues for EVENT NAME, and we are reserving this issue for Mentored Contribution during the event.
   
   After EVENT DATE + 1 DAY (UTC), this issue returns to being open to all. Thanks!
   
   </td>
   </tr>
   </tbody>
   </table>

10. Return to searching, if you have time, to find more novice tasks.

Summary Mermaid Graph of the above process, courtesy of ChatGPT:

graph TD
    B["Identify event priorities"]
    C["Locate and search the issue queue"]
    D["Evaluate if issue has suitable tasks for new contributors"]
    E["If no novice tasks, remove 'Novice' tag and return to search"]
    F["If suitable, add/update 'Novice' and 'Needs...' tags, then detail tasks"]
    G["Finalize issue with comments and event-specific tags"]
    H["Return to search if time allows or end process"]
    
    B --> C
    C --> D
    D -->|No suitable novice tasks| E
    E --> C
    D -->|Suitable novice tasks| F
    F --> G
    G --> H