Hi TSC, In light of the conversation at the TSC meeting about CI/CD last week, I spent the weekend looking closer at the Fabric CI/CD setup as well as considering Silas' comments carefully. I am of

That would be 4 pm UTC and 00:00 midnight UTC (April 4th for UTC and points East) Hello all, Multiple calls at different times with the same Agenda. This is an attempt to escape the time zone

Reminder: Hyperledger Fabric Quarterly Update Due #tsc-project-update When: Thursday, 4 April 2019 Organizer: community-architects@... Description: The Hyperledger Fabric update to the TSC was due

Reminder: Hyperledger Ursa Quarterly Update Due #tsc-project-update When: Thursday, 4 April 2019 Organizer: community-architects@... Description: The Hyperledger Ursa update to the TSC was due

This is great news!

Happy to hear that! I am currently away for a short vacation — someone from the team might jump in and help now. Let me check this after Monday next week. Nikolai

Hi TSC, I just completed an updated DCO audit of Iroha. The list of people we should try to contact is now down to 10. I got there by taking all of the Iroha repos and finding all of the commits that

To Shawn, This idea is based off of what Sovrin has set up for Ursa. Mike Lodder had done the bulk of the legwork here and deserves most of the credit...unless you guys hate the proposal, then blame

Dave, Can you elaborate on the proposed direction of travel regarding testnets? Is the idea that HL will run a CE instance of Gitlab in some infrastructure or that gitlab.com will be the instance? If

Sounds cool. Perhaps we could do an evaluation period were projects can evaluate using the gitlab setup to determine if it is sufficient to replace existing tooling, with the intent to report back on

Hi TSC, I put together a summary with details on what I propose we do to rework the HL CI/CD pipeline. The proposal can be found here: https://wiki.hyperledger.org/display/HYP/Software+Delivery As

I am pleased to announce that last week Hyperledger Indy finished the last outstanding CII badge requirement, and with that last hurdle cleared, we believe the project is ready to move from incubating

Reminder: Hyperledger Ursa Quarterly Update Due #tsc-project-update When: Thursday, 28 March 2019 Organizer: community-architects@... Description: The Hyperledger Ursa update to the TSC was due

Hi all, A brief recap of the experiment conducted on the 20th which was to have two calls with roughly the same Agenda at different times to spur participation across the globe. Also, evangelized on

Hi TSC, I just sent out the final survey to the Internship selection committee. They have today to fill it out. I will report the final selections tomorrow to this list. Dave --- David Huseby Security

I understand the concern; but since all writes require a login (as opposed to anonymous), the version history is kept, and authors being notified on edits (and others like me who subscribe to the

also without sounding too snarky... i would suggest that the access controls on that page are broken. for something as important as the agenda, it seems rather important to have a single owner who can

Regrets, I’ve been pulled into a client briefing this morning. Chris

Without trying to sound too snarky, there is an edit button in the upper right when you're logged in. To atone for any inadvertant snark, I've added those links myself, aside from

I believe a production ready release should imply that the project embodies mature technology and open source practices including community. That is, the project is ready to use in production because