Conversation

Notices

1. Forgejo (forgejo@floss.social)'s status on Monday, 24-Apr-2023 02:43:00 JST Forgejo

   The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.

   Learn about how Forgejo v1.19 came to be, the recent developments of Forgejo Actions and more.

   https://forgejo.org/2023-03-monthly-update/

   • silverpill (silverpill@mitra.social)'s status on Monday, 24-Apr-2023 02:42:56 JST silverpill

     in reply to

     • Ryuno-Ki
     • tallship

     @tallship @RyunoKi I've read through articles but it's such a mess. Could you describe what happened in simple terms? Are we going to see another fork?

   • tallship (tallship@public.mitra.social)'s status on Monday, 24-Apr-2023 02:42:57 JST tallship

     in reply to

     • Ryuno-Ki

     @RyunoKi @forgejo

     One can redact, especially since Loïc Dachary will need to have regular GPL so his twice failed GNA can effectively embed proprietary code into the Forĝejo flavor he intends to run for his hosting service.

     You see, if it's AGPL3 - which Forĝejo is and has been since 15 April following a duly held election - then he would have to make available any changes to that code on the hosted service to anyone that asks... Such is the reason for the AGPL itself, because SaaS providers must make the modifications to any hosted AGPL daemons available on demand, while you don't have to do that with plain old GPL code (only the code you distribute after you modify it).

     I suspect this is why Loïc Dachary artificially extended the adoption of any Copyleft license.

     After his GNA was a miserable failure (twice, after trying to carry Savannah to that domain name after the leadership itself of the FSF initially had to wrest control away from him), first, with a Savannah clone followed by an unsuccessful attempt to provide hosting services for devs using Gitea, he's turned now to try and give it a go with Forĝejo - so from a hosting provider's perspective it's very convenient to modify the code and not have to reveal it make available for inspection any of it.

     So he bowed out the Forĝejo project after half a dozen active community members left in disgust, (at least) one founding member after promising a salary and then performing a rug pull (his first offer to resign in disgrace after being called to the carpet for that transgression).

     Finally, after mishandling the move to Copyleft and dragging it asking for over three months he left there project and community completely. Perhaps he was surprised that an orderly affect for rotation of the organization's 🗝️ keys 🔐 with business carrying on as usual, getting underway without him or the infrastructure he had deployed that wasn't even community controlled (since taken offline and replaced) , he returned, after a day and a half...

     His org admin/owner privs still had not yet been rescinded - at this point her literally claimed he was, himself, going to reboot the community as he saw fit, and usurped and gutted the community status quo, reshaping governance and rules to suit himself... The parallel to that same type of usurpation by general Pinochet just a couple of days after the President of Chile promoted him to commander of all the armed forces -subsequently deposed and replaced with a Junta by Pinochet... was... astounding.

     Like I said, one can redact - but you cannot erase. You cannot erase any of these truths as they are all archived... Including the real reasons why Loïc Dachary's wiki pages were removed, as per the Wikimedia editors who state why, and not simply as Loïc Dachary stated... But that's a really embarrassing topic for another time, not particularly pertinent today.

     One can redact https://archive.is/7v7Ax

     Butt you can't erase. Archives of all of Loïc Dachary's antics are archived and screenshotted in convenient redundancy.

     This is all so very unfortunate, because Forĝejo is otherwise a good thing, save for the damage to good people and then project itself in his destructive wake.

   • Ryuno-Ki (ryunoki@layer8.space)'s status on Monday, 24-Apr-2023 02:42:58 JST Ryuno-Ki

     in reply to

     @forgejo
     For the record: perfectly fine comments are getting redacted:

     https://codeberg.org/forgejo/website/pulls/204#issuecomment-878163

     There's no official enforcement of moderation in place towards this #Forgejo member.

   • Ryuno-Ki (ryunoki@layer8.space)'s status on Monday, 24-Apr-2023 02:43:00 JST Ryuno-Ki

     in reply to

     @forgejo
     I hereby demand a correction.

     I *did not* executed my Right to be Forgotten. The article is misleading.

     See https://jaenis.ch/blog/2023/forgejo-sacrifice-inclusiveness-and-calls-it-healing/ for my point of view

     #Forgejo

   • silverpill (silverpill@mitra.social)'s status on Monday, 24-Apr-2023 03:36:44 JST silverpill

     in reply to

     • Ryuno-Ki
     • tallship

     @RyunoKi @tallship As a potential user, I'm primarily concerned with execution. If the team can create a functional federated forge and maintain it for years to come, I don't really care about their culture and internal processes.

     Conflicts are unavoidable... But sometimes a misaligned person or a group takes over the project and drives away people who do the real work. I hope this is not the case with Forgejo

   • Ryuno-Ki (ryunoki@layer8.space)'s status on Monday, 24-Apr-2023 03:36:45 JST Ryuno-Ki

     in reply to

     • silverpill
     • tallship

     @silverpill
     Now there might be people (think straight white men) that don't have a problem with Tech Bro Culture.

     But it's not living up to its full potential if you ask me.
     There's so much more people could do with a forge!

     I'm saying that as straight white man.

     @tallship

   • Ryuno-Ki (ryunoki@layer8.space)'s status on Monday, 24-Apr-2023 03:36:46 JST Ryuno-Ki

     in reply to

     • silverpill
     • tallship

     @silverpill
     Unlikely.
     We won't have enough people to run that.

     I expect copyleft code to be integrated into Forgêjo this year. Likely the federation capabilities.

     As much as it concerns me, the technical side is strong in the project.
     But the governance is lacking.

     This could very much lead to a „Tech Bro“ culture. May or may not be okay.

     What bugs me is that the lived culture doesn't match the proclaimed one.
     That's plain dishonest.
     Therefore I speak up.

     @tallship