Commit Together by Github VS Nike OSS

• Enhanced Collaboration
  Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
• Improved Code Review Process
  With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
• Accountability
  By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
• Efficiency in Pair Programming
  When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages

• Complex Commit History
  Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
• Potential Workflow Conflicts
  Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
• Initial Setup Overhead
  Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
• Tooling Compatibility
  Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

• Innovation
  Nike's open-source software allows for innovative solutions and contributes to the evolution of technology by making code available to the public.
• Community Collaboration
  By open-sourcing their software, Nike fosters a community of collaboration, allowing developers to contribute to and improve the software over time.
• Cost Efficiency
  Open-source software can reduce costs for Nike by leveraging community contributions and reducing the need for in-house development for certain projects.
• Transparency
  Open source promotes transparency in code, which can lead to improved trust from users and stakeholders who can review the code for security and quality.

Possible disadvantages

• Loss of Competitive Advantage
  By open-sourcing software, Nike might lose some competitive edge as their proprietary solutions become available to competitors.
• Quality Control Challenges
  Managing the quality of contributions can be challenging, as open-source projects often involve diverse contributors with varying levels of expertise.
• Security Vulnerabilities
  Open source software can be an attractive target for malicious actors who can identify vulnerabilities within the publicly available code.
• Dependency Management
  Relying on open-source components can pose risks due to dependency management issues, where updates or changes in third-party libraries may affect functionality.

• Ask HN: Do you rewrite pull requests?

  There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / over 4 years ago

Tracking Nike OSS since Mar 2021.