On Fri, 12 Nov 1999, J. op den Brouw wrote:
> Date: Fri, 12 Nov 1999 16:48:02 +0100 (MET)
> From: "J. op den Brouw" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [htdig3-dev] About HtDig Patch Sites
>
>
>
> In his e-mail on 17 mar 1998
> (http://www.htdig.org/mail/1998/04/0017.html),
> Joe R. Jah ([EMAIL PROTECTED]) sort-of
> announced his unofficial patch site. Some weeks ago, Gilles released a
> patch and it was put on the htdig server. Needless to say, that
> people are looking at two different places for patches. The
> htdig dev site point to Joe's site, whereas Gilles placed his
> patches under http://www.htdig.org/files/contrib/other/.
> Anyway, this would not need to be a problem as long as the two sites
> use the same name.
>
> While in conversation with Geoff, the idea came to life to let our
> minds go on:
>
> - Should we have to sites:
> If yes, should they be an exact copy.
> If not, which one will go on?
I think it's a good idea to have alternative sites in case one becomes
unreachable. We can better coordinate, though, to have the patches
present on both sites;)
> - Naming conventions.
I am all for some formal naming convention, documentation, etc. that makes
the job of the person who writes the patch easier because s/he has certain
concrete steps to take; it also makes the job of the site maintainer
easier because s/he doesn't have to try to invent relevant patch names,
descriptions, etc; and no two persons end up with the exact same results;(
> - "Tested", "Untested", "Recommended",
I think this also falls in the patch author's lap, so s/he can describe
the tests in the comments, docs, readme's, etc.;)
> "Do-not-use-unless-you-really-have-problems".
> - Which of the patches go into the next release.
I think developers as a whole can decide those two items, and the
maintainers can post them specially if the patch closes security holes.
I have an open mind on the whole subject and look forward to others'
ideas.
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah [EMAIL PROTECTED]
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
