--On onsdag, januar 11, 2006 08:13:57 -0600 Spencer Dawkins
<spencer@xxxxxxxxxxxxx> wrote:
Not sure if this is in-scope for PESCI or not...
... but there are sensible people on this list, so let's just chat....
I had a coversation with Brian in the Vancouver timeframe about some
process ID (doesn't matter which), during which Brian asked me,
(paraphrasing) "given that publishing this process document as a BCP/RFC
makes it harder to modify, and increases the expense of publishing it at
all, should we just publish this process document on a website and
declare victory?".
We already have some process specs (including some "rfcxxxxbis" process
specs) that look like they will live forever as drafts, including drafts
on websites. It might be lovely to figure out how to know whether a
process ID should be published in archival form or not, and, if not,
where it SHOULD be published, in a consistent way.
I'd LOVE to have a specification for a publication mechanism that allows:
- the leadership to publish a revised version "whenever they have to"
- me to get at the current version extremely easily
- me to be notified when it changes (announcement, RSS, changelog...)
- me to be able to get at any older version with a little dilligence
A set of web pages with CVS version control, links to previous versions and
an open subscription "notification" mailing list would satisfy approx 95%
of my needs....
(I run a CVS with a notifier script; I'm pretty sure the web interface part
exists too).
SHOULD be easy to set up....
Harald
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
