On Friday, February 23 at 03:37 PM, quoth Amitai Schlair:
This vision of a Qmail Patch Repository is probably, of course, an
unattainable pipe-dream. But it would still be awfully nice.
Agreed. How should it work? One from-the-hip idea: select a handful
of knowledgable people and make them admins of a SourceForge project
which keeps the latest knowledgable-people-approved patches under
source control.
I was thinking of something more sourceforge-ish itself, so that a
person could subscribe to a given patch (and get notified when it
updates) and patch maintainers could have the power to keep their
patch up to date. A good example of what I'm thinking of would be the
vim.org scripts database.
http://www.vim.org/scripts/script_search_results.php
It would, however, need a good organizational scheme, with multiple
categories and script tags, so that you can find scripts by file,
author, RFC (if any), and other keywords (i.e. "authentication" or
"rcpt check").
Sourceforge, though, is certainly always good for free bandwidth.
Collecting scripts and grouping them and making them work together,
though, is more labor intensive than "hard" per-se. The real hat-trick
would be creating something that qmail patch writers *want* to use to
publish/host their patches. If it's just "My Little Patch Archive",
it'll be pretty pointless.
~Kyle
--
Mathematicians stand on each other's shoulders while computer
scientists stand on each other's toes.
-- R. W. Hamming
pgp6Fx9w2oxda.pgp
Description: PGP signature
|