Post APKaccIfZuTlwuvSim by ascott@fosstodon.org
 (DIR) More posts by ascott@fosstodon.org
 (DIR) Post #APKaccIfZuTlwuvSim by ascott@fosstodon.org
       2022-11-06T02:05:07Z
       
       0 likes, 3 repeats
       
       If you use #gitea, a service that runs it (e.g. #codeberg), or just follow its development, how likely is it that their recent announcements will change your use of the software?A few links if you need a little background:- Oct 25, original Gitea blog post https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-of-gitea/- Oct 28, open letter to Gitea from community members expressing concern https://gitea-open-letter.coding.social- Oct 30, Lunny and techknowlogick reaffirm their intent to proceed as previously announced https://blog.gitea.io/2022/10/a-message-from-lunny-on-gitea-ltd.-and-the-gitea-project/
       
 (DIR) Post #APLpFegIFi9N8zRdHE by clacke@libranet.de
       2022-11-07T00:55:47Z
       
       1 likes, 0 repeats
       
       @ascott I trust the Codeberg and others will fork when it becomes necessary. The option "wait and see, jump ship later maybe" is missing.Switching to GitLab makes no sense, as GitLab represents the worst-case scenario for Gitea.Switching to GitHub, BitBucket ... ? No.Some people will switch to sourcehut, pagure and other less-webby alternatives, but I belong to that group of people who believe the web PR flow was a step forward in usability.
       
 (DIR) Post #APOOqUMEsJHiJ8c5Z2 by Codeberg@social.anoxinon.de
       2022-11-08T11:34:13Z
       
       1 likes, 1 repeats
       
       @uncomfyhalomacro You can follow the Gitea fork progress here: https://codeberg.org/codename/meta/issuesCryptofoo: We usually don't like it.@clacke @ascott