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.

Sign up for GitHub

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

Jump to bottom

Minutes: Core Staff Weekly Syncs [every Monday] #36

Open
moul opened this issue Nov 19, 2023 · 31 comments
Open

Minutes: Core Staff Weekly Syncs [every Monday] #36

moul opened this issue Nov 19, 2023 · 31 comments
Assignees
@moul @zivkovicmilos @piux2
Labels
⌚️ minutes Issues tracking meeting notes from recurring meetings.

Comments

@moul
Copy link
Member

moul commented Nov 19, 2023 •
edited
Loading

Purpose: This issue compiles meeting notes for the Gno Core Staff's recurring meetings.

Process:

  1. Drafting: Notes are initially taken in Hackmd or Google Docs during meetings.
  2. Posting: Finalized notes are posted here as comments for easy tracking.
  3. Linking Issues: Include links to related GitHub issues for back-references.

Template

# Weekly Gno Staff Sync

Previous Syncs: https://github.com/gnolang/meetings/issues/36.

Welcome to our Weekly Gno Staff Sync. Our goals are to showcase progress, identify risks, align with stakeholders, and lay the groundwork for strategic discussions related to Gno. This meeting helps us make decisions and focus on critical issues and goals.

**First 10 Minutes: Silent Meeting Style**
> [Learn about Silent Meetings](https://www.eficode.com/blog/silent-backlog-refinement-meetings-a-more-effective-agile-meeting#:~:text=In%20a%20silent%20meeting%2C%20you,communication%20than%20talking%20and%20listening.)

For the first 10 minutes, we'll have a silent meeting. This lets team members add discussion points, review the meeting's scope, and make quick comments. We'll start with general updates and callouts before discussing points and addressing comments. Each meeting should end with action items and noting key decisions.

> If you have no discussion points or they've already been covered, please state so, like "no new updates since the last sync" or "already covered by xyz."

**This document is reused periodically. The first section has instructions. After the first horizontal line, you'll find the content section. Remember, the content will be shared on GitHub later, so only input content after the first horizontal line.**

---
<!-- Silent Meeting -->

## Discussion Points

### Your Name...

- foo
- bar
- ...

### Your Name...

### Your Name...
 
---
<!-- Discussion -->

## Callouts

1. Foo
    - Outcome of callout (discussion) (GH issue / textual explainer...)
    - ...
2. Bar
3. ...

## Action Items

1. Foo
2. Bar
3. ...
@moul
Copy link
Member Author

moul commented Nov 21, 2023 •
edited
Loading

20th nov 2023 - weekly worldwide sync

Discussion Points

Manfred

  • Team Retreat: any question?
  • I'm going to hire two freelancers (QA, CI/CD) to help us with an audit and gather suggestions. This will help us decide if we want to keep working with them or handle things ourselves. We should create tasks to list questions, ideas, needs, and limitations.
  • Roadmap Workshop w/ Adriana last week:
  • OKRs
    • Team OKRs will be shared this week, and you'll have to write yours and send them to me for review (Mig will come back to you with instructions)
    • I'm adding a split where 2/3 of the bonus is based on individual OKRs, and 1/3 on team shared OKRs + "forced individual OKRs"
  • My tech next focuses
    • release network of DAOs v0
    • release DAO interface with example of standalone action (goal is that each action can have its own repo and forks)
    • Effective Gno Doc v0
    • FAQ v0

Morgan

  • Last week
    • started efforts to carry over work from GnoChess into monorepo
      • Probably going to be in steps, packages gno.land/p/demo/chess, then sub-packages glicko2, zobrist ...
      • Full chess will be blocked by math stdlib PR, itself blocked by floats inc/dec ops
      • Ray agreed to merge today since Jae hasn't gotten back to us.
    • Last week created the proposal for maps as binary trees, as mentioned in the dev call last wed
    • A lot of peer reviews...
    • p/demo/seqid
  • This week
    • Continue work on re-structuring GnoChess repo & bringing what I can to monorepo. Probably starting by adding just a few packages, then iterate once we merge math.
    • Peer reviews, more bureaucracy, help with TPM hiring process
    • Finish work on gnoutil, update math PR after merge of 1221
    • Add base32-based IDs to p/demo/seqid
    • And the usual bunch of reviews :) (please do reviews as well: we have 81 open non-draft PRs)

Dylan

  • Feedback on fix for fix: properly mark array elements when an realm slice is updated gno#1305 appreciated
  • Thoughts on collecting metrics, traces, maybe logging differently? Currently looking at opentelemetry
    • Collect metrics to measure p2p performance under load
    • Traces used to more accurately estimate how much gas different VM ops cost
    • Indexed and meaningful logs would be good to have
    • Looking at open source solutions presently -- datadog gets expensive quick
      • Opentelemetry produces data that is standardized and consumable by many tools
      • Started using prometheus and grafana for metrics and visualization
      • Considering signoz for traces and logs

    • Morgan: In previous projects I worked on we had a great experience with Grafana/Prometheus. It can also provide us a dashboard for "normal" logging (as opposed to time-series, which is more useful for metrics) using Loki.

  • Started looking at issue also related to realm storage unexpected unreal object when assigning a local variable to a global variable (pointer) gno#1326

    • Morgan: ❤️

Guilhem

Milos

  • Last week was OOO, this week is mainly focused on playing catch up with ongoing efforts
  • This week will focus on the indexer implementation, since it's something that's coming up more frequently with implementation partners like Berty and Onbloc
  • Will sync with the DevRel team for potential efforts / docs related functionality we need in the short term
  • Open question: Current status of the gas estimation effort (gas formula)?; Mainly a question for Michael

