Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for TSC Members to Attend (Pseudo)random Meetings #21

Closed
hartm opened this issue Dec 9, 2021 · 3 comments
Closed

Proposal for TSC Members to Attend (Pseudo)random Meetings #21

hartm opened this issue Dec 9, 2021 · 3 comments
Labels
approved Approved by TOC vote decision-log Decisions before the TOC

Comments

@hartm
Copy link

hartm commented Dec 9, 2021

Background:
One thing that could possibly benefit the TSC (and Hyperledger as a whole) is more awareness of and interaction with different projects. This could spur more cross-project collaboration, less fragmentation between projects, and, in general, more project happiness with the TSC.

Proposal:
The TSC collectively requests that each TSC member attend one project meeting a month for a project with which they are unaffiliated and have not been a contributor (and, ideally, one that they have not attended before). Whether people want to introduce themselves and participate or just listen wouldn't matter too much: just attendance would be great.

On the TSC wiki, a page will be created to keep track of meeting attendance in some kind of spreadsheet (either public, if people are OK with it, or private to the TSC) with the main purpose being that TSC members know which meetings other members have attended so that TSC members can stagger their attendance across many project meetings. This is because this initiative will be much more effective if TSC members attend many different meetings rather than all attending, say, a meeting of what is perceived to be a currently popular project.

We also propose to include SIGs and working groups as possible options for TSC members to attend. Finally, if non-TSC maintainers wish to be included, we propose to include them as well.

The time commitment--one meeting a month--should be pretty small, and the hope is that going to these meetings would be very informative for TSC members, and an opportunity for projects who aren't strongly connected to the TSC to ask questions about HL as a whole if they want.

We also propose that TSC members be invited (but not required) to report back during TSC meetings about anything they found interesting, noteworthy, or that needs addressing in some sort of brief discussion. We also suggest that TSC members that adhere to this schedule be rewarded with food and/or drink by the HL staff at the next in-person event.

@hartm
Copy link
Author

hartm commented Dec 9, 2021

Note: Add in suggestion that TSC members should rotate through different groups' meetings, not just attend one repeatedly.

@ryjones ryjones added the decision-log Decisions before the TOC label Dec 9, 2021
@knagware9
Copy link

Its good initiative +1

@tkuhrt tkuhrt added the approved Approved by TOC vote label Dec 16, 2021
@tkuhrt
Copy link
Contributor

tkuhrt commented Dec 16, 2021

Approved during December 16, 2021 TSC meeting
Votes:

  • 12 approved
  • 1 abstained
  • 2 absent

@tkuhrt tkuhrt closed this as completed Dec 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Approved by TOC vote decision-log Decisions before the TOC
Projects
None yet
Development

No branches or pull requests

4 participants