You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by rg...@apache.org on 2005/10/03 00:19:36 UTC
svn commit: r293179 -
/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html
Author: rgardler
Date: Sun Oct 2 15:19:26 2005
New Revision: 293179
URL: http://svn.apache.org/viewcvs?rev=293179&view=rev
Log:
howto on collaborative editing, written collaboratively by Addi, Diwaker and Ross)
Added:
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html (with props)
Added: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html?rev=293179&view=auto
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html (added)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html Sun Oct 2 15:19:26 2005
@@ -0,0 +1,294 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V2.0//EN"
+"http://forrest.apache.org/dtd/howto-v20.dtd">
+<howto>
+ <header>
+ <title>How to Participate in Forrest Tuesday Events</title>
+
+ <version>0.1</version>
+
+ <abstract></abstract>
+
+ <last-modified-content-date date="2005-07-18" />
+ </header>
+
+ <audience title="Intended Audience">
+ <p>Developers wanting to participate in the collaborative meetings known as
+ "Forrest Tuesday". Users interested in what goes on at these events.</p>
+
+ <warning>This is a document written whilst testing the Gobby software. It is
+ included here for reference only. Gobby is not currently the preferred choice
+ of communication media for Forrest Tuesdays, we still use IRC at this time.</warning>
+ </audience>
+
+ <purpose title="Purpose">
+ <p> On the first Tuesday of each month we have a 24-hour get-together using the dev mailing list, Internet Relay Chat (IRC), and other collaborative tools, to work on Forrest development and get to know each other.</p>
+ <p>
+ We exploring the use of a <a href="http://gobby.0x539.de">Gobby</a>, a collaborative editor, to assist in focused development tasks. This HowTo will show you how.
+ </p>
+
+ <p>ForrestTuesday starts at 06:00 UTC (6am Greenwich Mean Time in London) and lasts for 24 hours.</p>
+ </purpose>
+
+ <prerequisites title="Prerequisites">
+ <p>You will not need anything more than knowledge of how to
+ install software on your computer. You will also need an Internet connection
+ to participate in the meetings.</p>
+ </prerequisites>
+
+ <steps title="Steps">
+
+ <section id="preparation">
+ <title>Perparing for Participation</title>
+ <section id="gobby">
+ <title>What is Gobby?</title>
+ <p>
+ From the <a href="http://gobby.0x539.de">Gobby web site</a>:
+ </p>
+ <p>
+ <em>
+ Gobby is a free collaborative editor based on libobby, a library which provides synced document buffers. It supports multiple documents in one session and a multi-user chat. It runs on Microsoft Windows, Mac OS X, Linux and other Unix-like platforms.
+ </em>
+ </p>
+ <p>
+ You can see some of its <a href="http://gobby.0x539.de/features.html">features</a>. People interested in the technical details of how Gobby works should read <a href="http://darcs.0x539.de/trac/obby/cgi-bin/trac.cgi/wiki/ObbyInternals">this document</a>.
+ </p>
+ </section>
+
+ <section id="software">
+ <title>Installing Required Software</title>
+ <p class="instruction">Download Gooby from Gobby's web site (http://gobby.0x539.de/download.html). If you use one of the popular Linux distributions, chances are that Gobby is already available as a binary package for you. Debian/Ubuntu users, for instance, can simply <code>apt-get install gobby</code>.
+ </p>
+ </section>
+ <section id="session">
+ <title>Creating a Collaborative Session</title>
+ <p>
+ When you first fire up Gobby, you will be presented with a blank screen with a toolbar on the top. Click on "Create Session" to host a session. If you need to join an existing session, click "Join session" instead.
+ </p>
+ <p>
+ To create a session, you need a computer connected to the Internet and you need to know its IP address. On Linux, this can be obtained with a <code>ifconfig -a</code>. On windows, try doing <code>ipcongfig /all</code>. For most cases, leaving the port values at default should be sufficient. Once you have specified the IP address and the name of the session, click "Create".
+ </p>
+ <p>There is an early version of a server available for Gobby. This
+ allows you to run a (semi-)permanent server. It is currently only
+ available for linux.</p>
+ </section>
+ </section>
+
+ <section id="participation">
+ <title>Participating in a Forrest Tuesday event</title>
+ <section id="login">
+ <title>Logging in to the session</title>
+ <p>
+ To join a Gobby session, click on "Join session" on the toolbar. You will need to know the IP address of the machine the session is being hosted at. In the "Name" field, just put in your name. Choose a color (which you can change later) and click OK. You will
+ then be prompted for the session password before joining.</p>
+ <p>When you first enter the Gobby session, if a document is already open,
+ you will be informed the document exists but that you are not currently
+ subscribed to it. There will be a "Subscribe" button below this notice that
+ will give you access to the document once clicked. Documents that are
+ created or opened during the session will also need to be subscribed to
+ in a similar manner.</p>
+ </section>
+
+ <section id="discussion">
+ <title>Using Chat for Discussion</title>
+ <p>Gobby has a chat session at the bottom of the window. This can be
+ used to discuss what needs to be done and who is going to be doing it.
+ Here is an (edited) chat session log from when this document was
+ written.</p>
+
+ <source><![CDATA[
+[22:24:16] <addi> we should also make note about the preferences
+[22:24:40] <addi> in the editor
+[22:25:02] <addi> tab width, tab spaces, etc
+[22:25:30] <Ross> +1, are you going to do that?
+[22:25:39] <diwaker> I am
+[22:25:58] <diwaker> under FAQ
+[22:26:07] <addi> ok
+ ]]></source>
+
+ <source>
+ <![CDATA[
+[22:26:38] <Ross> Note that the last sections of this document are cut and paste from the how-to-howto
+[22:26:46] <Ross> feel free to delete irrelevant content
+]]>
+ </source>
+
+ <source><![CDATA[
+[22:29:52] <Ross> Do either of you have a problem with me putting some
+[22:30:04] <Ross> of the content from the chat log in section <section id="discussion">
+[22:30:18] <addi> nope, fine with me
+ ]]></source>
+
+ <source><![CDATA[
+[22:41:47] <diwaker> hey do we have a blockquote/cite element in the v20 dtd?
+[22:42:01] <diwaker> i can't seem to find one
+[22:42:26] <diwaker> tip: the text entry widget has history (if you press Up, you can see earlier messages)
+[22:46:07] <Ross> There is no blockquote.cite element
+[22:46:24] <Ross> there may be a class in the CSS (<p class="cite"> or similar)
+ ]]></source>
+ </section>
+
+ <section id="authoring">
+ <title>Using Gobby for Collaborative Authoring</title>
+ <p>
+ Gobby uses colors to identify the edits being done by participants. In order to make it easier to follow whats going on, its a good idea to choose visibly distinct colors. While joining a session, if you choose a color thats already in use by someone else, Gobby will refuse to connect to the session. Just choose some color that gets you in, because you can always change your color later on while a session is in progress (see "Set Color" under the "User" menu item).
+ </p>
+ <warning>If you close a document it closes for everyone, and remote users
+ are not given the option to save any changes. So think carefully
+ before closing anything. Generally speaking you should not close a
+ document without asking all participants first.</warning>
+ </section>
+ </section>
+
+ <section id="wrapup">
+ <title>Wrapping up</title>
+
+ <section id="closingSession">
+ <title>Closing the Session</title>
+ <p>To close, or leave a session, simply click on the "Quit Session"
+ button in the toolbar. Be sure to save the files before doing so,
+ especially if you "own" the file.</p>
+
+ <p>Note that the host must be careful not to quit the session until
+ all participants ahve finished their work. It is a good idea to use
+ chat to ensure everyone is done, alternatively, you could leave the
+ session open until everyone else has quit.</p>
+
+ <warning>With the current version of Gobby (0.2.2) if any user leaves
+ a session the document is closed in all remaining users sessions. Any
+ unsaved changes are lost. Do not leave a session without agreeing
+ to do so with all other participants.</warning>
+ </section>
+
+ <section id="logs">
+ <title>Recording the logs</title>
+ <note>
+ At this point, we're not very sure if Gobby stores the chat logs somewhere on disk (we were not able to locate them). If you know the location of the logs, please let us know.
+ </note>
+ </section>
+
+ <section id="commit">
+ <title>Committing Documents to SVN</title>
+ <p>Any user can save a copy of a file being edited locally. However,
+ it is recomended that someone be nominated as the person responsible
+ for committing the file to SVN at the end of the session.</p>
+ <p>
+ As mentioned before, the person responsible for committing should make sure that the document is properly formatted before committing.
+ </p>
+ </section>
+ </section>
+
+ </steps>
+<!--
+ <extension title="Extension">
+ <p>Solutions can be extended to cover many different problem domains. A
+ nearly unlimited number of potential How-To topics, from simple to
+ complex, are available right now, limited only by your imagination.</p>
+ </extension>
+-->
+ <faqs id="faqs">
+ <title>Frequently Asked Questions</title>
+ <faqsection id="faq-general">
+ <title>General issues</title>
+ <faq id="faq-difference">
+ <question>What is the difference between a How-To and a
+ tutorial?</question>
+
+ <answer>
+ <p>The goal of a How-To is to help the reader to accomplish a specific
+ task with clear and consise instructions. While tutorials may contain
+ How-To-like instructions and content, they also include additional
+ background and conceptual content to help teach their readers higher
+ order concepts along the way. How-Tos are concerned about filling an
+ immediate, short-term need. Tutorials often provide long-term
+ knowledge which can be applied across a range of needs.</p>
+ </answer>
+ </faq>
+ </faqsection>
+
+ <faqsection id="faq-style">
+ <title>Style issues</title>
+ <faq id="coding">
+ <question>What coding convention should I follow?</question>
+ <answer>
+ <p>
+ Gobby is a good collaborative editor, but not a very good editor. It allows minimalistic configuration flexibility for editing. For Gobby sessions, it is sufficient to choose a convention and stick with it. For instance, using 4 spaces for a tab indent, and using spaces to fill up the tabs -- this can be done through the "Preferences" item under the "Edit" menu.
+ </p>
+ <p>
+ The nominated committer should make sure that the document is properly formatted before committing to SVN.
+ </p>
+ <note>The current version of Gobby is 0.2.2, hopefully the editor will
+ improve.</note>
+ </answer>
+ </faq>
+ <faq id="spelling">
+ <question>What spelling convention should I follow?</question>
+
+ <answer>
+ <p>Use whatever spelling convention (American, British, etc.) that is
+ most intuitive to you.</p>
+ </answer>
+ </faq>
+ </faqsection>
+ </faqs>
+
+ <tips title="Tips">
+ <section id="tip-jotlive">
+ <title>Collaborative Note Taking</title>
+ <p>
+ <a href="http://www.jotlive.com">JotLive</a> is a nice little web-app for taking notes collaboratively. Its almost like Gobby (each user has a different color, you can see the edits in <em>real time</em>), except that its web based. From the same folks who did <a href="http://jot.com">Jotspot</a>.
+ </p>
+ </section>
+ <section id="editing-tips">
+ <title>Editing Tips</title>
+ <section>
+ <title>Is Anyone Editing?</title>
+ <p>A quick way to see if someone is currently working on a document is
+ to look at the revision number in the status bar. This number will
+ increase by one with each keypress.</p>
+ </section>
+ </section>
+ <section id="chat-tips">
+ <title>Chat Tips</title>
+ <section>
+ <title>History</title>
+ <p>The text entry widget (where you type for chat) can show you an editable history
+ of your previous entries by hitting the up arrow on your keyboard. This functions
+ much like the up arrow key in a Linux terminal.</p>
+ </section>
+ </section>
+ <!--
+ <section id="tip-dtd">
+ <title>How-To dtd</title>
+
+ <p>The document structure is likely to change at some time. Please note that
+ this HOWTO page is likely to change as well.</p>
+ </section>
+ -->
+ </tips>
+<!--
+ <references title="References">
+ <p>This is not the first, nor will it be the last, How-To on writing
+ How-Tos. For other ideas and opinions on the matter, check out the
+ following sources.</p>
+ </references>
+-->
+</howto>
+
+
Propchange: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html
------------------------------------------------------------------------------
svn:eol-style = native
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by Ross Gardler <rg...@apache.org>.
Diwaker Gupta wrote:
> I think real time collaborative editors are complementary to Lenya et al. The
> "real time" part is what is important. In Lenya, I can't see in real time
> what others are doing with the document.
>
> In my head, Gobby and such are only meant for short, highly focused
> interactions and not much more than that. So if people have ideas for some
> document, they can write it up on Gobby and publish as usual through Lenya.
> Further edits etc would also go through Lenya.
+1
Lenya is asynchronous, Gobby is synchronous.
Gobby is great for "pair programming" (which includes documentation).
Another example of its use we discussed is addressing something like the
refactoring of sitemaps to use the locationmap. Imagine a Forrest
Tuesday with three people online, one xmap file each, shared loationmap
file.
Ross
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by Diwaker Gupta <di...@apache.org>.
> We could create a howto for each tool:
> Lenya, SubEthaEdit, Gobby, InkScape.
SubEthaEdit is Mac only, and IIUC will remain so.
Inkscape is a tool for creating SVG files. I'm not sure how useful that is to
us.
I think real time collaborative editors are complementary to Lenya et al. The
"real time" part is what is important. In Lenya, I can't see in real time
what others are doing with the document.
In my head, Gobby and such are only meant for short, highly focused
interactions and not much more than that. So if people have ideas for some
document, they can write it up on Gobby and publish as usual through Lenya.
Further edits etc would also go through Lenya.
Diwaker
--
Web/Blog/Gallery: http://floatingsun.net
On Apache: http://people.apache.org/~diwaker
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by Ross Gardler <rg...@apache.org>.
Ross Gardler wrote:
> (are we having a Forrest Tuesday tomorrow? I just realised the date, I'm
> up for it and will be around from around 2pm BST and an hour or so in
> the morning - focus could be a bug fix drive, everyone who logs in tries
> to fix an issue or two, or at least evaluate what needs to be done. I'm
> out all day today, so i'll go with wnything that is decided, then please
> set up the IRC channel anyway and I'll sit in there when I can working
> on bugs).
I've seen the proper thread now. Please ignore this here.
Ross
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by rg...@saafe.org.
> Ross Gardler wrote:
>> David Crossley wrote:
>> >
>> >We should also explore other tools. I got a bit worried
>> >that we rushed to a certain software.
>>
>> We rushed to test, we have not rushed to adopt ;-)
>>
>> >A quick Google found me this for example ...
>> >http://www.inkscape.org/
>>
>> The document has a section for alternatives, we should add real
>> alternatives there.
>>
>> However, I do not believe inkscape is an alternative. It is an XVG
>> drawing package, as far as I can tell it does not allow multiple people
>> to work on the same document at the same time.
>
> You snipped my research that it is in the process
> of incorporating such a feature, if not already.
Oh, sorry. I was rushing too much. In that case this is a pretty good
candidate since it has drawing tools as well.
>> >We could create a howto for each tool:
>> >Lenya, SubEthaEdit, Gobby, InkScape.
>>
>> I agree we should examine alternatives, but the only one in this list
>> that is an alternative is SubEthaEdit, unfortunately that is Mac only
>> (is it not?). Gobby is cross platform, although too dificult to install
>> on Mac at this time (work in progress).
>
> As i was suggesting, my quick search revealed one
> possibility. There must be more.
There is a section in the document for other tools, Addi (or was it
Diwaker?) added another alternative there. If we need to use such tools we
know Gobby works, but is a long way from perfect. I'm more than happy to
experiment with other alternatives as well.
Ross
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by addi <ad...@rocktreesky.com>.
On Monday October 03 2005 3:51 pm, Ross Gardler wrote:
> addi@rocktreesky.com wrote:
> > Quoting David Crossley <cr...@apache.org>:
> >> Ross Gardler wrote:
> >>> David Crossley wrote:
> >>> >We should also explore other tools. I got a bit worried
> >>> >that we rushed to a certain software.
> >> >
> >> >A quick Google found me this for example ...
> >> >http://www.inkscape.org/
>
> ...
>
> > I have Inkscape .42 and it is a great little SVG program but as far as I
> > can
> > tell, you can't use it to edit the kind of text files we are working
> > with - at
> > least I can't open a .xml file in it. If I'm wrong about that, Inkboard
> > will
> > be in .43 which is in hard freeze and due to be released soon. Again
> > though,
> > the demo only showed WYSIWYG editing of SVG files.
>
> Yes, that is the mistake I made. I'm an Inkscape user and didn't realise
> that David had found a reference saying that they planned to add
> collaborative editing. I'm still to check this out.
Yes, that is the Inkboard I refered to, but it is a collaborative GUI *SVG*
editor from what I can see so far. I haven't found anything about additional
text editing capabilities in any of the documentation or mail lists. As far
as I know Inkscape only allows editing of SVG files, so unless it is an
additional feature of the Inkboard code I don't think we will be able to open
and work with regular xml files in it.
>
> Inkscape is a cool tool, collaborative editing with it would be killer.
I agree and this is definitely something to keep an eye on but I don't think
it is going to be a code editor like we need. Also, for those who are
interested the Inkboard component uses Jabber for the sessions so you will
need a Jabber account to use it.
- Addi
>
> [For those interested, Cocoon is having a similar discussion for use at
> the forthcoming GetTogether]
>
> Ross
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by Ross Gardler <rg...@apache.org>.
addi@rocktreesky.com wrote:
> Quoting David Crossley <cr...@apache.org>:
>
>> Ross Gardler wrote:
>>
>>> David Crossley wrote:
>>> >
>>> >We should also explore other tools. I got a bit worried
>>> >that we rushed to a certain software.
>>>
>> >A quick Google found me this for example ...
>> >http://www.inkscape.org/
...
> I have Inkscape .42 and it is a great little SVG program but as far as I
> can
> tell, you can't use it to edit the kind of text files we are working
> with - at
> least I can't open a .xml file in it. If I'm wrong about that, Inkboard
> will
> be in .43 which is in hard freeze and due to be released soon. Again
> though,
> the demo only showed WYSIWYG editing of SVG files.
Yes, that is the mistake I made. I'm an Inkscape user and didn't realise
that David had found a reference saying that they planned to add
collaborative editing. I'm still to check this out.
Inkscape is a cool tool, collaborative editing with it would be killer.
[For those interested, Cocoon is having a similar discussion for use at
the forthcoming GetTogether]
Ross
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by ad...@rocktreesky.com.
Quoting David Crossley <cr...@apache.org>:
> Ross Gardler wrote:
>> David Crossley wrote:
>> >
>> >We should also explore other tools. I got a bit worried
>> >that we rushed to a certain software.
>>
> >A quick Google found me this for example ...
> >http://www.inkscape.org/
... snip ...
>>
>> I agree we should examine alternatives, but the only one in this list
>> that is an alternative is SubEthaEdit, unfortunately that is Mac only
>> (is it not?). Gobby is cross platform, although too dificult to install
>> on Mac at this time (work in progress).
>
> As i was suggesting, my quick search revealed one
> possibility. There must be more.
>
> -David
>
I did some more poking around re: David's concerns and really didn't come up
with much.
From my searches I came across a few free collaborative editors (oxyd,
DocSynch,
Yarrr) that were in very early development (pre-alpha or planning) or were
plugins/extensions to other programs. Besides Gobby the only other one
I found
that is free, stand-alone and currently usable is MoonEdit but it only has
Linux, FreeBSD and Win versions with no mention of Mac at all.
Besides stand-alone there is also the option of web-based, but all the ones I
came across were designed for editing html pages in a gui and none with real
code editing in mind. (JotSpot Live, Writely)
I have Inkscape .42 and it is a great little SVG program but as far as I can
tell, you can't use it to edit the kind of text files we are working with - at
least I can't open a .xml file in it. If I'm wrong about that, Inkboard will
be in .43 which is in hard freeze and due to be released soon. Again though,
the demo only showed WYSIWYG editing of SVG files.
So, after spending a goodly amount of time wandering around, Gobby is the most
referenced and, I think, still at the top of our list. Hopefully they will
complete the ports for Mac soon.
- Addi
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> David Crossley wrote:
> >
> >We should also explore other tools. I got a bit worried
> >that we rushed to a certain software.
>
> We rushed to test, we have not rushed to adopt ;-)
>
> >A quick Google found me this for example ...
> >http://www.inkscape.org/
>
> The document has a section for alternatives, we should add real
> alternatives there.
>
> However, I do not believe inkscape is an alternative. It is an XVG
> drawing package, as far as I can tell it does not allow multiple people
> to work on the same document at the same time.
You snipped my research that it is in the process
of incorporating such a feature, if not already.
> >We could create a howto for each tool:
> >Lenya, SubEthaEdit, Gobby, InkScape.
>
> I agree we should examine alternatives, but the only one in this list
> that is an alternative is SubEthaEdit, unfortunately that is Mac only
> (is it not?). Gobby is cross platform, although too dificult to install
> on Mac at this time (work in progress).
As i was suggesting, my quick search revealed one
possibility. There must be more.
-David
Re: collaborative editing tools (Was: svn commit: r293179)
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Ross Gardler wrote:
>
>>>Author: rgardler
>>>Date: Sun Oct 2 15:19:26 2005
>>>New Revision: 293179
>>>
>>>URL: http://svn.apache.org/viewcvs?rev=293179&view=rev
>>>Log:
>>>howto on collaborative editing, written collaboratively by Addi, Diwaker
>>>and Ross)
>>>
>>>Added:
>>> forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html (with props)
>>>
>>
>>I've not linked this in to the site yet because the text talks about
>>using it for ForrestTuesdays and we can't do that until it can be
>>installed on Macs easily (site says it is in the pipeline)
>>
>>We'll give a more complete summary of our impressions some other time
>>(I'm going to bed now). For the curious this document will tell you what
>>you need to know.
>>
>>In short, it was great and I think could be really useful.
>
>
> How does our plan for a Lenya instance fit with
> this collaborative editing exploration?
Lenya is not real-time collaborative. It serves a different purpose to
Gobby et. al.
> We should also explore other tools. I got a bit worried
> that we rushed to a certain software.
We rushed to test, we have not rushed to adopt ;-)
> A quick Google found me this for example ...
> http://www.inkscape.org/
The document has a section for alternatives, we should add real
alternatives there.
However, I do not believe inkscape is an alternative. It is an XVG
drawing package, as far as I can tell it does not allow multiple people
to work on the same document at the same time.
> We could create a howto for each tool:
> Lenya, SubEthaEdit, Gobby, InkScape.
I agree we should examine alternatives, but the only one in this list
that is an alternative is SubEthaEdit, unfortunately that is Mac only
(is it not?). Gobby is cross platform, although too dificult to install
on Mac at this time (work in progress).
As Diwaker says in another mail in this thread. Gobby is great for a
very focussed problem. For example, writing documentation (it is amazing
how fast that howto came together with the three of us working on it). I
think it's real strength will be in documenting our ForrestTuesday
sessions. It was great to agree on something in the chat area then see
someone jump in and documennt that in the document.
(are we having a Forrest Tuesday tomorrow? I just realised the date, I'm
up for it and will be around from around 2pm BST and an hour or so in
the morning - focus could be a bug fix drive, everyone who logs in tries
to fix an issue or two, or at least evaluate what needs to be done. I'm
out all day today, so i'll go with wnything that is decided, then please
set up the IRC channel anyway and I'll sit in there when I can working
on bugs).
Ross
collaborative editing tools (Was: svn commit: r293179)
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> >Author: rgardler
> >Date: Sun Oct 2 15:19:26 2005
> >New Revision: 293179
> >
> >URL: http://svn.apache.org/viewcvs?rev=293179&view=rev
> >Log:
> >howto on collaborative editing, written collaboratively by Addi, Diwaker
> >and Ross)
> >
> >Added:
> > forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html (with props)
> >
>
> I've not linked this in to the site yet because the text talks about
> using it for ForrestTuesdays and we can't do that until it can be
> installed on Macs easily (site says it is in the pipeline)
>
> We'll give a more complete summary of our impressions some other time
> (I'm going to bed now). For the curious this document will tell you what
> you need to know.
>
> In short, it was great and I think could be really useful.
How does our plan for a Lenya instance fit with
this collaborative editing exploration?
We should also explore other tools. I got a bit worried
that we rushed to a certain software.
A quick Google found me this for example ...
http://www.inkscape.org/
The thing that attracted Google attention was
the press release at openclipart.org that mentioned
"picking up the development of Inkboard (http://inkboard.sf.net/)
to integrate networked collaborative editing of documents to Inkscape".
It was a GSoC addition so would be base work.
We could create a howto for each tool:
Lenya, SubEthaEdit, Gobby, InkScape.
-David
Re: svn commit: r293179 - /forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html
Posted by Ross Gardler <rg...@apache.org>.
rgardler@apache.org wrote:
> Author: rgardler
> Date: Sun Oct 2 15:19:26 2005
> New Revision: 293179
>
> URL: http://svn.apache.org/viewcvs?rev=293179&view=rev
> Log:
> howto on collaborative editing, written collaboratively by Addi, Diwaker and Ross)
>
> Added:
> forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-collaborativeEditing.html (with props)
>
I've not linked this in to the site yet because the text talks about
using it for ForrestTuesdays and we can't do that until it can be
installed on Macs easily (site says it is in the pipeline)
We'll give a more complete summary of our impressions some other time
(I'm going to bed now). For the curious this document will tell you what
you need to know.
In short, it was great and I think could be really useful.
Ross