It's 100% oriented around the US political compass, too.
I noticed this in ~2012 in the Python community. PyCon 2013 was the last "real PyCon" in my eyes. That was "Donglegate" happened, and was the last TiP BoF.
Since then it's only increased both in both scale and scope.
The politics of each "side" completely aside, it has worried me for a long time that the division has infected F/OSS as well, and weakened it as a result.
As best I can see, bookstack has not experienced much in the way of concrete issues with Github. And there there are no concrete benefits from migrating to Codeberg. It is his project, his perogative, completely. But the major disbenefit of being on some other forge is that people are less likely to find the software and so less likely to adopt it.
I use Bookstack for a family wiki. I probably would not have gone with it if it had not be hosted on Github as the visible activity on Github makes it clear that it's a project with momentum (18k stars, lot's of activity) etc.
I can't help but feel that moving will make the project less successful than otherwise...
I can understand that viewpoint. Ultimately though, audience/growth is not a core success metric for me, and the values/points explained in the blog post are more important. Plus there's a factor of wanting to help de-centralise away from GitHub, and help provide momentum to alternatives.
Looking at those who have starred the new Codeberg repo, at least 15 people are new today, and thus form part of a bigger audience on Codeberg.
>Care has been taken to ensure minimal impact to BookStack end users. The original GitHub repository is still staying around, and will essentially act as a mirror of the codebase on Codeberg, so any existing instances fetching updates from GitHub can continue to do so.
Since they are keeping the github as essentially a mirror, doesn't this obviate those concerns?
-edit- although also:
>although eventually we will only create releases on Codeberg so it’s advised to watch/subscribe to them there instead:
I guess someone _else_ could choose to fork and keep up-to-date.
BookStack maintainer here. Just to clarify on that, the GitHub repo will continue to be updated and mirror the Codeberg repo (including release tags/code) for the foreseeable future, it's just that I might stop specifically publishing GitHub release entries (details on the release tag) at some point to avoid the duplication of work.
I feel like this is a much better link for this: https://www.bookstackapp.com/blog/project-migrated-to-codebe...
OSS is increasingly bisecting into two camps, and you can tell which camp they are in depending on whether their developers use X or Mastodon/Bluesky.
It's 100% oriented around the US political compass, too.
I noticed this in ~2012 in the Python community. PyCon 2013 was the last "real PyCon" in my eyes. That was "Donglegate" happened, and was the last TiP BoF.
Since then it's only increased both in both scale and scope.
The politics of each "side" completely aside, it has worried me for a long time that the division has infected F/OSS as well, and weakened it as a result.
It's best to ignore such things.
How much degradation are you wiling to observe before you conclude maybe it should not be ignored?
Caring about whether a user is on team 'x' or team 'bluesky' is the degradation.
As best I can see, bookstack has not experienced much in the way of concrete issues with Github. And there there are no concrete benefits from migrating to Codeberg. It is his project, his perogative, completely. But the major disbenefit of being on some other forge is that people are less likely to find the software and so less likely to adopt it.
I use Bookstack for a family wiki. I probably would not have gone with it if it had not be hosted on Github as the visible activity on Github makes it clear that it's a project with momentum (18k stars, lot's of activity) etc.
I can't help but feel that moving will make the project less successful than otherwise...
I can understand that viewpoint. Ultimately though, audience/growth is not a core success metric for me, and the values/points explained in the blog post are more important. Plus there's a factor of wanting to help de-centralise away from GitHub, and help provide momentum to alternatives.
Looking at those who have starred the new Codeberg repo, at least 15 people are new today, and thus form part of a bigger audience on Codeberg.
Fair enough. I didn't say so but - bookstack is great. Thanks so much for it.
On the flip side, had it not migrated, it wouldn't have shown up on HN today and I would never have heard of Bookstack :-)
>Care has been taken to ensure minimal impact to BookStack end users. The original GitHub repository is still staying around, and will essentially act as a mirror of the codebase on Codeberg, so any existing instances fetching updates from GitHub can continue to do so.
Since they are keeping the github as essentially a mirror, doesn't this obviate those concerns?
-edit- although also:
>although eventually we will only create releases on Codeberg so it’s advised to watch/subscribe to them there instead:
I guess someone _else_ could choose to fork and keep up-to-date.
BookStack maintainer here. Just to clarify on that, the GitHub repo will continue to be updated and mirror the Codeberg repo (including release tags/code) for the foreseeable future, it's just that I might stop specifically publishing GitHub release entries (details on the release tag) at some point to avoid the duplication of work.
be the change you want to see
good for you but do we need to post every no name project that moves away from github? feels weird
a project with 18k+ stars on GitHub considered random? I mean, yeah, React has 245k, and Kotlin has 52.7k, but it's not your average pet project :)