1. Fabric
  2. Topics

regular weekly hyperledger/fabric technical planning with maintainers

Binh Q Nguyen <binhn@...>
 

Hi Folks,

I'd like to propose a weekly or bi weekly technical planning discussion on Hyperledger Fabric project. The discussion will be about the key items to take on, based on the issues created by the community, whether changes to the existing functions, restructuring, new functions/features, bus, more tests, more documents, etc.

We would document these items as issues on Boards->Current and requesting contribution from the community to implement.

I would suggest the meeting to be Monday at 11am EST to accommodate folks from other time zones (I know that's not the best for many regions).

Let me know if this is workable for you or propose a few time slots.

Thanks,

- Binh
Haskins, Gregory <GHaskins@...>
 

Hi Binh,

 

I think that is a good idea, and Monday 11a ET works for me.

 

-Greg

 

From: Binh Q Nguyen [mailto:binhn@...]
Sent: 16 May 2016 16:50
To: Haskins, Gregory; Tamas Blummer; robert@...; Sheehan Anderson
Cc: hyperledger-fabric@...
Subject: regular weekly hyperledger/fabric technical planning with maintainers

 

Hi Folks,

I'd like to propose a weekly or bi weekly technical planning discussion on Hyperledger Fabric project. The discussion will be about the key items to take on, based on the issues created by the community, whether changes to the existing functions, restructuring, new functions/features, bus, more tests, more documents, etc.

We would document these items as issues on Boards->Current and requesting contribution from the community to implement.

I would suggest the meeting to be Monday at 11am EST to accommodate folks from other time zones (I know that's not the best for many regions).

Let me know if this is workable for you or propose a few time slots.

Thanks,

- Binh

Please read these warnings and restrictions:

This e-mail transmission is strictly confidential and intended solely for the ordinary user of the e-mail address to which it was addressed. It may contain legally privileged and/or CONFIDENTIAL information.

The unauthorised use, disclosure, distribution and/or copying of this e-mail or any information it contains is prohibited and could, in certain circumstances, constitute a criminal offence.

If you have received this e-mail in error or are not an intended recipient please inform London Stock Exchange Group (“LSEG”) immediately by return e-mail or telephone 020 7797 1000.

We advise that in keeping with good computing practice the recipient of this e-mail should ensure that it is virus free. We do not accept responsibility for any virus that may be transferred by way of this e-mail.

E-mail may be susceptible to data corruption, interception and unauthorised amendment, and we do not accept liability for any such corruption, interception or amendment or any consequences thereof.

Calls to London Stock Exchange Group may be recorded to enable LSEG to carry out its regulatory responsibilities.

London Stock Exchange Group plc

10 Paternoster Square
London
EC4M 7LS

Registered in England and Wales No 05369106
Sheehan Anderson <sheehan@...>
 

+1

-Sheehan

"Haskins, Gregory" ---05/16/2016 06:01:45 PM---Hi Binh, I think that is a good idea, and Monday 11a ET works for me.

From: "Haskins, Gregory" <GHaskins@...>
To: Binh Q Nguyen/Raleigh/IBM@IBMUS, Tamas Blummer <tamas@...>, "robert@..." <robert@...>, Sheehan Anderson/Durham/IBM@IBMUS
Cc: "hyperledger-fabric@..." <hyperledger-fabric@...>
Date: 05/16/2016 06:01 PM
Subject: RE: regular weekly hyperledger/fabric technical planning with maintainers




Hi Binh,

I think that is a good idea, and Monday 11a ET works for me.

-Greg

From: Binh Q Nguyen [mailto:binhn@...]
Sent: 16 May 2016 16:50
To: Haskins, Gregory; Tamas Blummer; robert@...; Sheehan Anderson
Cc: hyperledger-fabric@...
Subject: regular weekly hyperledger/fabric technical planning with maintainers

Hi Folks,

I'd like to propose a weekly or bi weekly technical planning discussion on Hyperledger Fabric project. The discussion will be about the key items to take on, based on the issues created by the community, whether changes to the existing functions, restructuring, new functions/features, bus, more tests, more documents, etc.

We would document these items as issues on Boards->Current and requesting contribution from the community to implement.

I would suggest the meeting to be Monday at 11am EST to accommodate folks from other time zones (I know that's not the best for many regions).

Let me know if this is workable for you or propose a few time slots.

Thanks,

- Binh

Please read these warnings and restrictions:

This e-mail transmission is strictly confidential and intended solely for the ordinary user of the e-mail address to which it was addressed. It may contain legally privileged and/or CONFIDENTIAL information.

The unauthorised use, disclosure, distribution and/or copying of this e-mail or any information it contains is prohibited and could, in certain circumstances, constitute a criminal offence.

If you have received this e-mail in error or are not an intended recipient please inform London Stock Exchange Group (“LSEG”) immediately by return e-mail or telephone 020 7797 1000.

We advise that in keeping with good computing practice the recipient of this e-mail should ensure that it is virus free. We do not accept responsibility for any virus that may be transferred by way of this e-mail.

E-mail may be susceptible to data corruption, interception and unauthorised amendment, and we do not accept liability for any such corruption, interception or amendment or any consequences thereof.

Calls to London Stock Exchange Group may be recorded to enable LSEG to carry out its regulatory responsibilities.

London Stock Exchange Group plc

10 Paternoster Square
London
EC4M 7LS

Registered in England and Wales No 05369106
Baohua Yang
 

+1 to support the meeing.

Would like to try attending it, while hour earlier would be better for me.

Thanks!

On Tue, May 17, 2016 at 4:49 AM, Binh Q Nguyen <binhn@...> wrote:

Hi Folks,

I'd like to propose a weekly or bi weekly technical planning discussion on Hyperledger Fabric project. The discussion will be about the key items to take on, based on the issues created by the community, whether changes to the existing functions, restructuring, new functions/features, bus, more tests, more documents, etc.

We would document these items as issues on Boards->Current and requesting contribution from the community to implement.

I would suggest the meeting to be Monday at 11am EST to accommodate folks from other time zones (I know that's not the best for many regions).

Let me know if this is workable for you or propose a few time slots.

Thanks,

- Binh


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




--
Best wishes!
Baohua
Tamas Blummer <tamas@...>
 

Good idea. Please send schedule suggestion.


Tamas Blummer
CHIEF LEDGER ARCHITECT



C: +36 30 4605877 

On 17 May 2016, at 00:17, Sheehan Anderson <sheehan@...> wrote:

+1

-Sheehan

<graycol.gif>"Haskins, Gregory" ---05/16/2016 06:01:45 PM---Hi Binh, I think that is a good idea, and Monday 11a ET works for me.

From: "Haskins, Gregory" <GHaskins@...>
To: Binh Q Nguyen/Raleigh/IBM@IBMUS, Tamas Blummer <tamas@...>, "robert@..." <robert@...>, Sheehan Anderson/Durham/IBM@IBMUS
Cc: "hyperledger-fabric@..." <hyperledger-fabric@...>
Date: 05/16/2016 06:01 PM
Subject: RE: regular weekly hyperledger/fabric technical planning with maintainers




Hi Binh,

I think that is a good idea, and Monday 11a ET works for me.

-Greg

From: Binh Q Nguyen [mailto:binhn@...]
Sent: 16 May 2016 16:50
To: Haskins, Gregory; Tamas Blummer; robert@...; Sheehan Anderson
Cc: hyperledger-fabric@...
Subject: regular weekly hyperledger/fabric technical planning with maintainers

Hi Folks,

I'd like to propose a weekly or bi weekly technical planning discussion on Hyperledger Fabric project. The discussion will be about the key items to take on, based on the issues created by the community, whether changes to the existing functions, restructuring, new functions/features, bus, more tests, more documents, etc.

We would document these items as issues on Boards->Current and requesting contribution from the community to implement.

I would suggest the meeting to be Monday at 11am EST to accommodate folks from other time zones (I know that's not the best for many regions).

Let me know if this is workable for you or propose a few time slots.

Thanks,

- Binh

Please read these warnings and restrictions:

This e-mail transmission is strictly confidential and intended solely for the ordinary user of the e-mail address to which it was addressed. It may contain legally privileged and/or CONFIDENTIAL information.

The unauthorised use, disclosure, distribution and/or copying of this e-mail or any information it contains is prohibited and could, in certain circumstances, constitute a criminal offence.

If you have received this e-mail in error or are not an intended recipient please inform London Stock Exchange Group (“LSEG”) immediately by return e-mail or telephone 020 7797 1000.

We advise that in keeping with good computing practice the recipient of this e-mail should ensure that it is virus free. We do not accept responsibility for any virus that may be transferred by way of this e-mail.

E-mail may be susceptible to data corruption, interception and unauthorised amendment, and we do not accept liability for any such corruption, interception or amendment or any consequences thereof.

Calls to London Stock Exchange Group may be recorded to enable LSEG to carry out its regulatory responsibilities.

London Stock Exchange Group plc

10 Paternoster Square
London
EC4M 7LS

Registered in England and Wales No 05369106





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.

1 - 5 of 5