Re: MaintainerDatabase Copyright
srivasta@datasync.com (Manoj Srivastava) wrote on 04.10.97 in <[🔎] 87zpopz5n7.fsf@tiamat.datasync.com>:
> ps. How would YOU like your email address to be changed to
> user@tiamat.datasync.com? or to user@Yes.We.Spam.com?
So what? Where's the problem with that, exactly?
Somehow, I can't see it.
As to all the talk about authors - a maintainer of a database cannot have
more than a collection copyright on that database; the information in it
belongs to those that provided it (as long as it's not public anyway).
"Author" is, IMO, a misleading term in this area.
As far as I'm concerned, the only problem with that database is privacy
(and the current set of data doesn't even touch the areas where I'm
concerned about privacy).
So, we want different privacy levels - at least debian-private type
privacy and public, maybe also an even smaller circle of people who know
stuff like emergency reachability or data so they can externally verify
someone's identity, if people don't want to broadcast stuff like that to
all developers.
As to changeability of the data set, so what? PGP-sign the original, so
people can verify if they _have_ the original, and forget about the
"problem".
Don't forget that everybody can generate a similar dataset already, with
whatever data (s)he wants.
Also, as to email harvesting, there are other methods to get at the same
information.
I just fail to see that there is anything at all gained by these
restrictions, except maybe a false sense of security.
MfG Kai
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: