Forks
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 4
Description
@jonc125 's open question (which I'm not sure how to answer) how does the UCL community contribute to OSS via forking?
We're currently removing all forks and mirrors (#13) in our Augur/8Knot and Grimoire deployments.
What would be interesting: how much work is done e.g. on a fork into the @UCL organisation, and then is this pushed back upstream.
As-is: we're pretty sure both tools would not treat the forked repo in any special way (a repo is either fully included in the metrics or not).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named; start by defining how forks into the UCL organisation and upstream contributions should be identified in Augur/8Knot and Grimoire deployments. Done means a documented answer to the fork contribution question, including whether the tools distinguish forked repositories and how much work is pushed upstream.
Written by the indexing model from the issue text.
Assessment
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100