Re: [Pesci-discuss] Hoping Pesci is still flopping around...

"Lucy E. Lynch" <llynch@darkwing.uoregon.edu> Thu, 12 January 2006 04:29 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ewu5O-0000Iq-7h; Wed, 11 Jan 2006 23:29:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ewu5M-0000If-Qq for pesci-discuss@megatron.ietf.org; Wed, 11 Jan 2006 23:29:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19017 for <pesci-discuss@ietf.org>; Wed, 11 Jan 2006 23:27:56 -0500 (EST)
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwuCP-0006jv-4S for pesci-discuss@ietf.org; Wed, 11 Jan 2006 23:36:33 -0500
Received: from darkwing.uoregon.edu (llynch@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.13.5/8.13.5) with ESMTP id k0C4T4bx022529; Wed, 11 Jan 2006 20:29:04 -0800 (PST)
Received: from localhost (llynch@localhost) by darkwing.uoregon.edu (8.13.5/8.13.5/Submit) with ESMTP id k0C4T3JA022523; Wed, 11 Jan 2006 20:29:04 -0800 (PST)
Date: Wed, 11 Jan 2006 20:29:03 -0800
From: "Lucy E. Lynch" <llynch@darkwing.uoregon.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Re: [Pesci-discuss] Hoping Pesci is still flopping around...
In-Reply-To: <891203CD54336170FB609658@svartdal.hjemme.alvestrand.no>
Message-ID: <Pine.GSO.4.58.0601112021090.2920@darkwing.uoregon.edu>
References: <099201c6113c$6aaf4860$0500a8c0@china.huawei.com> <43C264E0.10101@zurich.ibm.com> <Pine.LNX.4.64.0601091740120.6192@netcore.fi> <43C506A5.4020306@zurich.ibm.com> <03fc01c616b9$455d6fb0$d0087c0a@china.huawei.com> <891203CD54336170FB609658@svartdal.hjemme.alvestrand.no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: PESCI Discuss Mailing List <pesci-discuss@ietf.org>
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process Evolution Study Committee of the IETF discussion <pesci-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pesci-discuss>
List-Post: <mailto:pesci-discuss@ietf.org>
List-Help: <mailto:pesci-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=subscribe>
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org

On Wed, 11 Jan 2006, Harald Tveit Alvestrand wrote:

>
>
> --On onsdag, januar 11, 2006 08:13:57 -0600 Spencer Dawkins
> <spencer@mcsr-labs.org> 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....

substitute subversion for cvs and you're there...
http://www.edgewall.com/trac/

for example - http://svn.nuxeo.org/trac/pub/wiki

I set it up under Fedora core 4 (.9.3 w/ webadmin) in under a day -
still struggling w/ a freeBSD .9.2 install (webadmin doesn't work
for me).


>                         Harald
>
>
>
>
>
>
> _______________________________________________
> Pesci-discuss mailing list
> Pesci-discuss@ietf.org
> https://www1.ietf.org/mailman/listinfo/pesci-discuss
>

_______________________________________________
Pesci-discuss mailing list
Pesci-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/pesci-discuss