+1 Thanks, Hart

Thank you for the objective summary Mic. To follow up on this, I think it’s also important to consider what audience we are targeting. Are we intending the whitepaper for: 1. People who are not curren

Thanks everyone for the comments and feedback. It's been really nice for me to hear some of the ideas from the community, and I'm sure others in the whitepaper WG would agree. There has been a lot of

I’d love to contribute, but the meeting time is just a bit too brutal for me (4am in California). What would the working group’s preferred method of commenting be if I can’t make the meeting? Thanks,

I agree with Mic here. In the long term, it would be nice to have some sort of outline of APIs and modules for “core” Hyperledger projects (although exact APIs and technical details should be left out

As far as I am concerned, the more outreach we have, the better. So I definitely support this.

Hi Everyone, I just wanted to clarify some of the points I brought up in the discussion during the TSC meeting yesterday about the incubation exit criteria and see what other people have to say about

Hi Everyone, On behalf of the whitepaper working group, I’d like to send out two documents: 1. Our working group charter. This should be extremely straightforward. 2. A “skeleton”—or detailed outline—

Hi Mic, and Arnaud, Thanks for the feedback. Has the TSC (or Hyperledger community in general) even decided upon a position about standards? I’m not aware of any position, other than the fact that usi

+1

Hi Everyone, I agree with Chris here. I think a tiered system makes a lot of sense, and will enforce some important communication. For instance, suppose I wanted to create (for the purposes of example

+1/+1 for me. Thanks!

Hi Everyone, Thanks for all the discussion on this. I’ll wade back in the discussion with some of my thoughts on what people have proposed so far. The block of text that seems to be causing the most c

Thanks for the summary and arguments Dan (and others). If we do think it is the case that the risk of large projects squelching small projects is more than that of small projects harming large project

+1 from me as well. Thanks Dave!

RE: [Hyperledger Project TSC] Project Proposal: Consensus Platform Hi Martin, Is there a reason this hasn’t been submitted to a conference for peer review? I’d highly recommend doing so—you’ll have a

Hi Ray, Thanks for your reply. Correct me if I'm wrong, but is this the original hashgraph paper: http://www.swirlds.com/downloads/SWIRLDS-TR-2016-01.pdf ? I want to make sure I'm reading the right th

RE: [Hyperledger Project TSC] Project Proposal: Consensus Platform Hi Martin, Thanks for replying. There isn’t a set TSC policy on this—what I have said is just my opinion. However, if you can convinc

RE: [Hyperledger Project TSC] Project Proposal: Consensus Platform Hi Brian, I think there is an important distinction here. There are two kinds of potential projects here that I think are getting con

RE: [Hyperledger Project TSC] Project Proposal: Consensus Platform Hi Brian, Thanks for your reply. I’ve got some questions and comments to your responses below. “That doesn't seem to map to what I've