Hello All, I have made changes discussed in the last meeting. Please see https://docs.google.com/document/d/1J4d_Mwq-qhP07LZw2buPlALoxdMpW926xePCH_Avw6c/edit?usp=sharing Please look at the language

White Paper Update (Dave Voell) https://github.com/hyperledger/hyperledger/pull/8 Code of Conduct (Arnaud Le Hors) Finalize decisions Results are visible here:

my first comment may still apply: The major thing I see missing from the WC3-based CoC is to keep discussions/material on-topic. On Wed, Mar 16, 2016 at 1:15 PM, Arnaud Le Hors via

I didn't see any response to my email.Additional votes were cast and there is now a clearer preference for theW3C-based draft. I therefore suggest the TSC endorses the W3C-based draftas our starting

Hyperledger Project Technical Community, If you have not already registered for the Technical F2F next week in Brooklyn, NY, Please register as soon as possible:

Thanks Dave for a good reminder of thegoal of this effort. I assume everybody joined the project to work on blockchainrather than CoCs so let's not spend more time than necessary on this. :-) To that

In case it is thought to useful to work iteratively on a Code of Conduct, this link has the W3 doc as a text object. The object is flat, but can of course be

Hi, For what it's worth, my experience is that having a code of conduct at all is a significant positive step. Communities can spend a lot of time debating the relative benefits of approaches, terms,

Just a quick update on the Code of Conduct. It appears with 47 voters participating, we have a near even split between the two options. At least one participant chose not to vote for one of the other

I like the W3C code of conduct because it has a clause explicitly discussing conflict of interest. If we do wind up going with another one as a base I think the COI clause in some form should be

Hyperledger Project Technical Steering Committee (TSC) Meeting March 10, 2016 (7:00am - 8:30am PT) via GoToMeeting TSC Members Emmanuel Viale Accenture Stan Liberman CME Group Yes Tamas

Of the two drafts currently being considered, I’m more comfortable with the one based on CloudFoundry. Adding to the comments made by Zhipeng, I like section 3 of the TODO CoC draft in that it

Just a quick update. We have 25 responses so far. If you’ve not weighed in, please do so today. As mentioned yesterday on the call, this is about which CoC to start from and there may be provisions

We did look at this. Arnaud has actually been engaged with the TODO group and has the history. That document was abandoned because there was quite a bit of disagreement within the

Hi Arnaud, I don;t have a strong preference, I like the todo one since it is succinct and hosted on github, HLP could just fork it, make some adjustments (borrow certain session from CF and w3c ones),

Hi, You're right, we could use that. I happento be involved with the TODO group so I'm familiar with this. As I saidon the call there are many other CoCs out there we could leverage. That'sone of

the open CoC draft by TODO group is also worth a look: https://github.com/todogroup/opencodeofconduct/blob/gh-pages/codeofconduct_redo.md It is basically a template and HLP could make its own

Hi Allen, The CF-based one also has a clause on"stepping down considerably" which isn't in the W3C one. But as I said on the call, we're freeto take from each one whatever we feel is worth having. The

The major thing I see missing from the WC3-based CoC is to keep discussions/material on-topic.

Members of the Hyperledger technical community, on the TSC call today, there was a discussion on options for adopting a code of conduct for the community. There were various aspects of both the W3C