coreinfrastructure
Show "forked" on GitHub projects that are forks
The Cuckoo project here: https://bestpractices.coreinfrastructure.org/en/projects/1712 is a fork of the original project, not the original project. That may be confusing to people.
Sometimes only the fork is the live project, so we don't want to forbid it. However, it may be valuable to mark such things somehow.
One idea: If a project is on GitHub, and GitHub notes that it's a fork of a different project, show "[FORK]" after the name in the project list and project display. We can store that as a boolean value in the project, and a detective can determine that. We probably want admins (but only admins) to be able to set/clear this value.
It wouldn't be hard to evade automatic detection. E.g., just copy the files, and re-upload them. But I don't see an easy way to deal with that, and it may not be necessary to do more.
Unfortunately, I think that plan would result in a lot of false positives like:
https://github.com/couchbase/manifest https://landscape.cncf.io/selected=couchbase
A safer rule might be forks with less than a hundred stars.
-- Dan Kohn [email protected] Executive Director, Cloud Native Computing Foundation https://www.cncf.io +1-415-233-1000 https://www.dankohn.com
On Thu, Apr 12, 2018 at 12:30 PM, David A. Wheeler <[email protected]
wrote:
The Cuckoo project here: https://bestpractices.coreinfrastructure.org/en/ projects/1712 is a fork of the original project, not the original project. That may be confusing to people.
Sometimes only the fork is the live project, so we don't want to forbid it. However, it may be valuable to mark such things somehow.
One idea: If a project is on GitHub, and GitHub notes that it's a fork of a different project, show "[FORK]" after the name in the project list and project display. We can store that as a boolean value in the project, and a detective can determine that. We probably want admins (but only admins) to be able to set/clear this value.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/coreinfrastructure/best-practices-badge/issues/1123, or mute the thread https://github.com/notifications/unsubscribe-auth/AC8MBmUlgfmQv1qNKitPxvaI_YssvXudks5tn4ERgaJpZM4TSHQZ .
The "less than a hundred stars" rule won't really work for smaller projects with less exposure. What about something like "the number of stars is smaller than one order of magnitude below the number of starts of the original project", as in the fork with less than 10 stars vs. the original repo with 100+stars.
