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

Create agenda #7 {31.05.2023}.md #13

Merged
merged 1 commit into from
Jun 13, 2023
Merged

Conversation

michelleellen
Copy link
Contributor

@michelleellen michelleellen commented May 30, 2023

Description
Join Gnolang's core tech team and partners for the monthly developer call, a regular sync with Gnolang developers working on the technology and community members interested in the engineering and development discussions. You can find the proposed agenda below, if you have additional technical points to discuss, please add them to this issue.

Date: May 31s at 5pm CEST Dial in details shared with core contributors (if you're interested in joining, and actively contributing to the code base, please reach out) and live stream on Gno.land YouTube

You can add the Developer Call to your calendar here.

Agenda

  • Updates from the Gno core tech and core contributors (Everyone 🙏)
  • onbloc
  • Gnoswap, Adena Wallet, and more!
  • Tinkers: Zack -> new realm demo
    discussion on gas pricing potentially requires a new issue @zivkovicmilos
    link to commit with changes
  • Sage

Core topics

  • IBC dev (Jae)
  • Error check pr (r3v4s)
  • grc20 admin token link
  • previous realm issue 667
  • Testnet Gnoland 4 (Moul)
  • Native bindings issue (Morgan)
  • CLI refactor (Moul)
  • Handling nested packages issue (Hariom)
  • Tendermint2 clean up issue (Piux2)
  • Modularized VMs issue (Antonio)

Joke (Petar) 😂

@gnolang/core-contributors @gnolang/tech-staff

@michelleellen michelleellen added the Developer Call The bi-weekly public facing developer meeting label May 30, 2023
@michelleellen
Copy link
Contributor Author

michelleellen commented May 31, 2023

Testnet 4
Discussion on banking module added, needs a fix
Should we make it multinode testnet? Or two testnets - single node (4) for building and a branch testnet will be designed for multinode experience.
What's stopping a multi node testnet?
Idea - community managed testnet

Discussion continues in link above.

@michelleellen michelleellen merged commit 600c42f into main Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Developer Call The bi-weekly public facing developer meeting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant