To write up my straw man proposal from the white paper conversation today:

Suggestion: rename this from "Hyperledger White Paper" to "Hyperledger Community Architectural Vision" - a broad view of what we as a community feel is necessary for the various projects within Hyperledger to collectively address. That is reflected in the example use cases; in the description of where current technologies are insufficient; and in the long term, aspirational need for things like confidential transactions. This document can serve as a way to map our projects and how they relate to each other, to harmonize terms across projects and drive cross-project discussions and learning, and perhaps even identify gaps (such as confidential transactions) where proactively building a new project/community may make sense.

And then in parallel, each project would be asked (required?) to maintain a project-level White Paper that serves as the ground, specific, technical overview of how that project solves what it intends to solve, serving a more traditional understanding of the term "White Paper".

Thoughts?

Brian

--
Brian Behlendorf
Executive Director at the Hyperledger Project
bbehlendorf@...
Twitter: @brianbehlendorf

Dear Brian,

I agree with the approach suggested. I can help to build in a page view linking all together. It will help in navigation and help everyone understand how they fit together.

Regards,
Partha

  Original Message  
From: hyperledger-tsc@...
Sent: 15 September 2016 4:23 p.m.
To: hyperledger-tsc@...
Reply to: bbehlendorf@...
Subject: [Hyperledger Project TSC] White Paper feedback, straw man proposal

To write up my straw man proposal from the white paper conversation today:

Suggestion: rename this from "Hyperledger White Paper" to "Hyperledger
Community Architectural Vision" - a broad view of what we as a community
feel is necessary for the various projects within Hyperledger to
collectively address.  That is reflected in the example use cases; in
the description of where current technologies are insufficient; and in
the long term, aspirational need for things like confidential
transactions.  This document can serve as a way to map our projects and
how they relate to each other, to harmonize terms across projects and
drive cross-project discussions and learning, and perhaps even identify
gaps (such as confidential transactions) where proactively building a
new project/community may make sense.

And then in parallel, each project would be asked (required?) to
maintain a project-level White Paper that serves as the ground,
specific, technical overview of how that project solves what it intends
to solve, serving a more traditional understanding of the term "White
Paper".

Thoughts?

Brian

--
Brian Behlendorf
Executive Director at the Hyperledger Project
bbehlendorf@...
Twitter: @brianbehlendorf

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

Works for me. My hybrid suggestion of “stick with one paper but restructure it so it starts with the broad umbrella and then describes fabric as an example” was a compromise to save the whitepaper team from having to perform open heart surgery on the doc… but I agree a better outcome would be as you propose… ie an overarching “vision” paper and a series of separate project-level whitepapers.

Richard

Richard Gendal Brown
R3 | Chief Technology Officer
City Tower, Floor Fifteen
40 Basinghall Street
London, EC2V 5DE
Cell: +44 776 466 6821
richard@... | www.r3cev.com <http://www.r3cev.com/>

Email Disclaimer <https://drive.google.com/open?id=0B8-B63wHiCBnRlZIY0l4Z282LUE>