OSS Dashboard Spec

[marisamorby]

Problem

With the amount of PRs we have coming in each day, OSS core team doesn’t have time to go through everything effectively. That means that it takes a long time for issues to get addressed and PRs closed.

Solution

Create a process that shows contributors how to create, direct, and close issues. This will help empower contributors and free up some time for the OSS team.

Goals

• Contributors don't need to install ZenHub to manage issues for the repo.
• Contributors need to be able to quickly open filtered views of different issue buckets. For example, first-time contributors should be able to see a link to all issues labeled with good first issue.
• MVP is a page in the docs with links to various GitHub filtered views.
• Someone with no familiarity with the repo or Gatsby in general could follow our checklist/flow chart to put new issues into the right channels.

Metrics

Decrease time to initial response

• 75th percentile: ~24 hours
• 90th percentile: ~72 hours

What we have

• Diagrams to show how issues should be automated
  • Stale issues
  • Bugs
  • How to handle PR reviews
• Labeling system for OSS issues
• Bot for Stale PRs and Bug Validation

What we need

Checklist to follow for putting a new issue in the right channel

• How to get this done?
  • Identify the following:
    • What are the categories that issues can go in?
    • Where are issues going now?
    • Talk with OSS team to do checklist for each category
      - blocked until we have new OSS team member

Additional documentation that clearly explains where to find all of the OSS Process Resources, how to use them, and where to go for help.

• How to get this done?
  • Create the OSS checklist that lists the step by step process of an issue from creation to close
  • Review which of these docs already exist
  • Create docs that detail how to use the checklist
    - onboarding doc
    - merging your first PR
  • Review docs with OSS team and make updates

A path to the documentation

• How to get this done?
  • create a separate page: gatsbyjs.org/how-to-contribute
    • work with Amberley on this
  • Include path to documentation in onboarding materials for contributors
    • gatsbyjs.org/how-to-contribute
    • update README on gatsbyjs/gatsby repo

Core maintainers need a process to identify and label/update issues correctly for community discovery (in maintainer meetings).

• How to get this done?
  • Set up interviews with core maintainers to understand how they label things now
    - blocked until we have additional OSS help
  • Document that process and share it with team members
  • Standardize the process and make updates as necessary

[marisamorby]

@jlengstorf

Here is the OSS Dashboard Spec that is a work in progress: https://docs.google.com/document/d/1DrH5I0dR6K9p3Mt3aigH5y2En7vikqHD0-P5u95hLH0/edit#

[jlengstorf]

Related ideas here: #4295

I'm going to close that one, but didn't want to lose the discussion.

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

[gatsbot]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

Thanks again for being part of the Gatsby community!