Add Strategy.md and Align Governance Documents with RuFaS Strategic Direction#3161
Open
JuanTricarico wants to merge 5 commits into
Open
Add Strategy.md and Align Governance Documents with RuFaS Strategic Direction#3161JuanTricarico wants to merge 5 commits into
JuanTricarico wants to merge 5 commits into
Conversation
Add the 'Strategy.md' file.
simple formatting edits
Update README to reference Strategy.md
Align CONTRIBUTING.md with Strategy.md
Clarify that forking guidance aligns with RuFaS Shared Operating Principles.
Contributor
Author
|
This PR intentionally focuses on establishing strategic direction and alignment. It should be evaluated based on whether the proposed Vision, Mission, Strategic Pillars, Core Values, and Operating Principles accurately reflect the intended long-term direction of the RuFaS ecosystem and provide useful guidance for future governance and project decisions as discussed by the PML. |
JuanTricarico
marked this pull request as ready for review
July 21, 2026 16:19
Contributor
|
Current Coverage: 99% Mypy errors on add-strategy-document branch: 1136 |
Contributor
|
🚨 Please update the changelog. This PR cannot be merged until |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Issue(s) closed by this pull request: closes #
What
This pull request adds a new Strategy.md document to the root of the repository and updates related governance documents to align with the approved strategic direction of RuFaS.
The strategy document establishes a shared vision, mission, strategic pillars, core values, and operating principles that guide decision-making across the RuFaS ecosystem. The intent is not to prescribe specific projects, roadmaps, or implementation plans, but rather to provide a durable framework that helps contributors, maintainers, sponsors, and leadership make coordinated decisions while preserving flexibility and autonomy.
Why
RuFaS is a collaborative initiative involving multiple organizations, disciplines, and contributors. As participation grows, a shared understanding of the program's purpose, direction, and expectations becomes increasingly important. The purpose of this PR is strategic alignment.
This strategy provides:
How
Changes Included
New File = Strategy.md
Vision
Mission
Strategic Pillars
Core Values
Shared Operating Principles
Updated Files
README.md
Align Vision and Mission statements with the strategy document.
Add a reference to Strategy.md as the source for RuFaS strategic direction.
CONTRIBUTING.md
Add references to RuFaS Core Values and Shared Operating Principles.
Clarify that contribution categories and responsibilities operate within the strategic framework established by Strategy.md.
FORKING.md
Clarify the role of forking as a legitimate outcome within an open-source ecosystem.
Reinforce principles of openness, shared stewardship, and voluntary participation.
This PR does not modify:
The Code of Conduct.
Licensing terms.
Release processes.
Branching strategy.
Technical development workflows.
Versioning policies.
Expected Outcome following this PR:
Test plan
Input Changes
Output Changes
Filter