-
Notifications
You must be signed in to change notification settings - Fork 349
[Docs] Adding table lead guide documentation #2708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
48b6686
Adding table lead guide
fellyph fcf1549
Update packages/docs/site/docs/main/contributing/contributor-day-tabl…
fellyph 6166acd
Update packages/docs/site/docs/main/contributing/contributor-day-tabl…
fellyph a82de70
Update packages/docs/site/docs/main/contributing/contributor-day-tabl…
fellyph 03bde14
Update packages/docs/site/docs/main/contributing/contributor-day-tabl…
fellyph d4dc72f
adding changes pointed out at the review
fellyph e1e5196
add punctuation on the list and fixing feedback instruction
fellyph 165c4fe
Update packages/docs/site/docs/main/contributing/contributor-day-tabl…
fellyph File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
74 changes: 74 additions & 0 deletions
74
packages/docs/site/docs/main/contributing/contributor-day-table-lead.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,74 @@ | ||||||
--- | ||||||
slug: /contributing/table-lead-guide | ||||||
title: Table Lead Guide for Contributor Day | ||||||
description: A concise guide for leading a WordPress Playground table at WordCamp Contributor Day. | ||||||
--- | ||||||
|
||||||
# Table Lead Guide for Contributor Day | ||||||
|
||||||
This guide helps table leads prepare for and manage a WordPress Playground contributor table at WordCamp events. | ||||||
|
||||||
## Before Contributor Day | ||||||
|
||||||
### 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. | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
- **Coordinate with the Team**: Confirm if team members are available online to provide remote support during the event, especially for flagship WordCamps. | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
- **Connect with Local Contributors**: Identify regular contributors in the region attending the event. This is an opportunity to gather feedback and strengthen community connections. | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
||||||
## Starting the Day | ||||||
|
||||||
### Setup and Onboarding | ||||||
|
||||||
1. **Create Your Agenda**: Prepare a flexible checklist of key activities while allowing for organic collaboration. Share it in the project documentation if helpful. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would appreciate an example here. |
||||||
|
||||||
2. **Guide Contributors to Slack**: Direct everyone to the `#playground` channel on WordPress Slack. This centralizes communication and enables asynchronous collaboration with late arrivals. | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
||||||
3. **Post a Welcome Message**: Share an initial message in the Slack channel announcing your presence (in-person or online) and welcoming contributions from everyone. | ||||||
|
||||||
4. **Share Essential Links**: Post these resources in the `#playground` channel: | ||||||
|
||||||
- [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) | ||||||
fellyph marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
5. **Introduce the GitHub Repository**: Provide a brief walkthrough of the repository structure, highlighting different packages and their purposes for first-time contributors. | ||||||
fellyph marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
## During the Day | ||||||
|
||||||
### Managing Contributions | ||||||
|
||||||
**Encourage Different Contribution Types**: | ||||||
fellyph marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
- Documentation improvements and translations | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
- Carefully crafted issues describing problems with actionable solutions | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
- Blueprint creation and plugin demos | ||||||
- Testing and product feedback | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
||||||
**Foster Collaboration**: Look for cross-table opportunities. For example, contributors at the Translation(#polyglots) table might translate Playground documentation, or the #test-core team could provide valuable Playground feedback. | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
||||||
**Collect Feedback**: Ask contributors about their experience and note improvement suggestions. Document this feedback in a P2 post when possible. | ||||||
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
||||||
## After the Event | ||||||
|
||||||
### Follow-Up and Support | ||||||
|
||||||
1. **Review Pull Requests**: List PRs created during the day and assess their completion likelihood. Most contributions have a short momentum window—engagement within the first two weeks is critical. | ||||||
|
||||||
2. **Set Clear Expectations**: For incomplete PRs, follow this approach: | ||||||
|
||||||
- After one month of inactivity, leave a comment asking if the author plans to complete the work | ||||||
|
- After one month of inactivity, leave a comment asking if the author plans to complete the work | |
- After one month of inactivity, leave a comment asking if the author plans to complete the work. |
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
fellyph marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.