Browse Source

Remove references to GitHub Projects in README

[ci skip]
Sam Whited 1 year ago
parent
commit
1213692597
1 changed files with 4 additions and 70 deletions
  1. 4
    70
      README.md

+ 4
- 70
README.md View File

@@ -133,10 +133,8 @@ applies.
133 133
     defined in the XEP file itself.)
134 134
 
135 135
     1. Add the [Needs Council]/[Needs Board] label.
136
-    2. Put the PR in the [Council Tracking] project.
137
-    3. (Optionally, continue here with submitting the PR to Council via Trello
138
-        and move it right to the "On the agenda" column.)
139
-    4. Stop.
136
+    2. Put the PR in the [Council Trello] project.
137
+    3. Stop.
140 138
 
141 139
 2. Is the XEP in Experimental state and the PR opener is not an author of the
142 140
    XEP?
@@ -147,73 +145,11 @@ applies.
147 145
         1. Make sure the standards@ discussion (if it exists) is linked in the
148 146
            PR.
149 147
         2. Add the [Needs Author] label.
150
-        3. Put the PR in the [Author Tracking] project in the
151
-           "Not explicitly pinged" bin.
148
+        3. Put the PR in the [Editor Trello] project.
152 149
         4. Stop.
153 150
 
154 151
 3. Mark the PR as [Ready to Merge].
155 152
 
156
-
157
-Council Tracking
158
-----------------
159
-
160
-The [Council Tracking] project is used to track a PR through the Council
161
-approval process. The following columns are used:
162
-
163
-* On agenda: The PR has been added to the council trello and is awaiting
164
-  handling by Council.
165
-* Voting in progress: The PR has been discussed by council, but not everyone
166
-    has voted yet. Aside from exceptional circumstances, a PR can only reside
167
-    for at most two weeks in this column.
168
-
169
-    Note that council voting is veto-based and if someone did not vote, consent
170
-    is assumed. So a PR is rejected *iff* at least one person from council
171
-    explicitly voted against it.
172
-
173
-    When moving a PR into this column, make a comment on the PR which contains
174
-    the following information:
175
-
176
-    - The date at which the voting period started.
177
-    - Link to the respective meeting minutes.
178
-    - The date at which the voting period has ended or will end at latest.
179
-    - Possibly additional notes from the minutes, for example:
180
-
181
-        - "There will be additional discussion on standards@" (bonus points if
182
-            you add a link once the thread starts).
183
-        - "Two people will vote on-list after further consideration."
184
-
185
-* Done: The PR went through voting, but has not been merged yet. The
186
-    [Needs Council] label must be removed.
187
-
188
-    Add a comment with the result of the votes, possibly including links to
189
-    meeting minutes which contained the votes and on-list votes by the
190
-    respective council members.
191
-
192
-    If the PR was not vetoed, the [Ready to merge] label should be added.
193
-    Otherwise, the PR should be closed.
194
-
195
-    In any case, the PR can be removed from [Council Tracking] now.
196
-
197
-If a card awaits triaging, add it to the [Council Trello] in the first column
198
-*under* the "Find Minutes taker". Put the PR in the "On agenda" column (in the
199
-[Council Tracking], not the [Council Trello]).
200
-
201
-
202
-Author Tracking
203
----------------
204
-
205
-This is less formal and more a tool for the editors to keep track of at which
206
-stage of escalation we are when getting in contact with the Authors. The
207
-columns should be self-explaining.
208
-
209
-Use your gut feeling on how long you wait for an authors reaction, but giving
210
-them at least a week on each stage seems reasonable.
211
-
212
-When an author replies and a discussion starts, move the PR to "Discussion in
213
-progress" and remember to check back once in a while if the discussion
214
-resolved.
215
-
216
-
217 153
 Discussions
218 154
 -----------
219 155
 
@@ -339,7 +275,7 @@ New ProtoXEPs
339 275
 - Merge the PR as described in "Merging a PR". Once the email has been sent,
340 276
     continue here.
341 277
 - Create a card for the protoxep on the [Council Trello] under "Proposed
342
-  Agendums" and add the PR to the [Council Tracking].
278
+  Agendums".
343 279
 - Attach the PR to the card and link the generated HTML.
344 280
 - Comment on the PR with a link to the card, thanking the author for their
345 281
     submission and letting them know that their XEP will be voted on within the
@@ -468,8 +404,6 @@ When you get to the point that the PR is [Ready to Merge], do the following:
468 404
 [`is:open is:pr no:assignee`]: https://github.com/xsf/xeps/pulls?utf8=%E2%9C%93&q=is%3Aopen%20is%3Apr%20no%3Aassignee%20
469 405
 [Needs Author]: https://github.com/xsf/xeps/labels/Needs%20Author
470 406
 [Ready to Merge]: https://github.com/xsf/xeps/labels/Ready%20to%20Merge
471
-[Council Tracking]: https://github.com/xsf/xeps/projects/1
472
-[Author Tracking]: https://github.com/xsf/xeps/projects/2
473 407
 [Needs List Discussion]: https://github.com/xsf/xeps/labels/Needs%20List%20Discussion
474 408
 [Editorial Change]: https://github.com/xsf/xeps/labels/Editorial%20Change
475 409
 [xep-attic]: https://github.com/xsf/xep-attic

Loading…
Cancel
Save