<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: collaboration</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/collaboration.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2023-11-30T21:59:54+00:00</updated><author><name>Simon Willison</name></author><entry><title>Annotate and explore your data with datasette-comments</title><link href="https://simonwillison.net/2023/Nov/30/datasette-comments/#atom-tag" rel="alternate"/><published>2023-11-30T21:59:54+00:00</published><updated>2023-11-30T21:59:54+00:00</updated><id>https://simonwillison.net/2023/Nov/30/datasette-comments/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://www.datasette.cloud/blog/2023/datasette-comments/"&gt;Annotate and explore your data with datasette-comments&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
New plugin for Datasette and Datasette Cloud: datasette-comments, providing tools for collaborating on data exploration with a team through posting comments on individual rows of data.&lt;/p&gt;

&lt;p&gt;Alex Garcia built this for Datasette Cloud but as with almost all of our work there it’s also available as an open source Python package.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/projects"&gt;projects&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/datasette"&gt;datasette&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/datasette-cloud"&gt;datasette-cloud&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/alex-garcia"&gt;alex-garcia&lt;/a&gt;&lt;/p&gt;



</summary><category term="collaboration"/><category term="projects"/><category term="datasette"/><category term="datasette-cloud"/><category term="alex-garcia"/></entry><entry><title>I was wrong. CRDTs are the future</title><link href="https://simonwillison.net/2020/Sep/28/i-was-wrong-crdts-are-future/#atom-tag" rel="alternate"/><published>2020-09-28T21:03:57+00:00</published><updated>2020-09-28T21:03:57+00:00</updated><id>https://simonwillison.net/2020/Sep/28/i-was-wrong-crdts-are-future/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://josephg.com/blog/crdts-are-the-future/"&gt;I was wrong. CRDTs are the future&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Joseph Gentle has been working on collaborative editors since being a developer on Google Wave back in 2010, later building ShareJS. He’s used Operational Transforms throughout, due to their performance and memory benefits over CRDTs (Conflict-free replicated data types)—but the latest work in that space from  Martin Kleppmann and other researchers has seen him finally switch allegiance to these newer algorithms. As a long-time fan of collaborative editing (ever since the Hydra/SubEthaEdit days) I thoroughly enjoyed this as an update on how things have evolved over the past decade.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://news.ycombinator.com/item?id=24617542"&gt;Hacker News&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/algorithms"&gt;algorithms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/crdt"&gt;crdt&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/martin-kleppmann"&gt;martin-kleppmann&lt;/a&gt;&lt;/p&gt;



</summary><category term="algorithms"/><category term="collaboration"/><category term="crdt"/><category term="martin-kleppmann"/></entry><entry><title>Quoting Eric Dobbs</title><link href="https://simonwillison.net/2020/Feb/13/eric-dobbs/#atom-tag" rel="alternate"/><published>2020-02-13T18:48:41+00:00</published><updated>2020-02-13T18:48:41+00:00</updated><id>https://simonwillison.net/2020/Feb/13/eric-dobbs/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://wiki.dbbs.co/view/joint-cognitive-whiteboard"&gt;&lt;p&gt;A group of software engineers gathered around a whiteboard are a joint cognitive system. The scrawls on the board are spatial cues for building a shared model of a complex system.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://wiki.dbbs.co/view/joint-cognitive-whiteboard"&gt;Eric Dobbs&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;&lt;/p&gt;



</summary><category term="collaboration"/></entry><entry><title>Software Sprawl, The Golden Path, and Scaling Teams With Agency</title><link href="https://simonwillison.net/2018/Dec/2/the-golden-path/#atom-tag" rel="alternate"/><published>2018-12-02T19:40:33+00:00</published><updated>2018-12-02T19:40:33+00:00</updated><id>https://simonwillison.net/2018/Dec/2/the-golden-path/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://charity.wtf/2018/12/02/software-sprawl-the-golden-path-and-scaling-teams-with-agency/"&gt;Software Sprawl, The Golden Path, and Scaling Teams With Agency&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
This is smart: the "golden path" approach to encouraging a standard stack within a large engineering organization. If you build using the components on the golden path you get guaranteed ongoing support and as much free monitoring/tooling as can possibly be provided. I also really like the suggestion that this should be managed by a "council" of senior engineers with one member of the council rotated out every quarter to keep things from getting stale and cabal-like.&lt;/p&gt;
&lt;p&gt;Charity Majors describes the process like this:&lt;/p&gt;
&lt;blockquote&gt;
&lt;ol&gt;
&lt;li&gt;Assemble a small council of trusted senior engineers.&lt;/li&gt;
&lt;li&gt;Task them with creating a recommended list of default components for developers to use when building out new services. This will be your Golden Path, the path of convergence (and the path of least resistance).&lt;/li&gt;
&lt;li&gt;Tell all your engineers that going forward, &lt;strong&gt;the Golden Path will be fully supported by the org.&lt;/strong&gt; Upgrades, patches, security fixes; backups, monitoring, build pipeline; deploy tooling, artifact versioning, development environment, even tier 1 on call support. Pave the path with gold. Nobody HAS to use these components ... but if they don't, they're on their own. They will have to support it themselves. [...]&lt;/li&gt;
&lt;/ol&gt;
&lt;/blockquote&gt;

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://twitter.com/mipsytipsy/status/1069260988812161025"&gt;Charity Majors&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/software-engineering"&gt;software-engineering&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/charity-majors"&gt;charity-majors&lt;/a&gt;&lt;/p&gt;



