On Feb 23, 2007, at 4:23 PM, Kyle Wheeler wrote:
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").
Okay, next wheel-reinvention-avoidance idea: del.icio.us. It can
assign "description," "notes," and multiple tags to a bookmark. So we
could create a well-named del.icio.us account, share the password
with a handful of knowledgable people, bookmark the good patches in a
descriptive manner, and publicize the del.icio.us URL.
Being merely a collection of references means we wouldn't need any
particular special cooperation from patch authors, though we would
rely on their publishing their patches at stable URLs. Presumably
they'd be willing to do that, if they don't already, in order to be
included in the "repository."
I don't see that del.icio.us can track bookmark destinations for
content updates. But they do provide XML and HTML export mechanisms,
either of which is enough to independently script a periodic scraping
of patch URLs.
Here's a first stab at it:
<URL:http://del.icio.us/qmail.patch.repository>
Thoughts?
|