Council/council-docs
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

📝 docs(project): Add Upstream Comms section for Upstream First

Browse source 
This commit addresses feedback from @kevin in Matrix about how we engage
and work together with upstream communities. It emphasizes that while we
are not always going to agree with upstream's suggestions, we work hard
to maintain strong, healthy relationships with our upstreams, and Fedora
values the importance of working together in what we do as a community.

Signed-off-by: Justin W. Wheeler <jwf@redhat.com>
This commit is contained in:
Justin W. Wheeler 2025-02-17 16:02:22 -05:00
parent e7c8fa9b5f
commit 73112bf569
No known key found for this signature in database
GPG key ID: 7748B15FA8FA4C7E
1 changed files with 19 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

26
project/modules/ROOT/pages/upstream-first.adoc
View file

@ -16,6 +16,16 @@ Think of it like a river: the upstream is the source, and downstream projects ar
This metaphor is essential for understanding how open source projects depend on and interact with each other.
Different development models encourage varying types of upstream/downstream relationships.
[[upstream-benefits]]
=== The Benefits of Upstream First
Fedora's upstream-first approach has a ripple effect throughout the open source ecosystem.
Changes landed in Fedora often impact numerous downstream projects that use Fedora as a foundation.
Therefore, contributing to Fedora is a highly effective way to influence and improve the broader open source landscape, particularly within the RPM/Enterprise Linux ecosystem.
By prioritizing upstream contributions, Fedora aligns with its vision of a world where everyone benefits from free and open source software built by inclusive and welcoming communities.
This commitment extends to *all* open source software, not just Fedora itself.
[[upstream-why]]
== Fedora's Commitment to Upstream First
@ -54,16 +64,18 @@ Reasons for downstream patches include:
In these situations, Fedora strives to minimize the scope and duration of downstream patches, and continues to work towards upstreaming changes whenever feasible.
Understanding the reasons for downstream changes is essential for maintaining transparency and trust within the community.
[[upstream-communication]]
=== Open Communication with Upstream
[[upstream-benefits]]
== The Benefits of Upstream First
Fedora recognizes the importance of clear and open communication with upstream projects.
We believe in fostering strong relationships with upstream developers and communities, and actively seek their input and feedback.
Fedora's upstream-first approach has a ripple effect throughout the open source ecosystem.
Changes landed in Fedora often impact numerous downstream projects that use Fedora as a foundation.
Therefore, contributing to Fedora is a highly effective way to influence and improve the broader open source landscape, particularly within the RPM/Enterprise Linux ecosystem.
Fedora is always open to hearing from upstream projects about how we can improve our collaboration and integration processes.
We understand that Fedora's downstream usage can sometimes create challenges or friction for upstream projects.
We encourage upstream maintainers to reach out to us if they encounter any issues or have suggestions for improvement.
By prioritizing upstream contributions, Fedora aligns with its vision of a world where everyone benefits from free and open source software built by inclusive and welcoming communities.
This commitment extends to *all* open source software, not just Fedora itself.
Our goal is to work together constructively to find solutions that benefit both Fedora and the upstream projects we rely on.
While we cannot always accommodate every upstream request, we are committed to listening, learning, and adapting our practices to minimize any negative impact on upstream communities.
[[examples]]