Aegir core team

The Aegir maintainers are committers that have access to the code. They are responsible for specific parts of the project and are general go-to people for various things.

  • cweagans - maintainer of a number of contrib modules, and contributor to several more, as well as patches to Aegir core.
  • ergonlogic - Aegir Project Leader, release engineering, continuous integration testing, community site webmaster, documentation, general bugfixing, ubercart integration co-maintainer, SaaS contrib components
  • helmo - hairy bugfixes and generally great contributions in the queue, maintainer for several contrib components.
  • Jon Pugh - maintainer of devshop hosting/provision, provision_git, and tons of other contrib modules, submitter of many good patches
  • omega8cc - nginx support Provision Sandbox, Barracuda Project

Emeritus members

These members have decided to take a less active role in the project. However, out of respect for them, and all their previous efforts for the Aegir Project (and the hope that they'll become more active again ;), they continue to have commit access.

  • anarcat - debian packaging, crazy late night coding splurges, general goto guy for everything
  • mig5 - testing, release engineering, migressions and general bugfixing
  • Steven Jones - documentation, queueing and contexts stuff, Drupal 7 port, general bugfixing

Other contributors

Those people have given significant contributions to the project but do not yet have complete commit access.

Sorry if your name isn't here and you have done significant contributions!! Feel free to add it or contact us if you feel you have been forgotten...

All contributors of Aegir's history can also be found on's contributors page although that doesn't count patches that were sent in the issue queues.

Past contributors

  • vertice - project founder, retired
  • tbosviel - DNS support improvements
  • univate - views support and batch operations
  • seth.vincent - Google Summer of Code student, working on D7 port and DNS editor. Sandbox

How to join the core team

If you are interested in joining the core team, you should provide us with valuable patches or contribute to the issue queues significantly. The core team has access to all core git repositories for writing, so you will need to prove that you can provide good quality code through the issue queue. We usually notice such people and welcome them in the team directly, but you should also feel free to ask to join if you feel you are worthy.

Aegir Co-maintainer Criteria

The Aegir core team is somewhat selective about inviting co-maintainers. This is largely due to the complexity of the project, and the crucial functionality it plays for many of its users.

Below we detail the responsibilities of co-maintainership (apart from just commit rights to git), as well as what criteria we feel are important for new team members. Co-maintainership involves taking responsibility for the project's overall well-being. This includes:

  • Participation in the community: issue queues, IRC, community site, etc.
  • Technical involvement: bug-fixing, patch testing, new feature development and roadmap/architecture planning, release engineering, etc.
  • Maintenance of project infrastructure: debian repos, community and API sites, Jenkins, etc.
  • Community outreach: presentations and BoFs at Camps and Cons, blogging, screencasts, etc.

While this isn't an exhaustive list, nor are all these activities required for membership in the core team. We're looking for new team members with regular, productive activity in one or more of the above domains. This essentially boils down to two criteria:

  • code/patches submissions (quality over quantity) and
  • demonstrated interest in the project.

If you believe that you'd make a good addition to the core team, don't hesitate to contact any of us to discuss it.

Aegir Project Leadership

With the recent transfer of leadership, the project's core team has decided to move towards a more democratic model, to ensure clearer structure and smoother transitions in the future. Debian is a shining example of this (in particular, the DPL), and so we will model our leadership position(s) after them.

The Aegir Project Leader (APL) is the official representative of the Aegir Project. They have two main functions, one internal and one external.

In the external function, the Project Leader represents the Aegir Project to others. This involves giving talks and presentations about Aegir and attending trade shows, as well as building good relationships with other organizations and companies.

Internally, the Project Leader manages the project and defines its vision. They should talk to other Aegir developers, especially to active contributors to Aegir core, to see how they can assist their work. A main task of the Project Leader therefore involves coordination and communication.

Obviously, we're a much smaller project than Debian, and so we're adopting a pretty minimalist organizational structure. That said, Debian has many other structures in place to ensure the ongoing health of a large community driven project. As the Aegir Project grows, we can appropriate additional tools to overcome any new challenges that arise.

Finally, the responsibilities inherent in the APL role are not exclusive to it. That is, just because it is the Project Leader's job to give presentations and coordinate our efforts, other community members should not hesitate to continue doing so themselves.

How to welcome someone to the core team

Once someone is deemed worthy of joining the core team, you (a core member) should make a proposal on the core mailing list to welcome the new developer. Subject should clearly state the proposal and give ample time for other developers to chime in. Usually all core team members should give their explicit approval as we try to reach consensus (and usually do) over proposals.

Once the member is approved on the mailing list, you should follow this checklist: