Replicant » Replicant infrastructure

h1. ContribRepositories

h2. Requirement

At the time of writing, only GNUtoo and Putti are able to do that, as they are the only people in the admin group in gitolite (this can be changed in conf/gitolite in the gitolite repository).

h2. Procedure

First you need to clone the gitolite repository:

<pre>

git clone ssh://git@git.replicant.us/gitolite-admin

</pre>

Then you need to modify this repository to for adding a new user. In this tutorial we'll add the @newuser@ user.

Here's an example of modification to do that:

<pre>

diff --git a/conf/gitolite.conf b/conf/gitolite.conf

--- a/conf/gitolite.conf

+++ b/conf/gitolite.conf

[...] 

+repo contrib/newuser/..*

+    C       =   newuser

+    RW+     =   newuser

+    R       =   @admins daemon

+

[...]

diff --git a/keydir/userkey2/newuser.pub b/keydir/userkey2/newuser.pub

new file mode 100644

index 0000000..f8d32aa

--- /dev/null

+++ b/keydir/userkey2/newuser.pub

@@ -0,0 +1 @@

+ssh-rsa [...]

</pre>

Then it would be a good idea to explain a bit why we need to do that (for instance newuser wants to work on Replicant 15, or newuser wants to add support for 6G devices) in the commit message.

Once the change is pushed, I'm unsure if the newuser directory also needs to be created or not. 

If it does, the following commands could take care of it:

<pre>

su -l git

mkdir -p /var/lib/gitolite3/repositories/contrib/newuser

</pre>

The new user should then be able to create new repositories just using git push at the right address.

h2. Caveats

* Note that pushing to an address with a typo (like @ssh://git@git.replicant.us/contrib/newuser/hardware_replicant_libsamsung-pic@ instead of @ssh://git@git.replicant.us/contrib/newuser/hardware_replicant_libsamsung-ipc@) will create the @hardware_replicant_libsamsung-pic@ repository.

* Also I don't know how users can delete repositories, but people with root access to the VM (at the time of writing, GNUtoo and Putti) can still do that.