Drip by Kickstarter VS Commit Together by Github

• Creator Support
  Drip is designed to support creators by providing a platform for building a subscription-based income model, allowing creators to receive consistent financial backing from their fans.
• Integration with Kickstarter
  As part of the Kickstarter ecosystem, Drip allows existing Kickstarter users to easily connect and support ongoing creative projects, leveraging Kickstarter's established audience.
• Community Engagement
  Drip helps creators foster a sense of community among their backers by offering exclusive content and updates, enhancing the connection between creators and their audience.
• Creative Freedom
  Drip affords creators the flexibility to share various types of content, such as videos, podcasts, writings, and more, without being restricted by traditional content distribution methods.

Possible disadvantages

• Limited Discoverability
  Drip's current discovery mechanisms are not as robust as they could be, which may make it challenging for new creators to attract a wider audience on the platform.
• Competition with Other Platforms
  Creators might find it difficult to choose between Drip and other well-established subscription platforms like Patreon, which have larger user bases and more developed features.
• Revenue Share Model
  Kickstarter takes a percentage of the revenue generated on Drip, which is standard but might be a concern for creators who are looking for higher profit margins.
• Dependence on Subscription Model
  Drip’s focus on subscriptions might not suit all creators, especially those who prefer single-payment support models, potentially limiting its appeal to certain user groups.

• 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 Drip by Kickstarter 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