Adding table lead guide documentation #2708
Conversation
fellyph
added
the
[Type] Documentation
There was a problem hiding this comment.
Nice! I had a number of remarks trying to make it more hands-on and with clearer instructions. One other thing that I'd like to encourage to change is to set the expectation for contributors earlier, i.e. during the day. While they are there, they can agree for the PR to be taken over if they don't have time to finish it. Afterwards you might not be able to reach them
packages/docs/site/docs/main/contributing/contributor-day-table-lead.md
Outdated
Show resolved
Hide resolved
packages/docs/site/docs/main/contributing/contributor-day-table-lead.md
Outdated
Show resolved
Hide resolved
|
|
||
| ### Pre-Work Checklist | ||
|
|
||
| - **Curate "Good First Issues"**: Review and update the [good first issues list](https://github.com/WordPress/wordpress-playground/labels/good%20first%20issue) on GitHub. These should be straightforward tasks that new contributors can complete independently. |
There was a problem hiding this comment.
It could be helpful to suggest how they would curate the list. It says "update the list" but do they have the permission to change labels? I could see us suggesting to create a spreadsheet that they could share with contributors
| ### Pre-Work Checklist | ||
|
|
||
| - **Curate "Good First Issues"**: Review and update the [good first issues list](https://github.com/WordPress/wordpress-playground/labels/good%20first%20issue) on GitHub. These should be straightforward tasks that new contributors can complete independently. | ||
| - **Coordinate with the Team**: Confirm if team members are available online to provide remote support during the event, especially for flagship WordCamps. |
There was a problem hiding this comment.
Let's be more precise who we mean with "Team"
|
|
||
| - **Curate "Good First Issues"**: Review and update the [good first issues list](https://github.com/WordPress/wordpress-playground/labels/good%20first%20issue) on GitHub. These should be straightforward tasks that new contributors can complete independently. | ||
| - **Coordinate with the Team**: Confirm if team members are available online to provide remote support during the event, especially for flagship WordCamps. | ||
| - **Connect with Local Contributors**: Identify regular contributors in the region attending the event. This is an opportunity to gather feedback and strengthen community connections. |
There was a problem hiding this comment.
Is this advice to contact them before or to recognize them when they are there?
packages/docs/site/docs/main/contributing/contributor-day-table-lead.md
Outdated
Show resolved
Hide resolved
| - [WordPress Playground Web Instance](https://playground.wordpress.net/) | ||
| - [Playground Documentation](https://wordpress.github.io/wordpress-playground/) | ||
| - [Playground Step Library](https://akirk.github.io/playground-step-library/) | ||
| - [GitHub Repository](https://github.com/WordPress/wordpress-playground) |
There was a problem hiding this comment.
We should also link https://wordpress.github.io/wordpress-playground/contributing/contributor-day
| - [Playground Step Library](https://akirk.github.io/playground-step-library/) | ||
| - [GitHub Repository](https://github.com/WordPress/wordpress-playground) | ||
|
|
||
| 5. **Introduce the GitHub Repository**: Provide a brief walkthrough of the repository structure, highlighting different packages and their purposes for first-time contributors. |
There was a problem hiding this comment.
In this section I miss that the lead should discuss the potential issues to work on with the contributors.
They should also be able to give context, so it's not the first time they read the issue. If they don't know enoug about it, they should rather have not added it to the list. I wonder if we should add this guidance already to the section above.
|
|
||
| ### Managing Contributions | ||
|
|
||
| **Encourage Different Contribution Types**: |
There was a problem hiding this comment.
This should go in the previous section, no?
During the day I would suggest them to visit each contributor regularly, ask them if they need help, help connect them with docs and the playground team (maybe on Slack), and help them find a new issue if the one they picked didn't work out.
packages/docs/site/docs/main/contributing/contributor-day-table-lead.md
Outdated
Show resolved
Hide resolved
…e-lead.md Co-authored-by: Alex Kirk <[email protected]>
…e-lead.md Co-authored-by: Alex Kirk <[email protected]>
…e-lead.md Co-authored-by: Alex Kirk <[email protected]>
…e-lead.md Co-authored-by: Alex Kirk <[email protected]>
2 participants
Motivation for the change, related issues
This pull request adds a new documentation page that serves as a guide for table leads at WordCamp Contributor Day events, specifically focusing on managing a WordPress Playground contributor table. The guide covers preparation, onboarding, contribution management, and post-event follow-up.