[Libcdio-devel] libcdio copied from savannah.gnu.org to github

[Rocky Bernstein]

There is a new organization on github called libcdio
<https://github.com/libcdio/>. The git repository from savannah.gnu.org has
been copied there. The libcdio-paranoia
<https://github.com/libcdio/libcdio-paranoia> git repository that had been
underneath my account rocky has been moved there.

Invitations have been sent to join the organization based on membership
from savannah.gnu.org membership. If you don't have an invitation and would
like one, contact me.

On Mon, Sep 9, 2024 at 4:20 PM Rocky Bernstein <rocky@gnu.org> wrote:

> Thanks everyone for sharing your thoughts.
>
> TL;DR - I will be setting up a libcdio organization on github and will be
> migrating the git repository to github.
>
> For a while, both will co exist. There is no reason to shut down the
> mailing list or other things that savannah.gnu.org offers and that people
> are currently using. And releases can still go to ftp.gnu.org. If you
> happen to be unfamiliar with github, I'll do my best to help you out by
> using it,  and to make the transition from savannah.gnu.org to github.
>
> Basically, I agree with everything Pete Batard writes. And he probably
> says it better and shorter than I would.
>
> With respect to Matěj Cepl's comments:
>
> Going in the direction setting up and running my own server is not a
> direction I think we want to go in. I certainly do not.
>
> Adding extras like VSCode on top of the service that github offers I don't
> have problem with. VSCode is open source (MIT license). If you don't want
> to use VSCode you don't have to. Personally I generally do not use VSCode,
> although I sometimes try it to see what's up there.
>
> On the other hand if someone* wants *to use it bundled with github, fine.
> And there is no stopping someone who wants to use VSCode right locally
> using git pulled from savannah.gnu.org
>
> And that is kind of the point here - I am with Pete Batard and Eric
> Shattow in sentiment that any open-source project should be trying to make
> it easier for people to contribute. And by extension using software that
> currently feels clunky outdated and is hard to use discourages
> contributions.
>
> A case in point was the recent CDText patch. That posting did not use the
> savannah.gnu.org patch submission process. Instead, it was sent to this
> developer list. And even there, the person did not subscribe to the list
> before posting which caused me to take an additional step to decide whether
> it was spam or legitimate. This is not goodness.
>
> It appears that everyone agrees that Pull Requests (PRs) are a welcome
> addition to git (which by the way, make CI not the _only_ important feature
> that savannah.gnu.org is missing).
>
> Franky, mailing list discussion does not serve the same purpose as the
> discussion found in PRs. In fact, the mailing list software mangled the
> CD-Text patch in a way that it could not be applied as posted.
>
> Again I agree with Eric Shattow that while it would be nice to have PR
> discussion recorded forever. And if it isn't, that isn't the end of the
> world or a dealbreaker. We still have git commit comments (along with the
> actual commits). And at release time, the comments are bundled into a
> ChangeLog.
>
> With respect Eric Shattow comment of bringing up savannah.gnu.org's
> deficiencies with FSF and discussing. At some level, I think they have to
> know that savannah.gnu.org is not cutting it. It is not something I want
> to spend time on, but if others do please go ahead! If there turns out to
> be useful information, please let me know.
>
>
> On Thu, Sep 5, 2024 at 8:43 PM Rocky Bernstein <rocky@gnu.org> wrote:
>
>> I'd like your opinion about moving the libcdio git repository from
>> savannah.gnu.org to  github (or some other git repository)
>>
>> The mechanisms at savannah.gnu.org have not been improving or developing
>> while github, gitlab, etc., seem to be constantly improving.
>>
>> Your thoughts?
>>
>>
>>