Skip to content
This repository has been archived by the owner on Nov 30, 2017. It is now read-only.

Use standard incubation notice. Change HLP to Fabric-API #2

Merged
merged 1 commit into from
May 11, 2016

Conversation

srderson
Copy link
Contributor

@srderson srderson commented May 9, 2016

Update the README to include the standard incubation notice. Change HLP-Candidate to Fabric-API

@christo4ferris
Copy link
Contributor

The preamble:
"What we are making available today is the most recent stable version of a combination of many man years of work across multiple startups: Digital Asset, Bits of Proof, Blockstack, and Hyperledger. However, it is still a work in progress and we are in the process of replacing several components, adding others, and integrating with other open source projects. This particularly relates to security, scalability, and privacy.

Fabric-API was built with the requirements of enterprise architecture in mind by a team that has worked in financial institutions for decades. It has a highly modular design at both the code and runtime levels to allow for integrations with legacy systems."

was maybe appropriate for the proposed contribution, but not for the repo in incubation. I would suggest the following:
"The Hyperledger fabric-api is being built with the requirements of enterprise architecture in mind. It has a highly modular design at both the code and runtime levels to allow for integrations with legacy systems."

I would like to integrate our CONTRIBUTING.md but I can do that in a separate PR. We also need a MAINTAINERS.txt with @srderson and @tamasblummer listed (unless it is to be someone else on his team.

@tamasblummer
Copy link
Contributor

tamasblummer commented May 11, 2016

Thanks Chirs,

Yes, the text was copied from from the contribution project and needs rework. No problems with your suggestion and further edits might follow.

I added Robert Fajta @rfajta as maintainer.

Tamas Blummer
E: tamas@digitalasset.com mailto:address@digitalasset.com | W: digitalasset.com http://www.digitalasset.com/

On 11 May 2016, at 09:17, Christopher Ferris notifications@github.com wrote:

The preamble:
"What we are making available today is the most recent stable version of a combination of many man years of work across multiple startups: Digital Asset, Bits of Proof, Blockstack, and Hyperledger. However, it is still a work in progress and we are in the process of replacing several components, adding others, and integrating with other open source projects. This particularly relates to security, scalability, and privacy.

Fabric-API was built with the requirements of enterprise architecture in mind by a team that has worked in financial institutions for decades. It has a highly modular design at both the code and runtime levels to allow for integrations with legacy systems."

was maybe appropriate for the proposed contribution, but not for the repo in incubation. I would suggest the following:
"The Hyperledger fabric-api is being built with the requirements of enterprise architecture in mind. It has a highly modular design at both the code and runtime levels to allow for integrations with legacy systems."

I would like to integrate our CONTRIBUTING.md but I can do that in a separate PR. We also need a MAINTAINERS.txt with @srderson https://github.com/srderson and @tamasblummer https://github.com/tamasblummer listed (unless it is to be someone else on his team.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/hyperledger/fabric-api/pull/2#issuecomment-218455826

This message, and any attachments, is for the intended recipient(s) only,
may contain information that is privileged, confidential and/or proprietary
and subject to important terms and conditions available at
http://www.digitalasset.com/emaildisclaimer.html. If you are not the
intended recipient, please delete this message.

@tamasblummer tamasblummer merged commit 1559542 into hyperledger-archives:master May 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants