gnolang / meetings Goto Github PK

Our aim is to aggregate and archive our dialogues from multiple platforms like Signal, Discord, Google Meet, Zoom, enhancing their accessibility and searchability.

For private chats, I recommend a two-phase approach to ensure sensitive information remains confidential before making them publicly available.

Please, share your suggestions, here.

We're launching a series of workshops to refine and explain our long-term vision and strategize our roadmap to and beyond mainnet launch. These workshops will result in an actionable checklist (road to mainnet milestone), a repository of issues with additional ideas, and blogpost for wider sharing.

Steps:

• 1. Async: Share your ideas in a GitHub comment on this issue. We'll review these. <-- WE'RE HERE
• 2. Sync, recorded: We'll have a core team meeting to create a user needs-based roadmap.
• 3. Async: After creating the foundational roadmap, we'll seek more comments and inputs.
• 4. Sync, recorded: A meeting with our partners and top contributors will follow to discuss their specific needs.
• 5. Async+Sync: To ensure continuous progress, we'll update the roadmap repository regularly and propose a monthly public discussion.

Your contributions are invaluable - many thanks!

cc @gnolang/core-contributors @gnolang/tech-staff @gnolang/devrels @gnolang/tokenomics @gnolang/partners

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 3rd at 5pm CET
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.

Tentative agenda

• Updates from the Gno core tech and core contributors (Everyone 🙏)
  onbloc
  Adena upgrade
  Swap
  Sage
  Zack
  Microblog
  
• Benchmarking (Petar/Morgan)
• CLI refactor issue 731 (Manfred)
• Gno js SDK update and discussion - repo (Milos)
• Gno IDE updates (ilker)
• Garbage collector updates (Petar)
• IBC updates (Jae)
• Discussion on handling total supply and balance (issue)
• Protocol to support contract contract interaction continued discussion (issue) and handling grc20 treasury (linked to the Merkle airdrop) management
• - Best joke from Petar 😁 - always save the best for last

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

Longterm issue to keep track of discussions and PRs related to the "Golang Working Group" Meetings.

• Decide and use issues or PRs to list past and upcoming events (I suggest PRs).
• Update the README with instructions and explanations about events.
• Add links to calendar subscriptions.
• Consider writing a script that could keep the README.md file updated automatically by parsing PRs, folders, events, everything.
• Reorganize content when it start being hard to follow.

Description
Join Gnolang's core tech team and partners for the bi-weekly 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: September 6th 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).

You can add the Developer Call to your calendar here.

Agenda
Gno Contributor Updates

Teritori
Onbloc
Berty - Gno Mobile updated
GnoIDE

Gno Team Topics

GnoVM:
Issue #1082 cryptic error: v := f(), when f returns no values, panics with evalStaticTypeOf() only supports *CallExpr with 1 result (@thehowl)
Issue #1083 boolean operators (||, &&) allowed in return values (for non-boolean return values) (@thehowl)
Issue #1084 test files cannot contain a tests variable (@thehowl)
Issue #1085 conversion to uint64 is bounded to int64 values (when passing as a literal) #1085 (@thehowl)
Issue #1086 gnovm doesn't perform terminating statement analysis (@thehowl)
Issue #812 gnovm store: SetCachePackage stores packages on memory. Possible OOM errors. (@ajnavarro)
Other VM updates (@mvertes)

