You are here:

Technical Fork

Question: What are a number of technical forks of an open source project on code development platforms?

Overview

Technical Fork metric measures the number of independent copies of a project repository within the same code development platform. Data points consist of the count of distinct technical forks created from the original repository. A technical fork is a distributed version control copy of a project. Unlike clones, which is a copy on a local machine, a technical fork resides on the same platform as the original repository. Analysis of technical forks may provide insight into forking intentions (e.g., contributing vs. non-contributing forks). A high number of technical forks may indicate a strong interest in the project, a vibrant community, and opportunities for collaboration and innovation.

Want to Know More?

Click to read more about this metric.

Filters

  • Time Period (e.g., Weekly, Monthly, Annually)
  • Ratio of contributing fork to total forks (A contributing fork is a fork that has opened a change request against the original repository.)
  • Ratio of non-contributing fork to total forks (A non-contributing fork is a fork that has never opened a change request against the original repository.)

Visualizations

Technical Fork & Clones

Image is sourced from Stakeoverflow

Augur Implementation

Augur Implementation

GrimoireLab Implementation

GrimoireLab Implementation


References

Contributors

  • Vinod Ahuja
  • Sean Goggins
  • Matt Germonprez
  • Kevin Lumbard
  • Dawn Foster
  • Elizabeth Barron
  • Peculiar C. Umeh

Additional Information

To edit this metric please submit a Change Request here

To reference this metric in software or publications please use this stable URL: https://chaoss.community/?p=3431

The usage and dissemination of health metrics may lead to privacy violations. Organizations may be exposed to risks. These risks may flow from compliance with the GDPR in the EU, with state law in the US, or with other laws. There may also be contractual risks flowing from terms of service for data providers such as GitHub and GitLab. The usage of metrics must be examined for risk and potential data ethics problems. Please see CHAOSS Data Ethics document for additional guidance.

Tags:
Was this article helpful?
Dislike 0