Hi,
For me collaboration from Leo perspective would mean: Shared trees as
shared understanding. I would like to see a tree with a shared view (it
can contain private view nodes also) that is kind of a negotiation about
how a team sees a problem/code/doc.
Cheers,
Offray
El 30/08/11 11:28, Kent Tenney escribió:
Considering "collaboration":
One meaning, which seems virtually a solved problem:
"many people can work on the same set of files, conflict
hassles are minimized by version control"
Another:
"I expose my thinking process, others contribute reactions
and suggestions, resulting in mutual benefit."
This one seems to be in good hands with blogs, mailing lists,
... social networks in general.
Another:
"I expose my thinking process via breadcrumbs which I and
others can refer to"
Along the lines of http://diigo.com
I think "thinking process" really means "that which currently
tickles my fancy"
RE: Leo specifically: I'm not interested in others changing my
Leo files, nor in my changing theirs.
I am interested in using Leo to create an environment which
is tailored to structuring my thinking process, and automatically
exposes it, should others be interested. However they are not
as important as I am.
Maybe someone else would be interested,
but first and foremost I want to be getting things done, while
saving what I do in a form which offers easy access to it. I want
to figure out problems ONCE, including the problem of "how do
I figure out problems ONCE?"
Thanks,
Kent
On Tue, Aug 30, 2011 at 6:24 AM, Edward K. Ream<[email protected]> wrote:
On Aug 29, 1:22 pm, "Edward K. Ream"<[email protected]> wrote:
Rebecca and I needed a vacation from our vacation :-) I'm gradually
getting back to a more normal routine. I'll probably fix one or two
bugs a day for several weeks, and I'll be saying a few words about
what I think it next for Leo.
Here is an email Terry just sent me. I'd like to use it to kick off a
wider discussion.
On Mon, Aug 29, 2011 at 8:30 AM, Terry Brown<[email protected]>
wrote:
Weird, sitting in the back of an SUV driving to a meeting in Michigan,
fire up Leo just as we're passing through Ashland, practically outside
the hotel where we met.
I enjoyed our get together immensely. After vacation, I am inclined
to think of larger applications/domains for Leo. Say integrating Leo
with Google's big table, or vice versa. It's surprising how little
algorithms seem to matter these days: it's all about connectivity,
collaboration and big data.
Yes, Leo's focus on structure is important and useful, but Leo seems
to hamper collaboration just a bit. I've wondered how to fix that for
at least 10 years, without any real breakthrough...
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
