[Hyperledger Project TSC] Fabric SDK working group
We should set up a separate mailing list for the SDK work - potentially separate per SDK, e.g. python and java and others down the pipe - so as to provide persistence of communication & decisions, and ideally an alternative for weekly conference calls, since finding a good time for a global development team is increasingly difficult.
Is there more we (the LF) should or need to do to enable separate space on Jira and in Gerrit for the SDK work?
Brian
On 10/18/2016 11:07 AM, Vishnumolakala, Pardha S. via hyperledger-tsc wrote:
Vipin,
This group is specifically focused on Fabric and is defining how SDK needs interacts with Fabric (registering/enrolling) and what API is needed to develop applications. Definition of applications include all that you mentioned (legacy apps/explorers/wallets) or any other client that needs to interact with fabric to invoke/query/deploy chaincodes, send transactions etc..
Thanks
Pardha
From: vipin bharathan [mailto:vipinsun@...]
Sent: Tuesday, October 18, 2016 1:47 PM
To: Vishnumolakala, Pardha S.
Cc: hyperledger-tsc@lists.hyperledger.org
Subject: Re: [Hyperledger Project TSC] Fabric SDK working group
Hi Pardha,
Sounds like a great idea. I would love to join. If this is for a generic SDK why would it be called Fabric SDK?
Also when you say applications, does it mean legacy apps or others like blockchain explorers or wallets?Regards,
Vipin
On Oct 18, 2016 12:10 PM, "Vishnumolakala, Pardha S. via hyperledger-tsc" <hyperledger-tsc@lists.
hyperledger.org> wrote: Hi,
Fabric SDK working group is formed to create a common SDK specification describing the API required by applications to interact with blockchain network.
This group meets every week on Thursday @7am (US EDT). We request community members to participate and contribute.
All the details including the meeting link is posted on wiki @ https://wiki.hyperledger.org/
groups/fabric-sdk/fabric-sdk- wg
Thanks
Pardha
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger- tsc
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
_______________________________________________ hyperledger-tsc mailing list hyperledger-tsc@lists. hyperledger.org https://lists.hyperledger.org/ mailman/listinfo/hyperledger- tsc
-- Brian Behlendorf Executive Director, Hyperledger bbehlendorf@linuxfoundation.org Twitter: @brianbehlendorf
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger- tsc
We should set up a separate mailing list for the SDK work - potentially separate per SDK, e.g. python and java and others down the pipe - so as to provide persistence of communication & decisions, and ideally an alternative for weekly conference calls, since finding a good time for a global development team is increasingly difficult.
Is there more we (the LF) should or need to do to enable separate space on Jira and in Gerrit for the SDK work?
Brian
On 10/18/2016 11:07 AM, Vishnumolakala, Pardha S. via hyperledger-tsc wrote:
Vipin,
This group is specifically focused on Fabric and is defining how SDK needs interacts with Fabric (registering/enrolling) and what API is needed to develop applications. Definition of applications include all that you mentioned (legacy apps/explorers/wallets) or any other client that needs to interact with fabric to invoke/query/deploy chaincodes, send transactions etc..
Thanks
Pardha
From: vipin bharathan [mailto:vipinsun@...]
Sent: Tuesday, October 18, 2016 1:47 PM
To: Vishnumolakala, Pardha S.
Cc: hyperledger-tsc@...
Subject: Re: [Hyperledger Project TSC] Fabric SDK working group
Hi Pardha,
Sounds like a great idea. I would love to join. If this is for a generic SDK why would it be called Fabric SDK?
Also when you say applications, does it mean legacy apps or others like blockchain explorers or wallets?Regards,
Vipin
On Oct 18, 2016 12:10 PM, "Vishnumolakala, Pardha S. via hyperledger-tsc" <hyperledger-tsc@...> wrote:
Hi,
Fabric SDK working group is formed to create a common SDK specification describing the API required by applications to interact with blockchain network.
This group meets every week on Thursday @7am (US EDT). We request community members to participate and contribute.
All the details including the meeting link is posted on wiki @ https://wiki.hyperledger.org/groups/fabric-sdk/fabric-sdk-wg
Thanks
Pardha
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
_______________________________________________ hyperledger-tsc mailing list hyperledger-tsc@... https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
-- Brian Behlendorf Executive Director, Hyperledger bbehlendorf@... Twitter: @brianbehlendorf
Vipin,
This group is specifically focused on Fabric and is defining how SDK needs interacts with Fabric (registering/enrolling) and what API is needed to develop applications. Definition of applications include all that you mentioned (legacy apps/explorers/wallets) or any other client that needs to interact with fabric to invoke/query/deploy chaincodes, send transactions etc..
Thanks
Pardha
Sent: Tuesday, October 18, 2016 1:47 PM
To: Vishnumolakala, Pardha S.
Cc: hyperledger-tsc@...
Subject: Re: [Hyperledger Project TSC] Fabric SDK working group
Hi Pardha,
Sounds like a great idea. I would love to join. If this is for a generic SDK why would it be called Fabric SDK?
Also when you say applications, does it mean legacy apps or others like blockchain explorers or wallets?
Regards,
Vipin
On Oct 18, 2016 12:10 PM, "Vishnumolakala, Pardha S. via hyperledger-tsc" <hyperledger-tsc@...> wrote:
Hi,
Fabric SDK working group is formed to create a common SDK specification describing the API required by applications to interact with blockchain network.
This group meets every week on Thursday @7am (US EDT). We request community members to participate and contribute.
All the details including the meeting link is posted on wiki @ https://wiki.hyperledger.org/groups/fabric-sdk/fabric-sdk-wg
Thanks
Pardha
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email
and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
Hi Pardha,
Sounds like a great idea. I would love to join. If this is for a generic SDK why would it be called Fabric SDK?
Also when you say applications, does it mean legacy apps or others like blockchain explorers or wallets?
Regards,
Vipin
Hi,
Fabric SDK working group is formed to create a common SDK specification describing the API required by applications to interact with blockchain network.
This group meets every week on Thursday @7am (US EDT). We request community members to participate and contribute.
All the details including the meeting link is posted on wiki @ https://wiki.hyperledger.org/
groups/fabric-sdk/fabric-sdk- wg
Thanks
Pardha
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger- tsc
Hart,
You can add your comments to the Fabric SDK spec document
https://docs.google.com/document/d/1R5RtIBMW9fZpli37E5Li5_Q9ve3BnQ4q3gWmGZj6Sv4/edit
Thanks
Pardha
Sent: Tuesday, October 18, 2016 1:32 PM
To: hyperledger-tsc@...
Subject: Re: [Hyperledger Project TSC] Fabric SDK working group
I’d love to contribute, but the meeting time is just a bit too brutal for me (4am in California). What would the working group’s preferred method of commenting be if I can’t make the meeting?
Thanks,
Hart
From:
hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...]
On Behalf Of Vishnumolakala, Pardha S. via hyperledger-tsc
Sent: Tuesday, October 18, 2016 9:10 AM
To: hyperledger-tsc@...
Subject: [Hyperledger Project TSC] Fabric SDK working group
Hi,
Fabric SDK working group is formed to create a common SDK specification describing the API required by applications to interact with blockchain network.
This group meets every week on Thursday @7am (US EDT). We request community members to participate and contribute.
All the details including the meeting link is posted on wiki @ https://wiki.hyperledger.org/groups/fabric-sdk/fabric-sdk-wg
Thanks
Pardha
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email
and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
I’d love to contribute, but the meeting time is just a bit too brutal for me (4am in California). What would the working group’s preferred method of commenting be if I can’t make the meeting?
Thanks,
Hart
Sent: Tuesday, October 18, 2016 9:10 AM
To: hyperledger-tsc@...
Subject: [Hyperledger Project TSC] Fabric SDK working group
Hi,
Fabric SDK working group is formed to create a common SDK specification describing the API required by applications to interact with blockchain network.
This group meets every week on Thursday @7am (US EDT). We request community members to participate and contribute.
All the details including the meeting link is posted on wiki @ https://wiki.hyperledger.org/groups/fabric-sdk/fabric-sdk-wg
Thanks
Pardha
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
Hi,
Fabric SDK working group is formed to create a common SDK specification describing the API required by applications to interact with blockchain network.
This group meets every week on Thursday @7am (US EDT). We request community members to participate and contribute.
All the details including the meeting link is posted on wiki @ https://wiki.hyperledger.org/groups/fabric-sdk/fabric-sdk-wg
Thanks
Pardha
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.