[rpm-gitlab-list] Reminder of tomorrow's meeting

Achilleas Pipinellis axilleas at axilleas.me
Wed Apr 2 19:15:19 EDT 2014

A reminder that we will be having our bi-weekly meeting tomorrow,
2014-04-03 at 19:00 UTC in #fedora-meeting on the freenode network.

Suggested topics:

#topic Documentation

Gather in a page all the needed information about this effort. List of
members, info about the packaging process, mailing list, irc meetings, etc.

#topic Proven packagers

Who from the team is a proven packager and what kind of packages they
have experience with. Roles for folks that are not yet packagers but
wish to help. Packagers from other areas will need to read the ruby
guidelines. I can help with that by writing a guide (half is finished)
and have it ready by next week.

#topic Identify gems to be packaged

There are ~160 gems needed for GitLab and that's counting only the
runtime dependencies. Half of them are already in the Fedora repos but I
have no number for the RHEL repos.

One way is to use the list extracted from my script, the other is to
pick gems from the Gemfile and work down their dependency chain.

#topic Packaging workflow

Coordination is the key. What really helped me last year was a trello
board where I could manage the flow of my process. For those not
familiar with trello, it is a board promoting the kanban method for
development [0]. I took the liberty and setup a board some time ago for
this purpose [1]. We can discuss if it suits us. I also set up a group
at GitLab Cloud [2] where we could store the SPEC files, make unofficial
reviews prior to submitting to bugzilla, etc. Any other suggestions on
how this could be used are welcome :)

#topic Make quality packages

I guess we are all on the same page here. I'm only mentioning this
because almost every gem comes with a test suite. Although it is not
mandatory to include it in the spec file, be sure that in the review
request you will be asked to include it. That, sometimes requires
additional time as you might have to talk to upstream and solve any
issues that may arise.

#topic Use copr

http://copr.fedoraproject.org will be useful for setting a test repo. It
supports all maintained versions of Fedora (rawhide,19,20) as well as
epel (5,6,7). Discuss the details.

#topic Update/upgrade process

Packaging GitLab is one thing, maintaining it is a whole other issue.
We should really think this through. GitLab is in rapid development and
it won't stop anytime soon :) I don't think it's easy to follow the
monthly release cycle, we'll have to agree on which releases we'll
perform updates. Rawhide (the development branch) can always have the
latest versions of everything, but in stable releases of Fedora we want
stable packages.

There is also a thought of building a tool like CI for RPM builds,
testing if an upcoming release still builds. But that's in the long run.

That's all that came to mind right now, see you tomorrow!

[0] http://en.wikipedia.org/wiki/Kanban_board
[1] https://trello.com/b/RVgqDlw8/gitlab
[2] https://gitlab.com/groups/fedora-ruby

GPG : 0xABF99BE5
Blog: http://axilleas.me
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xABF99BE5.asc
Type: application/pgp-keys
Size: 2706 bytes
Desc: not available
URL: <http://lists.clefos.org/pipermail/rpm-gitlab-list/attachments/20140403/9bdb5ff4/attachment.bin>

More information about the rpm-gitlab-list mailing list