RE: [bpel4people-editors] Use of CVS to manage specifications

["Luc Clement" <luc.clement@activevos.com>]

Mary: the baseline documents are already in Kavi. 

One point of clarification relating to "is TC members approving documents
from the CVS repository rather than Editor Drafts uploaded to Kavi". The
only source of documentation to be considered by the TC will be the version
posted to Kavi. CVS is intended to be a temp/scratch working area and
nothing more.

-----Original Message-----
From: Mary McRae [mailto:marypmcrae@gmail.com] On Behalf Of Mary McRae
Sent: Friday, April 04, 2008 17:18
To: 'Dave Ings'
Cc: bpel4people-editors@lists.oasis-open.org; 'Luc Clement'
Subject: RE: [bpel4people-editors] Use of CVS to manage specifications

Hi Dave and Luc,

  I understand the concerns of the TC and am working with other members of
the
OASIS staff to come up with something that will meet the needs of the TC as
well
as ensure OASIS rules are adhered to. As TC Administrator it's my job to
make
sure the TC Process is not side-stepped; as someone who has spent 25 years
as a
document technologist I can't imagine coordinating multiple editors without
some
sort of management system in place. Of course I also can't imagine using
anything other than an XML vocabulary/grammar expressly designed for
specifications or other technical documentation. I wish I could snap my
fingers
and invent an entirely new infrastructure in which TCs have a full suite of
tools at their disposal; unfortunately the magic isn't working. The good
news is
that we are working on a new infrastructure which will include the OASIS
Library, a new platform for TC Public Pages, and many other changes; having
feedback from members like yourselves regarding the tools you'd like to see
is
vital to making sure we deploy the right applications.

  I hope to have the guidelines completed early next week (late Mon or
Tues). In
the interim, please upload all baseline documents to the Kavi repository.
The
one flaw that is evident from Luc's description below is  TC members
approving
documents from the CVS repository rather than Editor Drafts uploaded to
Kavi,
but I do want to walk through enough scenarios to make sure we have a solid
process in place that will be repeatable should other TCs wish to take
advantage
of systems such as this.

  Regards,

Mary  

