search

WardCunningham / Smallest-Federated-Wiki

This wiki innovates by: 1. federated sharing, 2. drag refactoring and 3. data visualization.
http://wardcunningham.github.com/
GNU General Public License v2.0
1.21k stars 188 forks source link

Dicussion: Expected behavior of federation - sibling collaboration? #210

Open EliezerIsrael opened 12 years ago

EliezerIsrael commented 12 years ago

I'm working to get my head around the expected behavior of the federated wiki ecosystem, so as to decide if it is appropriate for a project I am working on.

If I understand https://github.com/WardCunningham/Smallest-Federated-Wiki/wiki/Federation-Details correctly:

If I edit a page I own, it is edited in place. If I edit a page I don't own, then it is forked to the place that I own.

If edits by non owners create forks, then how can multiple people collaborate on a page on an ongoing basis?

EliezerIsrael commented 12 years ago

Experiments show that multiple users can edit the same page.
http://sandbox.fed.wiki.org/view/welcome-visitors/view/lev-israel#

In that case isn't the above referenced wiki page incorrect?

And if multiple users can edit the same page, what is the concept of ownership for, and when does a fork occur?

:confused:

WardCunningham commented 12 years ago

On May 1, 2012, at 6:11 AM, Lev Eliezer Israel wrote:

I'm working to get my head around the expected behavior of the federated wiki ecosystem, so as to decide if it is appropriate for a project I am working on.

If I understand https://github.com/WardCunningham/Smallest-Federated-Wiki/wiki/Federation-Details correctly:

If I edit a page I own, it is edited in place. If I edit a page I don't own, then it is forked to the place that I own.

If edits by non owners create forks, then how can multiple people collaborate on a page on an ongoing basis?

It is easier to believe this can work if one stops thinking of collaborating on a page and thinks instead of collaborating on an idea.

Here is an example where the collaborators don't even know the idea until they begin:

http://dorkbotpdx.org/blog/breedx/exquisite_corpse
EliezerIsrael commented 12 years ago

So ... the spec is correct, and the behavior that I see in sandbox is a bug?

EliezerIsrael commented 12 years ago

On the philosophical/design point - I'm still digesting...

The exquisite corpse example is fun, and I understand the evolutionary parallels.

Still - isn't collaboration a value, alongside evolution? To say that each version must be subsumed in order for positive growth to occur...doesn't sit well with me. I'd love to see some form of communicating up or sideways, not just down.

WardCunningham commented 12 years ago

The sandbox works like a traditional wiki because the software does not yet know who owns the site. For this one instance I interfere with the site claiming process so that one can try making a claim. (In the sandbox claims don't last.)

However, federated wiki has scant few mechanisms that support collaborative editing of a shared space. For shared editing of pages one can find excellent software elsewhere. For shared editing of ideas, what ever that means, one would be wise to explore here with us.

EliezerIsrael commented 12 years ago

I'm willing to go down the rabbit hole. :)

Thanks for the clarification on sandbox. I won't use that instance to test out collaboration concepts anymore.
I'm now editing http://ddd.fed.wiki.org/view/welcome-visitors/view/domain-driven-design. I found that it let me edit, but has neither saved my edits, nor (as best I can tell) forked to a page.

What should I expect to happen? A copy of the edited page on lev.fed.wiki.org?

Perhaps part of the issue is that I can't seem to log in on ddd.fed - it tells me "this isn't your wiki!" I didn't realize that login was a claim to ownership, I thought it was a claim to identity.