Skip to content

Commit

Permalink
fix typos
Browse files Browse the repository at this point in the history
  • Loading branch information
ivanov committed Jul 19, 2023
1 parent cb6e1cf commit 7e7a321
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions jep-process-v2/jep-process-v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ With that in mind, the JEP process operates under the following tenets:

- GitHub issue and PR templates, for example, across the entire Jupyter project, should have references to the JEP process as a possible outcome of a given PR.

- **There is one JEP repository, all Jupyter-governed projects must use it.** To faciliate the easiest possible adoption and high visibility of ideas, a single JEP repository will be used. Even if a JEP only applies to a single organization.
- **There is one JEP repository, all Jupyter-governed projects must use it.** To facilitate the easiest possible adoption and high visibility of ideas, a single JEP repository will be used. Even if a JEP only applies to a single organization.

- The JEP process **has multiple valid use cases**. Each use case might have a slightly different expected workflow or base JEP template. Some expected use cases include:

Expand All @@ -70,12 +70,12 @@ In order to transition out of the pre-proposal stage, the following checklist mu
1. A github issue on the Jupyter Enhancement Proposals repo is created that
2. 1. Briefly outlines the proposal

2. Suggests reviewiers (optional) in addition to the SSC members.
2. Suggests reviewers (optional) in addition to the SSC members.

3. Why it should be a JEP

4. 1. See the “JEP / Not-a-JEP Rubric” below.
3. A *Shepherd* is identified to see the process through. Shepherds are assigned from a set of people actively involved in the project (Sotfware subprojects, SSC or EC, Standing committees and Working groups), based on the scope of the JEP. The Shepherd can be the author of the JEP. If the author of the JEP cannot
3. A *Shepherd* is identified to see the process through. Shepherds are assigned from a set of people actively involved in the project (Software subprojects, SSC or EC, Standing committees and Working groups), based on the scope of the JEP. The Shepherd can be the author of the JEP. If the author of the JEP cannot
identify a Shepherd, the SSC is responsible for designating one.
4. A number is assigned to the JEP to track it through the rest of the process.

Expand All @@ -88,7 +88,7 @@ The Shepherd decides if the JEP criteria have been met.

### Phase 2: RFC for the JEP

Submission: The author submits an initial draft of the JEP as a PR to the JEP repository starting from the relevant template decided in the pre-proposal stage. The number assigned to the PR by Github is the JEP number. The Shepherd optionally assigns reviewers in addition to the SSC. Reviewers and the SSC are refered as the Review Team in the following.
Submission: The author submits an initial draft of the JEP as a PR to the JEP repository starting from the relevant template decided in the pre-proposal stage. The number assigned to the PR by Github is the JEP number. The Shepherd optionally assigns reviewers in addition to the SSC. Reviewers and the SSC are referred as the Review Team in the following.

Request For Comment (RFC) phase: The proposal is iterated on with feedback from the Review Team and the community at large. The Shepherd helps engage the Review Team. When the proposal matures, if there are no major objections, the Shepherd calls to a vote from the SSC members.

Expand Down

0 comments on commit 7e7a321

Please sign in to comment.