> -----Original Message-----
> From: Dave Ings [mailto:ings@ca.ibm.com]
> Sent: Friday, April 04, 2008 11:05 AM
> To: mary.mcrae@oasis-open.org
> Cc: bpel4people-editors@lists.oasis-open.org; Luc Clement
> Subject: RE: [bpel4people-editors] Use of CVS to manage specifications
> 
> Hi Mary,
> 
> Is there not flexibility for some interpretation here?
> 
> If I strictly read the OASIS policy it forbids downloading a copy of a
spec
> to your laptop for an extended editing session. This is clearly ludicrous
> yet this is what the policy seems to state. What Luc is requesting is a
> more collaborative version of editing working versions on your laptop,
> something that everyone is comfortable with as within policy.
> 
> ... Dave.
> 
> Regards, Dave Ings,
> Emerging Software Standards
> Email: ings@ca.ibm.com
> Yahoo Messenger: dave_ings
> 
> 
> 
>   From:       "Luc Clement" <luc.clement@activevos.com>
> 
>   To:         <mary.mcrae@oasis-open.org>, <bpel4people-
> editors@lists.oasis-open.org>
> 
>   Cc:         Dave Ings/Toronto/IBM@IBMCA
> 
>   Date:       2008/04/03 09:58 PM
> 
>   Subject:    RE: [bpel4people-editors] Use of CVS to manage
specifications
> 
> 
> 
> 
> 
> 
> Re: TCs and SCs may not conduct official business or technical discussions
> 
> <lc> The SC will be reporting all business via mailing list. It will
> conduct all email discussion via oasis mailing lists. And, it will post
all
> minutes, etc via the mailing list and once approved to kavi. I believe
that
> we are 100% compliant in form.</lc>
> 
> Re: Store documents or host web pages on servers or systems not designated
> by OASIS.
> 
> <lc>Notwithstanding the precedent established by the bpel TC and others
> (UDDI for example that I chaired) use of non-OASIS infrastructure such as
> sourceforge has occurred. We need a means by which to collaborate (check
> in/out) documents. We will do so in a way that is visible publicly either
> by allowing access to CVS anonymously at
> http://wsbpel4people.cvs.sourceforge.net/wsbpel4people/ ; anon RSS ;
and/or
> by emailing each other using the bpel4people-editors mailing list to
> indicate that a change has been checked-in and that others editors can
> check out a doc for editing. Kavi does not provide us this capability; CVS
> does. (OASIS should offer CVS...)
> 
> Think of CVS as a sandbox, or our respective mailboxes or personal file
> systems. It only represents intermediate storage/collab area. Kavi will be
> used to host approved versions once the TC has agreed to changes proposed
> by the editors.
> </lc>
> 
> RE: All web pages, documents, ballot results and email archives of all TCs
> and SCs shall be publicly visible.
> 
> <lc>100% compliant - the CVS project is visible to anonymous users at
> http://wsbpel4people.cvs.sourceforge.net/wsbpel4people/ or RSS. We only
> intend to use CVS as a sandbox. Once a set of changes are approved, the
> (Word) revisions are "accepted" and the documents posted to Kavi.
> 
> Net: CVS is a sandbox and a collaborative area where we work on a revision
> of a doc/xsd/wsdl. Nothing more.
> </lc>
> 
> 
> 
> -----Original Message-----
> From: Mary McRae [mailto:marypmcrae@gmail.com] On Behalf Of Mary McRae
> Sent: Thursday, April 03, 2008 21:25
> To: 'Luc Clement'; bpel4people-editors@lists.oasis-open.org
> Cc: 'Dave Ings'
> Subject: RE: [bpel4people-editors] Use of CVS to manage specifications
> 
> Hi Luc,
> 
>   Sorry - but it's against the rules. Since OASIS provides a document
> repository as well as a wiki, all work must be managed there, including
all
> ongoing discussions and interim revisions to documents.
> 
> http://www.oasis-open.org/committees/process-2008-02-05.php#visibility
> 
> "2.8 TC Visibility
> 
> "The official copies of all resources of the TC and its associated
> subcommittees, including web pages, documents, email lists and any other
> records of discussions, must be located only on facilities designated by
> OASIS. TCs and SCs may not conduct official business or technical
> discussions, store documents, or host web pages on servers or systems not
> designated by OASIS. All web pages, documents, ballot results and email
> archives of all TCs and SCs shall be publicly visible."
> 
> Regards,
> 
> Mary
> 
> 
> > -----Original Message-----
> > From: Luc Clement [mailto:luc.clement@activevos.com]
> > Sent: Thursday, April 03, 2008 8:56 PM
> > To: mary.mcrae@oasis-open.org; bpel4people-editors@lists.oasis-open.org
> > Cc: 'Dave Ings'
> > Subject: RE: [bpel4people-editors] Use of CVS to manage specifications
> >
> > Mary: these documents will be held on OASIS servers. We're planning to
> use
> > CVS on sourceforge to collaborate and intend to make periodic drops to
> > Kavi.
> >
> > -----Original Message-----
> > From: mary.mcrae@oasis-open.org [mailto:mary.mcrae@oasis-open.org]
> > Sent: Thursday, April 03, 2008 19:53
> > To: bpel4people-editors@lists.oasis-open.org
> > Subject: [bpel4people-editors] Use of CVS to manage specifications
> >
> > Hi folks,
> >
> >   Sorry for the interruption, but all documents (includes specs,
schemas,
> > wsdls, meeting minutes, etc.) related to TC work MUST remain on OASIS
> > servers per the TC Process Policy. The use of an external system to
> > maintain such documents is prohibited.
> >
> > Regards,
> >
> > Mary
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  You may a link to this group and all your TCs in
> > OASIS
> > at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php