Skip to content

Commit 3850f38

Browse files
authored
Consistent phrasing for the priority (#18)
1 parent b33aaba commit 3850f38

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/funding/priorities.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ _These are likely not exhaustive, but are included to help us understand the kin
4343
3. **Increase the frequency and transparency of minor releases.** “Release early, release often”, with an emphasis on minor releases providing bug fixes, security patches, non-disruptive performance improvements, and similarly non-disruptive new features. Ensure that releases always make it clear what has changed and what it means for a user. Minor releases with these characteristics are easier for Jupyter users and operators to deploy. This pattern also keeps the contributors familiar with the release process.
4444
4. **Increase the speed of security fixes.** Security vulnerabilities are a strong concern for organizations that deploy Jupyter technology as part of shared services. Improvements to Jupyter’s overall software quality should result in faster, more efficient processes for identifying, resolving, and releasing security errors.
4545

46-
### Examples of how to grow software quality
46+
### Examples of how to improve Jupyter software reliability, security, and consistency
4747

4848
- Hold events that allow subprojects to meet and co-work to solve their most pressing problems.
4949
- Fund contributor time to focus on security, testing coverage, etc.
@@ -71,4 +71,4 @@ _These are likely not exhaustive, but are included to help us understand the kin
7171
- Create feedback loops between the Jupyter community, the Jupyter Executive Council, Member Organizations, and the Foundation (both synchronous and asynchronous)
7272
- Develop mechanisms for reporting progress and outcomes to Members to sustain/grow funding commitments
7373
- Develop mechanisms to enable Member Organizations to shape funding priorities and balance this input with the needs of the Jupyter community
74-
- Give Jupyter subprojects visibility into the Foundation’s activities and opportunities for input
74+
- Give Jupyter subprojects visibility into the Foundation’s activities and opportunities for input

0 commit comments

Comments
 (0)