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 Microsoft's use of 30 day warranty pattern #399

Merged
merged 1 commit into from
Mar 1, 2022

Conversation

arnom-ms
Copy link
Contributor

@arnom-ms arnom-ms commented Mar 1, 2022

Add Microsof's use of the 30 day warranty pattern

@arnom-ms arnom-ms changed the title Main Add Microsoft's use of 30 day warranty pattern Mar 1, 2022
@robtuley robtuley merged commit ff255f7 into InnerSourceCommons:main Mar 1, 2022
@robtuley
Copy link
Collaborator

robtuley commented Mar 1, 2022

Thanks @arnom-ms great to add to the known instances of this pattern -- your update is now live at https://patterns.innersourcecommons.org/p/30-day-warranty#known-instances

Not sure if you saw Sebastian's comment in a recent similar PR, same applies...

Is there anything extra that you want to share about how this pattern is applied at Microsoft? e.g.
what warranty durations do teams typically ask for?
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 :)

@spier
Copy link
Member

spier commented Mar 2, 2022

Thank you @arnom-ms for the contribution.
And great job @robtuley for handling this PR so quickly.

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.

None yet

3 participants