Confrere VS Commit Together by Github

• Ease of Use
  Confrere offers a user-friendly interface that makes it easy for professionals and businesses to conduct video calls without needing technical expertise.
• Custom Branding
  Users can customize the platform with their own branding, providing a more cohesive experience for their clients during video consultations.
• Security and Compliance
  Confrere is designed to comply with GDPR and other privacy regulations, ensuring that user data is handled securely.
• No App Download Needed
  Clients do not need to download an app to join a call, which simplifies the process of connecting for users who may be less tech-savvy.
• Integration Capabilities
  Confrere can integrate with other tools and systems, enhancing its utility and efficiency for businesses.

Possible disadvantages

• Cost
  For small businesses or individual users, the pricing model might be a disadvantage compared to other free or lower-cost alternatives.
• Limited Features for Free Plan
  The free version of Confrere may have limited features, which could be restricting for users not willing to pay for a premium plan.
• Niche Market
  The platform is tailored more toward professional and business use, which might not appeal to casual users or those seeking a more general video calling solution.
• Internet Dependence
  As with any online video platform, Confrere's performance is heavily dependent on a stable internet connection, which could be a problem in areas with poor connectivity.
• Competition
  There are many established players in the video conferencing market offering similar solutions, which could make Confrere less attractive if users are already committed to another platform.

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

What Designers Can Learn from (Code) Review | Co-founder of Confrere | Ida Aalen

More videos

No Commit Together by Github videos yet. You could help us improve this page by suggesting one.

Tracking Confrere 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