Re: [Libcdio-devel] RFC - move libcdio from savannah.gnu.org to github?

[E Shattow]

On Fri, Sep 6, 2024 at 3:22 PM Matěj Cepl <mcepl@cepl.eu> wrote:
>
> On Fri Sep 6, 2024 at 7:29 PM CEST, Pete Batard wrote:
> > It is also my opinion that the benefits of being hosted on GitHub far
> > outweigh the drawbacks, especially considering the 1st class CI
> > environment it provides, among many other things.
>
> Yes, CI is the only reason why Git{Hub,Lab} have value, IMHO. And
> I find gitlab.com much better … based on more or less standard of
> Docker, and it seems to me that it could be more flexible than
> GitHub (but I have a way more experience with it than GitHub).
>
> Best,
>
> Matěj
>
> --
> http://matej.ceplovi.cz/blog/, @mcepl@floss.social
> GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
>
> The ratio of literacy to illiteracy is a constant, but nowadays
> the illiterates can read.
>     -- Alberto Moravia
>

Yeah, no.

The libcdio code base moves slowly and supports a technology that is
already ten years obsolete.

In 20-30 years' time all of these contributions and interactions will
be a matter of public record and not hidden behind some walled garden
that faded away into an acquisition of intellectual property rights.
Do you believe this if we stray from the code hosting resources FSF
directly supports?

The way that "kids today write code" is Continuous Integration first
then ask ChatGPT all the questions, submit pull requests and gamify
everything in the comments section with likes and follows and emoji
code-switching. I'm not a code contributor so I will just reinforce
both the positions that yes it is important to have all the fancy
development environment that young GitHub-only developers are
comfortable existing within (or you will not have any contributors
eventually);  and that it's probably a bad idea for social
responsibility reasons in the world software ecosystem to chase after
these contributors and lower the barrier for code contributions.

We're not waiting for Microsoft to ban or unban this github user or
that one at the moment, so what would be worthwhile to place this
important software in that restricted position? What could very
reasonably be done is to mirror the existing repo exported to GitHub
(for example, GitLab, et.al.) whatever platform is popular at the
moment, sure, here is what you want in the place that you expect it!
But we can ignore the dogfooding of social media distractions. People
are free to set up CI and making a mirror of the existing git repo
allows these "new style" coders to reference the github instance of
the repository to do these things. There's no downside to meeting
people halfway and not getting vacuumed up into the data mining casino
and time-wasting trash bin that is the comments section of a pull
request or bug tracker ticket not be preserved in the next decade
onward.

Bit of a rant but really you want this to get a good full discussion I
think it's a question we should pose to the FSF, what is it we want
that is not already there?

-E Shattow