281
Gentoo Linux Begins Codeberg Migration In Moving Away From GitHub, Avoiding Copilot (www.phoronix.com)
submitted 6 months ago by to c/linux@programming.dev
33 comments fedilink hide all child comments
 

The Gentoo Linux project last year announced plans to move their code hosting to Codeberg rather than GitHub. Gentoo's desire to move away from GitHub was motivated by Microsoft's Copilot training on GitHub repositories. Those plans are turning into action now with the main Gentoo project up on Codeberg and honoring pull requests.

Gentoo announced today they now have a presence on Codeberg and are welcoming code contributions there as an alternative to GitHub. Initially it's their ebuild repository being hosted on Codeberg while eventually all Gentoo GitHub repositories will be migrated. Codeberg is based on Forgejo and hosted in Germany as a non-profit.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 2 points 6 months ago (1 child)

It's probably something obvious i'm missing, but what is the root problem ?

The Lemmy network and the Threadiverse at large being associated as just a Tankie hangout

For example, this was from a Reddit thread last week I saw when it was just starting to get big:

In this case Rimu (PieFed dev) and others were quick to jump in and steer, so hopefully this whole boycotting/cross-posting campaign at the very least gives them more fuel when these comments come up on the outside something like "Tankies are there, but they don't have any important comms so you can just block those 3 instances or join [x] instance which blocks them for you"

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 6 months ago (1 child)

    I'm not sure catering to the opinions of random redditors is a useful approach, but that aside.

    The Lemmy network and the Threadiverse at large being associated as just a Tankie hangout

    Which would be solved by creating an instance (or building up an existing instance) that isn't the triad.

    In this case Rimu (PieFed dev) and others were quick to jump in and steer, so hopefully this whole boycotting/cross-posting campaign at the very least gives them more fuel when these comments come up on the outside something like “Tankies are there, but they don’t have any important comms so you can just block those 3 instances or join [x] instance which blocks them for you”

    Which would also be solved with the same solution.

    From your list:

    1. Promoting smaller instances, because of the volume of my posting it helps makes smaller instances more recognizable
    2. Making comms on fitting smaller instances (e.g. a programming comm id make on programming.dev)
    3. Mitigating against the imposter problem
    4. Better interconnecting smaller instances

    1 sounds like artificially inflating the numbers

    2 isn't that useful IMO because without the actual content / ongoing engagement you just end up with multiple ghost communities.

    3 i think the imposter problem is a user education error and/or could be better solved in a different manner.

    4 this is what cross-posting is for right (though I'll admit that experience is lacklustre right now)? You don't need a whole account to cross-post between communities.

    Artificially inflating the numbers might look like it helps in the short term, but is bringing someone here under false pretences a workable solution, or even a solution you want ?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 6 months ago* (1 child)

    I'm not sure catering to the opinions of random redditors is a useful approach, but that aside.

    It was but a mere example

    The Lemmy network and the Threadiverse at large being associated as just a Tankie hangout

    Which would be solved by creating an instance (or building up an existing instance) that isn't the triad.

    In this case Rimu (PieFed dev) and others were quick to jump in and steer, so hopefully this whole boycotting/cross-posting campaign at the very least gives them more fuel when these comments come up on the outside something like “Tankies are there, but they don’t have any important comms so you can just block those 3 instances or join [x] instance which blocks them for you”

    Which would also be solved with the same solution.

    It could help, but it's not a problem that any one solution is the solution. There's going to be some combination of solutions to actually solve it.

    1 sounds like artificially inflating the numbers

    Not really, I might have a lot of accounts, but it's still only 1 per instance so it's not really inflating the numbers. Besides most go by monthly active users for gauging the Threadiverse health which because of my pattern I might not even make up 1 MAU lol

    2 isn't that useful IMO because without the actual content / ongoing engagement you just end up with multiple ghost communities.

    I don't just make them, I do my best to actively contribute to them, like I said I also post "organically sourced" content and not just crossposts for this very reason

    3 i think the imposter problem is a user education error and/or could be better solved in a different manner.

    Um I'm not sure how that would be a user education error? I'm talking about someone maliciously making an imposter account and posting heinous crap "in their name" But there is currently no technical solution on the Threadiverse afaik for it

    4 this is what cross-posting is for right (though I'll admit that experience is lacklustre right now)? You don't need a whole account to cross-post between communities.

    Nah crossposts are a solution for a different problem, 4 is for when an instance hasn't federated with another instances remote comm yet and is therefore unknown to the instance

    For example, I made this post to my comm at !gunnerkrigg@lemmy.cafe today from this toast.ooo instance I'm on rn

    But toast.ooo never federated with that comm so as far as this instance knew !gunnerkrigg@lemmy.cafe didn't exist until I manually went to the comm by URL (toast.ooo/c/gunnerkrigg@lemmy.cafe) and subbed to it

    Until then nobody on this instance would have been seeing posts from that comm in their c/all/new/whatever feed, even if a post went "viral". But now they will and for every other comm I sub to as I go

    And that process happens a lot on these smaller instances I'm on, some will be missing even major comms like !pcgaming@lemmy.ca or !funny@sh.itjust.works

    That's what I mean by helping interconnect smaller instances

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 6 months ago

    It was but a mere example

    Fair enough.

    It could help, but it’s not a problem that any one solution is the solution. There’s going to be some combination of solutions to actually solve it.

    Also reasonable

    Not really, I might have a lot of accounts, but it’s still only 1 per instance so it’s not really inflating the numbers. Besides most go by monthly active users for gauging the Threadiverse health which because of my pattern I might not even make up 1 MAU lol

    Reasonable again.

    I don’t just make them, I do my best to actively contribute to them, like I said I also post “organically sourced” content and not just crossposts for this very reason.

    I missed that, if that's whats happening i retract my implication.

    Um I’m not sure how that would be a user education error? I’m talking about someone maliciously making an imposter account and posting heinous crap “in their name” But there is currently no technical solution on the Threadiverse afaik for it

    I think imposter account is a misnomer, two accounts with the same name on different instances are distinct entities afaik,

    like mike@gmail.com isn't the same as mike@outlook.com.

    if you look at a post and it's written by "mike" and you don't look at the instance it's from you're only getting half of the information you need.

    Solutions for this type of problem exist already (PGP keys etc), they just aren't very practical for regular people.

    The "could be better solved in a different manner." part was mostly about how the underlying software for the instances might be changed to allow for some of these existing solutions to be integrated more seamlessly.

    Or something entirely new, who knows.

    Nah crossposts are a solution for a different problem, 4 is for when an instance hasn’t federated with another instances remote comm yet and is therefore unknown to the instance

    For example, I made this post to my comm at !gunnerkrigg@lemmy.cafe today from this toast.ooo instance I’m on rn

    But toast.ooo never federated with that comm so as far as this instance knew !gunnerkrigg@lemmy.cafe didn’t exist until I manually went to the comm by URL (toast.ooo/c/gunnerkrigg@lemmy.cafe) and subbed to it

    Until then nobody on this instance would have been seeing posts from that comm in their c/all/new/whatever feed, even if a post went “viral”. But now they will and for every other comm I sub to as I go

    I didn't know this is how it worked, makes sense in that context.

  • permalink
  • fedilink
  • source
  • parent