I'm looking for "alpha testers" for an alternative forge ( based on #Forgejo )
Public registration is closed (for now), but we can create accounts if anyone wants one, or open registrations temporarily.
It will remain free for #floss projects, likely paid for private projects (although we are providing the service for free for a while, until we do an official launch).
Once/If we start having paid customers, we'll donate part of that income to the upstream Forgejo project.
This forge is 100% hosted in #Europe, and operated & maintained by a very small workers-owned #coop .
P.S.: Yep, we know about the great Codeberg 馃槉 .
Dear #Forgejo admins and users,
We are launching another series of user research interviews in the next weeks and invite you to participate. The 45-minutes interviews help us a lot to learn about your usage of Forgejo.
Visit https://cloud.splvs.net/apps/calendar/appointment/cHr5MB2PoZDp to learn more and to schedule an appointment.
Great news: Today, we have managed to distribute our Forgejo instance across two servers. A main instance still handles most traffic, but requests from #CodebergPages are now handled by another server. Going forward, we'll try to route more read-only traffic there to distribute the load.
This is an important milestone, because such a setup was never tested with #Forgejo at this scale.
This should improve availability of both Codeberg.org and Codeberg Pages.
Details: https://codeberg.org/forgejo/discussions/issues/259
Another small step in Forgejo federation.
Getting Forgejo and mastodon services to talk had some unexpected pitfalls. 
Mastodon only federates on port 443 for example, that means Forgejo needs to be able to listen on a privileged port even for testing. You can imagine the troubles setting up our e2e tests properly. 
This is finally behind us and were now aiming to integrate the test into the automated test suite (with a lot of work already done by @famfo)
Dear #Forgejo admins and users,
We are launching another series of user research interviews in the next weeks and invite you to participate. The 45-minutes interviews help us a lot to learn about your usage of Forgejo.
Visit https://cloud.splvs.net/apps/calendar/appointment/cHr5MB2PoZDp to learn more and to schedule an appointment.
In case you are running a #forgejo instance and you want to test #federation, please drop me a mail/toot. I set up a repo at https://forgejo.mayer.rocks/public/federation-test to play with it a bit.
Another small step in Forgejo federation.
Getting Forgejo and mastodon services to talk had some unexpected pitfalls. 
Mastodon only federates on port 443 for example, that means Forgejo needs to be able to listen on a privileged port even for testing. You can imagine the troubles setting up our e2e tests properly. 
This is finally behind us and were now aiming to integrate the test into the automated test suite (with a lot of work already done by @famfo)
 
      
  
             
      
  
             
      
  
             
      
  
             
      
  
             
      
  
             
      
  
                            
                        
                        