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 have an awesome community here. I’m excited! I’m going to try and stick with it. I know it might get hard though since things at work will always be more pressing. So, I think that’ll be a big part of it too: I need to make sure I schedule my time appropriately.
Daniel
————
Daniel L. Polanco Fledgling Programmer | Perl | C++
On 4 Oct 2014, at 2:23 pm, Daniel Polanco < dlpolanco05@gmail.com> 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 take me a while to learn Ruby if that’s what is required to create a package.
Having said that, I wanted to throw my name out there and see what you all thought. I’m very willing to learn new things, and I want to learn how to package debs at some point, but I also don’t want to take too much on and waste anyone’s time.
Hi Daniel. Having just started down this path myself I can say that everyone else has forwarded you some good links. I would start off relatively easy and try packaging up a couple of the dependent packages for gitlab. Looking at your list of dependencies perhaps crass, kaminari or nokogumbo. Those packages seem small enough and aren’t part of some larger project (e.g rails) that they’re easy to understand. I’ve set up a little build environment using Jenkins and Docker as the number of packages to keep track of can get bigger if your dependent packages have other build or test dependencies of their own. Being able to just click a link to rebuild and test a package is very useful. Regards, Tim.
|