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: process/sandbox-annual-review.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,19 @@
2
2
3
3
Sandbox projects are subject to an annual review by the TOC. This is intended to be a lightweight process to ensure that projects are on track, and getting the support they need.
4
4
5
+
To keep it lightweight, it is a single phase process - the review doesn't first pass through SIGs and then the TOC. The review document is shared with the community and SIG members can comment on each review, as can any other TOC contributor. The intention is to quickly reach a position where TOC members agree to continue sponsorship.
6
+
5
7
## How to file your annual review
6
8
7
9
CNCF staff will notify the project maintainers when the project review is due.
8
10
9
11
Project maintainers are responsible for agreeing between them who will complete the annual review. One of the maintainers should create the review in GitHub under [cncf/toc/reviews](https://github.com/cncf/toc/tree/master/reviews).
10
12
11
-
* Raise a PR titled *[Project name] Annual Review*
12
-
* The PR should include a file called `annual-<project name>-<year>.md` (for example, `annual-amazingproj-2019.md`) with the contents described below
13
+
* Raise a PR titled *[Project name][year]Annual Review*
14
+
* The PR should include a file called `<year>-<project name>-annual.md` (for example, `2019-amazingproj-annual.md`) with the contents described below
13
15
* Send an email to the TOC mailing list so that the community knows the PR is there and can comment on it
14
16
15
-
If your annual review isn’t complete within two months of notification, we will take this as a sign that the project is not under active maintenance and the TOC is likely to decide to archive the project.
17
+
If your annual review isn’t submitted within two months of notification, we will take this as a sign that the project is not under active maintenance and the TOC is likely to decide to archive the project.
16
18
17
19
## Review outcomes
18
20
@@ -32,7 +34,7 @@ Your annual review should answer the following questions:
32
34
* Include a link to your project’s devstats page. We will be looking for signs of consistent or increasing contribution activity. Please feel free to add commentary to add colour to the numbers and graphs we will see on devstats.
33
35
* How many maintainers do you have, and which organisations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.)
34
36
* What do you know about adoption, and how has this changed since your last review / since you joined Sandbox? If you can list companies that are end users of your project, please do so. (Feel free to link to an existing ADOPTERS file if appropriate.)
35
-
* How has the project performed against its goals since the last review?
37
+
* How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)
36
38
* What are the current goals of the project? For example, are you working on major new features? Or are you concentrating on adoption or documentation?
37
39
* How can the CNCF help you achieve your upcoming goals?
38
40
* Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
0 commit comments