#7

On GitHub we have:

  • rpm-ostree
  • CoreOS
  • Flatpak
  • buildah
  • podman

We could cross-reference issues and get contributors on those to have a look at Silverblue issues the easy way.

4 Likes
#8

FOSS platform vs closed one…

1 Like
#9

Gitlab is Open Core not FOSS, also I would not base the choice only on this criteria, I think now that GitHub is part of Microsoft it not forbidden to think that it could be Open Source in future.

1 Like
#10

GitLab CE (What I assume is being proposed here) is 100% free software.
Additionally, Microsoft taking over GitHub is essentially ensuring that it
will never be FLOSS.

2 Likes
#11

There are three versions of GitLab: The open-source Community Edition stack you download and host yourself, an enterprise version with more features, and the publicly-hosted gitlab.com. I’ve been assuming all along that “moving Fedora from Pagure to GltLab” meant the third option - publish the projects on gitlab.com. Is that not the case - would Fedora staff up and set up servers if they went the GitLab direction?

#12

This vote is absolutely about the hosted variants on github.com and gitlab.com - there are no plans (or resources) to have it on premise for now (meaning 1+ years) and it would also defeat the purpose of creating awareness in the next 2-3 years in non-Fedora communities.

2 Likes
Moving the Silverblue Docs to GitHub
#13

Whew! Glad to hear it! I’m still #teamgithub though. :wink:

#14

Oh, I see. I could probably provide a GitLab CE instance sponsored by
Splentity if that would be a reasonable option. GitLab CE is very easy to
maintain, and I already have an Ansible playbook to handle Splentity’s own
instance…

#15

Thank you for the offer, we appreciate that!

The issue with hosting Gitlab or any piece of software isn’t the setup, though, it’s the ongoing maintenance and updates. Unless you have dedicated ops people taking care of it, you outsource. That is the whole promise of cloud computing. Getting it into Fedora infrastructure by spinning up a VM and installing Gitlab isn’t the problem. It is that Fedora infrastructure is then reliable for maintaining it, managing backups, and guaranteeing up-time which they cannot do at the moment.

I used to maintain a Gentoo server for a small institute at university as well as my own for my own needs. The moment software needs to be reliable, you have to take a step back and admit you cannot do this on your own in some spare time anymore. Then it becomes about what you can and want to focus on and you have to make some decisions regarding time, money, and where you want to put your skills to use. Silverblue is bleeding edge, currently with lots of bleeding. So we need contributors to create content, documentation, and work on all the different bits and pieces - mostly rpm-ostree, GNOME, Flatpak.

4 Likes
#16

Ok, gitlab.com is not foss, altrought big part of it’s code is MIT licensed, you have a point there.

But it supports an eventual easy migration of code and issues to a selfhosted fully MIT licensed gitlab ce, it’s a big plus.

And yeah, github could be opened by ms, or could not :wink:

I don’t like the idea of being more and more dependant on a third party non open platform that doesn’t officialy support exporting the issues history.

I feel more confortable on a platform that eventually could be replicated on self hosted FOSS instance

2 Likes
#17

I would happily sign on to maintain it myself, along with the others, it’s not
hard to maintain GitLab CE at all, even with a patched version like the one
Splentity uses. Nobody has to work alone these days, automation is simple.
While I personally don’t see a usecase for Silverblue, I certainly do want to
help the project along and I’d love for it to keep to Fedora’s values. This is
not possible while hosting the project on a proprietary platform… Admittedly,
GitLab.com is not as bad as GitHub, we can at least see the code, even if we
don’t have rights to it.

#18

All fine with me, I just wanted to point out that this should not be the only criteria when making the decision :slight_smile:

3 Likes
#19

Wow, talk about close!

1 Like
#20

Doesn’t Gnome use GitLab? Although pragmatically speaking, there is the fact that core projects to Silverblue already are hosted on GitHub… But there are a lot of passionate people not wanting to give on principle of not really open source over slightly more not really open source. It is kinda splitting hairs, and the vote shows how fine the point I guess.

1 Like
#21

Yes, GNOME uses GitLab Community Edition. See https://gitlab.gnome.org/help

1 Like
#22

Hey, GNOME’s GitLab admin here.

@JohnMH Your offer is really nice, but I have to say that Sanja is right here. Maintaining your own GitLab CE it’s not trivial enough to be maintained just voluntarily and not widely supported by an organization. At GNOME we have a paid half time person doing the backend sysadmin stuff, and me doing the more administrative part.

It’s has small details that gitlab.com or github.com just take care of them already. For instance, some day SilverBlue will want to set up gitlab pages, and then you have to deal with domains, and also with redirections, etc. Same for CI, or tons of features gitlab has. Same for abuse reports, spam, etc.

Personally, I would love for Fedora to have its own GitLab CE, but I don’t think it’s a good idea if it’s not maintained widely and officially by Fedora as an organization itself, specifically with someone paid to do it.

8 Likes
#23

Why not Pagure?

#24

You should check the link mentioned on the first post by @sanja.

#25

:man_facepalming: it’s a shame

#26

@JohnMH Your offer is really nice, but I have to say that Sanja is right
here. Maintaining your own GitLab CE it’s not trivial enough to be
maintained just voluntarily and not widely supported by an organization. At
GNOME we have a paid half time person doing the backend sysadmin stuff, and
me doing the more administrative part.

Respectfully, I would have to disagree. In my opinion, maintaining GitLab CE
isn’t a complex task at all, even with custom patches.

It’s has small details that gitlab.com or github.com just take care of them
already. For instance, some day SilverBlue will want to set up gitlab
pages, and then you have to deal with domains, and also with redirections,
etc. Same for CI, or tons of features gitlab has. Same for abuse reports,
spam, etc.

The major difference here is that both gitlab.com and github.com are
proprietary platforms. Using GitLab Pages for Silverblue sounds like an
awesome idea, a declarative website for a declarative system. That isn’t
something that would only be usable on gitlab.io or github.$something.
Splentity uses GitLab Pages on wildcards of splentity.site.