News for hackers. Stuff that matters.
Re:The Two Cultures of Computing (2013) by Jtsummers on Friday August 05, 2016 @04:07PM (#12235396)
Actually, going on my other post, this isn't as limited a use-case as you might think.

Anyone doing contracts, requirements documents, writing/editing cycles could use something like this with varying additional capabilities.

With no change to philosophy (still staying on the user side), a system could be made based off the principles of existing software.

You need some workflow management software + a document store. The document store needs to provide rich text editing, and the ability to edit only specific sections in parallel. "section" is a customizable unit depending on the type of contract. Could be paragraphs, or larger logical units. Part of the workflow management is kicking the contract back and forth between you and your collaborators and the other stakeholders. At various stages it's editable by different people, some stages are just for review (not edit), finally various sign-off stages.

It's pretty typical of requirements document databases. You'd need it exposable to third parties outside your company, and you'd also need confidence in privacy and security. Neither are trivial, but neither are impossible.

The software for your needs literally exists, but isn't marketed to you. It's too costly for smaller offices (both licensing costs and management costs), and would require a good sales pitch because, well, people don't like change.

Re:The Two Cultures of Computing (2013) by zekevermillion on Friday August 05, 2016 @05:40PM (#12235909)
No one has yet managed to build the workflow management that is needed for this. The best efforts I have seen to date are Docracy and Contractual.ly. But neither quite got it right. It is an interesting problem, and seemingly straight-forward to solve, yet it is a graveyard of failed attempts so far...
Re:The Two Cultures of Computing (2013) by Jtsummers on Friday August 05, 2016 @05:51PM (#12235962)
Is the workflow uniquely complex? It was never my job but I've seen (trying to remember what we used) some pretty complex workflows for handling requirements documentation, testing, and code development (reviews and such, specific tasks handled in JIRA) handled pretty effectively. Would've been one of the Telelogic (now Rational) tools.
Re:The Two Cultures of Computing (2013) by zekevermillion on Friday August 05, 2016 @06:04PM (#12236023)
I doubt the workflow could be any more complex than what you have seen. In many ways, it should be less so. There are some nuances, however. Partly the problem is the extreme egos involved in many business negotiations. Every communication sent has to help the sender to look good. There has to be a bias against publicizing changes before the author is done. There also has to be flexibility to override approvals. A lot of big deals would never close if someone had to take personal responsibility for waiving closing conditions that aren't satisfied at closing.
Re:The Two Cultures of Computing (2013) by Jtsummers on Friday August 05, 2016 @06:32PM (#12236145)
Regarding hiding changes until they're done, that shouldn't be in feasible except that you (or your counterpart) may not want to use a system owned by the other, because you lose that guarantee. A third party hosting it could offer that (naturally), but takes on extra liabilities with securing the documents in progress.