| Arusha Project |
| Sidai (policy) |
| Ideas, etc. |
| Multiplatform-ism |
| Good namespaces |
| Source-ism |
| Design, etc. |
| ARK strategy |
| Blessed names |
| DChunks |
| Security model |
| Config mgmt |
| Tools |
| Sidai tools |
| ARK templates |
| Sidai pkg mgmt |
| *-config packages |
| Proto-packages |
| Sidai host mgmt |
| Sidai user mgmt |
| Sidai mailing-list mgmt |
| See also: |
| Sidai how-to, etc. |
| Sidai culture and opinion |
| Hosted by |
Sidai team: how it manages mailing-lists
This page relates to Sidai-style maillist things.For normal mailing-lists, we use Mailman, in the conventional way. That's separate from what we're talking about here.
A Sidai maillist is a mailing list that is somehow tied to your system infrastructure. Things like, ``Every user should be on the sys-announce mailing list''. Or ``The blah-people list is everyone in the Unix group blah''. Or ``Everyone on the such-and-such list should be a current employee.''
Implmentation: we still use Mailman to do the business; but we use ARK code to maintain the subscriber lists.
A maillist's status field
How we use the <status> field:- pending:
The maillist is not yet fully active, but will be
soon.
- active:
The maillist is `live' and in a state in which the ARK
machinery can be used to invoke methods on it.
- deprecated:
The maillist was once active, and is still valid, but it's
on its way out. (It's a zombie.)
- external:
The maillist is not in the ARK system at all (no methods to run).
We keep a little information about it in ARK land, and can access
that if we try hard.
- historical: The maillist is not in use at all. We may be retaining its records for historical purposes.