1. Toc
  2. Topics

[External] Re: [Hyperledger TSC] Call for topics for this week's TSC call

David Boswell
 

Peter,

Thanks for reviewing the doc.  And that's good feedback about providing a sentence or two at the top directing people where to go with feedback or questions.  I updated the doc to add that. 

And yes, having more specific pointers for each line sounds worth doing too.  If we decide that these are the right services to have, we can go in and provide more details for the specific items.

Thanks,
David


On Tue, Jan 11, 2022 at 10:46 AM Somogyvari, Peter <peter.somogyvari@...> wrote:
Hi David,

LGTM, I think there's plenty of incentives for projects to make the moves and the table in the document makes a lot of information available in a very efficient manner.

One thing that came to mind is that we could have one short sentence on the top or bottom clarifying where should people go with questions, e.g. we could explicitly encourage them to ask the questions in the comments of the wiki page or to email the community architects mailing list. 
If there is single answer, because it's topic dependent, then maybe we could even open a new column just for directions per line item (for example the security audit related questions may be different from marketing related questions, etc.)

Kind regards,
Peter

Peter Somogyvari

Technology Architect

Accenture Products & Platforms (APP)

Office: +1 (415) 537-5541

Mobile: +1 (650) 488-1741


From: tsc@... <tsc@...> on behalf of David Boswell <dboswell@...>
Sent: Monday, January 10, 2022 3:58 PM
To: Kuhrt, Tracy A. <tracy.a.kuhrt@...>
Cc: Hyperledger List <tsc@...>
Subject: [External] Re: [Hyperledger TSC] Call for topics for this week's TSC call
 
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.

For another topic, I'd be interested in feedback on the draft project services document.  Now that it is in a more readable grid format, it may be easier for people to review.  Does this look like the right set of services for each level?  Are we providing enough incentive for developers to move through the different levels?


Thanks,
David

On Mon, Jan 10, 2022 at 1:56 PM Kuhrt, Tracy A. via lists.hyperledger.org <tracy.a.kuhrt=accenture.com@...> wrote:
Hello, everyone.

Does anyone have any topics that they would like to add to this week's TSC agenda? At the moment, I have a single item The Importance of TSC Quarterly Project Updates.

We also have a number of quarterly reports that are due, but not yet been submitted:
  • 2021 Q4 Hyperledger Explorer (due 06 Dec 2021)
  • 2021 Q4 Hyperledger Avalon (due 13 Dec 2021)
  • 2021 Q4 Hyperledger Caliper (due 20 Dec 2021)
  • 2022 Q1 Hyperledger Cactus (due 10 Jan 2022)
  • 2022 Q1 Hyperledger Fabric (due 10 Jan 2022)

I am looking for other topics, presentations, or discussions that we would like to have.

Tracy



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com

Somogyvari, Peter
 

Hi David,

LGTM, I think there's plenty of incentives for projects to make the moves and the table in the document makes a lot of information available in a very efficient manner.

One thing that came to mind is that we could have one short sentence on the top or bottom clarifying where should people go with questions, e.g. we could explicitly encourage them to ask the questions in the comments of the wiki page or to email the community architects mailing list. 
If there is single answer, because it's topic dependent, then maybe we could even open a new column just for directions per line item (for example the security audit related questions may be different from marketing related questions, etc.)

Kind regards,
Peter

Peter Somogyvari

Technology Architect

Accenture Products & Platforms (APP)

Office: +1 (415) 537-5541

Mobile: +1 (650) 488-1741


From: tsc@... <tsc@...> on behalf of David Boswell <dboswell@...>
Sent: Monday, January 10, 2022 3:58 PM
To: Kuhrt, Tracy A. <tracy.a.kuhrt@...>
Cc: Hyperledger List <tsc@...>
Subject: [External] Re: [Hyperledger TSC] Call for topics for this week's TSC call
 
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.

For another topic, I'd be interested in feedback on the draft project services document.  Now that it is in a more readable grid format, it may be easier for people to review.  Does this look like the right set of services for each level?  Are we providing enough incentive for developers to move through the different levels?


Thanks,
David

On Mon, Jan 10, 2022 at 1:56 PM Kuhrt, Tracy A. via lists.hyperledger.org <tracy.a.kuhrt=accenture.com@...> wrote:
Hello, everyone.

Does anyone have any topics that they would like to add to this week's TSC agenda? At the moment, I have a single item The Importance of TSC Quarterly Project Updates.

We also have a number of quarterly reports that are due, but not yet been submitted:
  • 2021 Q4 Hyperledger Explorer (due 06 Dec 2021)
  • 2021 Q4 Hyperledger Avalon (due 13 Dec 2021)
  • 2021 Q4 Hyperledger Caliper (due 20 Dec 2021)
  • 2022 Q1 Hyperledger Cactus (due 10 Jan 2022)
  • 2022 Q1 Hyperledger Fabric (due 10 Jan 2022)

I am looking for other topics, presentations, or discussions that we would like to have.

Tracy



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com

1 - 2 of 2