Antonio

  • Issues commented on github: 2
    • println does not print nil slices gno#1377 - println does not print nil slices: The behavior wont be the same as in Go. Left a comment to continue the discussion. Question: What are the general rules of thumb about what should be Go like and what should not?

      • Morgan: I think as a rule of thumb we should do the same that Go does (up until Go 1.17), especially strictly for the programming language implementation.
        If we decide we want to go specifically in another direction as opposed to Go, we can, and of course we already do this for Gno specific features (like realm storage) or features that have been deliberately left out (ie. package main is not special in Gno).
        In the future, this could potentially be about how maps are iterated (re: my proposal on maps), or about how channels and goroutines are implemented.
        For print/println specifically, the functions don't return anything so how they behave is nothing that the program itself can actually rely on. The output is different from Go's, but Go already states that the format is implementation specific (otherwise they would have just said it's the same as fmt's Println -- and, by the way, it's not). Obviously, our eventual fmt.Println should be == Go's fmt.Println, because through Sprint that is code that other parts of the code can rely on. The same cannot be said about println.

  • Pull requests commented on github: 9
  • PRs:
    • Added Golden test on chore(deps): update btcec to the latest version #1329
  • Other: Team assesment. I started to do the assesment the last week, but everything dissappeared. Today I received new emails for new assesments. Should I do it again?

    • Morgan: I think some disappeared because they were duplicates. If you see none, though, it's probably by mistake and you should ask manfred.

Marc

  • parscan status:
    • added var, const and type declarations
    • support of arbitrary precision of constants (256 bits, big ints, rats and floats)
    • added structs, arrays, slices objects
    • selectors expressions (access to struct fields)
    • index expressions (access to slices/array elements)
    • in the process of adding pointers
  • this week: pausing parscan and looking at pending gno PRs: #1177 and reviews of serveral others

Morgan: 🎉

Jon

  • Github (org-level) layout redesign PR

    • Morgan: I am personally more in favour of a more minimal GitHub readme, but a more thorough and beginner friendly gno.land homepage, so we take the gno.land homepage as the central location where we should funnel newcomers.

    • ^Thanks, Morgan. I guess we'll hold off and see if we can figure out how to implement some of these changes on gno.land readme instead of at org. level.
  • Game of Realms (porting to Gno; WIP); architecture would be nice to have reviewed to ensure this flow makes general sense
  • Playground
    • Soft-launch moved to Tuesday, Nov 28 (due to Thanksgiving)
    • Realm examples + support code can be found within DevRel repo (for now)

Hariom

  • Working on a realm; encountered unknown import path "encoding/json"

    • Morgan: normal, we don't have reflection. Currently it will only work in test files. In GnoChess I painstakingly hand-wrote my marshalers 😢
      My suggestion is: if you want to work on reflection, work on a proposal on 1. how its design would be (and be conservative compared to Go's reflect package) and 2. get a rough idea of how it would be implemented.
      Otherwise, if your goal is to have JSON marshaling specifically, I think you can work on a codegeneration tool that does AST analysis and then creates the marshalers, in the same way that me and Dragos (who's working on Flippando) have been doing.

  • Will try to work on Realm with "import encoding/json" can't be addpkg via gnokey, but manually gno#808 with Blake
  • Continue my work on feat: addpkg command respects gno.mod file gno#922
  • Why pure pkgs can import realm? (Maybe will fix this behaviour?)

    • Morgan: yes, IIRC when we discussed this with @moul some time ago he did say this is something we should disallow. And I agree -- there may be a way for package code to call Realm code, but that should happen through dependency injection (ie. pkg.MyFunc(realm1.FuncToBeCalled)).

  • Try to continue working on gno test --cover this week.

Morgan: if you have a while this week, I'm curious to hear your thoughts about #1352.

Ray

  • Last week
    • Multinode POA in cloud for validator sync and none validator sync
    • Network performance testing set up design
    • Gas meter implemention investigation
  • Todo
    • Implement gas meter
    • Base line of profiling network performance
    • Base line of profiling gas meter

Michael

  • Forensic investigation w/ Sean & Jae (internal)
  • Finalizing gas/fee equations, next draft ~= 1 week Gno.land Fee Parameters gno#1106
  • Porting GoR scripts to main repos
  • Continued AI development (GPT vs Claude)
  • Finalized structure/documentation revamp (tokenomics & DAOs)
  • GNOT bonding design (staking alternative)
  • Prop 848 simulation & debate
  • Starting podcast w/ Michelle

Peter

gnors:

  • Test suite
  • Compiled bytecode file format (metadata, bytecode, security features, DLL)
  • Package Initialization/tracking global state

Callouts

  1. @moul - scope of freelance QA work?

    • We should create tasks to list questions, ideas, needs, and limitations.

    • from @moul: start with an audit, and provide a plan and suggestions; should be somethine like 2w, I guess.
  2. @peter - is the testing suite implementation agnostic (ex. can be used by parscan)?
    • from @marc: I intend to provide the agnostic test suite, independently of gno-rs internal suite. Will sync with Petar soon on that.
  3. @harry-hov's Qs:

    • Why pure pkgs can import realm? (Maybe will fix this behaviour?)

    • from @moul: We should panic when detecting an r/ import from a p/, at the AddPkg stage. Related with Panic when addpkg a Realm with subpaths gno#1041. The presence of global variables in p/ should be disallowed too (should be the case). Therefore, p/ will serve as the "pure" zone, akin to heaven, while the "realm" zone can be impure and more similar to earth.
  4. @ajnavarro's Qs:

    • What are the general rules of thumb about what should be Go like and what should not?

    • @moul, Team assesment. I started to do the assesment the last week, but everything dissappeared. Today I received new emails for new assesments. Should I do it again?

    • from @moul: it's a known bug, HR will come back to you.

Action Items

  1. @team: General feedback needed:
  2. @team: Create potential tasks / improvement areas for the future QA hires
    • @moul, should we create a GitHub project for this, or keep it simple?
    • from @moul: Good idea! We have two new projects: QA and CI/CD/Infra. Let's start working on these long-term projects. After that, I propose creating two META issues for the freelancer marketplaces or sourcing pipelines. These issues will contain a comprehensive overview of what we want to improve, along with our questions and suggestions. We can provide a single link to candidate.
  3. @moul: Increase time slot to 1 hr

@thehowl thehowl changed the title Weekly Syncs - Gno Core Staff - Meeting Notes Minutes: Core Staff Weekly Syncs [every Monday] Nov 24, 2023
@thehowl thehowl added the ⌚️ minutes Issues tracking meeting notes from recurring meetings. label Nov 24, 2023
@zivkovicmilos
Copy link
Member

zivkovicmilos commented Nov 28, 2023 •
edited by ajnavarro
Loading

27th nov 2023 - weekly worldwide sync

Discussion Points

Jon (@waymobetta)

What did I work on last week?

  • playground launch materials (example realms, video scripts)
  • did-you-gno tweet series
  • code-to-gno tweet series
  • bamboo reviews

What will I focus on this week?

  • playground launch materials

Do I have any blockers?

  • playground DNS (partial)
  • GOR meeting

Valeh put together this Miro board for GoR project management: https://miro.com/app/board/uXjVNL9VbLE=/

Milos (@zivkovicmilos)

What did I work on last week?

  • Scoping out the exact feature set for the event indexer (txs, blocks)
  • Focused on OKR definitions with Manfred
  • Synced with implementation partners on defining their exact needs from the event / emit functionality (from Realms)
    • TL;DR: There is a need for temporary transaction events (tx succeeded, failed), and also a need for permanent historical fetches of transaction / block events
    • I will open an issue that serves as a spec for the indexer, as the indexer will be able to index them in addition to transactions, blocks; Implementation partners will give their feedback and we will take it from there

What will I focus on this week?

  • Start implementation work on the indexer; post the spec as an issue for the community
  • Write up the P2P document for the team to review, along with the PoC repo @ajnavarro and I worked on a month back
  • Standard catchup with issues / PRs

Do I have any blockers?

  • Docs / Portal Loop still blocked by DNS access

Guilhem (@gfanton)

What did I work on last week?

  • I mainly works on gno dev:
    • Implement reset / reload feature
    • Implement file watcher with fsnotify for hot reaload based on file/realm change
    • Use raw term interface to be able to handle keypress commands (like ctrl+<key>) for fast reload, reset, ...
    • Add save state feature reload realm \w current state, and use tx-exporter to be able to create a state file
    • Work on a PoC with repl package to interact with the current working package (need more invistagtion and I will implement this on a next iteration, but looks promising)

What will I focus on this week?

  • finish gno dev:
    • cleanup, comment and organize my code
    • need to improve node's state management to correctly reload the package on update

Do I have any blockers?

  • gno dev: gnovm/cmd/gno have a dependency on gno.land/pkg/{gnoland/integration} which feels weird

Dylan (@deelawn)

What did I work on last week?

  • Working to get metrics and tracing set up (metrics working, tracing not yet)
  • Code reviews
  • Experimental changes to refactor out hard to read callback functions in the consensus event listener code
  • Working on 1326. First attempt to code a fix failed. Need to do more research and compare to execution plans that do the same thing but actually work.

What will I focus on this week?

  • Resuming 1326
  • Getting tracing set up using signoz

Marc (@mvertes)

What did I work on last week?

  • Finished work on pointers. Worked on interfaces and types representation in parscan.
  • prepared the debugger and stack analysis for gnovm, based on stdlib runtime package

What will I focus on this week?

  • Continue with interfaces/types work: I came up with a reflect.NamedOf() method to resolve this problem hanging for years in Go ecosystem and overcome reflect limitations (see reflect: NamedOf golang/go#16522): create interfaces, methods, recursive structs. Plus a separate package so we do not depend on a accepted proposal https://github.com/gnolang/parscan/pull/10.
  • RH stuff, security engineer first interviews

Do I have any blockers?

  • not yet but I haven't done the most difficult with regard to interface methods.

Peter (@GH_username)

What did I work on last week?

  • Porting Go semver library

What will I focus on this week?

  • Finishing the port and using it in go mod

Hariom Verma (@harry-hov)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • Need reviews on some of my PRs/Issues

Manfred Touron (@moul)

What did I work on last week?

  • perf review: initial round
  • OKRs: shared team OKRs + mine + instructions

What will I focus on this week?

  • perf review: finish
  • vision DAG:
    • update gnolang/roadmap with high-level tasks + use milestones for eras
    • then will open an issue for someone to improve the visualizer tool to take the milestones into account
  • porting high-level per-era roadmap to adriana's template
    • waiting for adriana's template
  • will organize the first weekly internal AMA (tomorrow?): focus on the launch and previous loom videos
  • review grantees scorecards to unlock the next round
  • will call and brief phil honigman on the upcoming tokenomics grant
  • review and release blogposts (3 in the pipeline iirc)
  • portal loop: tech and coordination
  • agenda for the upcoming retreat
  • review atomone and see how much we can help the topic happening without unfocusing (i.e, by changing some priorities)

Do I have any blockers?

  • lack of visibility on portal loop's infra tasks

Michael Frasinelli (@MichaelFrazzy)

What did I work on last week?

  • Twitter Spaces, research, and vote tracing for prop 848
  • Helping with ATOM One
  • GoR meetings: defining scoring, continued automation, defining the Governance Module
  • Rewriting articles (partially with Christina) and posting gov changes to GitHub
  • Continued AI development
  • OKRs

What I will focus on this week?

  • GoR documentation and scripts on GitHub and Notion (scoring and Governance Module)
  • Continued AI development
  • Helping Jae with ATOM One
  • Starting economics podcast with Michelle
  • Ideally finalizing the fee/gas equations within 2 weeks
  • Assisting with tax/financial analysis
  • Grant analysis

Do I have blockers?

  • Meeting with Petar/Milos needed for Astrovault
  • Meeting with Milos and maybe Ray for gas/fee implementation
  • Could use a Jae meeting to confirm some final changes
  • GoR meeting time cancelled 7 times in a row :)

Ray (@piux2)

What did I work on last week?

  • Implemented chained anteHandler for VM
  • Integrated gas store and VM in one gas meter
  • Prepared Elastic Search, Logstash and Kibana pipe line
  • OKR

What I will focus on this week?

  • Test gas meter
  • Profile gas meter and gas usage

Leon (@leohhhn)

Focuses during last Week

  • Chronological blog sorting
  • Tx-exports & archiving of packages & realms
  • Improving the dogfooding process
  • Organizing DevRel efforts & scope of work
  • Reviewing blog posts
  • Report of Gno@Devconnect

What will I focus on this week

  • Finishing blog-related issues
  • Scoping out dogfooding & getting started with it
  • Finishing tx-exports
  • Working on documenting more stuff, like testing, r-r interactions, etc
  • Map of Gno.land
  • Possibly work on a detailed explanation on the faucet that @zmilos wrote

Antonio Navarro (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • PR review
  • Bug fixings
  • Figure out my OKRs

Morgan (@thehowl)

What did I work on last week?

  • PR Review
  • Review The More You Gno
  • Help getting some PRs out the door (ie. 1330)
  • Continue writing a GnoChess retrospective
  • Second revision of ordered tree-structured maps
  • Update & merge for 1153
  • Continuing to work on splitting GnoChess and publishing it on the monorepo.

What will I focus on this week?

  • GnoChess:
    • Continue retrospective
    • Try once again to publish the contracts on the monorepo
  • Hiring:
    • Continue writing interview q's & tech task
    • Help selecting candidates
  • Finish watching Mainnet Roadmap videos
  • Write OKRs
  • Write proposal for "Implicit Proxy Pattern"

Do I have any blockers?

Callouts

  1. General question for Jon: What is the current status of the GoR effort? Are there any blockers from the core team side?
    • @moul: we just had a discussion with Leon, I think I need to clarify some high-level things for everyone; i suggest you attend or view the record of the upcoming GoR meeting happening this week or of the AMA tomorrow. -> https://miro.com/app/board/uXjVMtsnDvI=/
  2. What kind of metrics system are you setting up Dylan (and for which modules)?
    • @deelawn: OpenTelemetry, exporting to Prometheus
    • @gfanton: We can plug in the event bus system (TM2) to Prometheus
  3. Albert, what is leftover for the Portal Loop infra?
    • Blocked by the DNS access for publishing; but we can test internally (portal loop)
    • Trying to tie everything in with scripts, CLI improvements
    • A few days left for infra setup, pending other responsibilities
  4. Antonio, are you using a tool to generate your reports? Please share. Let's automate it for the team on the gnolang/gor repository. CC @team/devrels.
  5. Discussion points raised by @harry-hov:
  6. Antonio: Are the OKRs we're proposing too vague, and do they need to be more specific?

Action Items

  1. @team/devrels: Look into the did tool, which will automate the reporting process off-chain
  2. @team: Look into the discussions on:
  3. @harry-hov: Make a list of Packages importing Realms (related PR)
    • @harry-hov: would this check be gno.mod based or protocol based?
      • @moul: protocol-based; no need to check it on the gno.mod level
    • @moul: what would be the best place to raise an invalid import?
      • @piux2: we had a discussion about a related topic recently, will dig it up and forward it to the group; will reply to #1393

@zivkovicmilos
Copy link
Member

4th dec 2023 - weekly worldwide sync

Morgan (@thehowl)

What did I work on last week?

  • Help out with the hiring for TPM
  • Reviewed many PRs
  • Write OKRs
  • GnoChess
  • Continue catching up on roadmap videos

What will I focus on this week?

  • GnoChess
    • finish retrospective, ahead of Rouen Retreat
    • fix outstanding issues and merge above PR
  • Finish off TPM task and start interviews
  • Finish watching roadmap videos
  • Write proposal for "implicit proxy pattern for realm upgradability"
  • PR to add full support for stdlib package strconv
  • PR Reviews,
  • Off this Friday, possibly Thursday too.

Do I have any blockers?

  • I'll let you guess, but no prizes for winning, ok? It's native bindings review :)

Milos (@zivkovicmilos)

What did I work on last week?

  • Got up to speed with active issues / PRs
  • OKR discussions for the team
  • Worked with @ajnavarro on finalizing the p2p proof of concept; feedback appreciated
  • Continued speccing out the indexer API by researching use-cases across Ethereum (eth RPC endpoints)
  • Reviewed Dylan's ongoing metrics doc, proposed internally different metrics sources

What will I focus on this week?

  • Finalize the spec for the indexer; mainly because of Berty and Onbloc, so we can organize work on related efforts (event / emit); Should start implementing it as early as this week
  • Check out how I can contribute to AtomOne, and get the team more involved on connecting parts with Gno

Do I have any blockers?

  • Still waiting for DNS access for the docs / portal loop :)

Marc (@mvertes)

What did I work on last week?

  • gno: PR #1177. Addressed change requests, and fixed additional issue #1341. The PR is ready for a second review.
  • parscan: implemented defined types created by reflect (goal: have a proposal to improve Golang reflect and a reflect extension package). Works for basic types but not yet for composite types.
  • HR interviews and follow-ups for hiring a senior security engineer

What will I focus on this week?

  • gno: investigate stack dumps and debugger fonctions
  • parscan: continue work on reflect to create defined types.

Do I have any blockers?

  • extension of reflect is difficult (not blocking yet).

dylan (@deelawn)

What did I work on last week?

  • Wrote and merged 1399 to fix 1152
  • Opened 1398 as a draft, open for early feedback on the approach, to address 1326
  • Sent metrics to Signoz instead of prometheus to experiement with the features
  • Finished first iteration of VM execution traces instrumentation and viewing them in the Signoz UI and querying using SQL
    • Instructions to set up and run and gather traces locally are in this notion doc
  • Reviewed 1380
  • Put finishing touches on 1315

What will I focus on this week?

  • Begin working on 1085
  • I wasn't happy with the Signoz APM so I will resume configuring metrics and traces to export to the ELK stack and experiment with the query and visualization capabilities. Ray has been doing some work sending logs here so the logs, metrics, and traces can be unified in the same environment

Do I have any blockers?

No

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Continue reviewing stuff, a lot of things to be reviewed.

Do I have any blockers?

  • /

Guilhem (@gfanton)

What did I work on last week?

What will I focus on this week?

  • Merge gnodev
  • start working on a next iteration arount it ?
    • repl side tool to interact with it ?
  • Would love to continue @zmilos works on replacing logger with golang slog

Do I have any blockers?

  • I got some problems using a nested golang module in gno repo with go 1.21. (in /contribs)
    • gopls isn't working with nested go.mod

Jon (@waymobetta)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • org redesign feedback
  • Prioritize review of one GoR submission during our Thursday PR review meeting (or separate meeting preferable?)

Hariom (@harry_hov)

What did I work on last week?

What will I focus on this week?

  • Mostly I will focus on leftovers and things I promised last week
    (copy pasting below for reference)
  • Fix review comments on feat: implement gno bug gno#1325
  • Continue working on gno test -cover
  • forbid importing /r from /p
  • Maybe proposal: gno.mod resolve directive? -- Need to Discuss with @morgan
  • gno mod why

Do I have any blockers?

Petar

What did I work on last week?

  • Rust VM - go mod

What will I focus on this week?

  • GnoVM - improve test runtime (Which could necessarily making GnoVM faster in general, if there aren't some red flags in the test run itself)

Do I have any blockers?

  • No

Michael (@MichaelFrazzy)

What did I work on last week?

What will I focus on this week?

  • Confirming all documentation with Jae and/or Manfred
  • Continuing ATOMone contributions
  • Meetings to finalize the gas/fee systems so I can prep simulations & benchmarking
  • GoR internal scoring system
  • Prepping economics podcast
  • GnoSnake, airdrop sim, and AI coding

Do I have any blockers?

  • Meeting with Milos and Ray to finalize gas/fee implementation (scheduled)
  • Confirming all current systems with Jae (scheduled)

Ray (@piux2)

What did I work on last week?

  • Did gas profiling with transactions from test3.gno.land
  • Reviewed #1393, #1048

What will I focus on this week?

  • Exported 1000 txs from test3.gno.land and found about 300 txs that failed to be replayed as genesis transactions. Need to investigate how these transactions could be included in the test3.gno.land block at the first place.
  • Release the new gasmeter.

Do I have any blockers?

  • /

Leon (@leohhhn)

What did I work on last week?

  • Blog sorting & publishing new blog posts
  • Dogfooding process improvement
  • Disperse.app port
    • Reading up on coins/tokens & banker module
  • Wokring on creating DevRel team OKRs & processes
  • Merch for Rouen retreat 👀

What will I focus on this week?

  • Documenting coins/tokens/banker
  • Finishing Disperse.app
  • Start documenting stdlib
  • Wokring on creating DevRel team OKRs & processes
  • GoR-related work

Do I have any blockers?

  • /

Manfred (@moul)

What did I work on last week?

  • management (perf, OKRs, chores)
  • atomone hub: feedback, coordination, strategy

Callouts

  1. p2p repo (proof of concept) ready for team feedback

Action Items

  1. @harry-hov: need more 👀 #922

@zivkovicmilos
Copy link
Member

11th dec 2023 - weekly worldwide sync

Antonio Navarro (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Continue reviews and chores
  • Maybe have a look into Go(d) mode to try to have something working as a PoC?

Milos (@zivkovicmilos)

What did I work on last week?

  • Meetings meetings meetings
  • Standard PR reviews
  • Hiring calls for the TPM role
  • Played around with different indexer concepts
    • Will publish the implementation + spec by EOW

What will I focus on this week?

  • Bring open PRs to a close, a few of them have been dangling
  • Finishing up the indexer
  • Look into wrapping up the initial logger efforts I've started so @gfanton and @ajnavarro can jump on board. The idea is to swap out the TM2 logger for a "standardized" slog interface across the TM2 / entire codebase, and have future PRs improve actual log lines (since this swap would not change the API drastically)

Do I have any blockers?

  • DNS 🙏
    • @moul: for docs.gno.land?

Guilhem (@gfanton)

What did I work on last week?

  • Update my gnodev PR after Milos review
    • need a some tests to mark reviewable again
    • need to fix go.mod
  • Rebase and fix gno linter PR
    • updated contributing MD
  • worked on extracting gnovm and gno.lang from tm2
    • this should enable workspace
  • bonus: Made a simple PoC of gnobro, a gno browser in CLI this weekend

What will I focus on this week?

  • finish testing gnodev package
  • continue working on extracting gnovm and gno.lang from tm2
  • try to fix another BFT flaky test error that append on the CI

Do I have any blockers?

  • go.mod failed on my gnodev PR
    • it actually breaking gopls and other go features, and I beleive this is link with my error on the CI

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • collaborate to find the correct places to put other metrics we'd like to collect
  • maybe experiment with how an oracle system might look as a gno contract
  • review PR 1426

Do I have any blockers?

no

Hariom Verma (@harry-hov)

What did I work on last week?

What will I focus on this week?

  • Discuss about module caching on the browser (gno mod download) with Denis and Jerónimo
  • Forbid importing /r from /p
  • Fix review comments on gno bug PR

Do I have any blockers?

Leon (@leohhhn)

What did I work on last week?

  • disperse.app
  • update outdated tutorials
  • documenting the banker module
  • grc20 vs coin vs token

What will I focus on this week?

  • finish disperse app & testing
  • add coin/token docs
  • refactor grc20 folder
  • finish gnoland intro pack

Marc (@GH_mvertes)

What did I work on last week?

What will I focus on this week?

  • fixing reflect2.MakeMethod()

Do I have any blockers?

  • need final approval on PR #1177

Ray (@piux2)

What did I work on last week?

  • Fix gas meter and add additional testing cases
  • Published the gasmeter PR #1430
  • Went through 50% transactions exported for test3, and identified a few things we need to fix on main testnet

What will I focus on this week?

  • Continue the transaction analysis
  • Complete gas profiling report

Manfred (@moul)

What will I focus on this week?

  • discussions: braistorm and explain topics with peers
    • gnokey, existing and future wallets, account session system, gnokeykc, gnokey wrapping, etc
    • future hardware needs, so we can discuss with an R&D researcher team to see if we could work together and when
    • side projects like parscan/gnors, but also non-gnovm side-projects: strategy (repos, naming, constraints, how to highlight them)
    • game of realms, proof of contributions
    • gno & atomone & the rest
  • code: things I'd try to work on or help people to work on
    • effective gno doc
    • portal loop
    • gnodev
    • faucet
  • trying a new method with christina to blog about topics in series of episodes; similar to ADRs (Architecture Decision Records)

Jon (@waymobetta)

What did I work on last week?

What will I focus on this week?

  • finalize learn x in y (initial version)
  • content generation for code-to-gno

Morgan (@thehowl)

What did I work on last week?

What will I focus on this week?

Callouts

  1. @harry-hov: What should we do about existing pkgs importing realm?

    • we should fix them: we should remove all the r/ imports from p/; ping @albttx & @tbruyelle who introduced this test file

  2. @piux2: Went through 50% transactions exported for test3, and identified a few things we need to fix on main testnet

    • What were the things you've found?
    • @moul: I had an issue when I tried to apply some fixes and I lost some transactions because of a mistake; the history is probably a mix of very old transactions and super recent ones, I think we lost some of them (a lot!) in the "middle".
    • @moul: checkout this fix for the minting "bug": feat(stdlibs/std)!: namespace minted coins with realm path gno#875
    • @moul: if you can list all the bugs in an issue; but from what I know they are due to my mistake OR fixed OR known; but definitely worth a summary issue

  3. @moul: future hardware needs, so we can discuss with an R&D researcher team to see if we could work together and when

    • What are gonna be the minimum requirements for the validator machine on launch? What kind of AWS instances are we recommending?
      • @moul: launch target: commodity hardware, i.e., medium price dedicated server
      • @moul: IMO the two main focuses regarding hardware: 1. optimization, 2. storage rent + good gas price; and later -> the solution will be with sharding

  4. @zmilos blocked by DNS

    • @moul: we'll ask @jaekwon for the DNS
    • so you know I took gnoteam.com domain so we can have an independent domain for the team with different domain reputation, the goal is to use it when testing things before they become official in the *.gno.land space. -> ping @albttx

Action Items

  1. @harry-hov: Feedback needed on feat: addpkg command respects gno.mod file gno#922
  2. Compile a list of packages importing Realms, and resolve based on the list

@zivkovicmilos
Copy link
Member

18th dec 2023 - weekly worldwide sync

Antonio Navarro (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Continue with that Go(d) PoC
  • PR reviewing
  • Interviews
  • Meetings
  • Watch some meetings I missed from last week.

Marc (@mvertes)

What did I work on last week?

  • reflect2 in parscan: method calls
  • gnovm debug

What will I focus on this week?

  • reflect2
  • interview
  • gnovm debug

Guilhem (@gfanton)

What did I work on last week?

  • Feat(gnodev): Skip failing transaction on gnodev #1456
    • should fix #1447
  • Draft(gnodev): Add automatic gnoweb page reload on save #1457
    • everything is working, need some cleanup
  • Start digin again bft test for a better and durable fix
  • Make the import of previous keys/client failed on build #1483

What will I focus on this week?

  • gnodev hotreload
  • review contrib cards
  • dig on bft bug again

Michael (@MichaelFrazzy)

What did I work on last week?

  • Gnoland France trip (1 workshop + discussions on GoR and rewards)
  • Started Game of Life simulation in Go/Gno, ideally utilizing math/rand
  • Met with engineers to discuss gas/fee implementation. Meeting with Ray soon
  • Began GoR automation scripts v2 and GoR scoring v1 with Jon

What will I focus on this week?

  • GoR script(s) v2 before break
  • GoR scoring system v1 before break
  • Research into math/rand Gno port for Game of Life example
    • @zivkovicmilos: Implementing Game of Life is like an initiation step for any new language :)
    • John Conway demands a Game of Life sacrifice on a per-language basis or he haunts you, similar to the ghost of Hello World
  • Set up Dylan's Docker benchmark system on my machine for later fee estimation/benchmarking
  • Meeting with Google's Gemini AI directors regarding possible implementation

Do I have any blockers?

Milos (@zivkovicmilos)

What did I work on last week?

  • TPM interview process
  • Worked on finalizing the indexer spec + implementation
  • Almost lost my sanity with the poor WiFi of the calls in Rouen

What will I focus on this week?

  • Finalizing the TPM interview process for a few candidates
  • Finish the indexer implementation. I hit some hiccups in the implementation, where I realized our event dumping mechanism is way too clunky to be indexing transaction events. The indexer I'm working on will provide this option, but also more "source" functionality, such as indexing from a live node. Additionally, I'm leaving room for more types of items to be indexed (ex. Realm events)

Do I have any blockers?

  • No blockers for now; The blocker I had for the indexer has been resolved by simplifying the design, and staying true to the core function of the indexer: to easily fetch and serve data

Jon (@waymobetta)

What did I work on last week?

What will I focus on this week?

  • Need to finalize content for code-to-gno to provide to Design team before break
  • Need to reassess how we will go about Learn X in Y: X=Gno to be less like Go and more like Solidity/Cairo (blockchain-specific languages)

Do I have any blockers?

ray (@piux2)

What did I work on last week?

  • set up multinode with simulation tool and dataset
  • anlayzedi failed transactions on test3
  • reviewed code #1177 , #1305

What will I focus on this week?

  • complete gas meter changes and profiling
  • continue analyzing failed transactions

Leon (@leohhhn)

What did I work on last week?

What will I focus on this week?

  • Docs
    • Small reorg
    • Banker/Coins docs
    • stdlib
  • Extractor
    • Resolving @antonio's comments currently
    • Hopefully merged by end of tomorrow
  • Disperse.app
    • txtar tests for disperse
    • document txtar testing
  • Refactor grc 20 & 721 packages

Do I have any blockers?

  • :)

Manfred (@moul)

What did I work on last week?

What will I focus on this week?

  • Devrel strategy (OKRs, KPIs, etc)
  • Twitter Interview
  • Review AtomOne latest changes on the repo and try to propose improvements
  • Clarify future hiring needs with talent team
  • Interview for the Sec Engineer
  • Plan January
    • Roadmap Release
    • OKRs tweaks
    • Improving processes around PR/issue review
    • Improving core values clarity and making them known

Morgan (@thehowl)

What did I work on last week?

  • Le Retreat 🇫🇷
  • Helped organise and kick-start many discussions, including one on communications and the one last friday about mainnet/GoR/PRs
  • Reviews in the interview process, answer questions from candidates, etc.
  • Finally finished GnoChess retrospective -- I think it went well and unfinished
  • Got a coffee machine! ☕ Now I can become 200% more addicted
  • Contributed an idea for the IDE team
  • Went through Native Bindings, going through Milos' comments and merging today

What will I focus on this week?

  • Native bindings merge!
  • Gnochess!
  • Review Berty's grant
  • Add strconv package
  • Add link fixer for docs
  • Do a call tomorrow to show everyone my process for reviewing discussions and PRs
  • Review some docs, review PRs, and try to sort out a bunch of unfinished stuff by the start of the christmas break on Friday

Callouts

  1. Thanks to people that took care of the (meeting) owl last week for the meetings!
  2. @mvertes: How do you envision debugging working in the GnoVM? I see it mentioned as part of the parscan efforts
  3. @MichaelFrazzy: Any new developments for GoR / rewards while at the retreat last week?
  4. @thehowl: What coffee machine did you get? :)

@thehowl
Copy link
Member

thehowl commented Jan 12, 2024 •
edited by zivkovicmilos
Loading

8th jan 2024 - weekly worldwide sync

Guilhem (@gfanton)

What did I work on last week?

What will I focus on this week?

  • add workspace to gno if #1483 is merged
  • fix gnodev restore ordering
    • it appears that using broadcast sync to restore tx is a bad idea since we can lost ordering
  • add some tests to gnodev
  • check/close/cleanup my open PRs on gno repo
  • would love to start reworking the logger
    • @zivkovicmilos: Sorry I'm blocking you on this, will wrap up my initial slog PR so you can start tackling individual logs

Do I have any blockers?

  • nop

Morgan (@thehowl)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • All good :)

Milos (@zivkovicmilos)

What did I work on last week?

  • Totally did not work over the holidays 👀
  • Wrapped up the initial indexer implementation, will publish this week
    • @moul: are you working/sharing with onbloc and gno dx team?
  • Opened a PR for adding batch WS support, will open it once I add regression tests

What will I focus on this week?

  • Work on adding more unit tests for the indexer
  • Work on adding better unit tests for the JSON-RPC PR changes
  • Roadmap doc with @moul

Do I have any blockers?

  • I have started having nightmares in Amino binary

Antonio (@ajnavarro)

What did I work on last week?

  • Holidays!
  • Previous to holidays, some interviews, hiring decisions, and PR reviews.

What will I focus on this week?

Do I have any blockers?

  • I'm good right now

Leon (@leohhhn)

What did I work on last week?

What will I focus on this week?

  • Create issues for things I found while writing docs
  • Create naming discussion issue
  • Finalize OKRs
  • Start work on a GRC refactor

Do I have any blockers?

  • Nope

Hariom (@harry-hov)

What did I work on last week?

  • Holidays

What will I focus on this week?

Do I have any blockers?

  • Nope

Jon Roethke (@waymobetta)

What did I work on last week?

  • n/a

What will I focus on this week?

  • catch-up with everyone
  • finalize OKRs
  • finalize code-to-gno
  • clarify docs priorities

Do I have any blockers?

  • no

Peter

What did I work on last week?

  • Finished the PR for making the Machine data structure copyable so we can run tests in parallel.

What will I focus on this week?

  • TM2 - Fixing byzantine fault tolerance algorithm concurrency violations

Do I have any blockers?

  • Not really.

Ray (@piux2)

What did I work on last week?

  • Holidays
  • Finished one PR review

What will I focus on this week?

  • Complete Gas Meter changes
  • New Profiling

Do I have any blockers?

  • No.

Michael (@MichaelFrazzy)

What will I focus on this week?

  • GoR Submission Process v2
  • GoR Judging Criteria v1 and Governance Module tasks
  • Meeting with PhilH regarding his research grant proposal
  • Running analysis/sims using Dylan's and Ray's gas benchmark results
  • On-chain analysis, meeting with TRM Labs

What did I work on last week?

  • Break, prepped material for return
  • Completed CAIA Digital Assets credential
    • @zivkovicmilos: I read this as CIA Digital Assets credenrtial, and was very confused :)
    • I did start the top secret clearance process for MITRE, so maybe one day :D
  • Completed Wharton's top-level quant modeling & sim specialization capstone

Do I have any blockers?

  • None that already scheduled meetings won't solve

Manfred (@moul)

What will I focus on this week?

  • OKRs.
  • Roadmap doc workshop with some peers.
  • Help Milos and Ray with their new managees.
  • Bootstrap ADR-style articles with Christina.
  • Plan the month:
    • Proposal for the new bounty system (ETA week2).
    • weekly public workshop about GoR topics (ETA week2)
    • focus on optimizing code review and collab in general (ETA week2)
    • brainstorm on future HR needs (ETA week2)
    • release effective gno (ETA week3)
    • focus on gor (ETA week3)
    • focus on content writing & dogfooding from the core team (ETA week3)
    • release official roadmap (ETA week4)
    • focus on universities and events (ETA week4)

Dylan (@deelawn)

What will I focus on this week?

  • Catch up on various PRs and comments
  • Agent/oracle
    • Schedule meeting
    • Continue with prototyping
    • Create presentation

Callouts

  1. @thehowl: who's coming to FOSDEM? :)
    2. @moul: me!

Action Items

  1. @thehowl: @jaekwon, @zivkovicmilos, and whoever's interested, please review this PR: refactor(gnolang): handle duplicate method decls using TryDefineMethod gno#1459 -- it attempts to provide a better implementation for handling re-declarations in Gno code (which were introduced upon Jae's suggestion in the Native Bindings PR).
    2. @zivkovicmilos: Will look into it 🙏

@zivkovicmilos
Copy link
Member

zivkovicmilos commented Jan 22, 2024 •
edited
Loading

15th jan 2024 - weekly worldwide sync

Milos (@zivkovicmilos)

What did I work on last week?

  • Finished up the TM2 indexer 🎉
  • Prepped the Roadmap doc with Manfred and the team
  • Started setting up processes for the Gno EU team

What will I focus on this week?

  • Catchup on long-overdue PR / issue reviews
  • Unblock @gfanton on my logger PR, will wrap it up during the week
  • Team OKR finalization
  • Roadmap finalization with Manfred and the team

Do I have any blockers?

  • @moul the Dependabot GH bot needs write permissions on gno to push in Dependabot PRs (tidy go mod files)
  • @moul the indexer repo is ready to be made public

Hariom (@harry-hov)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • No

Guilhem (@gfanton)

What did I work on last week?

  • Worked on OKR
  • Work on a bft test fix on fix(bft): correctly drain channels events gno#1515
    • make bft test fail locally
    • add way to check which channel(s) hasn't been drained on failure
    • should fix most test from bft state_test.go
    • there are four tests that I was unable to fix
  • Merge time drifting fix for gnodev fix(gnodev): time drifting in gnodev gno#1510
  • Rework the way gnodev load packages by rewriting genesis instead of re-apply tx (in progress)
    • this way tx are loaded in the correct order

What will I focus on this week?

Do I have any blockers?

Antonio Navarro (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Start with my OKRs. Proposing a way to track proposed improvements using PIPs (parscan improvement proposals): https://github.com/mvertes/parscan/pull/1/files
  • Sync with Marc to see if that is a way that fits with him to be on sync and push together forward.
  • Do any modifications needed on the process as fast as possible and continue defining my following OKRs.

Do I have any blockers?

  • nope

Morgan (@thehowl)

What did I work on last week?

  • OKRs
  • TPM hiring stuff
  • Go through a huge chunk of email backlog (conversations on GitHub)
  • Talked with the community a bunch!
    • There's a big influx of activity on Discord and TG. hooray for docs! 🎉
  • Continue working on strconv
  • Mostly administrative week.
    • finished watching the roadmap videos
    • roadmap building

What will I focus on this week?

  • roadmap building, tpm interviews
  • focus on GnoChess + some native bindings (strconv issue).
  • also completing this PR: fix(cmd/gno): log panic information in gno test gno#1397
  • GnoChess:
    • finalize split of gnochess realm and packages
    • add (slightly polished) slides from the retrospective
    • seqid v2
    • reorganise tutorials and try to finalize them
    • kick-off adena integration, try to create some units of work that can be delegated.

Ray (@piux2)

What did I work on last week?

  • Gas meter
  • Sync up OKR
  • Reivew Code

What will I focus on this week?

  • Optimize gas meter
  • Profiling

Do I have any blockers?

  • No.

Michael Frasinelli (@MichaelFrazzy)

What did I work on last week?

  • Assisting with and writing various documentation
  • On chain data scraping and investigation
  • GoR tasks lists and script/user profile implementation into Manfred's GitHub directory
  • Meeting with teams to formulate the next month's plan (simulating gas/fees, airdrop final touches, etc)
  • PhilH research grant proposal
  • ATOM One design discussions

What will I focus on this week?

  • Completing additional documentation and summarizing current progress
  • Continuing gas/fee work
  • Continuing GoR v2 implementations and GitHub user profiles
  • Continuing to scrape data for onchain investigations and sims
  • Google AI experiments

Do I have any blockers?

  • None that currently scheduled meetings or plans won't fix

Leon Hudak (@leohhhn)

What did I work on last week?

What will I focus on this week?

  • OKRs, DevRel Team structure planning - AiB/DevX/Gno levels
  • Blog post sorting
  • More docs work
  • Reviewing beta.gnoswap.io
  • Issues about renaming, PRs implementing tha

Do I have any blockers?

  • nope

Manfred (@moul)

What did I work on last week?

  • Roadmap doc workshop with some peers, part 1.
  • Planning.
  • OKRs.
  • Bootstrap ADR-style articles with Christina.

What will I focus on this week?

  • Roadmap doc workshop with some peers, part 2.
  • OKRs (final?).
  • Proposal for the new bounty system (ETA week2).
  • weekly public workshop about GoR topics (ETA week2)
  • focus on optimizing code review and collab in general (ETA week2)
  • brainstorm on future HR needs (ETA week2)

Current plan for the weeks after.

  • release effective gno (ETA week3)
  • focus on gor (ETA week3)
  • focus on content writing & dogfooding from the core team (ETA week3)
  • release official roadmap (ETA week4)
  • focus on universities and events (ETA week4)

Petar

What did I work on last week?

  • tm2/consensus improvements

What will I focus on this week?

Do I have any blockers?

  • No

Marc (@mvertes)

What did I work on last week?

  • reflect for parscan: attempt to call interface methods for reflect named type values. Other method calls now work.

What will I focus on this week?

Do I have any blockers?

  • invoking interface methods for new reflect named type values currently panics, more investigation needed (later).

Callouts

@zivkovicmilos
Copy link
Member

zivkovicmilos commented Jan 29, 2024 •
edited
Loading

22nd jan 2024 - weekly worldwide sync

Milos (@zivkovicmilos)

What did I work on last week?

  • Opened a PR on fixing default config values - #1544
  • Opened a PR on standardizing the logging package - #1302
  • Standardizing Job Descriptions, wrapping up team OKRs

What will I focus on this week?

  • Resolve hanging personal PRs
  • Try to run just to stand still with new GH PRs / issues
  • Consensus engine improvement discussions with Petar
  • TPM hiring calls

Do I have any blockers?

  • For the TestingLogger discussion in #1544, what kind of format / output should the testing logger have? cc @gfanton

Leon Hudak (@leohhhn)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • Nope

Jon Roethke (@waymobetta)

What did I work on last week?

  • Administrative things
  • Finance talk/workshop
  • Small fmt docs fix

What will I focus on this week?

  • ETHDenver presentation
  • Faucet-hub user flows

Do I have any blockers?

  • no

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Parscan: add state management
  • Parscan: add missing expressions/statements to know better how everything works

Do I have any blockers?

  • No blockers

Guilhem (@gfanton)

What did I work on last week?

mainly:

What will I focus on this week?

  • Try to make some demo of gnodev
  • Improve gnodev:
    • Add tests to gnodev
    • Add a way to load local keybase
    • Add minimal configuration to use gnodev as remote server
  • Improve testscript:
    • make testscript not load exemple folder by default

Do I have any blockers?

  • nop

Michael (@MichaelFrazzy)

What did I work on last week?

  • GoR v2 scripts
  • Flippando modeling prep
  • Recording videos and reviewing docs for the community
  • Airdrop sim v2
  • Continued onchain datascraping for later use in gas/fee benchmarks and sims
  • Tokenomics review w/ Jae

What will I focus on this week?

  • GoR v2 scripts (potentially port some to Go)
  • Beginning Flippando modeling + sims
  • Tokenomics legal review
  • Assisting marketing w/ technical docs
  • Continue reviewing w/ Jae & Manfred

Do I have any blockers?

  • No, meeting w/ Ray and Dylan periodically regarding opcode data and oracles

Morgan (@thehowl)

What did I work on last week?

  • cford32: as mentioned on Signal, after making this work in Go I'll make this as a p/ package, too: after that, I'll add it to p/demo/seqid to have cool IDs.
    • Aside from dogfooding, this was a problem where I made a dumb solution in GnoChess -- ie. how do you have IDs that are compact, readable and sortable using lexical order (ie. AVL)? Note that strconv.Itoa is not valid (as "99" > "115")
    • And managed to find an issue in the Go stdlib :)
  • Reviews!
  • TMYG review
  • Clarify DevOps role for hiring
  • Merge a lot of PRs
  • Added GnoChess retrospective slides
  • I wanted to finish doing my workarounds on strconv, but turns out the best solution is to just wait for Maxwell's PR to be merged (gno type check).

What will I focus on this week?

  • Focus: GnoChess
    • finish seqid + cford32
    • finalize split of gnochess realm and packages
    • reorganise tutorials and try to finalize them
    • kick-off adena integration, try to create some units of work that can be delegated
  • NatBindings: Make precompilation work with Native Bindings
  • Berty grantee review
  • PR reviews
  • Possibly write-up a condensed summary from the rouen retreat + my thoughts on [RFC] Contract versioning (upgrade/proxy) gno#694

Marc (@mvertes)

What did I work on last week?

What will I focus on this week?

  • gno interactive debugger

Do I have any blockers?

  • no

Dylan (@deelawn)

What did I work on last week?

  • oracle
    • presentation
    • design
    • impelementation of package and gh realm
  • a few code reviews
  • looked at the latest BFT tests PR

What will I focus on this week?

  • open PR for gh example oracle realm using new packages
  • resume looking at 1326
    • run more behavioral tests
    • draw inspiration from the work in Jae's related PR
  • Get account set up for logz (managed ELK) for performance testing

Do I have any blockers?

  • not sure where we landed with 1434

Hariom (@harry-hov)

What did I work on last week?

Note: While working on r/demo/users missed some conveniece that i have while working with Go in vscode. So decided to improve vscode extension this week before continue working with Gno code.

What will I focus on this week?

Do I have any blockers?

  • No

Manfred (@moul)

What did I work on last week?

  • Roadmap doc workshop, part 2.
  • OKRs (final).
  • Brainstormed on future HR needs and wrote job descriptions.
  • Brainstormed on AtomOne hiring strategy and something similar for Gno products in AiB.

What will I focus on this week?

  • Mostly adhoc discussions, projects, meetings.

Callouts

  1. Kristov: Snyk / Deepsource? General thoughts?
  2. @gfanton: Mysterious discussion about: feat: use golang workspace gno#1567

    @moul: replied on GH.

  3. @thehowl: what is the final outcome for feat(sdk/vm): support float as arguments to maketx call gno#1434?
  4. @jon @leohhhn: we should give Hariom's VS Code extension some love: (https://drive.google.com/file/d/1F-HVNZbqapSf3MqRNPDamSyZOwJI4M8D/view?usp=sharing)

    @moul: In general, we need more dogfooding. Specifically, we should focus on vscode, gno playground, and gnodev. Devrel, please help improve the readmes of these projects and ensure they are linked from the main readme. Team members, please use these projects when sharing your screen to promote them. In general, we should share more screenshots, in reports, newsletters, twitter.

  5. @jon @leohhhn: Gno custom GPT?

@thehowl
Copy link
Member

thehowl commented Feb 5, 2024 •
edited by zivkovicmilos
Loading

29th Jan 2024 - weekly worldwide sync

Morgan (@thehowl)

did output

https://github.com/psss/did

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • feat: gno type check gno#1426 This PR addresses a number of issues at once and unblocks some dependency chains of mine (ie. putting GnoChess pkgs and contracts -> depends on strconv -> depends on this). I've asked Maxwell the status on it, and he said this:

    • I'm still on it and will be back to improve it soon, and yes I'm looking for more reviews, I had a feeling that it needs some iterations of review. I have added an overview of the solution and some comments to improve the readability but still not enough.

    • Please help me review it!

Hariom (@harry-hov)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • No

Antonio (@ajnavarro)

What did I work on last week?

  • Mainly working on implementing state memory dump and understanding better parscan

What will I focus on this week?

  • PR/issues reviews, continue with parscan

Do I have any blockers?

No blockers

Michael (@MichaelFrazzy)

What did I work on last week?

  • Finished testing GoR user profile scripts, currently testing GitHub CI/Actions implementation. Testing here, final repo/directory structure will be here
  • Continued GoR scoring rubric and reviewed plans with Jon & Morgan
  • Began preliminary AtomOne airdrop sim, using the data from Albert & Thomas (thanks again)
  • Continued onchain investigation and data scraping for future use
  • Gnoland legal discussions
  • Validator deterrent discussions

What will I focus on this week?

  • Continue (ideally finish) testing the user profile scripts on GitHub
  • Create first version of the AtomOne airdrop sim and prop weighting systems
  • Continue legal discussions
  • Begin Flippando modeling
  • Public Gno Office Hours starting again

Do I have any blockers?

  • Not at this time, eventually a repo token or access to our GitHub bot

Milos (@zivkovicmilos)

What did I work on last week?

  • Enabled secrets generation and management (#1593)
    • This PR is part of a series of PRs I'm working on to improve the chain initialization and connection flow
    • Verified our p2p implementation works fine with proper secrets / config setup 😎
  • Synced with Christina on the involvement of the core team for future blog posts
  • Converged with @petar-dambovaliev on what we need to scope out for the consensus engine improvements
  • Resolving pending PR comments, housekeeping with reviews

What will I focus on this week?

  • Publish a PR for config management
    • After this, we are fully capable of setting up and running multinode p2p consensus networks
  • Consensus engine work kickoff with @petar-dambovaliev
  • Use the "quiet" week to focus on pending PRs / issues

Do I have any blockers?

  • Blocked on subcommand naming discussions #1593 (check comments)
  • Blocked on how to structure the config commands (check callout)

Jon (@waymobetta)

What did I work on last week?

  • Docs config/scaffolding migrated + new repo established
    ^ also was pointed to this repo template but it looks blank so what is the ask there- to build out a proper template for forking into any new repo that is created?
    ^ I think CI on monorepo will also need to be adjusted? PR currently in draft awaiting CI additions.
  • Finished initial version of learn x in y minutes for Gno. It's not fully comprehensive, so wanted to gather feedback on what is missing and could be added while reducing redundancy with Go's version.
  • Shared feedback on miro board for GoR with diagrams and discussions on project origin, previous shortcomings, proposed version scopes, etc.
  • 2hr discussion with the finance team + a workshop
  • Faucet hub user flows

What will I focus on this week?

Do I have any blockers?

  • Waiting on Effective Gno PR to add recommendation to limit declaration of a single init() (discussion)

Guilhem (@gfanton)

What did I work on last week?

What will I focus on this week?

  • gnodev:
    • persistance data persistant data feature (berty request)
    • disable replay feature (berty request)
    • add tests
  • txtar:
    • continue working on use command (need feedback first)

Do I have any blockers?

  • need feedback on the use command

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • no

Marc (@mvertes)

What did I work on last week?

What will I focus on this week?

  • gno debugger

Do I have any blockers?

  • no

Leon Hudak (@leohhhn)

What did I work on last week?

Did output

What will I focus on this week?

  • Finishing Gnoclient multicall testing, mocking signer&rpcclient :)
  • Finish & test gnoblog-cli PR
  • Finish disperse.app, write issue on txtar testing, write up docs for txtar
  • Work on docs:
    • Realms as EOAs updates
    • Gnodev/gnoclient references

Do I have any blockers?

  • Having trouble mocking stuff :)

Kristov (@kristovatlas)

What did I work on last week?

  • AppSec planning
  • Code familizarization
  • Began Ledger PR review
  • Complete onboarding tasks & scheduled 1:1 Intros

What will I focus on this week?

  • Complete Ledger PR review

Do I have any blockers?

  • N/A

Ray (@piux2)

What did I work on last week?

  • finished new gas meter implementation
  • inital contract gas, op code and mem alloc profiling
  • integrated open telemetry protocol trace with Elastic Kibana

What will I focus on this week?

  • Gas meter workshop
  • Write benchmark contract
  • Seperate instrumnet code and merged gas meter code

Do I have any blockers?

  • N/A

Petar

What did I work on last week?

  • reviews, reading of Jae's consensus paper

What will I focus on this week?

  • Implement a generic consensus library with Milos

Do I have any blockers?

  • No

Albert (@albttx)

What did I work on last week?

  • Portal loop
  • Portal Loop monitoring Oracle (r/portal/counter)
  • Fix gno.land
  • docs.gno.land separated repository

