Re: [wemi] Re: Google Groups Invitation: WEMI

[Chet Ensign <chet.ensign@oasis-open.org>]

Jay,

Thanks very much for the clarification. That makes complete sense to me. Using it as a collaborative working environment is fine. As you say, at the point where you feel that a document is at some stage of semi-doneness, then loading it to Kavi would be appropriate. 

Your meeting minutes should indeed go into OASIS and should be announced on your mailing list. Some TCs just email the minutes directly, others keep them in a word processing document and just send out the link. 

Again, thanks for the clarification - I have no problem with using it as you described. 

Best - 

/chet 

P.S. - OASIS can also set up a wiki for you if you would find that useful. 

On Wed, Apr 11, 2012 at 11:12 AM, Jay Batson <jay@acquia.com> wrote:

As the guy who suggested its use, I'll chime in.

The principal motivation of the use of Google Docs was to get a live collaborative / simultaneous-editing capability, so that when we have either in-person, or voice meetings, we could all be adding content to the document at the same time, working on different parts of the stuff we're talking about a live, working item.  I know we do this at Acquia in our engineering brainstorming & design creation quite successfully; then once we're stable, we put the resulting content on our Drupal-based Intranet.

If nothing else, doing it this way is very similar to how someone might write a first draft of an OASIS spec in their local editor of choice (Word, etc.), then when happy with the draft, copy this content to the OASIS wiki / document platform.

There's a case to make that the minutes should have been on the OASIS doc server, vs. Google.  We're not doing simultaneous edits, so it could / should live there.  I think putting it on Google might just be a sign of initial deployment pains.

My (our?) intent is / was not for docs to stay on Google beyond a passing time; anything there should be considered transient things that would - as soon as they even feel like _wet_ mortar (much less dry) - would get copied / pasted to OASIS.

FYI, there was no intent to make these private; we'd even be happy to link to them from the OASIS pages.  But the co-editing feature of Google Docs would allow the working group to parallelize the actual text creation during meetings, and distribute the work more efficiently.

-jb

On Apr 11, 2012, at 10:58 AM, Chet Ensign wrote:

I'm just wondering why not use the document repository in the TC web
page? It will by default send a message to the mailing list when you
load the document and you can add to the message that is sent. We can
set up folders for you in it. It isn't all that different from Google
doc's really and it is the platform OASIS provides.

On Wed, Apr 11, 2012 at 10:30 AM, Peeter Piegaze
<peeter.piegaze@gmail.com> wrote:

Hi Chet,

Yes, the use of the group is just so we can easily share documents.

The document URLs are also available on the mailing list and are

accessible to anyone with URL.

If it is an issue, we can just stick to sharing the shared document

URLs through the OASIS mailing list without the use of the google

group.

Or is it the use of the shared documents themselves that is the problem?

Peeter

On Wed, Apr 11, 2012 at 16:20, Chet Ensign <chet.ensign@oasis-open.org> wrote:

Peeter, Cedric, Frank -

Hey, I just saw this note go out. Apologies, but I must ask you not to do this.

The TC Process rules for OASIS Technical Committees are quite clear

that using platforms other than OASIS for work is not allowed.

Specifically, in section 2.8, TC Visibility

(http://www.oasis-open.org/policies-guidelines/tc-process#visibility),

it reads:

"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.*** " (emphasis

added by me)

The reason for this is to ensure that all work done by a Technical

Committee is publicly visible and so that there can never be any

implication made that a TC performed any of its work in secret (and I

know that is not your intent - this is to avoid even the impression).

Democratic, open process is one of the guiding principles at OASIS and

the rule above is there to ensure that we live up to it at all times.

If this is a matter of convenience, please let me know so that I can

better understand what you are trying to achieve.

Thanks & please feel free to follow up with me on this...

/chet

On Wed, Apr 11, 2012 at 5:05 AM, Peeter Piegaze (Google Groups)

<noreply@googlegroups.com> wrote:

 Peeter Piegaze peeter.piegaze@gmail.com has invited you to join the WEMI

group with this message:

WEMI TC Members,

I have set up a Google Group for the TC membership in order to make sharing of

documents through Google Docs easier. We won't be using this group for email,

since we will be using the OASIS mailing list. However, having the group does

allow one-click sharing of Google docs, so please join.

Peeter Piegaze

Secretary, OASIS WEMI TC

Here is the group's description:

Web Experience Management Interoperability Technical Committee

---------------------- Google Groups Information ----------------------

You can accept this invitation by clicking the following URL:

http://groups.google.com/group/wemi/sub?s=dctpXBQAAABL0JNpR6J1qCxijU3B1oKmugH4tedXAhrgCkG_FY9m2g&hl=en

--------------------- If This Message Is Unwanted ---------------------

If you feel that this message is abuse, please inform the Google Groups staff

by using the URL below.

http://groups.google.com/groups/abuse?invite=YgAAAA-O_2uYAAAAA41AR7AAAAAAAFC5YBCIoAXgxE-Rf-bo2QyLEDU&hl=en

--

/chet

----------------

Chet Ensign

Director of Standards Development and TC Administration

OASIS: Advancing open standards for the information society

http://www.oasis-open.org

Primary: +1 973-996-2298

Mobile: +1 201-341-1393

Follow OASIS on:

LinkedIn:    http://linkd.in/OASISopen

Twitter:        http://twitter.com/OASISopen

Facebook:  http://facebook.com/oasis.open

--

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open

---------------------------------------------------------------------
To unsubscribe, e-mail: wemi-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: wemi-help@lists.oasis-open.org

-------------------------

Jay Batson, VP, Founder

jay@acquia.com
Direct: +1-781-238-8651
Mobile: +1-978-758-1599
Toll-free (US): 888-922-7842
Twitter: @batsonjay
Acquia | 25 Corporate Drive | 4th Floor | Burlington, MA 01803

Acquia named to Forbes' 100 list of America's Most Promising Companies! Click here to read more.

--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open