Re: [ebxml-msg] wiki for spec collaboration

If we decide to use the wiki a lot, I could create a backup of it periodically.  Maybe someone could volunteer to make a copy of the backup image weekly or something.

-Matt

On Jan 29, 2004, at 10:41 AM, Dale Moberg wrote:

I think we should try it out!

One question, does the wiki get backed up (in case it gets attacked or

trashed?)

If not we should save copies of what we posted to reconstruct it.

Obviously not a wiki operations person,

Dale Moberg

-----Original Message-----

From: Matthew MacKenzie [mailto:] 

Sent: Thursday, January 29, 2004 6:34 AM

To: 

Subject: [ebxml-msg] wiki for spec collaboration

Importance: Low

Group,

What do you think of collaborating on the 3.0 specification using Wiki? 

Basically, once our requirements list is updated, I can start the 

basis of the 3.0 specification in a word processor.  It would contain 

all of the boilerplate text + an outline of all of the sections.  That 

would be posted on the wiki, and topics would be created for each 

section.  We could all edit the document until some agreed upon time, 

then I would transfer all of the text and images into the actual 

document and begin a more traditional draft process.

If you are working offline, or we are at a face to face without net 

connections, I would create a barebones word file with all of the 

current wiki text for us to work on in the f2f, or you could just write 

a text file and update the wiki with it next time you are online.

I think this could work and could speed up the process, as well as 

leave us with a better quality spec.

Thoughts?

___________________________

Matthew MacKenzie

Senior Architect

Intelligent Documents Business Unit

Adobe Systems Canada Inc.

http://www.adobe.com/

506 869.0949

Group,

What do you think of collaborating on the 3.0 specification using Wiki?

Basically, once our requirements list is updated, I can start the basis

of the 3.0 specification in a word processor.  It would contain all of

the boilerplate text + an outline of all of the sections.  That would be

posted on the wiki, and topics would be created for each section.  We

could all edit the document until some agreed upon time, then I would

transfer all of the text and images into the actual document and begin a

more traditional draft process.

If you are working offline, or we are at a face to face without net

connections, I would create a barebones word file with all of the

current wiki text for us to work on in the f2f, or you could just write

a text file and update the wiki with it next time you are online.

I think this could work and could speed up the process, as well as leave

us with a better quality spec.

Thoughts?

<color><param>FFFF,1010,0D0D</param><bigger>___________________________<

/bigger></color><bigger>

Matthew MacKenzie

</bigger><color><param>FFFF,0F0F,0909</param><smaller>Senior Architect

Intelligent Documents Business Unit

Adobe Systems Canada Inc.

http://www.adobe.com/

506 869.0949</smaller></color>

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/members/leave_workgroup.php.

___________________________

Matthew MacKenzie

Senior Architect

Intelligent Documents Business Unit

Adobe Systems Canada Inc.

http://www.adobe.com/

506 869.0949