(Culture Goal) Upstream First
Description
Please provide a description of the activity.
This activity is concerned with developing awareness wrt the benefits of contributing back and enforcing the upstream first principle.
Opportunity Assessment
Why it is relevant to undertake this activity, What needs it addresses. What are the efforts expected. How much will it cost? What resources do we need? What RoI can be gained?
Explain why upstream first is important and its benefits. Developers must be trained. It's the responsibility of the team leader? Management must be aware to "retro-contributions"?
Progress Assessment
Question: How can I assess if the activity is acquired? How will progress be measured. What are the objectives? What are the KPIs? Suggest verification point.
How do you measure Upstream first is implemented?
Tools
Technologies, tools and products concerned by this activity.
- Wonderful Tool: a wonderful tool to do wonderful things.
Recommendations
Hints and best practices. Collected from GGI participants.
- Make people Happy.
Resources
Links to resources in the Resource Center
- A clear explanation of the Upstream First principle and why it fits in the Culture Goal: https://maximilianmichels.com/2021/upstream-first/.
Upstream First means that whenever you solve a problem in your copy of the upstream code which others could benefit from, you contribute these changes back upstream, i.e. you send a patch or open a pull request to the upstream repository.
- A paper by Dave Neary: Upstream first: Building products from open source software
- Explained from the Chromium OS design documents: [Upstream First] (https://www.chromium.org/chromium-os/chromiumos-design-docs/upstream-first)