Additional discussions:
Issue 1099 should we not allow injecting methods on a non-exist PackageNode (@piux2)
Issue #1100 Should the response of an RPC realm function call have the return value? #1100 (Jeff, Berty)
Issue #872 WorXDAO (@MichaelFrazzy @moul)
[Issue #863] Block data synchronization and full node operation on test3 (@dongwon @moul )
Issue 362 testnet 4 - multi node (@albttx and team)
Banker module
tm-js-2 and gno-js-2 updates

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: April 19th at 5pm CET
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.

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

Description

Join Gnolang's core tech team and partners for the bi-weekly 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: August 23rd 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).

You can add the Developer Call to your calendar here.

Agenda

Gno Contributor Updates

Teritori review gnolang/gno#1061
Onbloc
Berty - Gno Mobile updated
GnoIDE

Gno Team Topics

@thehowl Do we have an issue to discuss reflection?
Alternative to reflection, introspection gnolang/gno#971 (@peter7891)

Open issue discussions:

Discussion: META 'gno' CLI gnolang/gno#1017 and associated gnolang/gno#1045 (@moul @mvertes @gfanton )

Discussion banker module gnolang/gno#986 (@thehowl) maybe related by grc20 and dynamic call closure gnolang/gno#986 (@moul )

Discussion: Rust VM (@peter7891)

Question: The VM is no properly released back to sync pool feedback issue 1033 (@piux2 @peter7891 @mvertes)

Discussion (RFC): moving gnovm/pkg/gnolang/precompile.go out of gnovm/pkg/gnolang/ issue 1054 (@piux2)

Discussion: another improved error handling proposal gnolang/gno#1018 part of go proposals (@peter7891 @mvertes)

Discussion: How to ease local dev while keeping gno.land minimal? gnolang/gno#1020 (comment) (@gfanton)

Updates on Gno-js-client or TM2-js-client?

Finish pagination feature? gnolang/gno#883

Longterm issue to keep track of discussions and PRs related to the Tokenomics Meetings.

Instructions: TODO

Longterm issue to keep track of discussions and PRs related to the GitHub Review Meetings.

Instructions: https://github.com/gnolang/meetings#weekly-review-meeting

Ideas

• write a script making lists of issues/PRs with useful metrics (amount of changes, amount of comments, age, stale score, amount of dependents, etc) to ease choosing the best topics.
• write a script making lists of issues/PRs to generate public reports.
• consider having templated/canned answers and more labels, to make the review process faster and more consistent (maybe a bad idea).

Hey team,

I've got some exciting news for you all! We're organizing an internal workshop on Gnoffee, and I wanted to give you the lowdown.

The workshop is happening on Thursday, September 7th, and unfortunately, it's only open to the European Tilezone team. I know it's not ideal, but don't worry, we'll be recording the session so you can catch up later if you can't make it.

During the workshop, we'll be diving into the current proposed Proof of Concept (PoC) for Gnoffee. You can find all the details in this GitHub pull request. We'll also be discussing our short-term strategy, with a special focus on GopherconUS, and of course, the overall strategy.

Now, I want to make it clear that this workshop is completely optional. You're more than welcome to join if you can, but if you can't make it, no worries. I'd still love to hear your thoughts and comments on the pull requests or any related issues, like #23.

So mark your calendars and get ready for some Gnoffee action! Can't wait to see you there.

Cheers,
Manfred

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: April 5th at 5pm CET
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.

Hey @thehowl @zivkovicmilos @peter7891 @gnolang/core-tech @harry-hov let's build the agenda 🙏 plus the external core contributors.
cc: @jaekwon @moul

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: March 8th at 4pm UTC

Dial in details: Zoom and YouTube live

You can add the Developer Monthly calendar here.

Agenda

Recent and upcoming updates:

• Linter support for the codebase
• Gno fallthrough support
• Improved developer experience with gnodev run

Open Issues and PRs to discuss:

• Developer tool needs
• CLI refactor
• GOR Governance proposal
• GOR Leaderboard
• Support more GnoVM cases
• Package metadata
• Support for contract-contract interaction

The call will be streamed and available on Gno.land's YouTube channel for those unable to make it!

Description

Join Gnolang's core tech team and partners for the bi-weekly 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: October 4th at 5pm CEST (and can last from one to two hours)
Dial in details shared with core contributors (if you're interested in joining, and actively contributing to the code base, please reach out

You can add the Developer Call to your calendar here.

Gno Contributors - What they've been working on!

• Teritori - Gno Moderation DAO
• Berty - GnoMobile
• Onbloc - Adena, Gno Swap and Core Contributions
• Zack, resident tinker - upcoming workshop Go to Gno: Generation Audio with Smart Contracts
• Flippando, gaming app from Dragos

Gno Core Team

We were at GopherCon update!
GnoChess & tutorial & status or update on bugs detailed in the previous developer agenda (@thehowl)

TM-JS and Gno-JS-Client updates (@zivkovicmilos)

VMs
-gnovm: Brief intro to how it works (@piux2)

• Rust VM & Go VM updates? (@peter7891 @mvertes)

gnovm store: SetCachePackage stores packages on memory. Possible OOM errors #812 @ajnavarro @thehowl (long standing issue and listed for mainnet)

Discuss hackerspace Go(d) Mode issue #41 @ajnavarro @moul

Append Slice discussion related #issue 1117 #1170 #1167 relation to #939? (@tbruyelle @mvertes @thehowl Alex and Norman)

Discuss reset node states #1195 @piux2

Update - improve grc20/foo20 APIs - Merkle Airdrop (mainnet) @albttx

Vision for the Portal Loop (@moul)

• PoC for Genesis Libraries and Manipulation Tools issue #1189 (@moul)

Time and Block height manipulation in tests issue 1165- feedback from @leohhhn

Token economics update (@MichaelFrazzy)

Language specification updates from @peter7891

This meeting involves reviewing the current competition status and discussing strategies for enhancing our approach.

This meeting touches on scoring criteria, leaders assigned to each submission category, and what transparency into the entire GoR grading system looks like.

Related: DevRel #6.

Description

Join Gnolang's core tech team and partners for the bi-weekly 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: August 9th 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).

You can add the Developer Call to your calendar here.

Agenda

Gno Contributor Updates

• Teritori
• Onbloc
• Welcome Berty ❤️
• GnoIDE
• [ ]

Gno Team Topics

Follow ups from last time, any short updates?
Do we have an issue to discuss reflection?
Alternative to reflection, introspection issue 970 (@peter7891)

New topics for updates:
Gnopher Holes:

• Module VS Pkg VS Path VS Dir VS SubPkg VS SubModule VS SubDir VS SubPath issue 1024 (@harry-hov @moul @jaekwon)
• Unexpected panic error when fetching height issue 1037(@gfanton)
• [ ]

Open issue discussions:

• Discussion: META 'gno' CLI issue 1017(@moul @mvertes)
• Discussion language: Extending constant behavior issue 919 (@peter7891 )
• Discussion banker module issue 986 (@thehowl) maybe related by grc20 and dynamic call closure gnolang/gno#986 (@moul )
• Discussion: Merkle airdrop issue 906(@albttx)
• Discussion: Error handling in the send transaction function of issue 46 @zivkovicmilos @jaekwon -
• Discussion: another improved error handling proposal issue 1018 part of go proposals (@peter7891 @mvertes)
• Discussion on the draft allow args on main run issue 982 (@ajnavarro )
• Discussion on Contributors DAO --issue 872 (@moul
• Merged: Benchmark and performance metrics issue 881 and live @ajnavarro
• [ ]

Follow up/actions:

• @thehowl to open a META issue regarding reflection

Description

Join Gnolang's core tech team and partners for the bi-weekly 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: September 20th at 5pm CEST (only one hour today)
Dial in details shared with core contributors (if you're interested in joining, and actively contributing to the code base, please reach out

You can add the Developer Call to your calendar here.

Agenda

Gno Contributor Updates

Teritori
Onbloc
Berty - Gno Mobile
GnoIDE
Flippando introduction (Dragos)

Gno Team Topics

GnoVM:
New finds @thehowl
Issue #1135 for loops maintain the same block on iteration, which is referenced in any closures generated within
Issue 1136 can't append nil to a slice of interfaces
Issue 1148 division by zero panics cannot be recovered
[Issue #1149 ] in append([]T, ...T), constant types are not converted to T implicitly
Issue 1150 infinitesimal non-zero float values are rejected by the preprocessor
Issue 1151 floats not allowed in inc/dec statements linked to [PR] feat(stdlibs): add math and math/bits (to be reviewed)
Issue #1152 mixing untyped (negative) floats and integers in arithmetic sometimes drops the sign
Issue #1155 can't use unexported struct fields when converting using gno2go
From last time, any updates?
gnolang/gno#1082 cryptic error: v := f(), when f returns no values, panics with evalStaticTypeOf() only supports *CallExpr with 1 result
gnolang/gno#1083 boolean operators (||, &&) allowed in return values (for non-boolean return values)
gnolang/gno#1084 test files cannot contain a tests variable (@thehowl)
gnolang/gno#1085 conversion to uint64 is bounded to int64 values (when passing as a literal) #1085
gnolang/gno#1086 gnovm doesn't perform terminating statement analysis
☝️ finds are from the gnochess application build
gnolang/gno#1157 amino and protobuf comments

Rust or Go VM updates (@mvertes @peter7891) - VM face off issue?
Question: status on multi-sig?
Issue #1106 Gno.land Fee Parameters (@MichaelFrazzy @moul)
Issue #1101 new integration test method for Gno.land @moul and Issue #1117 wip: add txtar driver for gnoland integration test related to @gfanton
Plus Update on [Gno Go client ]feat: add gno.land/pkg/gnoclient (Gno.land Go client)
Issue #1108 The Portal Loop @moul

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: March 22nd at 5pm UTC
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

• Team updates from the past weeks (5 minutes)
• GnoVM:

1. Garbage Collector discussion (memory freedom)
2. Event management recap and discussion

• Contract communication overview
• Gnomod: package management status
• IBC & ICS follow ups (this will be the bulk of the meeting)

cc: @moul @harry-hov @jaekwon @zivkovicmilos @thehowl