Optibus VS Commit Together by Github

• Efficiency
  Optibus optimizes public transport operations by using advanced algorithms and big data, resulting in more efficient route planning and scheduling.
• Scalability
  The platform can scale to meet the needs of both small and large transit agencies, providing flexible solutions suitable for varying demands.
• Real-time Updates
  Optibus offers real-time updates, allowing for dynamic adjustments and improvements to transit operations as conditions change.
• User-friendly Interface
  The application provides a user-friendly interface that simplifies complex transit data, making it easier for transit agencies to manage and implement.
• Cost-effectiveness
  By enhancing operational efficiency and reducing waste, Optibus helps transit agencies lower operational costs over time.

Possible disadvantages

• Implementation Complexity
  The initial implementation of Optibus can be complex, requiring significant integration with existing systems and data sources.
• Training Requirements
  Staff may require additional training to effectively use Optibus, which can lead to initial downtime and require investment in resources.
• Dependency on Data Accuracy
  The effectiveness of Optibus heavily relies on the accuracy of the input data, which can be a limitation if data sources are incomplete or outdated.
• Cost of Software
  While Optibus can lead to long-term cost savings, the subscription or licensing fees can be significant, especially for smaller agencies.
• Internet Connectivity Reliance
  Optibus is a cloud-based solution, meaning consistent and reliable internet connectivity is necessary for optimal performance, which may be an issue in areas with poor infrastructure.

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