repo.or.cz is not currently looking for volunteers who would like to help running and developing the site (we had too much feedback!) We are
currently in the process of setting up the first collectively run admin team to
replace Petr Baudis as the sole site maintainer and developer.
Who do we want:
- People with motivation to help out one of the largest public Git hosting
sites who don't mind helping out some poor user once in a week and/or want
to enhance repo.or.cz services and features while also fixing few bugs
in the process
- People with reasonable experience in all of UNIX/GNU, shell scripting,
Perl and Git itself
- Trustworthy persons with no bad history and preferrably some existing
open-source community involvement - ideally (but not required) in the Git
- People who don't mind working in a team, are willing to put up with
a perfectionist pasky at the beginning
and can get used to thinking thrice before doing something on the live
What will you do (at least some of... ;-):
- Supporting users over email, possibly IRC. We get one support issue
per week on average, usually project deletion requests.
- Other maintenance tasks - checking if jobs don't get stuck, possible
project breakage, reviewing+applying patches from users, monitoring
bogus content tags usage, cleaning up badly created projects and handling
server overload (all fairly rare occurences)
- Implement gadgets to ease your maintenance tasks- could be e.g. issue
tracking system or ability for users to remove projects themselves.
- Fix repo.or.cz bugs. E.g. the mirroring process gets stuck once in a while
on misbehaving mirror source, and sometimes objects get lost during gc that
- Implement cool new features. E.g. something from the
Girocco TODO list,
cleaning up and adding support for more mirroring source VCSes, user experience
improvements, maybe some interesting statistical analysis...
What's in it for you:
- Most importantly, good warm feeling in your heart! ;-)
- Chance to play with a reasonably large site and try out interesting
- Learning more UNIX/shell/perl/git on a very practical project.
- Getting more involved in the Git development community, getting general
experience with OSS development of something that's actually immediately useful.
- Low and totally flexible time demands.
- Nice CV point to be sure!
Are you interested? Please apply at email@example.com.
(Note: If you want to look at the current repo.or.cz codebase or even
deploy a copy locally to play with, just look at girocco.git.)
TODO: Make everything below this line less public. ;-)
So far, no huge deal I guess.
Volunteers can see what will they work with.
The Admin Team Plan
These are pasky's ideas on how to set up the admin team and transfer
control to it:
- Gather feedback and confirmation from volunteers that already applied.
- Set up firstname.lastname@example.org alias plus internal mailing list.
- Create accounts for new recruits with sudo access to the 'repo' account.
(We just got a complete tree backup while migrating, so we can be liberal
and relatively trusting at the beginning. ;)
- Let the new recruits start helping out and self-organizing. There will
be probably need to create a deployment staging area and some cooperation
rules to avoid race conditions, but I'd prefer the new admin team to already
figure that out for themselves.
- Give the two or three most experienced members root access after a while.
- Pasky would like to stay in the loop and keep veto power for a while
to protect the site from some bad deterioration or major turnovers.
New admins rules:
- Do not be shy doing stuff. If you are not doing it, noone else probably
is either. Just send a mail when you start doing something, and another
when you are done.
- Document everything you do outside of your sandbox. On the mailing list
for starters, we can figure out better book-keeping later. Reply on admin@
to all user requests that you have handled.
- Ask for consultations and acks whenever you have shadow of doubt.
- Think trice. Avoid doing unrevertable things!
- Think once. Make plenty of non-destructive quick experiments to learn about
- No abuse. We need to nurture the goodwill of our connection sponsors.
No peer-to-peer filesharing!
- Do not use Ctrl-C to quit screen. You could kill a task!
- All infrastructure is owned by the repo user, and runs as repo (except
web scripts, suexec is not set up - for now?)
- Always work under the shared screen so others can check out who
is working on what: .
screen -x repo/admins, this will get you to
our shared screen session. jobd (updating mirrors, running gc) and taskd
(creating mirrors, push notifications) run in the first two windows. Shells in
screen are owned by user
- Live copy lives in
chroot jail for pushing is in
~/j, codebase is in
- Do not work directly in
~/repo. If you want to
edit files, clone
Girocco.git and push after committing (and
verifying) your changes locally.
- To update the live copy,
(should fast-forward), then
This will OVERWRITE complete
New admins checklist:
- Make yourself a
.forward file so that you receive admin@ mail.
- Add yourself to the admin team page,
which is also a nice way to get comfortable with our girocco setup.
- Send a short introduction to email@example.com.
- Take a look at the list of TODO items in rorcz branch of girocco. Perhaps you could tackle something right away?
- If you are bored, ask for some ideas! Or perhaps we can bounce to you some requests we did not have time to deal with. Don't be shy!
- Please check periodically that the jobd in screen window 0 is not stuck.
- Try to deal with something from the TODO list.
Removing a project:
- Philosophically, I'm not too happy to remove a project unless there's
a good reason like turning it to a mirror or some consolidation or legal
reasons (or it's almost empty); I believe in archiving everything. This position
can change if others disagree.
mv /srv/git/project.git /srv/git-recyclebin/ - move forks
properly within the hierarchy, let pasky know in case of permissions problem
(ALWAYS remove by mv to recyclebin, never by deleting the directory for good)
vi ~repo/j/etc/group, find the line for the project and
remove it from the file. Don't keep the file open to avoid races.
Backups: There is a nightly rsync cronjob that backs up metadata to another
machine (which is now physically in the same building so we should do something
better long-term). No backlog is kept!
Other things running on the server:
- Pasky stores some harmless data on the server. He may run some niced
computations time by time if he thinks the server is really idle.
- There is a mailman instance running on the server that serves also
a beekeepers' mailing list.
- The server provides slave DNS services for few domains.
- There is a compendium of RSS->IRC gateways for couple of Czech news servers.
- A tiny IRC bot + assorted services.