Jan Lehnardt is an Apache CouchDB developer who writes about open source maintenance, licensing, CouchDB conflicts and Mustache.js.
HN commenters cite his post on CouchDB conflicts when discussing sync behavior, and quote his opinion on GitHub in a discussion of social coding.
How does PouchDB deal with conflicts when syncing to CouchDB?
~~Since the docs mention this being a bit of an open problem a decade ago when dealing with online clients and servers (https://writing.jan.io/2013/12/19/understanding-couchdb-conflicts.html) I'd imagine its a bit more complex with many intermittently online clients.~~
Documented here: https://pouchdb.com/guides/conflicts.html
Well, I'm not too sure - GitHub is part of how we roll in 2015, right? Git based version control with that is part of our culture now --> social programming :)
Edit:
OK so Jan Lenhardt's thoughts on this: "I'd stay away from it"
https://twitter.com/janl/status/621667609986076672
http://writing.jan.io/2012/07/22/jsfab.html