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: README.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,13 +19,27 @@ To make a new proposal for a special interest group, please create a new issue i
19
19
20
20
## Curator Documentation
21
21
22
+
### Pipelines
23
+
22
24
The curator workflow is as follows:
23
25
24
26
1. Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
25
27
2. Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/docs/checklists/community_governance/core_team#new-pipeline-proposals-and-onboarding).
26
-
3. Acceptance requires:
28
+
3. Acceptance requires a minimum of OKs from:
27
29
- Two members of the core team.
28
30
- One member of the core team and one member of the maintainers team.
29
31
5. If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
30
32
6. If a proposal is turned down, update both the label AND status to 'turned-down', and when closing select 'Close as not planned'
31
33
7. If a proposal is not completed or abandoned after a year, update both the label AND status to 'timed-out', and when closing select 'Close as not planned'
34
+
35
+
### Special Interest GRoups
36
+
37
+
The curator workflow is as follows:
38
+
39
+
1. Once a issue is made, update the 'Project' status to 'proposed' (right hand side bar, under 'new-<TYPE>-proposals')
40
+
2. Facilitate discussion on the the Issue thread, following the guidance [here](https://nf-co.re/blog/2024/special_interest_groups).
41
+
3. Acceptance requires a minimum of OKs from:
42
+
- Two members of the core team.
43
+
5. If a proposal is accepted, update both the label AND status to 'accepted', and when closing select 'Close as completed'
44
+
6. If a proposal is turned down, update both the label AND status to 'turned-down', and when closing select 'Close as not planned'
45
+
7. If a proposal is not completed or abandoned after a year, update both the label AND status to 'timed-out', and when closing select 'Close as not planned'
0 commit comments