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

Quick refresh of the Repository Management doc #13495

Merged
merged 3 commits into from Jan 29, 2019

Conversation

Projects
None yet
3 participants
@designsimply
Copy link
Contributor

designsimply commented Jan 24, 2019

This PR seeks to update the Repository Management documentation to reflect recent practices including the following:

  • Reorganize the labels section.
  • General updates to the triage section.
  • Add a note about how to handle help requests.
  • Update common examples of labels, milestones, and projects.
  • Change 'backlog' to 'list'.

Checklist:

  • My code is tested.
  • My code follows the WordPress code style.
  • My code follows the accessibility standards.
Quick refresh of the Repository Management doc
This PR seeks to update the Repository Management documentation to reflect recent practices including the following:

- Reorganize the labels section.
- General updates to the triage section.
- Add a note about how to handle help requests.
- Update common examples of labels, milestones, and projects.
- Change 'backlog' to 'list'.
@youknowriad

This comment has been minimized.

Copy link
Contributor

youknowriad commented Jan 25, 2019

Thanks, this is great 👍

@youknowriad

This comment has been minimized.

Copy link
Contributor

youknowriad commented Jan 25, 2019

Should we mention "Good First Issue" and "Good First Review" labels somewhere?

@gziolo

This comment has been minimized.

Copy link
Member

gziolo commented Jan 25, 2019

Yes, please include Good First Review 👍

Quick refresh of the Repository Management doc
Updating based on feedback received: 

- Be less specific about the version numbers in example milestones.
- Add more guidelines about the Needs More Info label.
- Mention "Good First Issue" and "Good First Review" labels.

@designsimply designsimply requested a review from gziolo Jan 28, 2019

@@ -69,6 +71,8 @@ When reviewing issues, here are some steps you can perform:
- If the issue is missing labels, add some to better categorize it (requires proper permissions).
- If the title doesn’t communicate the issue, edit it for clarity (requires proper permissions).
- If it’s a bug report, test to confirm the report or add the `Needs Testing` label. If there is not enough information to confirm the report, add the `[Status] Needs More Info` label and ask for the details needed.
- Remove the `[Status] Needs More Info` if the author of the issue has responded with enough details.
- Close the issue with a note if it has a `[Status] Needs More Info` label but the author didn't respond in 2+ weeks.

This comment has been minimized.

@gziolo
@gziolo

This comment has been minimized.

Copy link
Member

gziolo commented Jan 29, 2019

Added small tweaks to version X.X -> X.Y in c583347.

@gziolo

gziolo approved these changes Jan 29, 2019

Copy link
Member

gziolo left a comment

Looks good speaking myself. I would defer the final 👍 based on opinions from @youknowriad, @mapk and @desrosj.

@gziolo gziolo added this to the Documentation & Handbook milestone Jan 29, 2019

@youknowriad
Copy link
Contributor

youknowriad left a comment

Let's get this in and iterate.

@gziolo gziolo merged commit dc68e4b into master Jan 29, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@gziolo gziolo deleted the update/quick-refresh-repository-management-doc branch Jan 29, 2019

@gziolo

This comment has been minimized.

Copy link
Member

gziolo commented Jan 29, 2019

I merged this one. I would love still to see feedback on this one. We can always open a follow-up PR :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment