Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G ggi-castalia
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ggi
  • ggi-castalia
  • Issues
  • #39

Closed
Open
Created Mar 02, 2021 by Cedric Thomas@cedricOwner0 of 2 tasks completed0/2 tasks

(Culture Goal) Upstream first

Description

This activity is concerned with developing awareness with regard to the benefits of contributing back and enforcing the upstream first principle.

With the upstream first approach all development on an open source project are to be made with the level of quality and openness required to be submitted to a project's core developers and published by them.

Opportunity Assessment

Writing code with upstream first in mind results in:

  • better quality code,
  • code that is ready to be submitted upstream,
  • code that is merged in the core software,
  • code that will be compatible with future version,
  • recognition by the project community and better and more profitable cooperation.

Upstream First is more than just "being kind". It means you have a say in the project. It means predictability. It means you are in control. It means you act rather than react. It means you understand open source. (Maximilian Michels)

Progress Assessment

The following verification points demonstrate progress in this Activity: Upstream first is implemented?

  • Significant increase in the number of pull/merge requests submitted to third party projects.
  • A list of third party projects for which upstream first must be applied has been drafted.

Recommendations

  • Identify developers with most experience at interacting with upstream developers.
  • Facilitate interaction between developers and core developers (events, hackathons, etc.)

Resources

  • 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.

  • What is Upstream and Downstream in Software Development? A crystal clear explanation.
  • 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).
  • Red Hat on upstream and the advantages of upstream first.
Edited Oct 22, 2021 by Pierre-Yves Gibello
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking