Zenodo VS Commit Together by Github

• Open Access
  Zenodo provides open access to research outputs, making it easier for researchers and the public to access, share, and reuse scholarly work without restrictions.
• Diverse Content
  It supports various types of content, including publications, data sets, software, and presentations, catering to a broad spectrum of research outputs.
• Free to Use
  Zenodo is free for researchers to upload and share their work, which can help reduce the financial burden on individuals and institutions.
• Integration with GitHub
  Zenodo seamlessly integrates with GitHub, allowing for easy archival and citation of code repositories, enhancing the visibility and impact of software contributions.
• DOI Generation
  It automatically assigns Digital Object Identifiers (DOIs) to uploads, helping ensure persistent and citable research outputs.
• EU Backing
  Supported by CERN and the European Commission, Zenodo is part of an effort to ensure long-term stability and reliability of the platform.

Possible disadvantages

• Data Size Limitations
  There are limitations on the amount of data you can upload (typically 50GB per dataset), which could be restrictive for some large-scale research projects.
• Limited Curation
  Zenodo does not offer in-depth curation or peer review of uploads, so the quality and accuracy of the content can vary greatly.
• Search Functionality
  The search and discovery features on Zenodo could be improved, as the interface might not be as intuitive or powerful as other repositories, potentially making it difficult to find specific content.
• Funding and Sustainability
  Although supported by the EU, questions about long-term funding and sustainability remain, especially if institutional priorities change.
• User Interface
  Some users may find the interface less polished or modern compared to commercial platforms, which could affect user experience and engagement.

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

Why you shouldn't publish data to Zenodo

More videos

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

Tracking Zenodo since Apr 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