@@ -54,7 +54,7 @@ reviewing, discussing, implementing, and endorsing SPEC documents.
54
54
SPEC Steering Committee
55
55
: The [ Steering Committee] ( /specs/steering-committee ) leads the SPEC project and
56
56
manages the SPEC process including moderating
57
- the [ SPECs discussion forum] ( https://discuss.scientific-python.org/c/specs/6 ) ,
57
+ the [ SPECs discussion forum] ( https://discuss.scientific-python.org/c/specs/ ) ,
58
58
accepting SPEC documents, and maintaining the SPEC process documents.
59
59
60
60
SPEC Process
@@ -79,10 +79,7 @@ The SPEC documents are converted to HTML by code in the
79
79
[ scientific-python.org repository] ( https://github.com/scientific-python/scientific-python.org/ ) using
80
80
[ Hugo] ( https://gohugo.io/ ) and deployed to
81
81
[ https://scientific-python.org/specs/ ] ( https://scientific-python.org/specs/ ) .
82
- Each SPEC has a corresponding
83
- [ discussion] ( https://discuss.scientific-python.org/c/specs/accepted/15 )
84
- with the same title, where anyone can comment, ask questions, or vote on
85
- existing comments.
82
+ Each SPEC has two corresponding discussions: one under [ SPECS → Ideas] ( https://discuss.scientific-python.org/c/specs/ideas ) , where the SPEC committee discussed its viability, and another under [ SPECS → Web Comments] ( https://discuss.scientific-python.org/c/specs/web-comments ) , where public comments from https://scientific-python.org/specs are stored.
86
83
87
84
## Implementation
88
85
@@ -122,9 +119,10 @@ The decision to **accept** a SPEC is made by the Steering Committee,
122
119
at which point it is added to the main branch of the [ SPEC
123
120
repository] ( https://github.com/scientific-python/specs ) , clearly
124
121
labeled as a draft.
125
- Proposed SPECs are accepted once (a) the draft is written to clearly
126
- explain the area of common concern and a general approach to a shared
127
- solution and (b) there are contributors (from at least two Core
122
+ Proposed SPECs are accepted once (a) there is agreement that the SPEC
123
+ concept is applicable to the ecosystem, (b) a draft pull request is
124
+ written to clearly explain the area of common concern and a general
125
+ approach to a shared solution, and (c) there are contributors (from at least two Core
128
126
Projects) interested in working on the new SPEC and in championing it
129
127
to their projects as well as the larger community.
130
128
Additional details may be found in [ Steering Committee
@@ -248,11 +246,11 @@ the idea** by doing one or more of the following:
248
246
2 . discuss the idea with at least one other member of the ecosystem, or
249
247
3 . create a minimal, proof of concept prototype.
250
248
251
- Before a proposed SPEC can be accepted, the idea must be discussed on
252
- the discussion forum under the [ ` SPECS/Ideas `
253
- topic ] ( https://discuss.scientific-python.org/c/specs/ideas/9 ) .
254
- Thereafter a new SPEC document must be submitted as a pull request to
255
- the [ SPEC repository] ( https://github.com/scientific-python/specs ) .
249
+ Before a proposed SPEC can be accepted:
250
+
251
+ 1 . The idea must be proposed on the discussion forum under the [ ` SPECS/Ideas `
252
+ topic ] ( https://discuss.scientific-python.org/c/specs/ideas/9 ) .
253
+ 2 . A draft SPEC document must be submitted via pull request to the [ SPEC repository] ( https://github.com/scientific-python/specs ) .
256
254
257
255
Use the ` quickstart.py ` script to create the new SPEC document.
258
256
Located at the top-level of the [ SPEC
@@ -262,8 +260,6 @@ appropriately named with a basic template for you to complete (e.g.,
262
260
` spec-0000/index.md ` ).
263
261
Once the SPEC is in reasonable shape, file a pull request against the
264
262
[ SPEC repository] ( https://github.com/scientific-python/specs ) .
265
- The Steering Committee then considers the SPEC as presented in the
266
- pull request and will provide additional guidance.
267
263
268
264
## Notes
269
265
0 commit comments