Slashdot Mirror

← Back to Stories (view on slashdot.org)

The Importance of Collaborative Development

Posted by Hemos on from the working-together-for-bettering-us-all dept.

Eugene Eric Kim writes: "A few months ago, I wrote an essay entitled, "A Manifesto for Collaborative Tools," outlining a vision for how we can and should be making collaborative tools more interoperable. The article was published in the May issue of Dr. Dobb's Journal and is now available on the web." This manifesto is a good one, particularly if you aren't as a familiar with Doug Engelbart as you should be. There's also some interesting links to learn more about the Semantic Web, and social networks, well worth checking out as well.

1 of 61 comments (clear)

  1. Collaborative Work vis a vis locked down by beacher · · Score: 5, Interesting

    I don't know about your workplace environment, but my company has locked down shares and peering due to the fact that this an infection vector.
    I think peering/collaboration is the way to go, but this is becoming increasingly difficult thanks to the lax default permissions that was inside windows (yeah I'm not a windows admin, and the default share was always set at world full access). The knee jerk reaction was to disallow *all* peer/sharing.

    I'll probably get ripped and modded to hell for this but I was looking forward to the "hive" type setups that MS was proposing for peering(for work this would be a godsend, I wouldn't do this at home tho). My concern was their security model.

    Just how in the hell can this be done when virii explicitly target this functionality? CVS / Subversion is not an answer for business/end users...
    B