Skip to content
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

[EPIC] Tier 2 swag #168

Closed
amberleyromo opened this issue Nov 5, 2018 · 1 comment · Fixed by #219
Closed

[EPIC] Tier 2 swag #168

amberleyromo opened this issue Nov 5, 2018 · 1 comment · Fixed by #219
Assignees
Labels

Comments

@amberleyromo
Copy link

amberleyromo commented Nov 5, 2018

NOTE: This issue is an epic, which bundles up lots of related issues into a single goal. If you have the free ZenHub extension, you’ll be able to see overall progress and related issues, as well as a "board view" that shows this epic from a bird's-eye view.

Who will own this?

Area of Responsibility: Ecosystem

Role Name RACI
AoR owner @amberleyromo Consulted about the epic
Domain owner @amberleyromo Informed about epic
Project manager Responsible for setting epic tasks
Tech lead @amberleyromo Accountable for setting guidelines for epic
Contributors @amberleyromo @jlengstorf Responsible for completing assigned tasks

Summary

Update the Gatsby store to accommodate a second tier of contributor swag, for contributors with 5+ PRs to gatsby

How will this impact Gatsby?

Domains

  • Gatsby store

Goals

  1. Incentivize and reward active contribution to Gatsby above and beyond a first-time contribution by recognizing a higher degree of participation with an additional level of reward
  2. Communicate the level to which we value contribution by adding another level of reward

How will we know this epic is a success?

We will know this epic is a success when contributors of 5+ PRs are able to redeem tier 2 swag via the Gatsby store.

@amberleyromo
Copy link
Author

Major work on this epic was completed in PR #201, merged to the next feature branch.

Ongoing work to close out this epic will be PR'd against the next branch, and ultimately merged into master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant