Simon Tournier <zimon.touto...@gmail.com> writes: > Especially when it becomes so “easy” (familiar) to click on a button for > forking. Without counting on the “wish-to” effect: I would like to > contribute and even if I will never do it, I start to fork in case.
While on GitHub and GitLab forks can effectively live forever with no activity, Codeberg will likely notify you that they plan to delete your inactive fork. You can apparently "ask for preservation" though. Still, I am not sure whether it makes sense to make a fork "just in case". I do not know to what degree is the process automated on Codeberg's side, but if not fully, forking "just in case" will needlessly create a support load on their staff. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
