
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 24, 2007, at 2:02 AM, Jeff Breidenbach wrote:
Which brings me to suggestion #2, which is go ahead and write an RFC on how list servers should embed archival links in messages. This sounds like an internet wide interoperability issue as much as something mailman specific. Why not come up with a scheme usable by all list servers? And also describe a specification third party
archival services can comply to. Besides, I've always wanted to help write an RFC. If we go that route, it would be good to get input from a
range of people - one person I'd suggest is Earl Hood, author of mhonarc.
I've always thought that an RFC-like spec that describes how a
generic mailing list manager would interoperate with a generic
archiving service is the way to go. I've written up a somewhat more
formal spec of what I've implemented MM3 currently here:
http://wiki.list.org/display/DEV/Stable+URLs
If this looks good, I'd be happy to approach some of the related
communities to try to get buy-in.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRqZIjHEjvBPtnXfVAQLK9AP/VQveYtFuZhJam9TITYBuMyc8pig7nqDt efn4DIXhZhgtqBQ58/TgEFZnTkKfiZ1HLdoovrQye8HdKZmuAd+SJrOkq/aO9fIC ZgaV5HYBD7TcnQuO2z5eRuK3IY7FpWoeZrn/a6sxBObsaSOrOTjhqs1gv5go24d3 8CmG/bB9LTo= =EyoU -----END PGP SIGNATURE-----