|
Re: [Hyperledger Project TSC] Hyperledger Explorer Proposal
Yes to a "Hyperledger Blockchain Explorer" project, with three products under their scope (I don't know if that has to mean "three repositories" - seems like one repo per project is
Yes to a "Hyperledger Blockchain Explorer" project, with three products under their scope (I don't know if that has to mean "three repositories" - seems like one repo per project is
|
By
Brian Behlendorf
·
#245
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Release Taxonomy v0.1
We do add the git information as well to the version number. (And apparently use -git, not -dev for Jenkins - forgot about that.) So our full deb filename for example ends up looking like
We do add the git information as well to the version number. (And apparently use -git, not -dev for Jenkins - forgot about that.) So our full deb filename for example ends up looking like
|
By
Shawn Amundson
·
#244
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Explorer Proposal
+1
Could we start a project called "Hyperledger Blockchain Explorer" that started Incubation with three repos (DTCC, Intel, IBM contributions) with a goal of consolidating through incubation phase
+1
Could we start a project called "Hyperledger Blockchain Explorer" that started Incubation with three repos (DTCC, Intel, IBM contributions) with a goal of consolidating through incubation phase
|
By
Christopher B Ferris <chrisfer@...>
·
#243
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Explorer Proposal
Per our discussion in the TSC meeting today…
Sawtooth validators expose rest endpoints that an explorer like this one could consume.
Here’s the web
Per our discussion in the TSC meeting today…
Sawtooth validators expose rest endpoints that an explorer like this one could consume.
Here’s the web
|
By
Middleton, Dan <dan.middleton@...>
·
#242
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Release Taxonomy v0.1
Shawn,
Thanks for sharing this. I also agree that the -devN (number of commits since the tag) is very appropriate for publishing artefacts to the likes of npm, dockerhub, pypi, etc. The one point I'd
Shawn,
Thanks for sharing this. I also agree that the -devN (number of commits since the tag) is very appropriate for publishing artefacts to the likes of npm, dockerhub, pypi, etc. The one point I'd
|
By
Christopher B Ferris <chrisfer@...>
·
#241
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Release Taxonomy v0.1
+1 to Semver, I didn't realize it existed and was trying to replicate it, poorly. So all we'd need to agree to is that all Hyperledger projects must (should?) use the semver.org spec.
+1 to Semver, I didn't realize it existed and was trying to replicate it, poorly. So all we'd need to agree to is that all Hyperledger projects must (should?) use the semver.org spec.
|
By
Brian Behlendorf
·
#240
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Release Taxonomy v0.1
+1 on using semver to the extent practically possible.
Also, +1 to appending -devN, -alpha, -beeta, -rcN. as appropriate after the X.Y.Z. These get sorted properly by several packaging system
+1 on using semver to the extent practically possible.
Also, +1 to appending -devN, -alpha, -beeta, -rcN. as appropriate after the X.Y.Z. These get sorted properly by several packaging system
|
By
Shawn Amundson
·
#239
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Release Taxonomy v0.1
Won't make the TSC meeting, but some thoughts.
For our python modules, we are doing something similar to the openstack project where we have X.Y.Z-devN where N is the number of commits since X.Y.Z-1.
Won't make the TSC meeting, but some thoughts.
For our python modules, we are doing something similar to the openstack project where we have X.Y.Z-devN where N is the number of commits since X.Y.Z-1.
|
By
Shawn Amundson
·
#238
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Release Taxonomy v0.1
Sorry for not chiming in earlier... vacation will do that to ya (lose track of emails you intended to reply to).
Why not use semver [1]. I like the approach that Brian suggested, but I worry that
Sorry for not chiming in earlier... vacation will do that to ya (lose track of emails you intended to reply to).
Why not use semver [1]. I like the approach that Brian suggested, but I worry that
|
By
Christopher B Ferris <chrisfer@...>
·
#237
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Release Taxonomy v0.1
I've modified my proposal to include this numbering scheme as an alternative; on the call today we should pick one.
continue to iterate forward?
would like to propose a more converged versioning so
I've modified my proposal to include this numbering scheme as an alternative; on the call today we should pick one.
continue to iterate forward?
would like to propose a more converged versioning so
|
By
Brian Behlendorf
·
#236
·
|
|
Re: [Hyperledger Project TSC] 答复: Project Proposal - Onchain Antshares
Brian/Eric,
I agree with much of what Brian explained below. I too am very keen on developing broad, global support for all Hyperledger projects. I was just commenting on a PR that was providing a
Brian/Eric,
I agree with much of what Brian explained below. I too am very keen on developing broad, global support for all Hyperledger projects. I was just commenting on a PR that was providing a
|
By
Christopher B Ferris <chrisfer@...>
·
#235
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Explorer Proposal
I like this. It also sounds like there may be a similar offering from IBM, detaching their Bluemix-based console from Bluemix and making it stand-alone. Can I suggest that both efforts be
I like this. It also sounds like there may be a similar offering from IBM, detaching their Bluemix-based console from Bluemix and making it stand-alone. Can I suggest that both efforts be
|
By
Brian Behlendorf
·
#234
·
|
|
Re: [Hyperledger Project TSC] 答复: Project Proposal - Onchain Antshares
Hi Erik. I really appreciate the effort invested in bringing this technology to the public through Hyperledger, and the engagement of the China blockchain community. There are many
Hi Erik. I really appreciate the effort invested in bringing this technology to the public through Hyperledger, and the engagement of the China blockchain community. There are many
|
By
Brian Behlendorf
·
#233
·
|
|
[Hyperledger Project TSC] Hyperledger Explorer Proposal
Hi everyone,
I have submitted a Hyperledger Improvement proposal to TSC, to be discussed in the meeting tomorrow. The proposal is currently on the Wiki page.
Hi everyone,
I have submitted a Hyperledger Improvement proposal to TSC, to be discussed in the meeting tomorrow. The proposal is currently on the Wiki page.
|
By
Konrad Pabjan <konradpabjan@...>
·
#232
·
|
|
[Hyperledger Project TSC] Agenda for July 14, 2016
Action Item Review
Hackathon updates and planning (Todd Benzies)
July 26-27, San Francisco, REGISTER NOW / agenda planning
[August, Virtual]
Action Item Review
Hackathon updates and planning (Todd Benzies)
July 26-27, San Francisco, REGISTER NOW / agenda planning
[August, Virtual]
|
By
Todd Benzies <tbenzies@...>
·
#231
·
|
|
Re: [Hyperledger Project TSC] [technical-discuss] Ethereum Everywhere (C++ re-licensing)
Bob,
Sizable effort. Diligently and skillfully orchestrated. Large potential payoff. Thank you.
On Tue, Jul 12, 2016 at 5:15 PM Andrew Keys via hyperledger-technical-discuss
Bob,
Sizable effort. Diligently and skillfully orchestrated. Large potential payoff. Thank you.
On Tue, Jul 12, 2016 at 5:15 PM Andrew Keys via hyperledger-technical-discuss
|
By
Joseph Lubin
·
#230
·
|
|
Re: [Hyperledger Project TSC] [technical-discuss] Ethereum Everywhere (C++ re-licensing)
Strong work, Bob.
-- Please excuse spelling/grammatical errors in an attempt to respond as quickly as possible from my mobile.
On Jul 13, 2016, at 5:10 AM, Bob Summerwill via
Strong work, Bob.
-- Please excuse spelling/grammatical errors in an attempt to respond as quickly as possible from my mobile.
On Jul 13, 2016, at 5:10 AM, Bob Summerwill via
|
By
Andrew Keys <andrew.keys@...>
·
#229
·
|
|
[Hyperledger Project TSC] Ethereum Everywhere (C++ re-licensing)
https://bobsummerwill.com/2016/07/12/ethereum-everywhere/
TL;DR – What are you proposing?
I am proposing to the contributors that the C++ Ethereum client runtime cpp-ethereum be re-licensed from the
https://bobsummerwill.com/2016/07/12/ethereum-everywhere/
TL;DR – What are you proposing?
I am proposing to the contributors that the C++ Ethereum client runtime cpp-ethereum be re-licensed from the
|
By
Bob Summerwill <bob@...>
·
#228
·
|
|
Re: [Hyperledger Project TSC] Hyperledger Explorer Proposal
Konrad,
This is neat, thanks. Would you please complete a HIP (Hyperledger Improvement Proposal [1]
and add it to the wiki [2]. Thanks! I've asked Todd to add to this week's agenda.
[1]
Konrad,
This is neat, thanks. Would you please complete a HIP (Hyperledger Improvement Proposal [1]
and add it to the wiki [2]. Thanks! I've asked Todd to add to this week's agenda.
[1]
|
By
Christopher B Ferris <chrisfer@...>
·
#227
·
|
|
[Hyperledger Project TSC] Hyperledger Explorer Proposal
Hi everyone,
I've recently developed a Hyperledger Explorer UI that allows for information to be quickly queried from the blockchain and presented in a quick and easy to use manner. Similar to Bitcoin
Hi everyone,
I've recently developed a Hyperledger Explorer UI that allows for information to be quickly queried from the blockchain and presented in a quick and easy to use manner. Similar to Bitcoin
|
By
Konrad Pabjan <konradpabjan@...>
·
#226
·
|