3 ms·

The blog post mentions that you recently open sourced 18 features that were previously paid. I assume that refers to this announcement: https://about.gitlab.com

by db579 6y ago

The blog post mentions that you recently open sourced 18 features that were previously paid. I assume that refers to this announcement: https://about.gitlab.com/blog/2020/03/30/new-features-to-core https://about.gitlab.com/blog/2020/03/30/new-features-to-cor.... It seems those are proposals (or at best commitments) for things to be open sourced in future versions rather than things that actually are available as open source already? Could you clarify please?

boleary-gl 6y ago
GitLab Developer Evangelist here. They are commitments. Each feature has its own issue for the engineering effort behind moving it to Core with various milestones based on team capacity and complexity of the move. You can track each with the table in the post that relates the feature to “GitLab issue” that represents the move.
- db579 6y ago
  Fair enough. Don't get me wrong I'm very excited about the announcement and think it'll be great to have some of these features in the open source core, I just thought it was a little misleadingly worded in this blog post. Seemed to imply the work had already been done.
tr-gitlab 6y ago
GitLab PM here for the Package stage. We announced that the Package Registry offering will be included in GitLab Core. This means that for npm, Maven, NuGet, Conan and any future formats, you will be able to: - Establish GitLab as a private repository - Authenticate using your GitLab credentials, personal access or job token - Publish packages to GitLab - Pull packages from GitLab - Search for packages hosted on GitLab - Access an easy-to-use UI that displays package details and metadata and allows you to download any relevant files It does take a bit of work to migrate the code. We are currently investigating what work is required and will have a better sense of timing once the investigation is complete. We are hoping to have this complete in the next few months. You can follow along in the issue here: https://gitlab.com/groups/gitlab-org/-/epics/2867 https://gitlab.com/groups/gitlab-org/-/epics/2867.

by db579 6y ago

boleary-gl 6y ago

GitLab Developer Evangelist here. They are commitments. Each feature has its own issue for the engineering effort behind moving it to Core with various milestones based on team capacity and complexity of the move. You can track each with the table in the post that relates the feature to “GitLab issue” that represents the move.

db579 6y ago
Fair enough. Don't get me wrong I'm very excited about the announcement and think it'll be great to have some of these features in the open source core, I just thought it was a little misleadingly worded in this blog post. Seemed to imply the work had already been done.

tr-gitlab 6y ago

GitLab PM here for the Package stage. We announced that the Package Registry offering will be included in GitLab Core. This means that for npm, Maven, NuGet, Conan and any future formats, you will be able to: - Establish GitLab as a private repository - Authenticate using your GitLab credentials, personal access or job token - Publish packages to GitLab - Pull packages from GitLab - Search for packages hosted on GitLab - Access an easy-to-use UI that displays package details and metadata and allows you to download any relevant files It does take a bit of work to migrate the code. We are currently investigating what work is required and will have a better sense of timing once the investigation is complete. We are hoping to have this complete in the next few months. You can follow along in the issue here: https://gitlab.com/groups/gitlab-org/-/epics/2867 https://gitlab.com/groups/gitlab-org/-/epics/2867.