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

Add GitHub to known instances #397

Merged
merged 1 commit into from
Mar 1, 2022
Merged

Add GitHub to known instances #397

merged 1 commit into from
Mar 1, 2022

Conversation

zkoppert
Copy link
Member

@zkoppert zkoppert commented Mar 1, 2022

No description provided.

Copy link
Member

@spier spier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding a new Known Instance!

@spier spier merged commit 4127fd7 into InnerSourceCommons:main Mar 1, 2022
@spier
Copy link
Member

spier commented Mar 1, 2022

@zkoppert this is already merged and live at https://patterns.innersourcecommons.org/p/30-day-warranty.
Thank you! 🚀

Is there anything extra that you want to share about how this pattern is applied at GitHub? e.g.

  • why the 6 week?
  • how do people talk about it internally? do they say "warranty" or does it go by a different name?
  • are there any activities that the teams do at the point when the warranty runs out? (i.e. when the 6 weeks are over)
  • where do you communicate the "rules" of the warranty? is it in the Contribution Guidelines or elsewhere?
  • anything else about those rules that isn't covered in this pattern already?

If any of these are triggering some thoughts that you find are relevant to share, please do.
We would happily review another PR :)

@zkoppert zkoppert deleted the patch-1 branch March 1, 2022 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants