Maintainer creation policy

It sounds to me like it would be a better solution to make a person
object maintain itself in the absense of any other maintainer,
basically changing to rules such that:

	A person object can have either
		a maintainer
	or
		an authentication mechanism (password/mailfrom or pgp)

That would prevent a doubling of the number of records in the database.

--
Poul-Henning Kamp             FreeBSD coreteam member
phk at FreeBSD.ORG               "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal