> Itwould be better to call these "points of contact", as to notconfuse it with a decision-making capability. > Within some of the projects, wehave a team of long-term maintainers for decision making,

Examples of similar roles at other OSS projects: TPL or PTL or PLT are all terms that can be searched on for more examples of roles and additional responsibilities.

Point of contact (POC seems an overloaded, if not charged, acronym): While I can appreciate the intent here (thanks, Brian for the elaboration), it is less clear that a single point of contact, even

I think "point of contact" is fine. I'll take the blame for the word "Chair" - as we were discussing some of the issues Silona mentioned in her original email (and which we could have

I think this is the right idea. We can even generalize this system and have a project “point of contact for X” where X could be security, quarterly reporting, press releases, etc. Most (or

I want to point out that for the last two years, I have maintained a list of "security volunteers" that are "points of contact" in each project that are also on the security@... mailing list. I try

Agreed that the name "chair" implies more than what is actually intended. "Point of contact" seems more appropriate. Regarding the rotating TSC updates... i think there is a difference between who

Hello all, Fully support the sentiments expressed by Shawn and Chris. However, in practical terms, we do need someone (anyone) reporting to TSC or the community. When we do not have a "point of

+100 for what Shawn said "The CA team is seeing that larger projects that have many diverse repos and having Maintainers be responsible doesn't scale. There is often confusion on who to speak

It would be better to call these "points of contact", as to not confuse it with a decision-making capability. Within some of the projects, we have a team of long-term maintainers for decision making,

Reminder: Hyperledger Quilt Quarterly Update Due #tsc-project-update When: Thursday, 20 June 2019 View Event Organizer: community-architects@... Description: The Hyperledger Quilt update

Unofficial +1, this would be very helpful from the marketing side tooThis message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential

I would like all projects to either elect or have the TSC nominate Chairs and Vice Chairs. The Chairs would serve more of a project manager role within the project's community. The CA team is

Agenda is posted. Please suggest announcements etc. https://wiki.hyperledger.org/display/HYP/2019+06+20+TSC+Agenda Notice Caliper Update is live - please read in advance. I will also send a separate

Confluence will experience a short outage on Friday at 9am Eastern NYC time zone as we do a hard rebuild of Confluence's indexes to fix a bug. We apologize for the outage. We understand that the

AWESOME to see the energy around collaborating on Smart Contract design for Supply Chain use cases on Hyperledger!! Hyperledger Grid is fantastic landing place for that logic/implementation, and is

Hi Brad, That’s great to hear. Are you able to share the smart contract design that you speak of below? In the Supply Chain SIG, which I currently chair, we have a project proposal underway that

This whole podcast episode is good, https://www.thisamericanlife.org/674/get-a-spine but in particular the second act seemed relevant OSS communities.

Service Desk migration The Linux Foundation IT is migrating from email-based support system using Request Tracker to a web-based platform provided by Jira Service Desk. We

I wouldn't describe Indy or Grid as a library. A lot of Grid is library/component stuff, but describing it that way in a taxonomy minimizes the overall project, because it does attempt to dictate some