Conversation

Notices

1. Embed this notice
   Sarah Jamie Lewis (sarahjamielewis@mastodon.social)'s status on Thursday, 13-Feb-2025 06:58:10 JST Sarah Jamie Lewis

   in reply to

   At @openprivacy we've hosted our own gitea (formally gogs) instance for the last 7 years and while it's helped us get a lot of work done - it's a constant maintenance headache.

   Having every new contribution be public by default incentivizes spam.

   Forcing users to create account to make issues/pull requests limits accessibility.

   Dynamically generating every single commit tree means mass scraping campaigns require identification and siloing..

   • Blaise Pabón - controlpl4n3 repeated this.
   • Embed this notice
     Sarah Jamie Lewis (sarahjamielewis@mastodon.social)'s status on Thursday, 13-Feb-2025 06:58:10 JST Sarah Jamie Lewis

     in reply to

     I think the actual self-hosting of code management/issue tracking/CI is important, I want more projects to do it - but currently it is a pain and more expensive than it needs to be.

     It's one of the projects on my list of projects that I wish people would steal (https://sarahjamielewis.com/entry/privacy-projects.html)

   • Embed this notice
     Sarah Jamie Lewis (sarahjamielewis@mastodon.social)'s status on Thursday, 13-Feb-2025 06:58:11 JST Sarah Jamie Lewis

     What I really want in a software forge is static hosting of pretty much everything, with a very small online-app for receiving issues/pull requests, with an approval flow for anonymous/new contributors.

     I prototyped this a few years back, my inbox this morning makes me want to revisit it.

     The github model that pretty much all modern forges are based around doesn't map nicely to smaller projects and it causes so many problems.

     Blaise Pabón - controlpl4n3 repeated this.