How does Arusha Project collaboration work?
ARK collaboration works by sysadmin “teams” making some of their “added value” available to others, typically as “packages”. A team then assembles their own solutions from all of the available material, including their own and including tweaks they’ve made to others’ stuff. The core developers “control” the base team, `ARK’, which provides the core code that all Arusha teams will build on. `ARK’ is a mechanism-not-policy team. We (the core developers) also have a separate how-we-think-you-should-do-it (policy) team, called `Sidai’. For example, we think most people should use a “hubs-and-clients” sendmail configuration package. If our Sidai team had made such a sendmail configuration package, you could use it, or not. Maybe you prefer qmail. Maybe you think we’ve fluffed the sendmail configuration. Maybe you want to make one of your own. You can offer yours “in competition” to our configuration. A lot of people communication will be required for this process. Certain teams will have a
