public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
* [B.A.T.M.A.N.] RFC: Migration to a new git server backend
@ 2012-07-21 23:43 Sven Eckelmann
  2012-07-23 12:08 ` Sven Eckelmann
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Sven Eckelmann @ 2012-07-21 23:43 UTC (permalink / raw)
  To: b.a.t.m.a.n

[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]

Hi,

maybe some of you have seen that I talked in the channel to Antonio whether we 
should migrate to a different solution to serve our git repositories. This is 
(in my opinion) a good idea because gitosis [1] (the software that we are 
currently using) isn't maintained anymore and will be dropped [2] in the next 
version of Debian. My preferred replacement is gitolite [3].

I already talked with Simon and discussed what side effect this could have. 
Maybe side effects is not the correct word to describe it... lets call it 
options. Gitolite allows to define access rights for refs. For people that are 
not familiar with the storage in git: You can for example say that people can 
only commit to branches with a specific prefix.

Just to give an example. We want that only the release team can create tags -> 
refs/tags/ is only marked for the release team as read-write. Now we have more 
interesting features like ordex is only allowed to write in branches starting 
with ordex/ -> refs/heads/ordex/ is marked as rw for ordex.

Now the question is: Do we want to use this feature or not. We had following 
ideas:

1. 1 repository per project

   use only one repo for each project (batman-adv, batctl, batmand, ...) and
   use branch namespaces for individual users:
   * master, next, maint for the main stuff
   * ordex/ (for example ordex/dat), hundeboll/, ... for users
   * tags only for release team

2. 2 repositories per project

   use one official repo for each project (batman-adv, batctl, batmand, ...)
   and one for other people
   * master, next, maint in both repos (synced from the main one)
   * ordex/ (for example ordex/dat), hundeboll/, ... for users in the second
     repo
   * tags in both repositories allowed (but in the second repo only with
     user prefix)

3. 1+x repositories per project

   Keep everything like now
   * master, next, maint for the main stuff
   * each user has his own copy of the main repo in his user folder
   * tags can freely commit in his own repo

Special repositories with big differences like linux-merge are kept in a 
special repository.

Any other suggestions? Do you prefer any idea? Please also add other ideas 
like "user folder names for idea 3 have to start with a ~ and non-user folder 
names have to start with a +".

Kind regards,
	Sven

[1] https://github.com/tv42/gitosis
[2] http://packages.qa.debian.org/g/gitosis/news/20110909T215628Z.html
[3] https://github.com/sitaramc/gitolite

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-07-29 18:29 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-21 23:43 [B.A.T.M.A.N.] RFC: Migration to a new git server backend Sven Eckelmann
2012-07-23 12:08 ` Sven Eckelmann
2012-07-25 20:22 ` Simon Wunderlich
2012-07-29 17:49 ` Sven Eckelmann
2012-07-29 18:17   ` Marek Lindner
2012-07-29 18:29   ` Antonio Quartulli

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox