Date:
...
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
|---|
Attendees
- Anthony Lusardi (Deactivated)
- Hart Montgomery
- Tracy Kuhrt
- Bobbi Muscara
- Arun .S.M.
- Arnaud J LE HORS
- Travin Keith
- Csilla Zsigri
- David Boswell
- Daniela Barbosa
...
- Discussion on Landscape Layout- to replace greenhouse
- For Technical audiences/more experienced
- easy to update
- Can filter to dig deeper, Click on more info
- Experienced community members, trying to build and make connections between projects- already familiar with it
- Technical audience may want something further
- Can get into the details
- Github to updates- easy way
- Developer content: Landscape/projects, how related, SIGs/WGs- get started
- Explain Dependency between projects
- Stack/diagrams, helps
- all projects within a certain category would be kept equal, but there was some discussion on differentiating between projects by their stage (e.g v1) as well.
- it could make sense to surface active or graduated projects more than an incubating project.
- "project families" clustering idea.
- https://lfanalytics.io/projects/hyperledger
- https://landscape.hyperledger.org/
- https://lists.hyperledger.org/g/maintainers
Today
- Greenhouse: Review HL Member Landscape: https://landscape.hyperledger.org/card-mode?grouping=category&project=company&style=borderless
- Csilla: dlt landscape
- Also being formatted for HL for display of member companies (pulls info from SFDC)
Next steps
- Review HL Member LandscapeWhitepaper: Review Yearly report:
- Technical: Start here: https://
- Business: SIGs, Landscape, membership
- New Project:
- Take a fresh look at the mechanism of TSC governance to address the tension inherent in any multi-project community like ours in “driving projects toward convergence and giving them roadmap autonomy.” Should “convergence” be a goal? Should “interoperability”? How are those defined anyway? What’s the most useful form of alignment we should require, and ideally aim for, across all HL projects, and all HL maintainers? A task force representing the HL members could work with a subset of the TSC to draft specifics for GB review and approval.
- Take a fresh look at the mechanism of TSC governance to address the tension inherent in any multi-project community like ours in “driving projects toward convergence and giving them roadmap autonomy.” Should “convergence” be a goal? Should “interoperability”? How are those defined anyway? What’s the most useful form of alignment we should require, and ideally aim for, across all HL projects, and all HL maintainers? A task force representing the HL members could work with a subset of the TSC to draft specifics for GB review and approval.
- Start getting buy-in from maintainers, previous flat presentation to show people
- Ask "Want numbers to grow?"
- Connect with maintainers:
- Email List
- Attend calls for projects
- Present numbers on growth/shrunk, with what collateral, what we haven't tried - question adoption "should something be done"
- Are projects at a place where you want them to be
Next Meeting Deliverables
- Interface Landscape V1
- Choose your own adventure wireframe
Action items
- Csilla Zsigri Csilla to share demo of landscape work she is doing
- Helen Garneau Sort entry points between Business/Technical interest into shared doc
- Projects + labs + WG + SIGs / Usecase, webinars, meetups,