Skip to main content
 

GitLab are behaving like bad open-source community members. Without freely available open-source software, they wouldn't have been able to create GitLab, turn it into what it is today, and make money from it. And they still need external OSS for that. Giving back to the open-source community should not be dependent on if a person can put food on the table while working on it. The deciding factor should be: non-profit organization or not.

 

Open-source projects can have GitLab for free, but only if they're unsustainable. Rule: "Your project should not have paid support or pay contributors" (regardless of the fact that it's non-commercial/non-profit). https://gitlab.com/gitlab-com/gitlab-ultimate-for-open-source

 

No way in hell will they ever implement real federation for CE. Look at this sh**: https://about.gitlab.com/pricing/self-hosted/feature-comparison/

 

Here's a list of pretty basic standard features you have to pay for: https://gitlab.com/gitlab-org/gitlab-ee/issues/2624#list-of-features -- The main problem is that you have to pay per user, and there's no open-source project pricing. So if you want to use those features, you cannot add many contributors on your self-hosted open-source-focused instance.

 

At least it's easy to create org-wide issue labels, as opposed to GitHub.

 
 

If we want to move our free software from GitHub to self-hosted GitLab instances, we're going to need federated merge requests, and ideally also reviews, comments, etc.. This is possible with ActivityPub now. If you want this to happen, you could upvote https://gitlab.com/gitlab-org/gitlab-ce/issues/4013

 

Sad: GitLab doesn't seem to have RSS or Atom feeds for a repo's tags/releases page.

 

Already made lots of improvements to RS Inspector since I announced it recently. You can follow the releases and changes on GitLab: https://gitlab.com/skddc/inspektor/tags

 

Similar to Apple and Google, GitHub also cannibalize their own marketplace apps by re-implementing the popular ones as official features: https://github.com/blog/2470-introducing-security-alerts-on-github

Next up might be a CI solution, because GitLab pipelines are actually pretty awesome.

← An IndieWeb Webring πŸ•ΈπŸ’ β†’