Policy on "fork-and-reboot-in-fsprojects" proposals

fsprojects / .github

The place to request for projects to be added or removed from the incubation space

28 stars 7 forks source link

Policy on "fork-and-reboot-in-fsprojects" proposals #41

Closed dsyme closed 1 year ago

dsyme commented 2 years ago

@sergey-tihon From time to time people ask if it would be possible to fork-and-reboot an apparently-abandoned F# community project (e.g. in a personal repository) into fsprojects.

In general in the past we've never had to do this as project owners have either decided to move in or not. However it's a scenario we should think about, and probably have some reasonable policy guidelines.

Some notes:

Fork-and-reboot on active projects is generally really bad, but is seen as reasonable for abandoned projects.
Forking loses issues, PRs etc. Also loses access to be able to publish nuget packages and will lose package continuity

cc @cartermp

sergey-tihon commented 2 years ago

I think that we anyway try to contact original author and try to make a proper transfer.

So process may look like:

Person who volunteer themself to be a new maintainer should create issue in this repo
We will process such requests case by case and will try to contact owner using available channels.
If we do not receive response from the author in 1-2 month then we do official fork on behalf of fsprojects
We should keep credits in README and probably link to the issue in this project to keep track for a reasons for our behavior
We also need clear definition about what we count as abandoned (no commits for 1+/2 years and no response on issues from maintainer)

dsyme commented 2 years ago

Also offer a path back to reunion with the original project. And an open invitation for the originator to join back as a co-maintainer (or even have the project back if they want to resume repo duties)