Conversation

Notices

1. anarcat (anarcat@social.weho.st)'s status on Monday, 31-Jan-2022 09:12:47 UTC anarcat

   in reply to

   • John Goerzen

   @jgoerzen what you seem to be more concerned about is relying on a web browser and a central website for operations, and context-switching. there are various ways around that: sr.ht goes the "full email" route, but there are various client-side interfaces that allows you to integrate the PR workflow inside your IDE. magit-forge is one for emacs, for example...

   • Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • anarcat (anarcat@social.weho.st)'s status on Monday, 31-Jan-2022 09:12:48 UTC anarcat

     in reply to

     • John Goerzen

     @jgoerzen in other words, a #git repo is a not a #wiki (and even a #wiki is not a wiki anymore, in any traditional sense, because of spammers) which anyone can edit. you need "moderation" AKA "code review", and that can only happen with a central clearinghouse.

   • anarcat (anarcat@social.weho.st)'s status on Monday, 31-Jan-2022 09:12:49 UTC anarcat

     • John Goerzen

     @jgoerzen i think some centralization is necessary, you need some "authority" over the code, who decide what goes in or not, and that requires some degree of centralization, whether you like it or not.