From Fedora Project Wiki
(Created page with '{{header|infra}} = FIG Job Description: sysadmin-hosted = Members of sysadmin-hosted will be tasked with maintaining the collaborative repository environment for upstream devel...')
 
No edit summary
 
Line 32: Line 32:


== Current tools ==
== Current tools ==
Git version control system ([http://git-scm.com/documentation Git docs])
* Git version control system ([http://git-scm.com/documentation Git docs])
Mercurial version control system ([http://mercurial.selenic.com/guide/ Hg guide])
* Subversion version control system ([http://subversion.apache.org/docs/ Svn docs])
Trac project management system ([http://trac.edgewall.org/wiki/TracGuide Trac docs])
* Mercurial version control system ([http://mercurial.selenic.com/guide/ Hg guide])
Subversion version control system ([http://subversion.apache.org/docs/ Svn docs])
* Bazaar version control system ([http://doc.bazaar.canonical.com/en/ Bzr docs])
Bazaar version control system ([http://doc.bazaar.canonical.com/en/ Bzr docs])
* Trac project management system ([http://trac.edgewall.org/wiki/TracGuide Trac docs])





Latest revision as of 21:03, 15 September 2010


FIG Job Description: sysadmin-hosted

Members of sysadmin-hosted will be tasked with maintaining the collaborative repository environment for upstream developers of Fedora components. Members of sysadmin-hosted are responsible for creating new project environments and repos. Members of sysadmin-hosted may be called on to fix and modify branches, change SCM engines and remove projects.

Level of commitment

Average 4 hours per week

Expected duties

  • Creating new top level Fedora Hosted projects
  • Maintain and troubleshoot source code repositories in multiple version control systems
  • Performing repo level operations on existing projects
  • Manage disk space for repo storage
  • Manage Trac projects and integrations with various SCM systems
  • Troubleshoot remote access issues
  • Working with package maintainers on SCM issues
  • Handle SCM admin requests
  • Migrate projects between SCM systems

Required skills

  • Experience with Git
  • Experience with Subversion (svn)
  • Experience with Mercurial (hg)
  • Experience with bazaar (bzr)
  • Experience with Trac
  • Experience managing, deploying or maintaining at least one of the tools in current use
  • Expert level differentiation between humor and reality (even when humour is spelled with too many u's)
  • Experience with mid-level system administration tasks and troubleshooting (user / filesystem permissions, remote connectivity, vhost configuration)

Suggested skills

Current tools

  • Git version control system (Git docs)
  • Subversion version control system (Svn docs)
  • Mercurial version control system (Hg guide)
  • Bazaar version control system (Bzr docs)
  • Trac project management system (Trac docs)


Note.png
Adding tools
Names should be links to Fedora tool URL and a link to the upstream project documentation should also be included.

Typical Tasks

Hosted projects tickets