Quote from: BruceFenton on February 22, 2016, 03:49:28 PM

Quote from: bargainbin on February 22, 2016, 03:04:23 PM

do you see any points in that list that could be construed as legally binding? Other than block size limit won't be > 4MB when/if it happens?

I don't think any legally binding agreement is likely or even possible.

What we can do is work on things with broad industry buy in and can self enforce them.

For example -- if we agree to a code of conduct that agrees to not trash other tech opinions in the press and some a does....that violator can expect a call from half a dozen other participants saying "whoa, hold on, that's not what we agreed on" .... repeated and willful violations could result in many members of the industry working to reduce the influence of the violator

I'm talking about the wording of what was "signed." And how it's completely open to interpretation.
In other words, going down the list, point-by-point, starting with the first:

Quote

--We understand that SegWit continues to be developed actively as a soft-fork and is likely to proceed towards release over the next two months, as originally scheduled.

How can this be construed as ....well, anything? As long as it's "likely" that Core changes readme.txt once in a while, everything's copacetic.
I mean, it doesn't say anything about Core actually releasing anything in two months, merely "proceed towards release over the next two months."

Go down the whole list, and you'll find that there is nothing in it that anyone could ever say "whoa, hold on, that's not what we agreed on" to Sad