Re: Gitlab packaging project funding status changed.

On ചൊ, ജൂൺ 28 2022 at 06:13:32 വൈകു +00:00:00 +00:00:00, Georg Faerber wrote: Hi, On 22-06-28 18:37:27, Pirate Praveen wrote: tells: [...] Gitlab Inc sponsored work on this project for 6+ years until recently. Now we are looking for the commun

Re: Gitlab packaging project funding status changed.

Hi, On 22-06-28 18:37:27, Pirate Praveen wrote: > tells: [...] Gitlab Inc sponsored work on this project for 6+ years until recently. Now we are looking for the community to support it Did GitLab Inc. announce in public that they're not sponsoring this

Re: Gitlab packaging project funding status changed.

We have started an Open Collective to ask Free Software community to donate to continue maintaining gitlab and dependencies. Spread the word.

Gitlab packaging project funding status changed.

Hi Ruby team, A bit of disappointing news: Gitlab Inc is stopping their funding for the packaging work. So we will have to find other sources of funding or reduce the scope of the Debian Packaging project (we will have to depend on rubygems.org more and stop updating ruby dependencies) or find

GitLab Packaging - Github-markdown

Hi, One of the dependencies of GitLab is the gem "Github-markdown". But it seems that gem isn't released under any open source license and is not going to be. When I asked the Github guys about this, there reply was as follows Hi Balasankar, Although the github-m

Re: GitLab packaging

I totally agree about starting off easy. I’ll probably start off with the projects you mentioned since I don’t know which are easy just yet :D I just started looking into Jenkins for work work so that works out great as well. I haven’t looked at Docker just yet, so I’ll check it out. You guys h

Re: GitLab packaging

On 4 Oct 2014, at 2:23 pm, Daniel Polanco wrote: > Hello all: > > After looking a bit a the mailing list, I realized I might be a bit under > qualified to package GitLab myself. I’m a fairly new programmer, but I’m very > interested in giving back to the community. A big part is that it would

Re: GitLab packaging

>> guide me in the right direction if I’m using it incorrectly. >> > > Hi Daniel, > > Good to see your interest. You can start from > https://wiki.debian.org/GitLab/Packaging > > But steps would be very similar to Diaspora packaging which has more > documentation

Re: GitLab packaging

e point, but I also don’t want to take too > much on and waste anyone’s time. > > Daniel > > PS. This is the first time I’ve used a mailing list, so feel free to > guide me in the right direction if I’m using it incorrectly. > Hi Daniel, Good to see your interest. You c

Re: Re: GitLab packaging

Hello all: After looking a bit a the mailing list, I realized I might be a bit under qualified to package GitLab myself. I’m a fairly new programmer, but I’m very interested in giving back to the community. A big part is that it would take me a while to learn Ruby if that’s what is required to

Progressbar for GitLab Packaging

have started a wiki page for co-ordinating the packaging of GitLab - https://wiki.debian.org/GitLab/Packaging I don't know if one already exists. So, please comment on that also. -- Regards, Balasankar C http://balasankarc.in "Freedom is never easily won, but once established, fre

Re: GitLab packaging

(artwork, and so on). > > For the omnibus packages we already have a split directory structure, > see > https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md#directory-structure > Please let us know what else you need. > >>> I think packaging a big rails app is

Re: GitLab packaging

On Wed, Mar 26, 2014 at 04:06:28PM +0100, Sytse Sijbrandij wrote: > >> There will probably also be the need to add configuration points to > >> GitLab to accommodate a different directory structure, we are open to > >> help with this. > > > > Yes, having global constants to be able to change easil

Re: GitLab packaging

e we >> can set up a mailinglist for this (similar to the Fedora list at >> rpm-gitlab-l...@lists.clefos.org). > > I think we can keep discussion on debian-ruby@lists.debian.org. A large > number of packages are common to other Ruby projects, and I guess that > discussions on Gitlab pac

Re: GitLab packaging

ilar to the Fedora list at > rpm-gitlab-l...@lists.clefos.org). I think we can keep discussion on debian-ruby@lists.debian.org. A large number of packages are common to other Ruby projects, and I guess that discussions on Gitlab packaging will expose issues that would occur for the packaging of other

GitLab packaging

Dear people, I'm the CEO of GitLab.com and would like to offer our help to package it. I read the conversation about packaging GitLab for Debian in: Current status https://lists.debian.org/debian-ruby/2014/03/msg00027.html Stepping down https://lists.debian.org/debian-ruby/2014/03/msg00030.html E

Re: current status of GitLab packaging

Hello everyone, On Thu, Mar 06, 2014 at 11:53:45 +0100, Cédric Boutillier wrote: > Here is some information about where we stand today in the process of > packaging GitLab. I'm sure most of you are already aware of this, but I haven't been able to keep up with the packaging of Gitlab. Mostly beca

current status of GitLab packaging

Dear all, Here is some information about where we stand today in the process of packaging GitLab. GitLab has quite a lot of dependencies. Those are Ruby gems listed in the Gemfile in the source code. And these gems have themselves dependencies, having themselves dependencies... A graph of depend