What will I focus on this week?

  • docs.gno.land separated repository (part2)
  • Monitoring on all gno urls + alerting
  • Exporter for gnoland + tm2 + r/*

Do I have any blockers?

  • No

Callouts

  1. @thehowl: I've made a PR to make MsgRun able to return values like Call rather than simply returning what is println'd. What do you folks think? feat(sdk/vm): support return values from main in msgrun gno#1591
  2. @thehowl: dependabot PRs which change GH actions like this one fail because we don't have an API key set up for fossa (license detector for open source projects). cc @moul: what do we want to do about it?
  3. @zivkovicmilos: I have a dilemma on how we should structure the config management in the start command. Should we have a single jumbo config for the node, or multiple config files (for different modules, currently 5)?

Action Items

  1. @thehowl: need reviews:
  2. Everyone, check out @waymobetta's Learn Gno in 5 mins: https://github.com/gnolang/devrel/pull/27 before we send it off to the official website

@zivkovicmilos
Copy link
Member

5th Feb 2024 - weekly worldwide sync

Morgan (@thehowl)

Off today

did output

What did I work on last week?

What will I focus on this week?

  • GnoChess:
    • I'll probably finally finish the split this time (started re-working it last week).
  • NatBindings:
    • Make precompilation work
  • Reviews
  • bunch of calls this week

Do I have any blockers?

  • gno type check: feat: gno type check gno#1426
  • I'm still waiting on legal to get back to me for signing the Google CLA. this is required for making contributions to the Go repository (want to make one fixing up encoding/base32 for encodings without paddings).

Michael (@MichaelFrazzy)

What did I work on last week?

  • User profile script testing is well underway
  • GovGen Airdrop sim/data aggregation
  • Continued legal discussions
  • Gas/fee discussions with Ray

What will I focus on this week?

  • Finish profile testing/formatting and start adding extra features
  • Add extra parameters and templates to GovGen/Atom One sim framework
  • Meeting w/ Ray to check math and overall gas system discussions
  • Confirm initial Flippando models w/ Dragos
  • Office hours/townhall/community discussions

Do I have any blockers?

  • Eventually will need GitHub org access to secrets to add a variable (not needed right away)

Jon Roethke (@waymobetta)

What did I work on last week?

  • We're currently using this org-level repo redesign as an intro/starting point for external developers with our outreach (student program); please post comments in PR thread
  • GoR architecture discussions for offchain profiles with Michael, Morgan
  • Reviewed blog PRs
  • Learn X in Y rework (thanks Morgan)
  • ETHDenver presentation (still WIP)
  • PR to sort packages during addpkg
  • Playground video for allocating tokens at genesis

What will I focus on this week?

  • ETHDenver presentation (still WIP)
  • Overview presentation recording
  • Additional Playground videos requested

Do I have any blockers?

  • N/A

Antonio (@ajnavarro)

What did I work on last week?

did output

What will I focus on this week?

Do I have any blockers?

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • Continue work on opcode benchmarking improvements (code cleanup, export to elastic)
  • Keep looking at 1585 and post a code review if no better solutions come to mind
  • Discuss and plan for work to write benchmarks for certain VM operations using the builtin go benchmarks from the testing package

Do I have any blockers?

  • no

Hariom (@harry-hov)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • No

Marc (@mvertes)

What did I work on last week?

What will I focus on this week?

  • gnovm debugger:
    • fixing stack traces for non func blocks
    • print global variables
    • print index or selector expressions
    • add debugger unit tests

Do I have any blockers?

  • no

Milos (@zivkovicmilos)

What did I work on last week?

What will I focus on this week?

  • Wrap up the faucet swap, and pending PRs
  • Review PRs by @ajnavarro on the indexer 💃
  • Join @petar-dambovaliev in the tendermint engine code
  • Open a brand new bottle of Merlot if we merge #1593 and #1605

Do I have any blockers?

  • Blocked by reviews on the gnoland secrets PR
  • Blocked by reviews on the gnoland config PR

Petar

What did I work on last week?

  • Implementing Jae's consensus algorithm paper into a Go library

What will I focus on this week?

  • Same

Do I have any blockers?

  • No

Ray (@piux2)

What did I work on last week?

  • Gas meter profiling
  • Gas meter workshop
  • Reviewed package /p/ and realm /r/ access control
  • Reviewed AssertOriginCall access control

What will I focus on this week?

  • Refine gas meter profiling method based on the feedback
  • Design the benchmarking contract.

Do I have any blockers?

  • No

Leon (@leohhhn)

What did I work on last week?

did output

What will I focus on this week?

  • Write tests for gnoclient-cli
  • Finish up blog PR
  • Integrate Gnoclient's MsgRun with new baseTxConfig
  • revamp "Getting started" section in docs
  • Hold Gno office hours!!

Do I have any blockers?

  • Nope

Albert (@albttx)

What did I work on last week?

  • Migrate docs.gno.land (1/2)
  • Fix tx-archive
  • Gno autocounterd
  • Alerts on gno websites

What will I focus on this week?

  • Fix tx-archive
  • Merge portal loop

Do I have any blockers?

  • PR to merged, in progress

Kristov (@kristovatlas)

What did I work on last week?

  • Security review fix: ledger discover gno#1502
  • (Ongoing) golang static analysis security tools for gno repo
  • 1:1 intros with IT, DevOps
  • (Ongoing) planning gnokey internal audit
  • OnBloc product familiarization
  • AtomOne/GovNo familiarization

What will I focus on this week?

  • (Ongoing) golang static analysis security tools for gno repo
  • (Ongoing) early stage of gnokey internal audit
  • Catch up on any PR tags in GH

Do I have any blockers?

No

Callouts

  1. @thehowl: not in the call, but just wanted to confirm that there are no objections/disagreements on using Gno as the canonical name of the language, and avoiding "Gnolang" publicly entirely. The reasoning: unlike "go", we don't need gnolang because "gno" is not a common english verb/word. Please, tell me what you folks thinks as a comment on the PR. thanks!
    • @zivkovicmilos: After careful silence from the team, we agreed this was the best way forward indeed
  2. @zivkovicmilos: I need reviews on #1593 and #1605 to unblock for gnoland init and setup docs (multinode)

Action Items

  1. Please comment in org-level repo redesign PR thread about what you do/don't like.
    • After discussing: Implement collapsable sections for the README

@zivkovicmilos
Copy link
Member

zivkovicmilos commented Feb 14, 2024 •
edited by thehowl
Loading

12th Feb 2024 - weekly worldwide sync

Antonio (@ajnavarro)

What did I work on last week?

  • Mainly working on the tx-indexer, making it much faster on queries and ingestion (also much easier to use using a GraphQL Playground):

    graphql-complex-demo

    I am using low level Iterator functionality to avoid reading not needed entries when a filter is used. It can be improved more with secondary indexes, but not needed now (even with no limits results are shown in less than 50ms).

What will I focus on this week?

  • Finish tx-indexer work and addressing @zmilos comments on my previous PR
  • Continue with PR reviews.

Do I have any blockers?

  • Nothing

Michael (@MichaelFrazzy)

What did I work on last week?

  • Finished initial AtomOne airdrop analysis & testing framework, posting to AtomOne genesis repo after another round of tests
  • Continued contributor user profile testing here (request or ask for access) and here
  • Participated in AtomOne townhall and Gnoland event/marketing discussions
  • Started Gnoland office hours again on Discord with Michelle, Jon, and Leon
  • Continued Gnoland legal review (creating a doc as a "source of truth", do and don't list)

What will I focus on this week?

  • Continue AtomOne framework (1 main bug left) and start adding a bunch of cool features (auto-summarization, charting, maybe even a full dashboard)
  • Now that the profile permissions have been fixed, test and reformat CSV and .md outputs to look as nice as possible. Begin cross-repo/org-wide testing within my "Fraz Labs" test GH org
  • Additional Gnoland Office Hours on Discord and AtomOne townhalls
  • Create initial Flippando spreadsheet model to begin sensitivity analysis and model design

Do I have any blockers?

  • Not sure which tokenomics meeting time to go with (Tues, Wed, or both). Jae has confirmed larger overview meeting tomorrow, Manfred and others involved have confirmed smaller Wed architecture meeting time.

Guilhem (@gfanton)

What did I work on last week?

  • light week for me as I was off on monday and friday
  • worked on GnoDev:
    • Improving interaction, creating a proxy that load user keybase to create a rest API
    • Add more flags: -max-gas, -no-replay, -node-rpc-listener
    • Worked on gnodev persistance
    • tests
  • Addressing comments on txtar use PR

What will I focus on this week?

  • GnoDev intro video
  • GnoDev tests
  • GnoDev Interactions
  • GnoDev GnoDev GnoDev

Do I have any blockers?

  • nop

Marc (@mvertes)

What did I work on last week?

What will I focus on this week?

  • GnoVM debugger: improve print command (minor)
  • Yaegi: catchup the 2 last Go releases
  • parscan: composite types

Do I have any blockers?

  • no

Hariom (@harry-hov)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Milos (@zivkovicmilos)

What did I work on last week?

  • Not a super productive week
  • Finalized details regarding the faucet hub with @waymobetta
  • Discussed open PRs, reviewed pending blocked PRs

What will I focus on this week?

  • Review pending PRs, for real 🙂
  • Wrap up the requested gnoland config changes
  • Join @petar-dambovaliev in the tm engine code

Do I have any blockers?

  • Same blockers as last week, blocked by reviews on gnoland secrets and gnoland config

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • finish reviewing fix: []byte("xxx") should not be treated as const gno#1597
  • dedicate time to just reviewing PRs
  • make opcode benchmarking changes to record the type of evaluation for OpEval codes
  • look at where additional opcode benchmarking data might be gathered in the preprocessor
    • understand better how the preprocessor works
    • identify potential areas for improvement after package creation

Do I have any blockers?

  • no

Leon Hudak (@leohhhn)

What did I work on last week?

Output of `did`

What will I focus on this week?

  • Docs:
    • Remove/move faucet from getting started
    • revisit getting started section
      • read through, see what can have a revamp
    • update getting started with beginner friendly stuff- go setup?
    • include gnodev as first use
    • reorg concepts to include effective gno
  • Add more features to Disperse
  • Finish up testing blog realm
  • See if we can add analytics to test3 blog
  • OOO from Wednesday till next Wednesday

Do I have any blockers?

  • Nope

ray (@piux2)

What did I work on last week?

What will I focus on this week?

  • continue working on the OpCode benchmark contract and profiling
  • review code

Do I have any blockers?

  • no

Albert Le Batteux (@albttx)

What did I work on last week?

  • fix: tx-exports stats by CI
  • CI-ify Leon gno package exports
  • add exporter for gno websites (gno.land, {rpc.,}portal.gnoteam.com)

What will I focus on this week?

(small week, 3 days of bank holiday monday -> wednesday)

  • AtomOne stuffs
  • will try to works on improving Github runners
    • Add exporter
    • Multipler runners per servers
    • Single runner for benchmark

Do I have any blockers?

  • Need @moul for for Github tokens

Jon (@waymobetta)

What did I work on last week?

  • Overview presentation recording
    • Need to re-record based on a few incorrect statements
  • Additional Playground videos
  • blog PRs
  • office hours
  • gophercon planning
  • faucet-hub planning

What will I focus on this week?

  • Incorporate feedback from Morgan/Dylan
  • Incorporate feedback from Trevor (re: Playground videos)

Do I have any blockers?

  • no

Petar

What did I work on last week?

  • Jae's consensus algorithm - Message queue

What will I focus on this week?

  • same

Do I have any blockers?

  • no

Kristov (@kristovatlas)

What did I work on last week?

  • PR catch-up (complete)
  • Draft in progress: feat: Add malicious examples directory #1649
    • starting with solidity analogues
  • Started Adena wallet audit

What will I focus on this week?

  • Adena wallet audit

Do I have any blockers?

No

Morgan (@thehowl)

What did I work on last week?

did output
  • GnoChess: the split PR is almost complete. I really like the new set-up with gnodev
  • PR reviews
  • Drafting up PR triage system!
  • Helped michael with GOR automation
  • Went to meet Turin's local Gopher community :)

What will I focus on this week?

  • Off on monday
  • GnoChess:
    • Finish split PR
    • Get started on the adena integration
  • NatBindings: get rolling on the precompilation
  • Reviews
  • Finish drafting PR triaging (and possibly share & discuss with you all)
  • Some GoR work, probably
  • possible Side Endeavours of the Week:
    • I might try to dump all our (public) GitHub pull request data into a SQL database, as it would be useful to both me and Michael for stats and GoR.
    • contribs/gnok, contribs/gnost
    • I want to attempt a refactor that improves on what was started in #1417
    • and perhaps adding more benchmarks / trying to find a way to publish go benchmarks graphically (gnolang/benchmarks).

Do I have any blockers?

I have the usual bunch of PRs that need reviews :) (pretty please~!)

Callouts

  1. @MichaelFrazzy: What is currently being worked on for AtomOne? I see a lot of bullet points regarding it. Is it purely tokenomics now?
  2. @gfanton: Where are the Gnodev videos being hosted?
  3. Any features of Gno that you would like to call attention to with respect to security? e.g. previous chat about int vs big.int

@zivkovicmilos
Copy link
Member

19th Feb 2024 - weekly worldwide sync

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • I will be OOO for most of the week.

Do I have any blockers?

  • nope

Albert Le Batteux (@albttx)

What did I work on last week?

(small week due to bank holidays)

  • Moslty GovGen and infrastructure stuffs

What will I focus on this week?

  • Gno: Closing portal-loop #1400
  • Gno: Closing autocounterd #1620
  • GovGen

Do I have any blockers?

  • No

Hariom (@harry-hov)

What did I work on last week?

  • gno mod why - #1407 [NEEDS REVIEW]
  • Split r/demo/users - #1433 [NEEDS REVIEW]
  • gno bug - #1325 [NEEDS REVIEW from @Milos]
  • Versioning PR (#1631)

What will I focus on this week?

  • gnokey takes address from flag --key (Related PR: #877)
  • Versioning PR (#1631)
  • PR reviews
  • r/demo/postit (#1396)

Do I have any blockers?

Guilhem (@gfanton)

What did I work on last week?

  • Add GroupComments support to the VM
  • Add simple node tests to gnodev
  • Bump golang 1.20 to 1.21 with the release of go 1.22
did output * Pull requests created on github: 3 * gnolang/gno#1668 - feat(gnodev): add node tests * gnolang/gno#1658 - feat(vm): add `CommentGroup` and `Comment` attributes * gnolang/gno#1654 - feat(go): bump go 1.20 to 1.21

What will I focus on this week?

  • Finish and cleanup my open PR
  • Works on a REST api proxy for gnodev and gnoland

Do I have any blockers?

  • nop

Michael (@MichaelFrazzy)

What did I work on last week?

  • Base functionality besides directory creation working within the GoR/mainnet contributor profile system
  • Took a short break from the above to create a Flippando sim framework! (demo soon, will live in hackerspace)
  • AtomOne Analysis framework + dashboard nearly complete
  • Community engagement (co-hosted AtomOne townhall, Gnoland Discord assistance, doc edits, etc)

What will I focus on this week?

  • Redo profile system README, clean up structure, and combine YAML files. Add all recent changes to above test org
  • Finish remaining profile testing and bug fixing
  • Working on a GoR revamp presentation
  • Demo and expand Flippando sim framework (tracking FLIP, NFTs created, marketplace dynamics, burn rate, etc)
  • AtomOne townhalls and validator assistance

Do I have any blockers?

  • No

Morgan (@thehowl)

did output

What did I work on last week?

What will I focus on this week?

  • Document-writing: GoRv2 and PR triaging
  • Development-wise, mostly ctrl+c ctrl+v from last week:
  • NatBindings: get rolling on the precompilation
  • GnoChess: get started on the adena integration
  • Catch up on reviews
  • possible Side Endeavours of the Week:
    • I might try to dump all our (public) GitHub pull request data into a SQL database, as it would be useful to both me and Michael for stats and GoR.
    • contribs/gnok, contribs/gnost
    • and perhaps adding more benchmarks / trying to find a way to publish go benchmarks graphically (gnolang/benchmarks).
    • Codecov fixes.

Do I have any blockers?

  • Should be finalizing with legal the signing of Google's CLA. If that's sorted out, I might also start out making
  • feat: gno type check gno#1426 blocks me on feat(stdlibs): add package strconv gno#1464, which is actually important for the completion of native bindings efforts. If I get some time, I'd like to help maxwell push it forward (maybe by making a PR to address some changes / integrate the proposal me and antonio made.)

Milos (@zivkovicmilos)

What did I work on last week?

  • Reviewed pending PRs, resolved dangling discussions
  • High-level sketches for go-tendermint
  • Off for part of the week because of state holidays

What will I focus on this week?

  • Continue working on go-tendermint with @petar-dambovaliev
  • Outline the first core blogpost for Christina
    • It will most probably be a joint one by myself and Petar, for the go-tendermint effort so we can break the ice
  • Help @moul with consolidating the Roadmap document (Miro)
  • Write high-level tasks for the team that relate to the roadmap document
  • Review and make a game plan for tackling "blockchainless Gno" in Q1 with the team
  • Review Onbloc's event emit PR
  • Working with Mig to kickstart Belgrade retreat planning 🎉
    • There will be more news this week, we'll send out a survey for gathering input

Do I have any blockers?

  • No aparent blockers, apart from lack of PR reviews :(

Marc (@mvertes)

What did I work on last week?

What will I focus on this week?

  • PR reviews and follow-ups
  • a bit of yaegi
  • a bit of Go (reflect2 proposal) and parscan

Do I have any blockers?

  • no

Ray (@piux2)

What did I work on last week?

  • standardized opcode benchmarking contract
  • reviewed PR 1606 and analyzed the root cause of issue 1588

What will I focus on this week?

  • put load on the benchmarking node
  • review code

Do I have any blockers?

  • no

Petar

What did I work on last week?

What will I focus on this week?

  • Working on the library and getting old PRs merged

Do I have any blockers?

  • no

Callouts

  1. @zivkovicmilos: We need to start thinking about core team blog posts so Christina can plan for them in the coming months. I proposed an initial blog post by @petar-dombaliev and myself, for the work we're doing on go-tendermint. After that, we should aim for 1 blog post per month
  2. @thehowl: milos and leon, wen retreat? On this point, following what we discussed for the "Skiing non-retreat", I was thinking of possibly proposing a retreat in Trento (major city in South Tyrol, by the dolomites) at one point. Although it's probably best if we have ie. the date of the company retreat before planning that.
    • @zivkovicmilos: We are fortunate enough to have a good team retreat budget this year, so we can aim to have at least 2 team retreats 🙂
  3. @ajnavarro: I'll be OOO for the rest of the week due to some contractor work at home. Ping me if you need anything from my side and I'll answer ASAP.
  4. @thehowl: I see the protal loop has been deployed. Are we still working on the faucet? Are we blocked on the GH oracle for that?
  5. @ilker: ❓ mystery demo ❓

@zivkovicmilos
Copy link
Member

4th March 2024 - weekly worldwide sync

Michael (@MichaelFrazzy)

What did I work on last week?

  • Finished first successful tests of contributor profile system
  • Flippando analysis/sim framework + dashboard starting place nearly done testing, will be posted this week in hackerspace
  • AtomOne analysis/sim framework + dashboard similarly will be posted this or early next week
  • GovGen townhalls + validator prep
  • Legal reviews continued
  • Gnoland constitution prep

What will I focus on this week?

  • Finishing format and cross-repo testing for all contributor profile code
  • Rewriting profile system README based on the above work
  • Working with DevRel and Morgan to prep internal GoR presentation
  • Posting Flippando code asap
  • Posting AtomOne code asap
  • GovGen launch
  • Phil H grant beginning, coordinating and creating tasks

Do I have any blockers?

  • No

Jon (@waymobetta)

What did I work on last week?

  • Blog automation
  • Gophercon planning
  • Overview presentation recording
  • Gno rush campaign proposal
  • GoR presentation (internal)
  • Office hours

What will I focus on this week?

  • Gophercon planning
  • Gnome.town tutorials
  • Gno developer call
  • Fix 1618 and resubmit for review

Do I have any blockers?

Guilhem (@gfanton)

What did I work on last week?

  • Mainly worked on gnoapi: a gateway for interacting with Realm using REST api like.
    image
    • mainly designed for gnodev but can be use on any gnoland node remotely
  • Added tests to gnodev
    • I originally planned to use txtar to test gnodev, but it seems like overkill for now.

What will I focus on this week?

  • go workspace: got some idea to make it works
  • bft tests: I will take a look to finish fixing those
  • cleanup my open PRs

Do I have any blockers?

  • No

Milos (@zivkovicmilos)

What did I work on last week?

What will I focus on this week?

  • Finalizing implementation details for go-tendermint
  • Review comments left on PRs I've authored
  • Focus more on unblocking the team this week, the pipeline for PRs / issues is becoming disturbing

Do I have any blockers?

  • :)

Morgan (@thehowl)

What did I work on last week?

  • Transpiler refactor:
  • Quite a few PRs to fix CI (labeler, codecov), and a couple of other chores
  • Submitted two proposals to Gophercon EU and Gophercon US
  • Kick-start Gophercon US capture the flag challenge series
  • Lots of reviewing (12 PRs, but I'll avoid the did output following manfred and milos's feedback ;) )
  • finishing up pr triaging document

What will I focus on this week?

  • Finish up work on the transpiler
  • GitHub data puller
  • finish up PR triage / GoRv2
  • benchmarks
  • Reviews

Do I have any blockers?

Marc (@mvertes)

What did I work on last week?

  • updates to gnovm debugger

What will I focus on this week?

  • PRs review
  • investigate (de)coupling interpreter from storage transactions
  • some yaegi (generic stdlib packages) & parscan (improving Go reflect to create interfaces & methods in Go runtime) catch-up

Do I have any blockers?

  • no

Ray (@piux2)

What did I work on last week?

  • building tools to load large data to the node

What will I focus on this week?

  • continue building the tool
  • prepare a workshop for updated cpu cycle bencharmarking

Do I have any blockers?

  • no

Hariom (@harry-hov)

What did I work on last week?

  • Resolved Review comment on my PR(s)
  • Versioning PR (#1631)

    Mostly resolved merge conflicts and working on failing tests

  • Continued working on r/demo/postit (#1396)

    Frontend

What will I focus on this week?

  • gnokey takes address from flag --key (Related PR: #877)
  • Versioning PR (#1631)
  • r/demo/postit (#1396)
  • Try to do more PR reviews

Do I have any blockers?

  • No

Leon Hudak (@leohhhn)

What did I work on last week?

What will I focus on this week?

  • Implement gnoblog-cli feedback
  • Brush up Gno Coins functions
  • Rework disperse <3
  • Rework getting started on pages & go through getting started repo :)

Do I have any blockers?

  • nope

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Work on parscan/GnoVM. I'll try to catch up with Marc to see where I can help the most.

Do I have any blockers?

  • Intermitent internet/power/water/heating at home right now mixed with really bad weather.

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • review PRs
  • sync with Ray and focus more on helping to benchmark node performance
  • finish up tests for PR 1689 to get it ready for review

Callouts

  1. @MichaelFrazzy @waymobetta: What's the current status for the org profile README? I see it being mentioned from time to time, and have reviewed the PR, but we haven't merged it in yet
    • We have an old version from before the bulk of the work started, this week I plan on rewriting it with any time possible (Michael)
  2. @waymobetta: Did we attend / have any side gig at ETHDenver?

@zivkovicmilos
Copy link
Member

11th March 2024 - weekly worldwide sync

Antonio (@ajnavarro)

What did I work on last week?

  • PR reviews, mainly on faucet, tx-indexer and gno repos.
  • Continue with parscan memory state dump, thinking about different problems like, type data missed when encoding, performance issues applying the memory Dump, and how to avoid incompatibilities between Dumps (a dump is tightly coupled with the version that created it.) I guess these problems are also present on GnoVM and we have to address them.
    • @zivkovicmilos: > I guess these problems are also present on GnoVM and we have to address them. 🙂
  • Helping with the DevOps hiring process.
  • Address change requests on tx-indexer PR.

What will I focus on this week?

  • Create a final proposal after a lot of back and forth about how to do memory Dumps for saving the vm state, open an issue to do some research about how to run several vm versions at the same time to be able to execute a Dump, and/or how to avoid/migrate old dumps to be able to run them on newer vm versions.
  • tx-indexer: Implement secondary indexes to be able to query block transactions by hash.

Do I have any blockers?

  • no blockers

Guilhem (@gfanton)

What did I work on last week?

  • Worked on GnoDev blogpost
  • Implemented and merged #1745: unquote feature for gnoland txtar
    • allow quoting arguement and handle escape sequence
  • Update & cleanup some of my old PRs:
    • Add ChainID flag to gnodev #1622
    • Update Gnodev node test #1668
  • Helped Rouen students onboard with Gno and gnodev
    • @moul: do you plan to update things on gnodev, based on their feedback?

What will I focus on this week?

  • GnoDev blogpost
  • write Realm as part of my OKR
  • Conintue cleanup my open PRs
  • Error management

Do I have any blockers?

  • no

Hariom (@harry-hov)

What did I work on last week?

  • Versioning PR (#1631) (took most of my tim)e
  • r/demo/postit (#1396)
  • Overall short week cos public holiday.

What will I focus on this week?

  • Versioning PR (#1631)
  • gnokey takes address from flag --key (Related PR: #877)
  • r/demo/postit (#1396)
  • Fix broken vscode extension (precompile -> transpile)

Do I have any blockers?

  • Nope

Morgan (@thehowl)

What did I work on in the last 2 weeks?

What will I focus on this week?

Focus: GitHub data puller / Game of Realms / GC Challenge Series

  • gh-sql: continue adding resources, hopefully publish as repository by EOW.
  • Game of Realms
  • Booking for Serbia
  • Make a first Challenge Series for GC US.
  • Contribution to Go repository to fix up package encoding/base32.
  • Possibly start working through gno doc's http viewer (or some prep PRs, at least)
  • reviews
    • I'm changing up my workflows and so I won't be reading GitHub until I finish my existing review queue. If you're awaiting feedback on a PR I already reviewed, please ping me

Kristov (@kristovatlas)

What did I work on last week?

  • gnokey auditing
  • review int overflow PR
  • feedback on faucet hub API

What will I focus on this week?

  • gnokey auditing
  • review behavior of overflow library

Do I have any blockers?

  • No

Marc (@mvertes)

What did I work on last week?

  • parscan: refactor representations of VM values, following discussions with Antonio, to abstract out reflect, facilitate missing type kinds, and ease state checkpoint.
  • gnovm: study how to decouple memory state from interpreter

What will I focus on this week?

  • parscan: add missing type kinds
  • PR reviews

Do I have any blockers?

  • no

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • As a follow up to the observability call this week, make a PR to merge in the metrics that have been added on another branch
  • Finish one challenge series challenge proposal
  • Address an outstanding VM PR I'm the owner of
  • Work out how to test concurrent transactions

Do I have any blockers?

  • no

Ray (@piux2)

What did I work on last week?

  • completed initial load testing.
  • identified a few attacking point and performance improvment areas.
  • polished load testing tool.

What will I focus on this week?

  • complete standard OpCode benchmarking
  • prepare the workshop

Do I have any blockers?

  • No.

Leon Hudak (@leohhhn)

What did I work on last week?

  • Merch discussing & coordination with Aidar
  • Contact Tokyo venues for Gno Tokyo
  • Networked on ETH Belgrade event on Monday
  • Memeland package & realm v1 - PR
  • Work on coin.gno
  • Merged gnoblog-cli
  • PR to add index pages to sections
  • Write up budgets for Gno Korea & Gno Japan
  • Update From Zero to Gnoland Hero to include Playground - branch
  • Update gno.land content:
    • Home
    • GoR
    • Events

What will I focus on this week?

  • Working with Milos to integrate Memeland realm
  • Create presentation for Korea event using the Memeland realm
  • Write up issues I found for Playground when I was updating the FZGH tutorial
  • Update Docs: How-to guides to use the Playground
  • Create a Playground section in Getting started as the first thing people see

Do I have any blockers?

  • Nope

Milos (@zivkovicmilos)

What did I work on last week?

  • Swapping the legacy faucet implementation on the Gno monorepo
  • Various PRs for go-tendermint with @petar-dambovaliev (testing suite, cleanup)
  • Memeland UI work for the upcoming Korea workshop
  • DevOps hiring process
  • Onboarding Nemanja

What will I focus on this week?

  • Finalizing ongoing efforts / PRs / issues
  • DevOps hiring process
  • Setting the foundation for test4 (multinode testnet)

Do I have any blockers?

  • No blockers so far

Petar

What did I work on last week?

  • Investigating how generics can be implemented in gnovm
  • finishing up go-tendermint lib

What will I focus on this week?

  • same

Do I have any blockers?

  • no

Callouts

  1. @zivkovicmilos: Faucet Hub UI Demo
  2. @zivkovicmilos: Meme.land UI Demo
  3. @thehowl: 🎉 PR Triaging 🎉

@zivkovicmilos
Copy link
Member

zivkovicmilos commented Mar 25, 2024 •
edited
Loading

18th March 2024 - weekly worldwide sync

Hariom (@harry-hov)

What did I work on last week?

What will I focus on this week?

Continue from last week:

  • Versioning PR (#1631)
  • gnokey takes address from flag --key (Related PR: #877)
  • Fix broken vscode extention (precompile -> transpile)

Do I have any blockers?

  • Nope

Antonio (@ajnavarro)

What did I work on last week?

  • Add secondary indexes to the tx-indexer, making possible to query transactions by hash as before.
  • Continue with state dump on parscan, found that the best way to do it is on the compile.go side. Almost done with a preliminar implementation
  • Reviewed almost 30 PRs.

What will I focus on this week?

  • I want to finish parscan state dump. I was thinking about a way to save and recover states that are bigger than the available memory. I have to check with @marc733 about how feasible and how it fits on parscan.

Do I have any blockers?

  • no

Morgan (@thehowl)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Guilhem (@gfanton)

What did I work on last week?

  • Improve gnodev logger, make it easier to debug #1790:
    • Switch on charm log for a more convenient logger and improved overall display.
    • Add a way to catch node genesis deliver tx to be able to handle error
    • Improve column display
      Screenshot 2024-03-18 at 16.29.51
  • Add JSON arguments handler in MsgCall #1776
  • Started ways to improve errors management in gno:
    • Replacing all tm2 Warps and New errors methods with std errors methods (fmt.Errorf(%w) and errors.New)
    • Add a way to wrap Stacktrace into specifc error
    • Ultimatly my goal is to be able to split error from the stacktrace

What will I focus on this week?

  • finish gnodev improve logger PR #1790
    • Add a separate command to gnodev: gnodev-log, that connect to local gnodev and display node logs in real time (I will maybe do an)
    • Add server-mode to print all logs directly from gnodev and disable interaction.
  • Gnodev Blog post (I didn't work on it last week)
  • Im currently sick 🎉, so I will be in slow mode until i get better

Do I have any blockers?

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • Write out a complete challenge series task and test it. Will update the notion page with the full details
  • Get metrics sent to Grafana so I can accurately complete the README in the metrics PR; seems like I'll need the grafana agent
  • Keep up with and review work being done to fix the vm closure issue
  • Pick up on fix: handle assignments to dereferenced pointer values gno#1398 again
  • Start work on token distribution claim process @moul to provide some input based on previous work that has been done

Do I have any blockers?

Not presently

Leon Hudak (@leohhhn)

What did I work on last week?

What will I focus on this week?

  • Minor adjustments to Memeland realm
  • Memeland tutorial/presentation for Korea workshop
  • Fixing up tutorial bugs & issues
  • Finishing blocked howto & getting started refactors
  • Handle Tokyo venue contract issues, contact catering company for event
  • DevRel tasks overview - sort/prioritize. Clean up DevRel board
  • Fly to Korea and stay alive in the process

Do I have any blockers?

  • Waiting on the playground version release to finish how-to &
    getting started sections

Milos (@zivkovicmilos)

What did I work on last week?

What will I focus on this week?

  • DevOps hiring
  • Meeting the Onbloc team
  • Faucet Hub launch 🤞
  • Finalizing parts of go-tendermint
  • test4 testnet planning with the team

Do I have any blockers?

  • Waiting on legal to approve a Faucet Hub reCaptcha conundrum

Petar

What did I work on last week?

  • go-tendermint lib, resolve gno language design issues (shadowing, generics, closures)

What will I focus on this week?

  • same

Do I have any blockers?

  • no

Ray (@piux2)

What did I work on last week?

  • Finished the standardized OpCode benchmarking contract
  • Updated benchmarking tool
  • Completed the go dev profile and hiring plan review

What will I focus on this week?

  • Prepare the workshop
  • Code review

Do I have any blockers?

  • No

Michelle

What did I work on last week?

  • Presentation with Morgan on GoR
  • Gno.me presentation (educational and tutorial platform)
  • Working with Golang Paris to build a calendar of expert content (Marc, Manfred, Guilhem) from Go Generics to Gno.land (blockhcainless)

What will I focus on this week?

  • Teritori grant Start using this repo #3 review
  • Gnokey grant review
  • DecentraHub grant review
  • Compiling necessary info for the user beta program
  • Gno Core weekly agenda
  • Gno.me proposal on GitHub for feedback and DAO review
  • Helping with any final bits of Go to Gno Korea
  • Gno Unity SDK review with Jae and Varmeta
  • Joeson review with Jae and Greps

Do I have any blockers?

  • No, just time

Marc (@mvertes)

What did I work on last week?

  • parscan, gnovm PR reviews (#1750)

What will I focus on this week?

  • gnovm PRs
  • parscan

Do I have any blockers?

  • no

Kristov (@kristovatlas)

What did I work on last week?

  • (Mostly AtomOne/other token stuff)
  • gnokey auditing (ongoing)
  • working on plan for for securing code merges and binary releases, starting with atomone => gno in future

What will I focus on this week?

  • wrap up overflow review
  • wrap up gnokey auditing?
  • (OOO Thursday)

Do I have any blockers?

  • no

Callouts

  1. @zivkovicmilos: Tomorrow's mini test4 planning call
  2. @zivkovicmilos: Belgrade retreat - please start booking flights
  3. @thehowl, @MariMichelle22: What's the latest state on GoR?
  4. @gfanton: do you think it's worth making a demo on JSON MsgCall for wednesday Developer Calls
  5. @thehowl: quick q: can we merge #1700?

@zivkovicmilos
Copy link
Member

25th March 2024 - weekly worldwide sync

Milos (@zivkovicmilos)

What did I work on last week?

What will I focus on this week?

  • Defining an initial issue / PR plan for test4, so the team can start working on it / take up issues
  • Work in-person with the Onbloc team to crunch down on long-standing efforts and blockers
  • Resolve the discussions on gnoland secrets I've had internally with @thehowl

Do I have any blockers?

  • Going through our PR backlog gave me chills

Leon (@leohhhn)

What did I work on last week?

  • Brushing up Memeland p/r, fixing issues
  • Implementing docs PR feedback
  • Meeting with & helping SCP students
  • Go to Gno prep - Presentation & challenge
  • Back & forth with Tokyo venue for contract & payment

What will I focus on this week?

  • Organize devrel tasks, clear up DevRel project board
  • Add Gnoclient reference to Docs
  • Record a Memeland video/write up a tutorial based on Go to Gno challenge
  • DevPod integration
  • Fixing up GRC721 package
  • Gnodev Getting started PR
  • Testnets docs PR

Do I have any blockers?

  • No

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Parscan: research for a proposal to implement memory states bigger than actual available memory.
  • PR review.

Do I have any blockers?

  • no

Marc (@mvertes)

What did I work on last week?

  • parscan: implemented imports and initial support of 'fmt'.
  • preliminary study of a Go Object Notation to serialize memory objects in a source form (as pure Go declarations), so the parser can be the interpreter, and why it would be better than protobufs, json, gobs, etc.
  • study of how to better isolate the VM from the storage.

What will I focus on this week?

  • GnoVM: see if I can help on for + closure issue, from my experience on other interpreters.
  • hackerspace issue on GON
  • PR reviews

Do I have any blockers?

  • no

Guilhem (@gfanton)

What did I work on last week?

  • Mainly working on JSON Argument handling in MsgCall:
    • add support for array & struct in MsgCall
    • fix unexported field
    • add test for convert method
    • prepare demo
  • Coninue improving gnodev logging system
  • Interview Task Review

What will I focus on this week?

  • Gnodev Blog (again didn't work on it last week)
  • Continue on improving error handling

Do I have any blockers?

  • JSON arguments in MsgCall:
    • Need to find a solution for recursive nested struct for json marshal/unmarshal as it break before reaching json marshal in Go2GnoValue with a beautiful stack overflow.
    • is that ok to not use amino? as it is not possible to marshal unregistered type

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Morgan (@thehowl)

What did I work on last week?

What will I focus on this week?

  • GoR call; discussed next steps, will likely start figuring out scoring system.
  • Want to clear out my PR review backlog.
  • Gno doc web
  • Figure out travel to Gophercon US

Do I have any blockers?

  • ...

Ray (@piux2)

What did I work on last week?

  • finished store benchmarking
  • clean up benchmarking tool
  • prepare workshop
  • code review

What will I focus on this week?

  • have the work shop on benchmarking
  • code review

Do I have any blockers?

  • no

Kristov (@kristovatlas)

What did I work on last week?

  • (Mostly AtomOne/other token stuff)
  • gnokey auditing (ongoing)
  • overflow review (90% complete)
  • PR reviews
  • experimentation with gosec

What will I focus on this week?

  • wrap up overflow review
  • gnokey auditing
  • PR reviews
  • (OOO Thursday - Monday)

Do I have any blockers?

  • no

Callouts

  1. @zivkovicmilos: @deelawn, can you expand on locked / unlocked accounts?
  2. @zivkovicmilos: @deelawn, what kind of input do you need on the metrics PR, in terms of Grafana issues?
  3. @zivkovicmilos: @kristovatlas, what is the scope of the gnokey audit? Is there any timeframe?
  4. @thehowl: @zivkovicmilos, how's Seoul (and the workshop?) :)

@Kouteki
Copy link

Kouteki commented Apr 2, 2024

April 3, 2024 - Weekly Worldwide Sync

Lower attendance due to the Catholic Easter.

Milos (@zivkovicmilos)

What did I work on last week?

  • Worked in person with the Onbloc team, unblocked a lot of their efforts
  • Attended BUIDL Asia, and got convinced we saved a large amount of money (and time) by not sponsoring this year
  • Added and consolidated parts of the test4 milestone. Synced with @Kouteki on tackling this with the team starting from this week
  • Updated and got caught up on old PRs. I was honestly disturbed at how simple changes were waiting for months in the pipeline :(

What will I focus on this week?

  • Lots of reviewing for now unblocked PRs
  • Defining more detailed test4 issues, scope, making the team challenge the milestone / scope of work. Ultimately, this is our testnet release, so we should commit to the scope together. I will make sure everyone in the team has a larger chunk of the work to own, and maintain, so there is skin in the game
  • Give the JS (gno-js / tm2-js) clients some love (revised testing framework, improved release flow)
  • Wrap up the final boss battle with our gno JSON-RPC clients

Do I have any blockers?

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Organize my OKR tasks to continue pushing forward.
  • Continue writting a blog post talking about performance improvements applied to the indexer.
  • DecentraHub follow-up.
  • Development of a Gnolang Interpreter for the Terminal (Non-Blockchain) issue follow-up.

Do I have any blockers?

  • no

Leon Hudak (@leohhhn)

What did I work on last week?

  • Cleaning up DevRel board
  • Adding Gnoclient reference & how-to guide
  • Finalizing Gno Tokyo contract with venue
  • Update from Zero to Gno.land Hero
  • Minor docs updates/fixes

What will I focus on this week?

Do I have any blockers?

  • Nope

Ray (@piux2)

What did I work on last week?

  • prepare the profiling data and presentation
  • review code

What will I focus on this week?

  • complete PRs
  • review code

Do I have any blockers?

  • ...

Petar (@petar-dambovaliev)

What did I work on last week?

  • gnovm global declarations initialization

What will I focus on this week?

  • testnet4 issues

Do I have any blockers?

  • no

Callouts

None

Action Items

None

@Kouteki
Copy link

Kouteki commented Apr 12, 2024

April 10, 2024

Individual Updates

Petar

What did I work on last week?

  • following up on testnet4 VM issues, merging old PRs, reviews

What will I focus on this week?

  • same

Do I have any blockers?

  • no

Hariom (@harry-hov)

What did I work on last week?

  • Prepared documents and application for Serbian Visa
  • Travelled to Serbian Embassy

What will I focus on this week?

  • Continue working on existing efforts (mostly #1813, #1631, #922)
  • Catch up and review new/existing PRs

Sorry for not being active for last couple of weeks. The visa process was quite time and energy draining.

Do I have any blockers?

  • No

Leon Hudak (@leohhhn)

What did I work on last week?

What will I focus on this week?

  • Gno-by-example
    • Go through current tutorials, see if any changes needed
    • Suggest & implement new ones
  • Implement feedback for Learn X in Y PR
  • Work on GRC721 refactor
  • Gno Tokyo final points
  • Implement block & transaction fetching for Gnoclient
  • Add Gnodev to Getting started section in docs

Do I have any blockers?

  • No

Antonio (@ajnavarro)

What did I work on last week?

  • Decentrahub Managing
  • Preparing Gno interpreter meeting
  • tx-indexer PR review
  • General PR review
  • tx-indexer blog post (a lot of interruptions, so not a lot of work done here)

What will I focus on this week?

  • tx-indexer: final touches.
  • start having a look into how to substract GnoVM from all surrounding code.

Do I have any blockers?

  • Do we live in a simulation?
  • Is reality a controlled hallucination?

Guilhem (@gfanton)

What did I work on last week?

  • Cleanup the MsgCall JSON PR
    • unfortunatly the PR has been put on hold until we implement amino (Un)/Marshaler
  • Started working a simple realm (OKR Target)
    • try to add image and compress package to gno stdlib.
    • blocked by the addition of the compress package, which is waaay to slow for gno
    • will implement Bitmap package as it should be enough for my realm
  • Berty's gnokey review

What will I focus on this week?

  • Will start investing amino to see how much works need to be done to implement marshaler.
  • gnodev features:
    • genesis file flag
    • balance file flag

Do I have any blockers?

  • How much time/effort should I put on amino marhsal ?

Marc (@mvertes)

What did I work on last week?

  • gnoVM debugger gno#1563 (addressed review feedback)
  • parscan: literal composites

What will I focus on this week?

  • gnoVM: improve test coverage in gnovm/pkg/gnolang
  • gnoVM: more investigations on variable definition issues
  • parscan: slices and maps

Do I have any blockers?

  • no

Milos (@zivkovicmilos)

What did I work on last week?

  • DevOps interviews - so far we have promising candidates. All of them are at the task stage right now
  • Reviewed pending PRs, updated my personal dangling PRs
    • Currently all of them waiting for a review, apart from #1498 (see below)
  • Created new relevant test4 issues so the team can be assigned

What will I focus on this week?

Do I have any blockers?

  • No blockers at the moment

Ray (@piux2)

What did I work on last week?

What will I focus on this week?

  • PR review
  • Review test4 list
  • Multi nodes deploymet

Do I have any blockers?

  • No

Kristov (@kristovatlas)

What did I work on last week?

  • gnokey auditing (ongoing)
  • AIB Bug Bounty program - first draft complete, under review internally

What will I focus on this week?

  • gnokey auditing
  • libtm auditing: We will be groking the Tendermint consensus whitepaper and reviewing code compliance. This will likely take weeks to complete in the background of other (currently mostly AtomOne) tasks
  • Gathering information to decide between Bug Bounty Platforms (currently: HackerOne, HackenProof, Immunefi)

Do I have any blockers?

  • None

Dylan (@deelawn)

What did I work on last week?

  • was on vacation
  • created this PR at the end of the previous week in draft mode -- attempts to formalize (including some code changes) ideas around realm pointer ownership

What will I focus on this week?

  • catch up on all messages, emails, PRs to review, etc
  • begin work on making gno accounts locked by default and unlockable after some action is taken

Do I have any blockers?

  • not yet; I need to check some things

Michelle

What did I work on last week?

  • Worked with Morgan on Game of Realms challenge identification and historical scoring

What will I focus on this week?

  • Creating a draft of a ReadMe to include the new proposal for challenges and bounties
  • Making a list of current proposals that could be built out to help potential contributors

Do I have any blockers?

  • No

Callouts

  1. @zivkovicmilos: @deelawn: Did we fix the metrics PR? What's the status on that?
  2. @zivkovicmilos: Please check out the test4 board, and see what efforts you'd like to take up

    @moul l -> let's clarify the name of this board, please :) Or its role.

    I propose: named test4 and owned by Nemanja while having an inbox column; so that people can suggest but only TPM can decide if it's test4 or not
    Or: named "core team" where the core team can manage everything with individual styles

    I think we need to challenge the cards in this board, such as versioning, maybe we can make a workshop so we can expose the current state and initiatives and list what are the needs to be tackled.

@Kouteki
Copy link

Kouteki commented Apr 16, 2024

April 15, 2024

Individual Updates

Nemanja (@Kouteki)

What did I work on last week?

What will I focus on this week?

  • The More You Gno article
  • PR triage improvements with Morgan

Do I have any blockers?

None

Antonio (@ajnavarro)

What did I work on last week?

  • Pull request reviews
  • Improve release process on our satellite projects, making it easier to create a new version and supporting most important archs when using docker.
  • Fixing blocking bugs on Gno.
  • Helping with tx-indexer reviews and guidance for awesome contributions.

What will I focus on this week?

  • Versioning or VM substraction, whatever is more important.

Do I have any blockers?

  • Difficult to focus on something, too many things to do.

Hariom (@harry-hov)

What did I work on last week?

  • PR Reviews
  • Opened some minor PRs
  • Worked on my existing PRs

What will I focus on this week?

  • PR reviews
  • Versioning PR

Do I have any blockers?

  • No

Marc (@mvertes)

What did I work on last week?

  • finished #1563, will merge it if no objection
  • started to work on test coverage for pkg/gnolang

What will I focus on this week?

  • PRs, test coverage in GnoVM

Do I have any blockers?

  • no

Guilhem (@gfanton)

What did I work on last week?

  • interview and task review
  • cleaup supernova repo
  • Add arm64 docker image to gnoland repo:
    • gno docker image should run on apple silicon now 🎉
  • worked on gnodev feedback:
    • add keybase and balances support:
      • Load realm with specific creator using query like path gnodev ./myrealm?creator=francois
      • Load balance from a balances file
      • Load keybase from home folder (by default)
      • Add a flag to include a temporary user
      • Most of this options support bech32 addresses or name resolved from the user's keybase
      • All options should be composable
  • Slowly investigate amino for json (un)/marshal

What will I focus on this week?

  • Add tx file support gnodev
    • with balances file and tx file support, gnodev should support most of the common cases now 👍
  • I think I will then full focus on amino (un)/marshal

Do I have any blockers?

  • not yet

Leon Hudak (@leohhhn)

What did I work on last week?

What will I focus on this week?

  • Work on GBE
  • Finish PRs:
  • Report/mini blog post for Intro to Gno Tokyo
  • 1 day off to pack and finish up stuff in the city
  • Fly back home from Japan 😢

Do I have any blockers?

Morgan (@thehowl)

What did I work on last week?

  • Traveled back to Italy last monday :)
  • Catching up with conversations and progress being made over the past few weeks.
    • Game of Realms
    • Gophercon challenge series
    • On-Chain data moderation discussion
  • Review gno type check #1426 -- I'm making an in-depth review and also doing some pair reviewing with Maxwell.
  • Booked flights for Gophercon US and retreat.

What will I focus on this week?

  • Core work
  • Game of Realms
    • sync with finance, legal, jae+manfred; hopefully have the prize pool distribution structure done by EOW.
  • GC Challenge Series
    • Awaiting feedback from co-organizers
  • meta / processes
    • look through @Kouteki's documents and proposed improvements

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • Challenge series
    • move items to shared trello board for the gophercon challenge series
    • add new challenge ideas
  • Try a new solution to #1326
  • Continue reviewing things
  • Make an issue for #1927 to better explain the issue

Do I have any blockers?

  • no

Kristov (@kristovatlas)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

No

Milos (@zivkovicmilos)

What did I work on last week?

  • Had a few DevOps hiring calls and task reviews — thank you to Guilhem and Antonio for being a critical part of this role search
  • Focused on finally closing up the JSON-RPC client refactor. My initial approach was to simply tweak and minimize the code changes, until I realized it was basically impossible to add the functionality we needed without changing the architecture of the rpc client and client libraries in TM2. The result:
    • Much cleaner RPC client API (goodbye useless “/websocket” param)
    • Ability to create a WS client
    • Ability to send batches over WS / HTTP
    • RPC client code that now has ~100% coverage
  • Reviewed ongoing grantee progress (Zentastic, Berty, Onbloc), with the focus of unblocking them for finalizing their milestones
  • Regular housekeeping with PR reviews / issue discussions

What will I focus on this week?

  • Finishing up dangling PRs, so I can focus on the chain init flow issues

Do I have any blockers?

  • No blockers so far

Ray (@piux2)

What did I work on last week?

What will I focus on this week?

  • review indivisual PR on test4
  • deploy multi nodes in public network

Do I have any blockers?

  • no

Petar

What did I work on last week?

  • PR reviews, draft implementation for generics support

What will I focus on this week?

  • same same

Do I have any blockers?

  • no

maxwell (@ltzmaxwell)

What did I work on the last 2 weeks?

  • Completed the onboarding process and acquired a foundational understanding of the entire system.
  • PRs:
    • Successfully merged PR #1601 and #1733;
    • Conducted a refactor on PR #1426, which is currently under discussion with Morgan and Dylan;
    • Initiated a Proof of Concept (PoC) for loop externs in PR #1818.
  • Review: Actively reviewing PR #1689, planning with more reviews.

Callouts

  1. @harry-hov: can we fork jaekwon/testify to gnolang/testify?
    • @thehowl: my take is we should fork the original stretchr repository. this will avoid having both the fork and the original as dependencies (confusing automatic go import)
    • @harry-hov: Makes sense. Or we can transfer the repository. I wonder why actual/expected are flipped in jaekwon/testify.
    • Conclusion: we stick with stretchr as the option with the least overhead
  2. @thehowl: what should we do for VM cycles? (ref: this slack convo, revert PR by antonio)
    • Conclusion: revert. We can't allow nodes running with different limit, and smart contracts failing on one node, and being successful on another.

Action Items

  1. The Gno Core weekly agenda ready to go for all our updates!

@Kouteki
Copy link

Kouteki commented Apr 23, 2024

April 22, 2024

Individual Updates

Antonio (@ajnavarro)

What did I work on last week?

  • Mainly PR reviews (3 days week for me due to a force majeure)
  • Start tackling versioning issue. It is huge, deciding from where to start.

What will I focus on this week?

  • Versioning issue.

Do I have any blockers?

  • no

Guilhem (@gfanton)

What did I work on last week?

  • Mostly fixing, clenaing & improving previous PR
    • gnodev keybase: cleaning up & linting
    • gnodev tests: cleaning up & linting
  • Investigating amino marshal on TypedValue, and ended with:
    • Will Use already implemented AminoMarshaler: (Un)MarshalAmino (similar to MarshalJSON but for amino)
    • Will implement (Un)MarshalAmino on TypedValue (and probably on some Value implem when it make sense)
    • I will probably end up taking a lot of logic from Go2Gno and Gno2Go functions.
    • Still need to figure out the best way to pass Allocator and Store

What will I focus on this week?

  • Mostly focus on implementing MarshalAmino on TypedValue

Do I have any blockers?

  • If some peoples can confirm that im on the right path for implementing TypedValue marhshaling

Nemanja (@Kouteki)

What did I work on last week?

  • Introduced weekly Triage grooming
  • Put together a list of dependencies from the Intrastructure team

What will I focus on this week?

  • Learn Go
  • Update and publish The More You Gno 8
  • Write the Testnet4 explainer article
  • Get delivery dates for all the Infrastructure tasks we submitted to LaLi's team
  • PR triage process

Do I have any blockers?

  • Nope

Morgan (@thehowl)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • ...

Marc (@mvertes)

What did I work on last week?

  • PR #1563 (gno debugger)
  • gnovm test coverage

What will I focus on this week?

  • finalizing #1563: adressing one issue from Morgan and one from Hariom
  • gnovm tests
  • parscan if time allows

Do I have any blockers?

  • no

Petar

What did I work on last week?

  • PR reviews, monomorphization for generics

What will I focus on this week?

  • same, hope to have a reviewable PR soon

Do I have any blockers?

  • no

Leon Hudak (@leohhhn)

What did I work on last week?

What will I focus on this week?

  • GBE:
    • Had a call with Aidar & Alexis to discuss designs & organization of the website
    • Push out new section & tutorials
  • Finish small demo realm & Getting started revamp
  • Work on GRC721 by spec (opened up a larger scope of work than expected - testing is going to be fun)

Do I have any blockers?

Milos(@zivkovicmilos)

What did I work on last week?

What will I focus on this week?

  • Answering any questions on pending PRs, resolving comments
  • Taking up more work for the node directory changes for test4
  • Taking up parallel work for some test4 tasks
  • Reviewing pending PRs by the core team

Do I have any blockers?

  • No blockers

Hariom (@harry-hov)

What did I work on last week?

  • Rethinking versioning after comments from Milos and Ray
  • Played around with Marc's debugger PR. Found some bugs.
  • Read VSCode API docs for debugger integration.
  • PR Reviews

What will I focus on this week?

  • PR reviews
  • Will apply major changes on Versioning PR
  • Check Test4 board for some priority tasks to work in parallel.

Do I have any blockers?

  • No

Ray (@piux2)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • No

Kristov (@kristovatlas)

What did I work on last week?

What will I focus on this week?

  • Troubleshoot CodeQL errors
  • bug bounty program development
  • Review Adena wallet security fixes

Do I have any blockers?

No

Dylan (@deelawn)

What did I work on last week?

  • Working on a solution for #1326
  • Reviewed #1653
  • Added challenges for challenge series
  • Reviewed #1246

What will I focus on this week?

  • Continue work on #1326
  • Rework solution for #1861
  • Continue PR review
  • More work for challenge series

Do I have any blockers?

  • no

Maxwell (@ltzmaxwell)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • no

Callouts

  1. @leohhhn: Should we add a way to fetch genesis TX from the node? Issue/PR (indexing Portal Loop)
  2. @leohhhn: Where should we point Berty & other developers when talking about storing images/large data on-chain?
  3. @zivkovicmilos: A question primarily for @jaekwon: how do we see transaction simulation happening, if we want to utilize this kind of functionality for estimating gas for transactions? Do we still want to rely on the Antehandler / ABCI Query simulation, or use something different? The problem with ABCI Query simulation is that the user needs to sign the transaction before "simulating" them, and specify a gas price / gas limit

Action Items

  1. Guilhem to open a PR on implementing TypedValue marhshaling
  2. Leon to get back to Berty & others that posts can be on chain (unless there are too many users). Using Reddit as an example, we can split subreddits as shards. Images should be off-chain.
  3. Miloš to look into how Cosmos handles transaction simulations, and come up with a proposal. Jae is generally OK with the Ethereum approach, if we don't propose something better.

@Kouteki
Copy link

Kouteki commented May 6, 2024

April 29, 2024

Individual Updates

Antonio (@ajnavarro)

What did I work on last week?

  • After dedicating a good amount of hours to try to add /v1 prefix to our API, I gave up. I think we should have in mind versioning for our next protocol iteration, not this one. Trying to add anything there will be incomplete and unnecesary if following protocols have versions on them.

What will I focus on this week?

  • Improve state of our CI on gno repo
  • Improve state of releases on gno repo
  • Improve state of modules on gno repo

Do I have any blockers?

  • no

Guilhem (@gfanton)

What did I work on last week?

  • Gnodev:
    • Fix and merge gnodev keybase load
    • Fix and merge gnodev testing/lint base
    • Start implementing TX save/export/load
  • Digged a little bit more into amino for marshaling
    • I need a way to have custom type representation (TypeInfo) for amino
      • The main idea I have for now for this is to have a type that can self-describe itself by implementing a AminoTypeInfo method

What will I focus on this week?

  • Dig more into amino
    • I need to create an issue to keep track of this.
  • Finish TX loading into gnodev

Do I have any blockers?

  • no, but if anyone want to help implementing this amino marshaler, you are more than welcome :D

Dylan (@deelawn)

What did I work on last week?

  • Came up with solution to #1326 in PR #1919.
  • Reviewed #1949
  • Drafted more challenges for gophercon challenge series
  • Brainstormed gophercon workshop ideas with Leon
  • Worked on adding unit tests for gnorkle packages
  • Made changes and debugging for PR #1861 -- trouble diagnosing unexpected failing tests

What will I focus on this week?

  • Make transaction index change for #1777
  • Finalize challenge series drafts and request review from the organizers
  • Choose a gophercon workshop topic
  • Finish gnorkle tests, fix CI, get approval, and merge
  • Finish reviewing gno type check PR
  • Continue debugging #1861

Do I have any blockers?

  • TBD

Marc (@mvertes)

What did I work on last week?

What will I focus on this week?

  • gnovm/pkg/gnolang test coverage
  • pr reviews

Do I have any blockers?

  • no

Hariom (@harry-hov)

What did I work on last week?

What will I focus on this week?

  • Continue working on feat: implement genesis packages command suite #1988
    • genesis packages list
    • genesis packages get
    • genesis packages del
    • Write Tests and Docs
  • Continue efforts on forbid importing '/r' from '/p' #1393
  • Continue feat(gnolang): increase test coverage from 33% to 70% #1995
  • Continue gno test support external pkgs #682
  • Fix issue [GnoVM] Reset machine context after each Test function #1982
  • PR Reviews

Do I have any blockers?

  • No

Maxwell (@ltzmaxwell)

What did I work on last week?

  • Request review on #1426, waiting for review.
  • Finalize PR #1818, waiting for review.
  • Review PR #1919
  • Review PR #1989, ing.
  • Review PR #1653, ing.
  • Basic exploration on #1974.
  • Discussion on #1966

What will I focus on this week?

  • complete onging review;
  • review #1568;
  • push forward review work on [#1426] and [#1818];
  • have a look on #974;
  • have a look on #1463;
  • Reawaken #1775, #1890，denpends on the status of #1426.

Do I have any blockers?

Milos (@zivkovicmilos)

What did I work on last week?

  • Resolved pending PRs, attended to team PRs
  • Synced with Albert and Ops on immediate Gno infra needs
    • We started dishing out documentation and procedures for incident responses and resource upkeep
  • Pushed out a fix for gnokey sign, PR merged
  • Coordinated the Faucet Hub release -- going live tomorrow 🎉
  • Opened up a PR for gnoland init, PR out
  • Merged PRs for the gnokey cleanup + RPC cleanup, resolved with the team any breaking changes so we're running smoothly

What will I focus on this week?

  • OOO for most of the week (reachable via Signal, always)
  • Work on updating the gnoland init PR with detailed setup docs, as requested on the PR
  • Work on adding gas estimations

Do I have any blockers?

  • No blockers, only challenges :)

Ray (@piux2)

What did I work on last week?

  • merged PR #1340
  • analyzed the root cause issue #1326
  • drafted and brainstormed with dylan on the group review process.

What will I focus on this week?

  • continue on PR #1326
  • finished group review process for broader discussion
  • interviews and profiles review.

Do I have any blockers?

  • No

Leon (@leohhhn)

What did I work on last week?

  • Fixed up & submitted Learn X in Y tutorial PR
  • Held office hours
  • Worked on pushing out the Faucet Hub - repo README, a couple of chores
  • Merged math/overflow, r/demo/Userbook example realm, gnoclient supports fetching blocks now
  • Opened up 7 issues
  • Merged GBE sections PR - feat: add support for section directories gno-by-example#162
  • Reviewed PRs from students & partners

What will I focus on this week?

  • Wrap up docs for Gnoclient PR > today
  • Finish gnodev gs refactor - unblocked 25.4 > today
  • Research Belgrade Go & Web3 meetup > today
  • Push out GBE tutorials - unblocked 25.4. > tomorrow
  • Record Memeland tutorial - unblocked 25.4 > tomorrow
  • Review DAO SDK > tomorrow
  • Review GRC721 Metadata PR > tomorrow
  • Review #1983 student PR > tomorrow

Do I have any blockers?

  • Nothing specific right now

Callouts

  1. @leohhhn: everyone, please give some thought to this message 🙏
  2. @leohhhn: Jae, on the topic of Memeland - would you be fine with the limiting the users who can post to only users registered in r/demo/users, which is invite-only?
  3. Learn X in Y tutorial - our PR for this platform has been closed because "we are promoting cryptocurrency and cryptocurrency is a scam" - they didn't even read the tutorial - it's purely how to develop apps with Gno

Action Items

  1. @deelawn and @leohhhn would like some help coming up with a good workshop topic for Gophercon US. There are some ideas here. Please drop a comment or add an idea of your own.
  2. @gfanton and @ajnavarro want to improve by a lot the state of our CI (versioning, modules, docker image generations, use of goreleaser and so on). First step is use one go.mod for everything, including contribs. We did some research and on most PRs we are modifying 2 or more modules, so right now it makes sense to have only one go.mod on the repo. That will allow us to refactor all our github action scripts to be more understandable and easier to maintain.
  3. @zmilos to help Guilhem with the amino marshaler

@Kouteki
Copy link

Kouteki commented May 7, 2024

May 6, 2024

Individual Updates

Hariom (@harry-hov)

What did I work on last week?

  • PRs Ready for Review:
    • feat!: forbid importing '/r' from '/p' #1393
    • feat: implement genesis packages command suite #1988
    • refactor!: split r/demo/boards #1989
  • Helped Denis(devx) with gno mod commands and discussed about future of gno-ide, gnopls, and gno.mod!
  • WIP -> feat: gno test support external pkgs #682

What will I focus on this week?

  • Complete feat: gno test support external pkgs #682
  • Fix issue [GnoVM] Reset machine context after each Test function #1982
  • I will be out of office for most of this week and next week!

Guilhem (@gfanton)

What did I work on last week

  • Fix: some race that can happen in gnodev/emitter
  • NewPR: Added vhs tape file to generate gif for the doc:
    • It should enable us to generate constent and up to date gif/screenshot for the doc
  • DevOps Interview
  • Regarding Amino TypedValue Marshaling, I have a working PoC:
    • Currently, the PoC uses the gonative method (Go2Gno & Gno2Go).
    • I have added the TypeDesc() implementation for Amino.
      • If a type implements this method, it will check HasTypeDescription inside InterfaceInfo upon package registration.
    • During Unmarshaling (for ex.), it will:
        1. Obtain the Go native reflect.Type through the TypeDesc method (Gno2GoType).
        1. Populate a reflect.Value using the aminoDecodeJsonXXX method (Amino unmarshal).
        1. Ultimately, it will utilize the custom UnmarshalAmino to populate our TypedValue (Go2GnoValue).
    • This could be optimized, but it's the most straightforward way I've found for now.
    • Added resursive protection by ptraddr

What will I focus on this week?

  • If my PoC is good, I will focus on opening a PR:
    • Add some tests to amino/tm2
    • Rework and Improve API to use this
  • gnodev(tx): Finish TX file loading

Do I have any blockers?

Marc (@mvertes)

What did I work on last week?

  • debugger #1563. Address more feedbacks.
  • some HR stuff for future hires
  • gnovm test coverage

What will I focus on this week?

  • gnovm test coverage
  • finalize #1563
  • more HR stuff (prepare interviews, ...)
  • sone experiments about multi-VM (driving multiple VMs with 1 interpreter)

Do I have any blockers?

  • no

Morgan (@thehowl)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • ...

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • no

Maxwell (ltzmaxwell)

What did I work on last week?

  • Start work on #2008
  • review PR #1989
  • review PR #2035
  • Discussion on issues with #1426, Thanks Dylan.
  • Explore PR #1776, initial thoughts.
  • New issue #2041.

What will I focus on this week?

  • Finalize #1426 with reviewers.
  • Some more dig on realm related PR/issues.

Do I have any blockers?

  • No.

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • Finish reviewing Maxwell's PR
  • Finish adding gnorkle tests and merge
  • Work on solidifying the workshop topic
  • Some other VM issues that require work / review

Do I have any blockers?

  • no

Kristov (@kristovatlas)

What did I work on last week?

  • bug bounty program development: AiB now running program on HackenProof, will add Gno later this year
  • Reviewed Adena wallet security fixes: report is finalized

What will I focus on this week?

Do I have any blockers?

No

Callouts

  1. @ajnavarro: I noticed that we are not running all tests on Gno Repo. If someone could have a look about what is failing would be great. Thanks!:

    @harry-hov: I can take a look

  2. @ajnavarro: I added to the CI running tests with -race enabled and I had to deactivate it :(. We have ton of race conditions on all of our modules. Would be great too if someone could have a look at it.
    (marc: I can look at it, did already similar work on gnovm/pkg/gnolang)

  3. @harry-hov: Make gnopls official? (https://github.com/harry-hov/gnopls).

  4. @gfanton: Get someone from the team to validate that the Amino marshalling POC is on the right path. Manfred's comment: Maybe you can add unit tests now; that can confirm that the implementation works and then that can be used if you need to change the implementation. More :)

Action Items

  1. @harry-hov to initiate the gnopls move to the gno repo, and we can review and approve. Manfred is generally fine with this.

@Kouteki
Copy link

Kouteki commented May 16, 2024

May 13, 2024

Individual Updates

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • Add goreleaser to gno repo.
  • Find some time to add more tests to tx-indexer filters.
  • Prepare for traveling.

Do I have any blockers?

Individual Updates

Marc (@mvertes)

What did I work on last week?

  • #1563: fixed printing extern package values, panic if wrong print expression, lookup in if bodies, extensive tests (> 96% coverage), plus PR review feedbacks.
  • Lots of HR candidates review

What will I focus on this week?

  • gnovm test coverage (PR in progress)
  • improving parallel tests
  • local interpreter mode: looking at isolating interpreter part.

Do I have any blockers?

  • ...

Maxwell (@ltzmaxwell)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • no

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

  • Preparing workshop/presentation
    • Code
    • Slides
  • Work with Ray to finish moving benchmarking code into master
  • Review PRs

Do I have any blockers?

  • no

Guilhem (@gfanton)

What did I work on last week?

  • Mostly OOO
  • Worked on amino + Marshal Value
  • BFT fixes with Jae, just need approval, I will bring this to the review meeting

What will I focus on this week?

  • Continue Amino + TypedValue
  • Gnoland Namespace

Do I have any blockers?

  • no

Milos (@zivkovicmilos)

What did I work on last week?

  • Aligned with @moul on gnoland init, and how we should tackle it
    • We decided the best way forward is to not have syntax sugar like gnoland init, but to make our existing flows more documented and robust
  • Opened up a PR that gives our telemetry stack anabolic steroids
    • Current status: in draft because of adding gnoland and supernova Docker support, so you don't need to manually create and connect everything, it should just automatically work when you run docker compose up :)

What will I focus on this week?

  • Wrapping up #2059
  • Focusing with @ajnavarro and @gfanton on launching our test4 devnet (final prep)
  • Taking new test4 efforts

Do I have any blockers?

  • I can't wait for @ajnavarro to gift us with a better CI + Docker support

Ray (@piux2)

What did I work on last week?

  • Interview
  • Review code
  • Getting bottom of #1919 and finding alternative fixes.

What will I focus on this week?

  • Review Code
  • OKR items
  • Interviews

Do I have any blockers?

  • no

Petar(Петър)

What did I work on last week?

  • 2 initialization issues of globals. Since the graph solution was not desirable and was reverted, i fixed without a graph.

What will I focus on this week?

  • More VM issues

Do I have any blockers?

  • ...

Leon Hudak (@leohhhn)

What did I work on last week?

  • Recording Memeland video series
  • Gno By Example:
    • Updated generation of tutorials
    • Proposal for content, asked for feedback, implementation of the proposal - content ready for review, but it will look janky if we do not fix UI issues before merging
    • Opened issues for the UI
    • Styling & formatting for GBE · Issue #158 · gnolang/gno-by-example
    • Titles not escaped properly break generation · Issue #166 · gnolang/gno-by-example
    • Markdown not properly rendered · Issue #169 · gnolang/gno-by-example
    • Code blocks not escaped properly during tutorial generation · Issue #168 · gnolang/gno-by-example
    • Organized sync(s) with Aidar & Alexis on the frontend
    • Discussed new design & implementation (22nd April)
    • Synced with Alexis on how we can move forward (7th May)
  • Finished up GRC721 by spec refactor
  • Opened up tons of issues on monorepo and other repos, mainly GBE
  • Coordination for Golang Serbia meetup
  • Coordination for possible ETH Belgrade sideevent
  • Docs for Emit/event
  • Reviewed PRs from partners
  • & other housekeeping

What will I focus on this week?

Do I have any blockers?

  • docs ci :c wen gno devops

Kristov (@kristovatlas)

What did I work on last week?

  • Go analysis tools (CodeQl, SemGrep, Snyk, gosec)
  • Review feat(p/demo): PCG pseudo-random number generator gno#1993 PCG pseudo-random number generator (80% done)
  • Working on launching bug bounty on new platform

What will I focus on this week?

  • Complete Review feat(p/demo): PCG pseudo-random number generator gno#1993 PCG pseudo-random number generator
  • More PR review catchup

Do I have any blockers?

  • Waiting on feedback from legal team on new bug bounty platform

Morgan (@thehowl)

What did I work on last week?

What will I focus on this week?

OOO (at a conference) wed-fri.

  • GopherCon Challenge Series
  • test4: drop file paths from genesis.json
  • gnodoc web
  • Bounties
  • Itches
    • Change the debug variable to a build tag.
    • Swap gnolang and gnovm, upon jae's request

Do I have any blockers?

  • ...

Callouts

  1. Content writing OKR deadlines are looming closer. This Notion page lists all the content efforts in progress. Have you volunteered yet? :D
  2. @zivkovicmilos: for @ltzmaxwell: What is the status of the gno type check PR? Maxwell: Morgan and Dylan reviewed them already, need a regression review from @Tyge and @deelawn, or more review perhaps to finalize(this is a PR with break changes). we can merge #1426 first to unlock the following ones that depends on this.

Action Items

None

@Kouteki
Copy link

Kouteki commented May 24, 2024

May 20, 2024

Almost everyone from the Core team is on the Belgrade retreat for the whole week, hence the light update.

Individual Updates

Hariom (@harry-hov)

What did I work on last week?

What will I focus on this week?

  • Working on [GnoVM] bug: inconsistent map key #2060
  • Brainstorming on gno.mod and versioning
  • Blog topic
  • PR Reviews

Do I have any blockers?

Callouts

  1. In a team first, Antonio wrote an article on key/value stores. Mad props!
  2. Our round robin PR allocation experiment is live, and will be kicking for the next 3 weeks. At its end we will do a short retro and determine whether to keep the new allocation algorithm or to go back to the old ways.
  3. We're also kicking off the PR Triage experiment! Our volunteers for the first two weeks are Morgan and Guilhem. The experiment is scheduled to last one full cycle, meaning everyone will participate for two weeks before we sit down and hold a retrospective. Learn more

Action Items

None

@Kouteki
Copy link

Kouteki commented May 30, 2024 •
edited
Loading

May 27, 2024

Individual Updates

Guilhem (@gfanton)

What did I work on last week?

  • Serbia retreat
  • Make some PR review, certainly not enough (sorry Morrgan...)
  • Mostly finish gno fmt, working great:
    • It include gnoimports features
    • Use stdlibs and example folders packages as default
    • Other folder/packages can be easily added with -i (include) flags

What will I focus on this week?

  • Start working on workshop for Nebular
  • Setup back txtar coverage
  • Start looking at GnoSDK

Do I have any blockers?

  • not yet

Antonio (@ajnavarro)

What did I work on last week?

What will I focus on this week?

  • gnora (not final name, but it is easy to write as a command app and it contains gno in its name :)): https://hackmd.io/79ilyTyURAmL-Nas4Jw8lA (Feedback is welcome)
    • Gnora is a PoC for a GnoVM interpreter without any blockchain stuff.

Do I have any blockers?

  • I need to be focused on the Gno Interpreter and PoC (gnora) until everything is on route.

Marc (@mvertes)

What did I work on last week?

  • Serbia retreat
  • some studies on a single multi-node VM

What will I focus on this week?

  • debugger stage 2: break by func, 'next command', dynamic attach
  • improve test coverage #2143
  • PR reviews, in particular #1818

Do I have any blockers?

  • no

Leon (@leohhhn)

What did I work on last week?

  • Retreat
    • Many great discussions
  • Gno @ Golang Serbia meetup - full organization
  • Defining realms discussion
  • Worked on implementing feedback for Coins PR
  • Publishing & coordinating for the Rebranding blog post for Marketing
    • Parsing draft to markdown
    • Fixing blog package with @ajnavarro - Added the remove function, found a bug in the vm - issue coming soon
    • Coordinating a fix on Portal Loop with Albert
  • gnoland getting started tutorial
  • gnokey getting started tutorial
  • Working on Gno @ Golang Serbia recap blog with @michelleellen
  • Usual housekeeping

What will I focus on this week?

Do I have any blockers?

  • I sure hope I don't run into any

Michelle

  • What I will focus on?
    • Proof of Contribution Call to Arms Readme for bounties, grants and GoR
    • Grant contracts and a new Readme for individual contributors

Morgan (@thehowl)

What did I work on for the past two weeks?

  • Serbia!
  • Pull requests created on github:
    • gnolang/gno#2213 - test(gnovm): print unexpected error in filetests
    • gnolang/gno#2201 - feat(gnovm): add importer package
      • Work in progress, but will allow us to have a defined way to match an import path to source files
    • gnolang/gno#2187 - feat(pkg/commands): provide ExitCodeError to use in place of os.Exit
    • gnolang/gno#2173 - refactor(tm2/crypto): do not use build tags to mock ledger
    • gnolang/gno#2168 - fix(gnovm): remove sort from gonative packages
    • gnolang/gno#2164 - feat(stdlibs/std)!: change TestSetPrevRealm to TestSetRealm
    • gnolang/gno#2110 - test(gnovm): re-enable stdlibs tests
    • gnolang/gno#2106 - chore(stdlibs/std): use appropriate variable names for regex
    • gnolang/gno#2105 - fix(gnovm/store): copy store caches
  • Lots of reviews
  • Attempt PR triage last week, didn't manage to do much of it
  • Bounty programme
  • Went to Software you can love
  • Challenge series, GoR

What will I focus on this week?

  • Got a fresh start of the week by fixing test3
  • Focus: Challenge Series
    • Get stuff up and running for the first challenges.
  • Pull request reviews
  • Playing on the side with sogno.
  • Self-assessment.

Do I have any blockers?

Dylan (@deelawn)

What did I work on last week?

  • Prepared the meetup presentation
  • Retreat meetings
  • Discussed gnora with Antonio

What will I focus on this week?

  • Challenge series
  • Review PRs
  • Help with gnora

Do I have any blockers?

  • no

Maxwell (@ltzmaxwell)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • no

Milos (@zivkovicmilos)

What did I work on last week?

  • Mostly occupied with the team retreat
  • Worked on bringing test4 efforts to a close:
    • r/sys/vals
    • valset injection
    • gnoland start overhaul

What will I focus on this week?

  • Finalizing the validator set PRs
  • Trying to help out @ajnavarro with Gnora
  • Attend leftover contributor partner queries and issues

Do I have any blockers?

  • No issues so far :)

Ray (@piux2)

What did I work on last week?

  • Create gas benchmarking tool
  • Interviews
  • Review PR

What will I focus on this week?

  • Finish gas benchmarking tool
  • Interviews
  • Review PR

Do I have any blockers?

  • no

Callouts

  1. Test4 is at 62% completion rate!
  2. We're moving additional manpower to GnoVM in order to deliver a great demo on GopherCon US.
    a. Antonio is driving the effort
    b. Maxwell and Petar are primary developer support
    c. Marc will be working on the debugger
    d. Manfred will both develop and advise
    e. Morgan & Dylan will have an advisory role
  3. Test4 development will continue as planned, but with the GnoVM tradeoff we'll need to move the launch date. We're thinking of July 31, but we'll confirm in the next 1-2 weeks.
    a. Miloš will keep driving the effort
    b. Ray, Guilhem and Hariom are primary development support

@Kouteki
Copy link

Kouteki commented Jun 10, 2024

June 3, 2024

Individual Updates

Nemanja (@Kouteki)

What did I work on last week?

  • Published the Test4 Explained article
  • Opened a PR for the Gno messaging brief. This resource is built for Marketing for events and campaigns.
  • Created a website brief for GopherCon one-pager website.

What will I focus on this week?

  • Gno.land vision document
  • Ensure that the one-pager website is on track for GopherCon

Do I have any blockers?

  • Nope

Kristov (@kristovatlas)

What did I work on last week?

  • Ongoing work on bug bounty program development and Golang security testing tooling

What will I focus on this week?

  • Planning for internal gno audit June 10 - 21

Do I have any blockers?

  • N/A

Morgan (@thehowl)

What did I work on last week?

  • PR Triage, reviewed ~50 PRs
    • The triage went well, I set out in my case more specifically with the intention of trying to merge a lot of low-hanging fruits; in this sense I gave attention also at older PRs which had been lingering for a while.
    • We still merged and reviewed the vast majority of the "incoming PRs"; take a look at this search.
    • My suggestions is that generally GitHub PR search is good enough; I personally used is:pr is:open draft:false as my go-to query, and coordinated with Guilhem on what to review.
    • I provided an end-of-week update on what was created in our PR triage period, which was still unmerged. I think this is useful, especially as most of these will be PRs which we've failed to tackle and could get some help from the wider team in reviewing.
  • Challenge Series
  • GoR discussions
  • Helped to scope out Gnora

What will I focus on this week?

  • Pushing out the GoR bounty program
  • Focus: Challenge series
  • importer PR
  • std renaming PR

Do I have any blockers?

Antonio (@ajnavarro)

What did I work on last week?

  • Mainly gnora, defining final touches:
    • removing gno.mod from the requirements, easier for scripting and less moving parts.
    • Had some discussions about imports and how they should be implemented. Still TBD, didn't find a clear final solution for it.
    • Created all the gnora commands code, now implementing as a library our gno branch living in interp (Thanks Petar and Dylan )

What will I focus on this week?

  • I'll be away most of the week due to some family stuff.

Do I have any blockers?

  • Not work related.

Guilhem (@gfanton)

What did I work on last week?

  • Worked on Nebular Workshop
  • PR Reviews \w Morgan
  • fix bft deadlock that can happend when closing the node
  • Worked on Gnodev TXs handler
    • I find a better way to interact with gnodev, I keep this as a surprise
  • Cleanup gno fmt PR

What will I focus on this week?

  • I will focus more on the Nebular workshop
  • keep going on actual task:
    • Add unit test on gnofmt
    • finish gnodev txs handler branch

Do I have any blockers?

  • nop

Leon (@leohhhn)

What did I work on last week?

  • 3 days OOO
  • Worked on the gnokey tutorial
  • Worked on getting the blogs ready for publishing:
    • Gno Serbia Recap
    • GnoStudio Connect Intro
  • Created the Gno Infrastructure section in the docs by moving unindexed tutorials into it
  • Opened up 3-4 issues, mainly on gnokey
  • Some other small PRs, housekeeping classics

What will I focus on this week?

Do I have any blockers?

  • AVL/GnoVM bug - kind of a blocker for some blog-related stuff, would appreciate a pair of eyes / @mvertesvolunteered to take a look
  • How do you actually use gnokey verify? Posted the question on Signal Tech Staff.

Dylan (@deelawn)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • no

Jae (@jaekwon)

What did I work on last week?

  • DONE: #1919 -> #2255 (HeapItemValue)
  • WIP: improving #1702 to remove second store from getPackage
  • WIP: #1818 (varloops) -> make two/three phase
  • TODO: #2113, #1246

Ray (@piux2)

What did I work on last week?

  • Finished PR 2241, benchmarking tool

What will I focus on this week?

  • Complete the name and unnamed conversion part 3/3
  • take care of changes for PR 2241
  • Interview

Do I have any blockers?

  • No

Maxwell(@ltzmaxwell)

What did I work on last week?

what will I focus on this week.

  • solve Issue of longer import path consume more gas.
  • review PRs.

Do I have any blockers?

  • No

Hariom (@harry-hov)

What did I work on last week?

What will I focus on this week?

  • Investigate on faling gnovm test
  • Continue [GnoVM] bug: inconsistent map key #2060
  • Continue gnopls wasm compatibility
  • Start working on the blog
  • Versioning workshop

Do I have any blockers?

Marc (@mvertes)

What did I work on last week?

  • finished with #2143 and #2222
  • fixed a bug in debugger raised by Jae: #2251

What will I focus on this week?

  • review of candidates for atomone lead (HR)
  • improving debugger (next command, dynamic attach, break in functions)
  • review of #2221 as required, plus

Do I have any blockers?

  • no

Milos (@zivkovicmilos)

What did I work on last week?

  • Valset injection through the Realm (#2229)
  • Recalibrated the r/sys/vals PR based on Manfred's feedback and desired direction
  • Reviewed and discussed with @moul on the current DAO / validator proposal efforts (translated that feedback to the /r/sys/vals PR + #2229)
  • Standard PR reviews, upkeep

What will I focus on this week?

  • Bring the devnet efforts to a close with Albert (be on-call for features he needs pushed through and validated)
  • Bring the remaining test4 valset efforts to a close with @moul

Do I have any blockers?

  • Battling Albert on genesis.json No blockers that are worth mentioning :)

Albert Le Batteux (@albttx)

What did I work on last week?

  • Docker images with alpine + simplified
  • gnoland-devnet-1 (dynamic: 3 nodes)
  • Broke test3 (by restarting the node)

What will I focus on this week?

Do I have any blockers?

Callouts

  1. @ltzmaxwell & @deelawn are the next pair for the PR triage
  2. For the team, we will conduct an internal security audit Weeks 2 & 3 of June, what areas of gno code would you recommend to focus on? What areas should be skipped?

@Kouteki
Copy link

Kouteki commented Jun 12, 2024

June 10, 2024

Individual Updates

Antonio (@ajnavarro)

Focus items from the previous sync

  • I'll be away most of the week due to some family stuff.

What did I work on last week?

  • I was OOO most of the week, but basically integrating the gno interp branch on gnora. Found a couple of problems, but it is going well.

What will I focus on this week?

  • Have all the gnora commands working and implemented.

Do I have any blockers?

  • no

Dylan (@deelawn)

Focus items from the previous sync

What did I work on last week?

  • Reviewed #1919
  • Challenge series work
    • Create and adjust challenges
    • Restrict node endpoints via Morgan's proxy
  • Got gophercon workshop topic finalized
  • Triaged and reviewed PRs (together with Maxwell)
    • Reviewed at least 22
    • Merged at least 5
  • Created and merged #2281 for a gnodev genesis tx feature

What will I focus on this week?

  • Challenge series
    • Make PRs for challenges that follow the organizer repo's current style
    • Any other challenge series work
  • Continue reviewing and re-reviewing incoming PRs
  • Resume work on embedding examples and stdlib gno code directories rather than using the os package
  • Work on gophercon workshop

Do I have any blockers?

  • no

Guilhem (@gfanton)

Focus items from the previous sync

  • I will focus more on the Nebular workshop
  • keep going on actual task:
    • Add unit test on gnofmt
    • finish gnodev txs handler branch

What did I work on last week?

  • Finish up txs handler branch -> need review
  • Fix gno fmt resolver, should work correctly now
    • still need some tests on the gnoimports package
  • Started a JSON TypedValue branch
    • taking some inspiration from protojson encoding package
    • implemented basic marshaling, started unmarshaling implem
  • Nebular Workshop

What will I focus on this week?

  • Nebular Workshop <- main focus this week
  • finish gno fmt tests
  • gno namespace

Do I have any blockers?

  • nop

Kristov (@kristovatlas)

Focus items from the previous sync

  • Planning for internal gno audit June 10 - 21

What did I work on last week?

  • Planning for internal gno audit June 10 - 21

What will I focus on this week?

  • Gno internal audit in progress through June 21

Do I have any blockers?

  • N/A

Leon (@leohhhn)

Focus items from the previous sync

What did I work on last week?

  • Finished gnokey tutorial, up for reviews
  • Finished gnoland tutorial, up for reviews
  • Wrapped up gnolang/faucet tutorial, up for 2nd reviews
  • Wrapped up the [docs renaming & 404 link checker PR], up for 2nd reviews
  • Waiting on wrapping this up after resolved comments
  • Worked on finding issues in Memeland video series and rerecording some videos

What will I focus on this week?

  • Rerecording more Memeland videos & hopefully sending it over to an editor ASAP
  • GRC20 refactor
  • GC EU tweets, planning for activities during conference
  • GC US: challenge series intro blog post
  • Test out and document tx-indexer
  • Refactor getting-started repo

Do I have any blockers?

  • Nope

Marc (@mvertes)

Focus items from the previous sync

  • review of candidates for atomone lead (HR)
  • improving debugger (next command, dynamic attach, break in functions)
  • review of #2221 as required

What did I work on last week?

  • review of candidates for atomone lead
  • improving debugger (next command, in progress)
  • review of some PRs
  • Discussions about first batch of bounties

What will I focus on this week?

  • debugger
  • Investigate some VM bugs, look at how to easily improve coverage
  • PR reviews and follow-ups
  • start a blog post on debugger

Do I have any blockers?

  • no

Maxwell(@ltzmaxwell)

Focus items from the previous sync

  • (ongoing) solve Issue of longer import path consume more gas.
  • review PRs.

What did I work on last week?

What will I focus on this week?

  • review PRs according to the overall plan;
  • complete refactor work;
  • complete longer import path consume more gas. (depends on time)

Do I have any blockers?

  • no

Milos (@zivkovicmilos)

Focus items from the previous sync

  • Bring the devnet efforts to a close with Albert (be on-call for features he needs pushed through and validated)
  • Bring the remaining test4 valset efforts to a close with @moul

What did I work on last week?

  • Brought the Tendermint blog post to a close
    • In final review now, hoping to publish it during the week
    • We'll push it out to a GitHub review before making it public
  • Assessed the leftover work Albert needs finished in order to launch the devnet successfully (launch it more than once!)
  • Synced with @moul and @gfanton on our current valset / GnoSDK efforts, and came up with a game plan to tackle them (the leftover work)

What will I focus on this week?

  • Unblocking Albert with the previously mentioned efforts (he needs some functionalities added ASAP)
  • Make sure we follow through with the valset changes
  • Play around with the Gophercon challenges
  • Review and unblock implementation partner PRs (Monday was Onbloc day 🙂)

Do I have any blockers?

  • No blockers for now :)

Morgan (@thehowl)

Focus items from the previous sync

  • Pushing out the GoR bounty program
  • Focus: Challenge series
  • importer PR
  • std renaming PR

What did I work on last week?

  • Focused on Challenge Series
    • We now have an up and running staging server, and are starting trial runs
    • You may be contacted to try out some challenges :)
  • Bounties
    • We now have drafts for most of the bounties we're targeting for a first round. We're aiming to get out a few bounty issues out by EOW!
  • Some reviews, bug investigations.

What will I focus on this week?

Do I have any blockers?

Nemanja (@Kouteki)

Focus items from the previous sync

  • Gno.land vision document
  • Ensure that the one-pager website is on track for GopherCon

What did I work on last week?

  • GopherCon material in all shapes and sizes
  • The More You Gno 9 article drafted
  • Set up a new sync with DevX, so we could improve the feeedback loop with the team that's basically our power user

What will I focus on this week?

  • Gno.land vision document
  • Gno.land messaging brief
  • Gno.land high level roadmap
  • Finalize Test4 launch date
  • Hiring interview

Do I have any blockers?

  • None

Petar (@petar-dambovaliev)

Focus items from the previous sync

  • N/A

What did I work on last week?

  • ...

What will I focus on this week?

  • ...

Do I have any blockers?

  • ...

Ray (@piux2)

Focus items from the previous sync

  • Complete the name and unnamed conversion part 3/3
  • take care of changes for PR 2241
  • Interview

What did I work on last week?

  • conitue name and unnamed conversion part 3/3
  • PR 2241

What will I focus on this week?

  • continue name and unnamed conversion part 3/3
  • PR 2241

Do I have any blockers?

  • no

Jae

  • DevMos - presentation was good, Cosmos is interested in gno!
  • Is cross-realm object storage not disabled?
    ^^ namely, storing external realm object in object.
    e.g. ./cmd/gnoland/testdata/grc20_registry.txtar

Callouts

  1. PR reviews:
  2. PR triage volunteer for this week: @zmilos ; next week is the final round with @petar-dambovaliev & @piux2 after which we'll have a short retrospective of the experiment.
  3. Challenge series status check: On track
  4. Gnora status check: Do be rescoped
  5. @zivkovicmilos: @jaekwon, how was Devmos in NYC?
    • Answered as part of Jae's update :)

Action Items

  1. @thehowl to set up a codebase refresh for Kristov

@moul moul mentioned this issue Jun 14, 2024
Open
@Kouteki
Copy link

Kouteki commented Jun 24, 2024

June 17, 2024

Individual Updates

Antonio (@ajnavarro)

Focus items from the previous sync

  • Have all the gnora commands working and implemented.

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Dylan (@deelawn)

Focus items from the previous sync

  • Challenge series
    • Make PRs for challenges that follow the organizer repo's current style
    • Any other challenge series work
  • Continue reviewing and re-reviewing incoming PRs
  • Resume work on embedding examples and stdlib gno code directories rather than using the os package
  • Work on gophercon workshop

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

  • no

Guilhem (@gfanton)

Focus items from the previous sync

  • Nebular Workshop <- main focus this week
  • finish gno fmt tests
  • gno namespace

What did I work on last week?

What will I focus on this week?

  • Continue Nebular Workshop
  • Gno Namespace (haven't working on this last week)

Do I have any blockers?

  • nop

Kristov (@kristovatlas)

Focus items from the previous sync

  • Gno internal audit in progress through June 21

What did I work on last week?

  • Gno internal audit in progress through June 21

What will I focus on this week?

  • Gno internal audit in progress through June 21

Do I have any blockers?

  • N/A

Leon (@leohhhn)

Focus items from the previous sync

  • Rerecording more Memeland videos & hopefully sending it over to an editor ASAP
  • GRC20 refactor
  • GC EU tweets, planning for activities during conference
  • GC US: challenge series intro blog post
  • Test out and document tx-indexer
  • Refactor getting-started repo

What did I work on last week?

  • GRC20 Refactor
  • GC EU Tweets
  • GC US Challenge stuff; reviews/blog post
  • Played around with tx-indexer

What will I focus on this week?

  • Attending GC EU
  • Completing GC US blog post
  • Docs:
  • Making a v1 of r/demo/events

Do I have any blockers?

  • No

Marc (@mvertes)

Focus items from the previous sync

  • debugger
  • Investigate some VM bugs, look at how to easily improve coverage
  • PR reviews and follow-ups
  • start a blog post on debugger

What did I work on last week?

  • GnoVM: Make Locations Accurate Again #2362: follow-up on debugger, but also of general interest (ensure uniqueness of nodes) and necessary for coverage of gno files.

What will I focus on this week?

  • GopherConEU
  • debugger blog post

Do I have any blockers?

  • no

Maxwell(@ltzmaxwell)

Focus items from the previous sync

  • review PRs according to the overall plan;
  • complete refactor work;
  • complete longer import path consume more gas. (depends on time)

What did I work on last week?

What will I focus on this week?

  • preprocessor refactor work;
  • gno type checkr moving forward according to the review;
  • issue about longer import path consume more gas;
  • review PRs;

Do I have any blockers?

  • no.

Milos (@zivkovicmilos)

Focus items from the previous sync

  • Unblocking Albert with the previously mentioned efforts (he needs some functionalities added ASAP)
  • Make sure we follow through with the valset changes
  • Play around with the Gophercon challenges
  • Review and unblock implementation partner PRs (Monday was Onbloc day 🙂)

What did I work on last week?

  • Unblocked Albert and DevOps frens on blocking issues (JSON output + additional subcommand support)
  • Wrapped up the performance reviews for the team
  • Did a first attempt at the PR triage, reviewed pending PRs
    • Our core team board now has dedicated "views" for different PR categories like contributors

What will I focus on this week?

  • Port in changes to r/sys/vals
  • Kick off the onboarding process for Sergio
  • GopherCon EU with the team

Do I have any blockers?

  • @MariMichelle22 thinks my keyboard is too loud so I can't be 20% faster when typing IRL :(

Morgan (@thehowl)

Focus items from the previous sync

What did I work on last week?

  • Challenge series
    • Write a guide for blockchain beginners
    • Clean-up
  • Review PRs
  • Kristov Walk-through
  • Make a few PRs and fixes

What will I focus on this week?

Do I have any blockers?

Nemanja (@Kouteki)

Focus items from the previous sync

  • Gno.land vision document
  • Gno.land messaging brief
  • Gno.land high level roadmap
  • Finalize Test4 launch date

What did I work on last week?

  • Opened a PR on docs.gno.land to add @gnolang/tech-staff as code owners, because the PRs weren't being assigned automatically
  • Test4 dates defined:
    • June 24: Scope freeze. There are no changes and pivots, and the only items added to the Test4 effort are bugs.
    • July 1: Feature development complete. We can now focus on fixing bugs.
    • July 10: Bug fixes complete. Test4 reaches launch readiness. Soft launch.
    • July 16: The official launch.
  • Shared the high level roadmap with Marketing & DevRel
  • 1st draft of the Gno.land vision document ready

What will I focus on this week?

  • 2nd draft of the Gno.land vision document

Do I have any blockers?

  • None

Petar (@petar-dambovaliev)

Focus items from the previous sync

  • N/A

What did I work on last week?

  • ...

What will I focus on this week?

  • ...

Do I have any blockers?

  • ...

Ray (@piux2)

Focus items from the previous sync

  • Continue name and unnamed conversion part 3/3
  • PR#2241

What did I work on last week?

  • Finished PR 2241 changes for more accurate vm OpCode measurement

  • Completed the name and unamed conversion part 3/3 PR#2367

What will I focus on this week?

  • Multi Node
  • Minimun Gas Price
  • Code Review

Do I have any blockers?

  • no

Jae Kwon

Focus items from the previous sync

  • #1426 (big one), #2147, #2140, #2077

What will I focus on this week?

  • same.
  • also, AtomOne + Gno.land

Do I have any blockers?

  • myself.

June 17, 2024

Callouts

  1. Fixed automation for all the GitHub repos. We should now have a more accurate state of our repositories. 115 PRs in review :D
  2. How does the team feel about enabling automatically merging a pull request on the monorepo? Noone minds
  3. Round robin experiment complete. Team's feedback: No noticeable effect, because the backlog is already huge. We will keep this setting and possible reevaluate once our PR review backlog is 10% of what it is today.
  4. Ray are up next for the PR triage
  5. Screenshot 2024-06-14 at 18.11.15

@Kouteki
Copy link

Kouteki commented Jun 26, 2024

Weekly Gno Staff Sync

Previous Syncs: #36.

Welcome to our Weekly Gno Staff Sync. Our goals are to showcase progress, identify risks, align with stakeholders, and lay the groundwork for strategic discussions related to Gno. This meeting helps us make decisions and focus on critical issues and goals.

First 10 Minutes: Silent Meeting Style

Learn about Silent Meetings

For the first 10 minutes, we'll have a silent meeting. This lets team members add discussion points, review the meeting's scope, and make quick comments. We'll start with general updates and callouts before discussing points and addressing comments. Each meeting should end with action items and noting key decisions.

This document is reused periodically. The first section has instructions. After the first horizontal line, you'll find the content section. Remember, the content will be shared on GitHub later, so only input content after the first horizontal line.

June 24, 2024

Core Team Updates

Antonio (@ajnavarro) (OOO)

Focus items from the previous sync

  • N/A

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Dylan (@deelawn)

Focus items from the previous sync

What did I work on last week?

What will I focus on this week?

  • Gophercon workshop
    • Finish coding what will be the finished project
    • Break this down into chunks that can be done in a workshop setting
    • Create slides to guide participants
  • Challenge series
    • Various things will probably come up
  • Review PRs
  • Follow up on responses to PRs I've reviewed

Do I have any blockers?

  • no

Whatever (@gfanton)

Focus items from the previous sync

  • Continue Nebular Workshop
  • Gno Namespace (haven't working on this last week)

What did I work on last week?

What will I focus on this week?

  • Typed Value JSON:
    • it seems that this is really needed on all side, I want to focus on this
  • continue: gno namespace
  • Workshop

Do I have any blockers?

  • no

Kristov (@kristovatlas)

Focus items from the previous sync

  • Gno internal audit in progress through June 21

What did I work on last week?

  • Gno internal audit
  • Forked gosec for scanning gno files
    • Can process a lot of /examples files as Go!
    • If we stick with a gosec fork, need to write our own AST tools in the future
    • Should also consider other static analyzer frameworks, but gosec does come with some useful checks already carried over from Go

What will I focus on this week?

  • More gno auditing!
  • Refining/planning dependency vulnerability checking infra

Do I have any blockers?

  • N/A

Leon (@leohhhn)

Focus items from the previous sync

  • Attending GC EU
  • Completing GC US blog post
  • Docs:
  • Making a v1 of r/demo/events

What did I work on last week?

What will I focus on this week?

  • Adding a few extra things to wrap up the gnokey tutorial
  • Finishing r/gnoland/events realm
  • Implemeting feedback for the docs linter on this PR
  • Working on the tx-indexer tutorial
  • Planning the next period out

Do I have any blockers?

  • Nope

Marc (@mvertes)

Focus items from the previous sync

  • GopherConEU
  • debugger blog post

What did I work on last week?

  • GopherCon EU
  • small fixes in parscan

What will I focus on this week?

  • debugger blog post
  • ensure that #2362 (gnovm location, approved) can be merged
  • HR reviews (atomone lead)

Do I have any blockers?

  • no

Maxwell(@ltzmaxwell)

Focus items from the previous sync

  • issue about longer import path consume more gas.

What did I work on last week?

  • Small PRs:
    #2390(merged)
    #2409
  • Code reviews;
  • Exploration issues on #2077(global var dependency), understand #2148.
  • Exploration issue #2083(longer import path consume more gas), there are some uncertainties that need to be discussed to clarify whether this is an issue worth fixing;

What will I focus on this week?

  • Clean follow up PRs after #1426(type check): #1775, #1890, #1891, make them reviewable;
  • Multi-phase preprocess on varloop (with the help of #2148);

Do I have any blockers?

  • No.

Milos (@zivkovicmilos)

Focus items from the previous sync

  • Port in changes to r/sys/vals
  • Kick off the onboarding process for Sergio
  • GopherCon EU with the team

What did I work on last week?

What will I focus on this week?

  • Apply feedback for #2130 (r/sys/vals)
  • Coordinate the soft launch of test4 (3 weeks away!)

Do I have any blockers?

  • No blockers so far

Morgan (@thehowl)

Focus items from the previous sync

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Nemanja (@Kouteki)

Focus items from the previous sync

  • 2nd draft of the Gno.land vision document

What did I work on last week?

  • TMYG9 article published
  • Hiring interview
  • Still working on the 2nd draft of the Gno.land vision document

What will I focus on this week?

  • 2nd draft of the Gno.land vision document

Do I have any blockers?

Petar (@petar-dambovaliev) (OOO)

Focus items from the previous sync

  • N/A

What did I work on last week?

  • ...

What will I focus on this week?

  • ...

Do I have any blockers?

  • ...

Ray (@piux2)

Focus items from the previous sync

  • Multi Node
  • Minimun Gas Price
  • Code Review

What did I work on last week?

  • Dynamic minimum gas price
  • Multi Node

What will I focus on this week?

  • Dynamic minimum gas price
  • More benchmarking

Do I have any blockers?

  • no

Sergio (@sw360cab)

Focus items from the previous sync

  • N/A

What did I work on last week?

  • Onboarding (non-tech) stuff
  • Learning principles of Blockchain / Web3 and Gno
  • Exploring Gno.land and current infra

What will I focus on this week?

  • Starting exploring and documenting infra (what we have / what we want)
  • Improving general knowledge

Do I have any blockers?

  • no

Albert Le Batteux (@albttx)

FYI: I'll be off July 4-14th, need to onboard Sergio on the infra before that.

What did I work on last week?

What will I focus on this week?

  • govgen stuffs
  • improve monitoring / graphs /
  • improve internal infra documentations

Do I have any blockers?

Jae @jaekwon

What did I work on last week?

  • merged #1919 (star expr assign), #2147, #2140 (boolean optimization), #1702 (small improvements)
  • #2418 (initialize static blocks), alt/dependency for #2077 (global var dependencies)

What will I focus on this week?

  • varloops/loop-externs (#1919) ideally multiphase
  • review #2367
  • maybe start sync GC

Do I have any blockers?

  • no

June 24, 2024

Callouts

  1. Scope freeze! Now let's wrap up all open issues.
  2. Antonio and Petar are the last round of PR triage volunteers
  3. Any volunteers interested in testing Gno challenges for the challenge series? Ask @deelawn
  4. @thehowl: do we want to have the guestbook realm?
  5. GopherCon EU feedback: Planned for Wednesday
  6. Challenge series: on track
  7. Ray: looking for gas benchmarking tool suggestions

@Kouteki
Copy link

Kouteki commented Jun 28, 2024

June 24, 2024

Core Team Updates

Antonio (@ajnavarro) (OOO)

Focus items from the previous sync

  • N/A

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Dylan (@deelawn)

Focus items from the previous sync

What did I work on last week?

What will I focus on this week?

  • Gophercon workshop
    • Finish coding what will be the finished project
    • Break this down into chunks that can be done in a workshop setting
    • Create slides to guide participants
  • Challenge series
    • Various things will probably come up
  • Review PRs
  • Follow up on responses to PRs I've reviewed

Do I have any blockers?

  • no

Whatever (@gfanton)

Focus items from the previous sync

  • Continue Nebular Workshop
  • Gno Namespace (haven't working on this last week)

What did I work on last week?

What will I focus on this week?

  • Typed Value JSON:
    • it seems that this is really needed on all side, I want to focus on this
  • continue: gno namespace
  • Workshop

Do I have any blockers?

  • no

Kristov (@kristovatlas)

Focus items from the previous sync

  • Gno internal audit in progress through June 21

What did I work on last week?

  • Gno internal audit
  • Forked gosec for scanning gno files
    • Can process a lot of /examples files as Go!
    • If we stick with a gosec fork, need to write our own AST tools in the future
    • Should also consider other static analyzer frameworks, but gosec does come with some useful checks already carried over from Go

What will I focus on this week?

  • More gno auditing!
  • Refining/planning dependency vulnerability checking infra

Do I have any blockers?

  • N/A

Leon (@leohhhn)

Focus items from the previous sync

  • Attending GC EU
  • Completing GC US blog post
  • Docs:
  • Making a v1 of r/demo/events

What did I work on last week?

What will I focus on this week?

  • Adding a few extra things to wrap up the gnokey tutorial
  • Finishing r/gnoland/events realm
  • Implemeting feedback for the docs linter on this PR
  • Working on the tx-indexer tutorial
  • Planning the next period out

Do I have any blockers?

  • Nope

Marc (@mvertes)

Focus items from the previous sync

  • GopherConEU
  • debugger blog post

What did I work on last week?

  • GopherCon EU
  • small fixes in parscan

What will I focus on this week?

  • debugger blog post
  • ensure that #2362 (gnovm location, approved) can be merged
  • HR reviews (atomone lead)

Do I have any blockers?

  • no

Maxwell(@ltzmaxwell)

Focus items from the previous sync

  • issue about longer import path consume more gas.

What did I work on last week?

  • Small PRs:
    #2390(merged)
    #2409
  • Code reviews;
  • Exploration issues on #2077(global var dependency), understand #2148.
  • Exploration issue #2083(longer import path consume more gas), there are some uncertainties that need to be discussed to clarify whether this is an issue worth fixing;

What will I focus on this week?

  • Clean follow up PRs after #1426(type check): #1775, #1890, #1891, make them reviewable;
  • Multi-phase preprocess on varloop (with the help of #2148);

Do I have any blockers?

  • No.

Milos (@zivkovicmilos)

Focus items from the previous sync

  • Port in changes to r/sys/vals
  • Kick off the onboarding process for Sergio
  • GopherCon EU with the team

What did I work on last week?

What will I focus on this week?

  • Apply feedback for #2130 (r/sys/vals)
  • Coordinate the soft launch of test4 (3 weeks away!)

Do I have any blockers?

  • No blockers so far

Morgan (@thehowl)

Focus items from the previous sync

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Nemanja (@Kouteki)

Focus items from the previous sync

  • 2nd draft of the Gno.land vision document

What did I work on last week?

  • TMYG9 article published
  • Hiring interview
  • Still working on the 2nd draft of the Gno.land vision document

What will I focus on this week?

  • 2nd draft of the Gno.land vision document

Do I have any blockers?

Petar (@petar-dambovaliev) (OOO)

Focus items from the previous sync

  • N/A

What did I work on last week?

  • ...

What will I focus on this week?

  • ...

Do I have any blockers?

  • ...

Ray (@piux2)

Focus items from the previous sync

  • Multi Node
  • Minimun Gas Price
  • Code Review

What did I work on last week?

  • Dynamic minimum gas price
  • Multi Node

What will I focus on this week?

  • Dynamic minimum gas price
  • More benchmarking

Do I have any blockers?

  • no

Sergio (@sw360cab)

Focus items from the previous sync

  • N/A

What did I work on last week?

  • Onboarding (non-tech) stuff
  • Learning principles of Blockchain / Web3 and Gno
  • Exploring Gno.land and current infra

What will I focus on this week?

  • Starting exploring and documenting infra (what we have / what we want)
  • Improving general knowledge

Do I have any blockers?

  • no

Albert Le Batteux (@albttx)

FYI: I'll be off July 4-14th, need to onboard Sergio on the infra before that.

What did I work on last week?

What will I focus on this week?

  • govgen stuffs
  • improve monitoring / graphs /
  • improve internal infra documentations

Do I have any blockers?

Jae @jaekwon

What did I work on last week?

  • merged #1919 (star expr assign), #2147, #2140 (boolean optimization), #1702 (small improvements)
  • #2418 (initialize static blocks), alt/dependency for #2077 (global var dependencies)

What will I focus on this week?

  • varloops/loop-externs (#1919) ideally multiphase
  • review #2367
  • maybe start sync GC

Do I have any blockers?

  • no

June 24, 2024

Callouts

  1. Scope freeze! Now let's wrap up all open issues.
  2. Antonio and Petar are the last round of PR triage volunteers
  3. Any volunteers interested in testing Gno challenges for the challenge series? Ask @deelawn
  4. @thehowl: do we want to have the guestbook realm?
  5. GopherCon EU feedback: Planned for Wednesday
  6. Challenge series: on track
  7. Ray: looking for gas benchmarking tool suggestions

@Kouteki
Copy link

Kouteki commented Jul 2, 2024

July 1, 2024

Core Team Updates

Antonio (@ajnavarro)

Focus items from the previous sync

  • N/A

What did I work on last week?

What will I focus on this week?

  • Continue with Realms and Package versioning specs, trying to have it done before Wenesday to be able to present the proposal on Thu.

  • Continue with test4 PRs reviews.

  • Maybe helping with missing parts on Gov DAO if needed.

Do I have any blockers?

  • No

Dylan (@deelawn)

Focus items from the previous sync

  • Gophercon workshop
    • Finish coding what will be the finished project
    • Break this down into chunks that can be done in a workshop setting
    • Create slides to guide participants
  • Challenge series
    • Various things will probably come up
  • Review PRs
  • Follow up on responses to PRs I've reviewed

What did I work on last week?

What will I focus on this week?

  • Workshop
    • Finish slides
    • Make changes based on internal feedback
  • Challenge series
    • Address my open PRs and review other open PRs
    • Tie up any other loose ends
    • Go through them all once more to make sure they work as expected

Do I have any blockers?

  • no

Гиле (@gfanton)

Focus items from the previous sync

  • Typed Value JSON:
    • it seems that this is really needed on all side, I want to focus on this
  • continue: gno namespace
  • Workshop

What did I work on last week?

What will I focus on this week?

  • I need to submit my workshop before friday 5th so i will focus on that ...
  • ... Then anything the team needs help for test 4

Do I have any blockers?

Kristov (@kristovatlas)

Focus items from the previous sync

  • Gno internal audit in progress through June 21

What did I work on last week?

  • More gno auditing!
  • Refining/planning dependency vulnerability checking infra:
    • Outcomes:
      • We can delete indirect deps and run go tidy mod to clean up some false positives for dependency vuln tracking
      • SemGrep standing out as a tool that implements reachability analysis; planning to integrate into CI for most deterministic level
      • If interesting to team, I can prepare short doc or presentation contrasting various code analysis tools against gno
  • Started testing gophercon challenges

What will I focus on this week?

  • More gno auditing! (currently focused on vm)
  • More gophercon challenges

Do I have any blockers?

  • No

Marc (@mvertes)

Focus items from the previous sync

  • debugger blog post
  • ensure that #2362 (gnovm location, approved) can be merged
  • HR reviews (atomone lead)

What did I work on last week?

  • Review PRs #2081, #2454, #2455, #1469, #2361
  • Merged #2362 🎉
  • Debugger blog post ready blog#100

What will I focus on this week?

  • more PR reviews
  • integrate debugger in repl, so it can also be used from playground
  • start work on AIB specification, as per #1842

Do I have any blockers?

  • no

Maxwell(@ltzmaxwell)

Focus items from the previous sync

  • Clean follow up PRs after #1426(type check): #1775, #1890, #1891, make them reviewable;
  • Multi-phase preprocess on varloop (with the help of #2418);

What did I work on last week?

  • Clean follow up PRs after #1426(type check): #1775, #1890, #1891.
  • Resolves issues on PR #2081.
  • Follow up multi-phase preprocessor #2418.
  • Follow up on the new solution for loop externs: #2429, auxiliary works is on #2440.

What will I focus on this week?

  • Finish #1775, #1890, #1891;
  • Review/feedback #2081.

Do I have any blockers?

  • No.

Milos (@zivkovicmilos)

Focus items from the previous sync

  • Apply feedback for #2130 (r/sys/vals)
  • Coordinate the soft launch of test4 (3 weeks away!)

What did I work on last week?

  • Tested out the GopherCon US challenges, hats off to Dylan and Morgan for putting it together 🙇
  • Applied feedback for #2130, (r/sys/vals), waiting on a final screen by @moul and then merging
  • Updated #2229 (valset injection), dependent on #2130, on standby for review and merge
  • Coordinated the JS client migration for #2285 (MsgCall lowercase field names in JSON) -> Found an Amino / proto bug we solved with the help of Alex
  • Opened up a proof of concept PR that aligns the genesis.json validator set to the on-chain one (go templates / simple genesis tx modification, without modifying local disk source code in examples)

What will I focus on this week?

  • Setting up the needed infra with our Ops and implementation partners for test4
  • Wrapping up leftover test4 tasks, including additional govdao improvements. Totally not stressed both Gno DevOps engineers are on vacation during the testnet launch :)
  • Coordinating the roles for the launch (what we'll do with test2, test3...). Having the first sync call tomorrow morning to define validator specs and expected infra setup

Do I have any blockers?

  • I need @moul's approval on #2130 to unblock #2229 by Wednesday

Morgan (@thehowl)

Focus items from the previous sync

What did I work on last week?

  • Challenge series
    • Addressing Milos' feedback
    • Coordinating infra set ups
  • Gophercon Raffle (helping out on some items to make it work smoothly)
  • std re-organization kick-off
  • Synced on bounties; writing and reviewing with Michelle the "homepage" with information about the program
  • Reviews

What will I focus on this week?

Do I have any blockers?

  • Not much, I think I'm the one blocking others this time around :)

Nemanja (@Kouteki)

Focus items from the previous sync

  • 2nd draft of the Gno.land vision document

What did I work on last week?

  • Gno.land messaging brief waiting for review from Manfred and Jae. Feedback from the rest of the core team is welcome.
  • Onboarded on the rest of the contributor calls

What will I focus on this week?

  • Test4 launch

Do I have any blockers?

  • PR reviews in order to meet the Test4 milestone. See Callouts for more details

Petar (@petar-dambovaliev) (OOO)

Focus items from the previous sync

  • N/A

What did I work on last week?

  • ...

What will I focus on this week?

  • ...

Do I have any blockers?

  • ...

Ray (@piux2)

Focus items from the previous sync

  • Dynamic minimum gas price
  • More benchmarking

What did I work on last week?

    • Dynamic minimum gas price

What will I focus on this week?

  • Dynamic minimum gas price

Do I have any blockers?

  • Discussion, should we store minimum gas price and gas used in the block as in block header, and consensus parameters? Plan B,

Sergio (@sw360cab)

Focus items from the previous sync

N/A

What did I work on last week?

  • Exploring existing Github Actions for:
    • Gnoland
    • Supernova
    • Benchmarks
  • Made my first PR(s)
  • Understanding full workflow for automatic benchmarks of Gno repository
  • Working on restoring benchmarks for Gnoland's test suite to be automatically launched and publicly available (on the dedicated repository)

What will I focus on this week?

  • Helping on provisioning for Gnochallenge24 GopherCon with Morgan (if needed)
  • GoRelease blocker on Supernova
  • Benchmarks workflows and corresponding (repo)[https://github.com/gnolang/benchmarks]

Do I have any blockers?

DevRel

Leon (@leohhhn)

What did I work on last week?

What will I focus on this week?

Do I have any blockers?

Michelle

What did I work on last week?

  • Content for the GopherCon landing page, waiting to add raffle info and challenge series content
  • GopherCon Newsletter content

What will I focus on this week

  • Finishing the 'call to contribute' content for bounties, grants and Game of Realms notable contributions
  • Onboarding junior developer grantees
  • Content for Test4 launch and validator communication (kicking off wg tomorrow)

Do I have any blockers?

Guest Stars

Jae @jaekwon

What did I work on last week?

  • #2429 (varloops) >50% done
  • which depends on #2418 (initialize static blocks)

What will I focus on this week?

  • #2429 (varloops) 80% done, and hand off.
  • gophercon talk & slides

Do I have any blockers?

  • need help w/ slide content; esp regarding performance related learnings about Go itself, in the context of legible code vs performant code. DM me please.
  • make _dev.stringer is broken. (running stringer manually works)

Albert Le Batteux (@albttx)

What did I work on last week?

  • Sentry node architecture (it's working!)
  • fix :26657/status voting_power
  • Telemetry expose prometheus endpoint with OTEL + improvement

What will I focus on this week?

Do I have any blockers?

Callouts

July 1, 2024

  1. PR review summary
    • 2160 (Onbloc / CI FAILS): Miloš (DONE), Morgan
    • 2130 (Miloš): Antonio (DONE), Manfred. Major blocker for the Test4 launch, needs to be reviewed by EOD Wednesday
    • 2081 (Maxwell): Petar (DONE), Marc
    • 1921 (Onbloc): Miloš (DONE), Morgan
    • 2367 (Ray / CI FAILS): Maxwell, Dylan
    • 2418 (Jae / CI FAILS): Petar, Marc
  2. @thehowl: do we want tool?
  3. @thehowl: do we want the guestbook realm?
  4. @thehowl: check-in on what we want for versioning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@moul moul

@zivkovicmilos zivkovicmilos

@piux2 piux2

Labels
⌚️ minutes Issues tracking meeting notes from recurring meetings.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@moul @thehowl @Kouteki @zivkovicmilos @piux2