Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: proposal: upgrade Gnus Git repo to GitLab server
Date: Wed, 11 Nov 2015 06:37:11 -0500	[thread overview]
Message-ID: <87oaf0sr6g.fsf@lifelogs.com> (raw)

Lars and others, I'm putting this out for the whole list:

I think GitLab would be a good choice for the Gnus Git repo.

The community edition is free according to
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/LICENSE

It offers many features we could use. The downside is that it's probably
best to install it on a dedicated server; it's a Ruby on Rails app. It
can be installed via packages, in any case:
https://about.gitlab.com/downloads/ offers CentOS, Debian, and Ubuntu
packages. Plus Raspberry Pi Raspbian, of course, for that very demanding
group of 3 people :)

I think it would make some things easier, especially pull ("merge")
requests for quick changes because you can edit files right in the web
browser to propose a change. It's also a bit more secure than our
current setup. And most importantly, the current workflows won't change.

Thanks
Ted




             reply	other threads:[~2015-11-11 11:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 11:37 Ted Zlatanov [this message]
2016-01-25 15:22 ` Ted Zlatanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oaf0sr6g.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).