In case you're interested, there are actually some legal use cases for WP that make sense. If I'm not mistaken, the Office of the Reporter at the Supreme Court uses WP due to its superior hyphenation, kerning, and other publication-quality print readiness features. The clerks, justices, Reporter, and print staff can all work in the same program from draft to distribution to GPO.
Historically, at least, WP HTML export was also much cleaner, lighter, and more machine-readable than Word's. The Supreme Court of Texas has opinions online, for instance. Last I heard (a couple years ago) that HTML was exported from WP.
nice euphemism. I have a colleague who is a WP fiend -- and has an AOL email address. Not that old either.
I think the word you're looking for is "convenient" it's easier to just upload the .doc they're using and write a blog post than create a Github repository with a readme, and review pull requests of people correcting spelling / grammar mistakes and such and such.
Props to YC to give this away for free, I read it, looks good, but don't try to excuse them for their laziness by calling it "pragmatism" just because it's YC and we're writing on their forums, great content but they shoulda been more professional before using the words "open source".
This is a LEGAL agreement, that says in the announcement is OPEN SOURCE and doesn't have a license attached to it... Think about it.
While there isn't any clear reason form contracts can't be copyrighted, it isn't at all clear who would hold the copyright or whether it could ever be effectively enforced.
Ken Adams has a nice write-up of associated issues:
http://www.adamsdrafting.com/downloads/Copyright-NYLJ-8.23.0...
Edit: typo
AFAIK by the open-source definition, it is all about the license: http://opensource.org/osd-annotated
Something without a license meeting that definition is not open-source.
First the industry standard for contract negotiation is to determine if you even need a contract like this that has to be "signed" and/or negotiated.
Missing is the dollar amount of a transaction or type of transaction that using an agreement like this relates to. It's overkill for many transactions and will kill deals. Companies don't sue over small amounts of money however deals do get killed if you give customers to much to think about.
Specifically:
"We've just open-sourced a sales agreement any company can use. Though obviously you should use this at your own risk, we've had a lot of experience with what makes good and bad sales agreements."
If you leave it up to the lawyers they are going to try and wrap up every single detail without considering any of the downside risk to having a customer have to review an agreement. Many of these agreements came to being by corner cases of liability that are few and far between.
Bottom line: Make sure to consider if this is necessary in this form at all (for your company) and if there is another easier friction (edit "free") way to provide some protection. This is not a case of "it can't hurt" it can hurt getting a sale.
If it's the other side's lawyers who are overlawyering the agreement, why not politely suggest to your counterpart that they, not their lawyers, should be driving the deal?
Because here we're talking about sales, in which asking your counterparty to do things they don't already intend to do injects friction into the process, thus reducing your chance of closing the sale.
They can still edit if they really want to, but it leaves the impression your contract isn't intended to be negotiable...
Also see my comment below.
If you'd like to chat more about the project, or would like me to walk you through the main ideas or any part of it, please feel free to e-mail me. I'm looking for feedback and dog-fooding the system at present, trying to ferret out flaws in the data model before building out the web interface.
Similar concerns make it difficult to adapt Git for use with opposing parties, since many of Git's features flow from the way it addresses its tamper-evidence design goal. The only notion of a commit with two ancestors in Git is a merge commit, which nonetheless preserves the complete history of both parents. So one side can't manage internal revisions with in-house commits (bearing author name, timing, exact content, etc.) and then issue a PR, while keeping the history of internal revisions secret. They have to edit history and make a squashed commit available for pull. At that point the incremental benefit of Git is just SSH or HTTP instead of e-mail. It's just managed patchfiles.
Squashing works to hide edit history from the opposing side, but it also pulls history out of your own history. You can create a branch at your local head before squashing to save those commits, but when you get an edit back, its new commit will reference your squashed commit. If you rebase onto the branch with your local changes, you can reconstruct "your history", but you'll have to be careful not to push commits from that branch to opposing next round, since it now contains your private edit history again.
http://ethics.calbar.ca.gov/Portals/9/documents/Opinions/CAL...
The best practice is clearly to run the diff from your own last revision, but that may not be available to the attorney. Sometimes clients forward opposing markups of drafts that were prepared without an attorney, perhaps based on a form. Business people may tweak a draft between attorney revisions, as they closed on deal points. It might be worthwhile to go over and attribute each unrecognized change, but not always. Clients may vouch that all changes needing review are in Track Changes. Sometimes speed matters more. Between repeat-player attorneys, or when reputations for ethics and rigor otherwise precede each side, the risk of this kind of thing approaches zero, and everybody saves money.
I have seen things "slipped in", often inadvertently (turned Track Changes off, diffed the wrong files), but sometimes maliciously. I have also done very long days of nothing but verifying execution copies of documents as they were closed out in the run up to big-dollar closings and low-dollar slug-fests. When the transaction is large or important enough, attorneys will handle exchanging drafts across sides and enforce more rigorous change control.
Terrible state of affairs!
People suggesting that this instead be released on Genius or Github should also remember that there are corner cases in contracts where formatting actually matters. Not only is .DOC the most pragmatic choice for a high-profile template contract, but it's also the safest.