</summary><category term="collaboration"/><category term="software-engineering"/><category term="charity-majors"/></entry><entry><title>Looking for a modern day wiki for a group project</title><link href="https://simonwillison.net/2017/Apr/11/looking-for-a-modern-day/#atom-tag" rel="alternate"/><published>2017-04-11T07:12:00+00:00</published><updated>2017-04-11T07:12:00+00:00</updated><id>https://simonwillison.net/2017/Apr/11/looking-for-a-modern-day/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;em&gt;My answer to &lt;a href="http://ask.metafilter.com/307865/Looking-for-a-modern-day-wiki-for-a-group-project#4454765"&gt;Looking for a modern day wiki for a group project&lt;/a&gt; on Ask MetaFilter&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;GitHub offers a wiki for each repository. It's free for public projects (no need to upload any code, just create a repo and ignore the other tabs) of you can pay $7 monthly for private ones.&lt;/p&gt;
&lt;p&gt;With public wikis you can still control which users are allowed to make edits.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://help.github.com/articles/about-github-wikis/"&gt;https://help.github.com/articles/about-github-wikis/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The only missing feature in your list is WYSIWYG editing, but they do offer a good &amp;quot;preview&amp;quot; tab.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/ask-metafilter"&gt;ask-metafilter&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/wiki"&gt;wiki&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/resolved"&gt;resolved&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="ask-metafilter"/><category term="collaboration"/><category term="wiki"/><category term="resolved"/></entry><entry><title>Quoting Neil Fraser</title><link href="https://simonwillison.net/2009/Aug/14/neil/#atom-tag" rel="alternate"/><published>2009-08-14T10:38:57+00:00</published><updated>2009-08-14T10:38:57+00:00</updated><id>https://simonwillison.net/2009/Aug/14/neil/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://neil.fraser.name/news/2009/08/14/"&gt;&lt;p&gt;Last night I woke up at 2am and realized that there was a fundamental problem with cursor preservation in today’s real-time collaborative applications [...] MobWrite now has what I believe to be the most advanced cursor preservation algorithm available.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://neil.fraser.name/news/2009/08/14/"&gt;Neil Fraser&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mobwrite"&gt;mobwrite&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/neil-fraser"&gt;neil-fraser&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/realtime"&gt;realtime&lt;/a&gt;&lt;/p&gt;



</summary><category term="collaboration"/><category term="mobwrite"/><category term="neil-fraser"/><category term="realtime"/></entry><entry><title>google-mobwrite</title><link href="https://simonwillison.net/2009/Jan/24/googlemobwrite/#atom-tag" rel="alternate"/><published>2009-01-24T23:55:18+00:00</published><updated>2009-01-24T23:55:18+00:00</updated><id>https://simonwillison.net/2009/Jan/24/googlemobwrite/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://code.google.com/p/google-mobwrite/"&gt;google-mobwrite&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Neil Fraser’s terrifyingly clever differential synchronization algorithm (for SubEthaEdit-style collaboration over the web) is now available as an open source Python and JavaScript library.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mobwrite"&gt;mobwrite&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/neil-fraser"&gt;neil-fraser&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/open-source"&gt;open-source&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/subethaedit"&gt;subethaedit&lt;/a&gt;&lt;/p&gt;



</summary><category term="collaboration"/><category term="google"/><category term="javascript"/><category term="mobwrite"/><category term="neil-fraser"/><category term="open-source"/><category term="python"/><category term="subethaedit"/></entry><entry><title>Google apps for your newsroom</title><link href="https://simonwillison.net/2008/Jan/7/newsroom/#atom-tag" rel="alternate"/><published>2008-01-07T21:24:05+00:00</published><updated>2008-01-07T21:24:05+00:00</updated><id>https://simonwillison.net/2008/Jan/7/newsroom/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.postneo.com/2008/01/07/google-apps-for-your-newsroom"&gt;Google apps for your newsroom&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
How the LJ World team use online tools like Google Spreadsheet, Swivel, ManyEyes and Google MyMaps to collaborate with the newsroom and build data-heavy applications even faster.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/data-journalism"&gt;data-journalism&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google-calendar"&gt;google-calendar&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google-docs"&gt;google-docs&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google-maps"&gt;google-maps&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/journalism"&gt;journalism&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ljworld"&gt;ljworld&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/manyeyes"&gt;manyeyes&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/matt-croydon"&gt;matt-croydon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mymaps"&gt;mymaps&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/news"&gt;news&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/newsroom"&gt;newsroom&lt;/a&gt;&lt;/p&gt;



</summary><category term="collaboration"/><category term="data-journalism"/><category term="django"/><category term="google"/><category term="google-calendar"/><category term="google-docs"/><category term="google-maps"/><category term="journalism"/><category term="ljworld"/><category term="manyeyes"/><category term="matt-croydon"/><category term="mymaps"/><category term="news"/><category term="newsroom"/></entry><entry><title>Chat rooms and meetings</title><link href="https://simonwillison.net/2003/Jan/11/chatRoomsAndMeetings/#atom-tag" rel="alternate"/><published>2003-01-11T17:28:52+00:00</published><updated>2003-01-11T17:28:52+00:00</updated><id>https://simonwillison.net/2003/Jan/11/chatRoomsAndMeetings/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;a href="http://www.openp2p.com/pub/a/p2p/2002/12/26/inroom_chat.html"&gt;In-Room Chat as a Social Tool&lt;/a&gt;: Clay Shirky describes an experiment with an online chat room set up to accompany a meeting of 30 people taking place in the same room. The chat room (available to attendees via Wifi laptops and displayed on a big screen at the front of the room) had some interesting effects on the dynamics of the meeting, not least of which was the dramatic impact the chat room had on the "interrupt logic" of the proceedings.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/clay-shirky"&gt;clay-shirky&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/collaboration"&gt;collaboration&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="clay-shirky"/><category term="collaboration"/></entry></feed>