Skip to content

Commit 6a2132b

Browse files
committed
adding section on distribution
1 parent c5a2345 commit 6a2132b

File tree

1 file changed

+19
-7
lines changed

1 file changed

+19
-7
lines changed

29-jep-process/README.md

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Several sub-goals exist for this process:
4040

4141
With that in mind, the JEP process operates under the following tenets:
4242

43-
- **The JEP process is intended for proposed changes of non-trivial scope. “**Non-trivial” is addressed below in the “JEP / Not-a-JEP Rubric” of this document. If proposals that go through the JEP process do not receive the benefits listed above, the JEP process should be amended to better scope what applied.
43+
- **The JEP process is intended for proposed changes of non-trivial scope.** “Non-trivial” is addressed below in the “JEP / Not-a-JEP Rubric” of this document. If proposals that go through the JEP process do not receive the benefits listed above, the JEP process should be amended to better scope what applied.
4444

4545
- **The JEP process naturally complements the PR process, but does not replace it.** A thoroughly-reviewed and approved JEP is a valuable reference during a PR to reduce friction, reduce time-consuming context sharing, and encapsulate decisions and other discussions. Moving a premature PR into a JEP should be a lightweight process that doesn’t cause friction for the contributor.
4646

@@ -70,18 +70,18 @@ In order to transition out of the pre-proposal stage, the following checklist mu
7070

7171
2. Suggested review team (optional)
7272

73-
3. Why it should be a JEP
73+
3. Why it should be a JEP
7474

7575
4. 1. See the “JEP / Not-a-JEP Rubric” below.
7676
3. A *Shepherd* is identified to see the process through. (Shepherds are assigned on a round-robin basis from a set of interested engaged volunteers).
7777
4. A number is assigned to the JEP to track it through the rest of the process.
7878

79-
Outcome:
79+
Outcome:
8080

8181
The Shepard decides if the JEP criteria have been met.
8282

83-
- *It's a JEP! Please create a new PR with the JEP contents using template X. On that basis, you can resolve this issue unless you have further questions.*
84-
- It’s not a JEP. (Provide reasons and close the issue.)
83+
- *It's a JEP!* Please create a new PR with the JEP contents using template X. On that basis, you can resolve this issue unless you have further questions.*
84+
- *It’s not a JEP*. (Provide reasons and close the issue.)
8585

8686
### Phase 2: RFC for the JEP
8787

@@ -125,7 +125,19 @@ This section contains a list of principles and scenarios that can be used to hel
125125
- - Sandboxed cell outputs
126126
- The proposal involve creating a new repository or subproject?
127127

128-
### Glossary
128+
## Distribution
129+
130+
This section describes how information about the JEP process (e.g., new JEPs, updates to
131+
current JEPs, etc) is communicated to the community.
132+
133+
### The JEP public archive website
134+
135+
A list of all current JEPs and the content present in the pull request exists at
136+
the JEP text, all relevant metadata about the JEP, and links to PRs and issues
137+
for the JEP. When a JEP enters into a final state (e.g., "Completed",
138+
"Withdrawn", "Rejected"), it is added to this website.
139+
140+
## Glossary
129141

130142
- Jupyter Enhancement Proposal (JEP): A written document that describes a proposed unit of significant work on Jupyter.
131143

@@ -139,7 +151,7 @@ This section contains a list of principles and scenarios that can be used to hel
139151

140152
- JEP Status:
141153

142-
- - Inactive
154+
- Inactive
143155
- Submitted
144156
- Assigned
145157
- Rejected

0 commit comments

Comments
 (0)