Open Source @IFTTT VS Commit Together by Github

• Cost-effective
  Open source software is generally free to use, reducing the cost associated with purchasing licenses for proprietary software.
• Community Support
  Open source projects often have a strong, active community that contributes to development, bug fixes, and support.
• Flexibility and Customization
  Users have the ability to modify and customize open source software to fit their specific needs.
• Transparency
  With open source, the code is available for review, providing transparency into its functionality, security, and potential vulnerabilities.
• Rapid Innovation
  A broad base of contributors enables faster evolution and innovation through collective problem-solving and idea-sharing.

Possible disadvantages

• Lack of Official Support
  Open source software might lack dedicated professional support services, making it challenging for users who need immediate assistance.
• Varying Quality
  The quality of open source software can vary significantly, sometimes leading to stability or security issues if not properly vetted or maintained.
• Complexity
  Customization and configuration of open source software can be complex and require specialized technical knowledge.
• Compatibility Issues
  Open source projects may not always be compatible with existing proprietary systems or require additional configuration.
• Limited Documentation
  Comprehensive documentation may be lacking or inconsistent, making it harder to understand and use the software effectively.

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

Tracking Open Source @IFTTT since Mar 2021.

• 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