You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: community/prioritization_response.md
+17-17
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
## Overview
2
2
3
-
Given that we are a small functional team that is meant to maintain :wrench:, support ::phone::, care for :heart:, and cultivate :sunflower: our amazing Octokit :octocat: and Terraform community we often have to make decisions that are best for the entire community.
3
+
Given that we are a small functional team that is meant to maintain :wrench:, support :phone:, care for :heart:, and cultivate :sunflower: our amazing Octokit :octocat: and Terraform community we often have to make decisions that are best for the entire community.
4
4
We don't take this act of prioritization lightly nor are we haphazard about it. We want to honor the time and thought that everyone has put into all of the SDKs that we have come to know and :heart:.
5
5
6
-
Add that to the number of repos that we need to maintain (70+) and weekly interactions (500-1000 +/-) that we end up having with everyone I am sure it's clear why we have to define how we **prioritize** and our commitment to respond (think of an **SLA** of sorts) to those priorities.
6
+
With the number of repos that we need to maintain (70+) and weekly interactions (500-1000 +/-) that we end up having with everyone, we have to define how we **prioritize** and our commitment to respond (think of an **SLA** of sorts) to those priorities.
7
7
8
8
### What are the Priorities?
9
9
10
-
In each of the repositories we own you'll see the same [labels](https://github.com/octokit/octokit.net/labels) for priority.
10
+
In each of the repositories we own you'll see the same [labels](https://github.com/octokit/octokit.net/labels) for priority.
Incidentally, these map directly to the priorities set in our [Octokit Active community board](https://github.com/orgs/octokit/projects/10/views/4).
15
+
These map directly to the priorities set in our [Octokit Active community board](https://github.com/orgs/octokit/projects/10/views/4).
16
16
17
17
|[Repo label](https://github.com/octokit/octokit.net/labels)|[Community board](https://github.com/orgs/octokit/projects/10/views/4)| Example |
18
18
|----------|:-------------:|:-----------|
@@ -23,34 +23,34 @@ Incidentally, these map directly to the priorities set in our [Octokit Active co
23
23
24
24
### What are our response commitments?
25
25
26
-
Note: This does not represent a commitment to resolution, just how quickly we'll respond and begin working on it
26
+
Note: This does not represent a commitment to resolution, just how quickly we'll acknowledge and respond.
27
27
28
-
| Priority | Response expectation |
28
+
| Priority | Response expectation |
29
29
|----------|:-----------|
30
-
| Urgent | 0 to **24hrs**: A security advisory will be posted if needed and updates publically posted to the corresponding repository |
31
-
| High |=<**1 Week** : Typically, we'll respond in issue/pr and will have a plan of action within the response expectation time window. |
32
-
| Normal | >= **1 Week** : We'll acknowledge and make administrative assignments to the issue or PR. They might get labeled "up-for-grabs". |
33
-
| Low | > **1 Week**: Typically, little to no action will take place on these items. They will often get labeled "up-for-grabs". |
30
+
| Urgent | 0 to **24hrs**: A security advisory will be posted if needed and updates publically posted to the corresponding repository in issue or discussion form. |
31
+
| High |<=**1 Week** : We'll respond in issue/PR and will have a plan of action within the response expectation time window. |
32
+
| Normal | >= **1 Week** : We'll acknowledge and make administrative assignments to the issue or PR. It may be labeled "up-for-grabs", where we encourage community contribution. |
33
+
| Low | > **1 Week**: Typically, little to no action will take place on these items. |
34
34
35
35
36
-
### How do we Prioritize?
36
+
### How do we prioritize?
37
37
38
-
Remembering that we as a team have to prioritize not at the individual SDK or community level but across many repositories and communities our, methods need to consider several variables.
38
+
Remembering that we as a team have to prioritize not at the individual SDK or community level but across many repositories and communities, our methods need to consider several variables.
39
39
Our process, while not exactly scientific, is aimed at protecting the interests of our communities first - we use a modified version of [RICE](https://www.productplan.com/glossary/rice-scoring-model/).
40
40
41
41
Here are some data points, empathetic aspects, and questions we use to help us prioritize.
42
42
43
43
* Does the issue compromise data integrity, user security, or the integrity of GitHub?
44
-
* How serious is the need?
44
+
* How serious is the need?
45
45
* What's the overall impact on the SDK community?
46
-
* What's the overall impact on the package communities
47
-
* What's the overall impact on the language communities
46
+
* What's the overall impact on the package communities?
47
+
* What's the overall impact on the language communities?
48
48
* How active is the SDK community?
49
49
* How many open issues are there?
50
50
* How many open PRs are there?
51
51
* What is the throughput of the given SDK where the issue is?
52
52
* What is the overall usage footprint?
53
-
* What’s the difficulty of the change set/fix?
53
+
* What’s the difficulty of the changeset/fix?
54
54
* How much friction is the issue causing?
55
55
* What's the overall time/effort cost of addressing the issue/need?
@@ -16,16 +16,17 @@ If you're already a contributor we can't thank you enough for being part of maki
16
16
17
17
## Code of conduct
18
18
19
-
Open source projects can be amazing things and while the source code they provide is an important component of the project
20
-
it's definitely not the only thing that makes it amazing... you are!
19
+
Open source projects can be amazing things and while the source code they provide is an important component of the project
20
+
it's definitely not the only thing that makes it amazing... you are!
21
21
22
22
Practice kindnes, be welcoming, and always assume that we all have something to learn. Take a minute to read more about our [code of conduct](CODE_OF_CONDUCT.md).
23
23
24
24
## Contributing
25
25
26
-
While each community in our collection of Octokit communities is unique and have some really great nuances we have standard approaches across all of our repos
27
-
to lower barriors to entry and reduce the friction of getting things done. Make sure to have a look at each of the repositorie's `CONTRIBUTING` docs above when
28
-
making contributions. Oh, and thanks for being amazing and helping to both improve our communities and code! ❤️
26
+
While each community in our collection of Octokit communities is unique and has its own individuality, we have standard approaches across all of our repos
27
+
to lower barriors to entry and reduce the friction of getting things done. Make sure to have a look at each repository's `CONTRIBUTING` docs above when
28
+
making contributions. For more information on how our team prioritizes and responds to issues, PRs, and discussions, please see [this document](../community/prioritization_response.md).
29
+
Oh, and thanks for being amazing and helping to both improve our communities and code! ❤️
29
30
30
-
[^1]:Official just means GitHub and folks from GitHub support and maintain these libraries on an ongoing basis.
31
+
[^1]:Official just means GitHub and folks from GitHub support and maintain these libraries on an ongoing basis.
31
32
You can checkout some of the other amazing SDKs created and maintained by the community [here](https://docs.github.com/en/rest/overview/libraries)!
0 commit comments