Versions Compared

Old Version 5

changes.mady.by.user Sean Bohan

Saved on

compared with

New Version Current

changes.mady.by.user Tracy Kuhrt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: Hyperledger Code of Conduct

Announcements

Quarterly reports

  • 2022 Q1 Hyperledger Cello (due  )
  • 2022 Q1 Hyperledger Explorer (due )
  • 2022 Q1 Hyperledger Firefly (due )

...

Discussion

  • Creation of a short term task force for reviewing mentorship projects Angelo de Caro, Danno Ferrin, kamlesh nagware, and Peter Somogyvari have volunteered to serve on the task force
    • 3-4 people to review the proposals to make sure the projects are a good fit as mentorship projects and the activity/results/outcomes will be relevant to the Hyperledger community.
    • review period will be 2 weeks from March 10-24
    • determine if any changes should be made to existing criteria:
      • The selected proposals have clearly scoped learning objectives and outcomes that are suitable for one mentee, either a student developer/researcher or a new contributor, to complete within 12 weeks if working full time or 24 weeks if working part time.  
      • The selected proposals will represent a nice mix of project difficulty levels. Some low, medium, and high difficulties.
      • The selected proposals will maximize the diversity of the proposals, mentors, and mentees.
      • The selected proposals should have a direct connection or relevance to an existing Hyperledger project or lab or ecosystem.
      • The selected proposals will further increase the contributor/maintainer base of the related Hyperledger project or lab or ecosystem.
      • The selected proposals are related to as many Hyperledger projects or lab as possible.
      • The mentors of the selected proposals will represent a nice mix of experienced and new mentors.
  • Open discussion on improving the TSC :(What should we be doing differently to allow you to be more engaged in the discussions both during the TSC calls and between the TSC calls?What  What are the reasons why we are not reviewing project reports (yes, there are no 2022 Q1 quarterly reports were all TSC members have reviewed)?What  What can we do to improve the meetings that we are having as a TSC?)
    • In other organizations, the committee members each have a responsibility that they report on during the call.
    • Task forces are seen as a popular way to engage. → Brainstorm different task forces that we can create.
    • Having broader discussions on projects during the TSC call. → Open invitation to present at the TSC call for SIGs, WGs, projects, and labs. Find a way to get back the hackfest vibe where we can get updates on what is happening in the projects.
    • Unknown responsibilities → Document TSC responsibilities and have a refresher discussion with existing TSC members and a welcome discussion with new TSC members.
    • TSC is responsible for removing blockers in the community. → Ask the community what is the most helpful thing to be engaged on.
    • Differences in the structure of the SIGs reporting to the GB and WGs and TFs reporting to the TSC → Staff is working on structure.
    • How do we steer instead of react? →
      • Consider whether we should have a TAC instead of a TSC
      • Review Ry's proposal on Reforming the TSC
      • Create a task force on evaluating the Hyperledger ecosystem from a technology perspective. Specifically, a gap analysis of what we might be missing compared to the public blockchain ecosystem.
      • Consider ways in which we might be able to standardize certain pieces of technology
  • Follow up on Hyperledger Project Families (please provide thoughts in document prior to meeting)
  • Creation of Task Force for Project Health Collection issue (please provide thoughts in issue prior to meeting)

...

Recordings

Attachments

Attended by: