Skip to content

Working Group Meeting ‐ July 29th 2024

itsbrandond edited this page Jul 30, 2024 · 1 revision

Meeting Date: July 29th 2024 at 10am ET

Meeting Recording (Video): Google Drive Link →


Attendance:

  • Brandon Davenport, Hgraph
  • Tyler McDonald, Hgraph
  • Adrián Marín, Kabila
  • Ashe Oro, Hashgraph
  • Greg Scullard, Hashgraph
  • Ihor Zinchenko, Blade Wallet
  • May Chan, HashPack
  • Nikhil Asrani, Bonzo Finance
  • Tyler Cote, HashPack
  • Volodymyr Rozhnov, Blade Wallet

Agenda:

  • Intros & housekeeping
  • Start recording & transcripts
  • Updates on Hedera WalletConnect integration.
  • Review of open pull requests and issues.
  • Discussion on the implementation and demo improvements.
  • Strategy for prioritizing and resolving issues.
  • Community support and communication channels.
  • Vote to make meeting public
  • Publish minutes & recording to Github
  • Review & outline action items
  • End meeting

Votes:

  • Publicize video recording and notes for this meeting (majority vote via poll)
    • Results: APPROVED

Meeting minutes

1. Updates on Hedera WalletConnect Integration

  • Brandon Davenport opened the meeting discussing the initiative's ongoing efforts to simplify the implementation for dApps.
  • Focus on expanding the initiative beyond standards to include implementation details and library usage improvements.

2. Review of Open Pull Requests (PRs)

  • Brandon Davenport and Tyler McDonald reviewed key PRs: #134, #125, #97, #77, and a new PR #224 by Tyler McDonald.

  • PR #224:

    • Aims to resolve issues with esbuild causing problems in Next.js 14.
    • Changes the bundling process to improve compatibility.
    • Introduces a pre-release process to facilitate testing.

Action Item: Move forward with PR #224, pending further testing and feedback.

3. Discussion on Implementation and Demo Improvements

  • Discussion on where to host demo projects: within the main repository or in a separate repository.
  • May Chan suggested creating a React project with the WalletConnect library pre-integrated for ease of use by new developers.
  • Adrián Marín proposed having a dedicated website or GitHub page to host these examples and provide clear documentation.

Consensus:

  • Host example projects within the main repository.
  • Use GitHub Pages for live demos.

4. Strategy for Prioritizing and Resolving Issues

  • Ashe Oro suggested implementing a priority labeling system (P0-P3) and T-shirt sizing (small, medium, large, extra-large) for issues.
  • Tyler McDonald and Brandon Davenport to take initial steps in labeling and prioritizing existing issues.

Action Item:

  • Tyler and Brandon to label and prioritize issues.
  • Community to review and provide feedback asynchronously.

5. Community Support and Communication Channels

  • Adrián Marín proposed creating a dedicated Discord channel for developers to resolve issues collaboratively.
  • Tyler Cote mentioned an existing Hedera developer Discord, which will be activated soon.

Action Item:

  • Tyler Cote to share the Discord link in Slack.
  • Discussion on whether to use GitHub discussions for formal issue tracking or keep it within Discord.

6. Specific Issue Discussions

  • Issue #184: Discussion on implementing get account key functionality.

  • General agreement to avoid direct mirror node calls in the front end due to security concerns.

  • Suggested allowing developers to provide their own mirror node endpoints.

Next Steps:

  • Further discussion needed to finalize the implementation approach for get account key.

7. Final Notes

  • Brandon Davenport reminded everyone to be mindful of time and offered to continue discussions post-meeting for those interested.
  • A poll was conducted to make the recording and meeting minutes public, resulting in a majority agreement.

Action Items Summary

  1. PR #224: Move forward with testing and merging.
  2. Labeling and Prioritizing Issues: Tyler and Brandon to label and prioritize issues, community to review.
  3. Discord Channel: Tyler to share the link and activate the developer Discord.
  4. Implementation Discussions: Continue discussions on get account key and demo hosting strategy.
  5. Meeting Minutes and Recording: Publish and make public.