System Crafters git server?

Hello everyone,

Based on this recent post of prot to leave sourcehut I thought it could be interesting to start a discussion about hosting a git sever for the system crafter community, for example with forgejo.

Are there already any plans for this?

Of course this should host the content directly related to system crafters, e.g. crafted emacs or crafted guix.

What else?
It could also host new community projects.
It could mirror emacs configurations that could be used as example configs for others.
Same for guix.
It could also mirror guix channels. So far they are all over the place (on Github, Gitlab, SourceHut, Codeberg…). That way it would be easier to find packages for guix.

On a meta level, it could even work as an entry point for new members to contribute to software that uses “alternative” code hosting platforms (FSF…)?

I am of course aware that it would not be for free, but I guess the benefits are well worth it.

Any thoughts?

:slight_smile:

1 Like

I have considered it a few times but wasn’t sure whether people would find it worthwhile.

You do raise some interesting use cases though regarding mirroring repos. The SC Git doesn’t necessarily need to be the primary home for all repos, but it could be a place where repos can be aggregated to be found more easily.

Anyone else have thoughts or suggestions about this?

1 Like

The mirror sounds like a good idea, especially since you cannot deactivate the issue tracker and merge/pull requests on some forges. That’s why GitHub - torvalds/linux: Linux kernel source tree still has pull requests open, you cannot deactivate them, even though Linus will never use those.

1 Like

I’d generally recommend against it, unless you really have the desire to provide a long-term home for people’s software projects. There are already so many good forge hosts out there. A list of the top-3 SC-recommended ones could be as good as or better than hosting one yourself.

Hmm. I see the point against hosting software projects directly, considering that nobody knows the long-term outlook of this community.

But I still think my use case of mirroring certain projects is valid.
It happened two times for me now that I was working on package definitions for Guix only to find out later someone else already worked on them. Both times I only found them more or less by chance via the mail archive, because the indexing of e.g. Gitlab is so bad.
Similar for Emacs configurations, that I only found because someone linked them on e.g. Reddit.

Also, it’s just sad imo if even Prot is now mainly relying on Github (as do most other Emacs packages).

Fair point! I wouldn’t want to do it unless I knew I could provide stable service long term. The ideal solution would be to pay for Forgejo hosting from someone reputable so that I don’t have to deal with outages.

I’d say the likelihood of it happening is like 60%.

It seems to me that the way to discover Guix package definitions ought to be through an index provided by Guix (e.g. for non-Guix definitions and channels, there could be a community index on the Guix site). Searching forges or googles won’t ever be a reliable way to find them.

That would be better. But I guess as soon as it involves any non-libre software, it would not be included :frowning:

True. I guess the job falls to you to host a non-libre Guix package/channel index, then. :slight_smile:

It actually does exist, it just has a totally non-memorable domain name:

https://toys.whereis.みんな/

Oh, that’s, uh…per…fect…ly…natural…

Maybe instead of a full-blown forge, just a curated list of System Crafter’s projects? Something like a SystemCrafters/awesome-projects repository, similar to the other "awesome" link lists on GitHub and other places?

1 Like

umm, interesting name … :melting_face:
But thanks, that’s great to know

There are a number of “awesome-FOO” repositories. Seems to be a blurry line between helpful and star-farming.

Yeah, eventually I wanted the Community page to be that:

https://systemcrafters.net/community/#community-projects

Hmmm, I need to fix the metadata on the site so that Discourse embed view works correctly.

Anyway, we should have a listing like that at the very least.