Hi, I work with Chris Ferris in the Open Technology group at IBM and to help with the development of a Code of Conduct I put together two drafts for your consideration: the first one is based on Cloud

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 free to take from each one whatever we feel is worth having. T

Hi, You're right, we could use that. I happen to be involved with the TODO group so I'm familiar with this. As I said on the call there are many other CoCs out there we could leverage. That's one of t

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

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

Hi all, To try and move the discussion further on the exit criteria I put together a first draft based on the notes taken so far. Please, have a look and comment as appropriate. https://docs.google.co

Hi all, I took another pass at the exit criteria leveraging the ASF ones. I invite everyone to have a look and comment: https://docs.google.com/document/d/1hmZY5LnZydTiYmkbtwyEYEkHEsSedlUhJbnlXGFrEP0/

Per my action items I renamed the "Mature" state to "Active" in the Project Lifecycle document, I cleaned up the Incubation criteria draft, and moved Jeremy's and Rick's content to a new doc: Updated

+1. -- Arnaud Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM Cloud hyperledger-tsc-bounces@... wrote on 09/29/2016 05:41:40 PM: > From: Tamas Blummer via hyperl

I think I'd be able to make it. -- Arnaud Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM Cloud From: "Haskins, Gregory via hyperledger-tsc" <hyperledger-tsc@...

Regarding the issue concerning the Incident procedure of the Code of Conduct, let me share the following background: LF is advocating reuse of our Code of Conduct in other LF projects to have one stan

On the topic of documentation I started an effort to improve our wiki and would appreciate feedback. Please, have a look at the "top level projects" pages: http://wiki.hyperledger.org/ My goal is to h

I think that's a fair question actually. As I started looking into the wiki I found the name of the section called "Top level projects" somewhat puzzling. It got me wondering whether this was the righ

Same here. Sounds great. -- Arnaud Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM Cloud From: "Bowman, Mic via hyperledger-tsc" <hyperledger-tsc@...> To: "hyper

One minor point on this: Why do you call this *Technical* Working Group. Do we have any other types of Working Groups? So far I believe we have the Architecture WG, the Identity WG, etc. which are all

While I'm all for experimenting with an alternative to Slack which I like using but is pretty terrible without history, I think we need to try and time-box these experiments a bit better. Failing to d

I agree. Having discussed this with Ram earlier today, I've come to the conclusion that we cannot just pull the plug on the github wiki. Instead it would be better to have redirects in place of old pa

Ah, thank you. Do you know if there is any support for some form of redirect? A quick web search didn't turn anything up. -- Arnaud Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM

Yes. This is what I'm working on. I already put a big warning at the top of the page and started going through the list of pages and replacing their content with a link to the new page, as in: https:/

Hi, It works fine for me so this might be a local problem and hopefully temporary. I'd be happy to be told otherwise but I'm guessing we won't be able to mirror the new wiki on github wiki because the