On Thursday 20 September 2007 04:44, Ben Finney wrote: > Atsuhito Kohda <[EMAIL PROTECTED]> writes: > > Recently, perhaps mainly due to so many spams, it looks common to > > write email address like "foo at some.where" etc. and I wonder if it > > is acceptable to use such modified email address in Upstream Author > > field of debian/copyright file. > > IANADD, but would argue that making the copyright file, including any > email addresses, machine-parseable is a worthwhile goal. This goal > precludes munging the address.
I disagree on this view. The file is freeform, so anything 'parsing' it will end up getting a list of email addresses that are included in it without relevant context. And even if you have such a list, what are you going to do with it? I do not to see a usecase for automatically mailing upstreams based on debian/copyright... seems quite undesirable even. Upstream clearly has an intent in preventing spam through obfuscating their email. That's their choice, and I don't think they'll be happy when we undo that, without having some really convincing goal to actually use that email address. We're currently not parsing anything email related in that file, so let's respect upstream's wishes. What do you think we have to gain by overruling them? Thijs
pgpTkghQXNcBq.pgp
Description: PGP signature
