Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agenda Core dev call #33 #58

Open
hesterbruikman opened this issue Jun 26, 2020 · 2 comments
Open

Agenda Core dev call #33 #58

hesterbruikman opened this issue Jun 26, 2020 · 2 comments

Comments

@hesterbruikman
Copy link
Contributor

hesterbruikman commented Jun 26, 2020

Monday June 29
13:00 UTC
Participate: meet.google.com/uyn-yfrq-uka
View: https://www.youtube.com/channel/UCFzdJTUdzqyX4e9dOW7UpPQ/videos

  1. Assign notetaker
  2. Agenda setting (~5')
  3. Announcements (~5')
    a. ...
  4. Review previous actions (~5')
  5. Specs review > open PR's for Discussion (~10')
    a. Add audio messages
    b. Address feedback
  6. Expected changes/proposals
    a. Stimbus Implementation proposal - feedback (~10')
    b. Waku version 2 - feedback (~10')
    c. Layer2 solutions to remove gas cost barrier for in-Status SNT transactions - intro (~10')
  7. Notifications on iOS (progress, decisions that have been made) - update (~10')
  8. AOB (~5')

YouTube: https://www.youtube.com/watch?v=U6u8Ee1inps
Google Hangouts: https://meet.google.com/uyn-yfrq-uka
Notes: https://notes.status.im/core-dev-call_33#

@oskarth
Copy link
Contributor

oskarth commented Jun 29, 2020

Forgot where it was mentioned but I think 90m would be fine, considering how many topics there are. The main thing is that people should come prepare so we don't have to spend too much time recapping what should be done as individual prep already.

Topics:

  1. Waku v2
  • Feeedback probably best async in Discuss thread.
  • What I need is clear commitment from Core Desktop/Stimbus (@andremedeiros @iurimatias) on individuals participating so we can kick-start this effort. There has been some suggestions already.
  1. Stimbus
  • We also need to have a clear path for devs to write new code in Nim asap, e.g. PN server stuff (likely happening in Go now, eg)
  1. Clarity on metrics

Also see https://discuss.status.im/t/user-growth-and-retention/1782

@yenda
Copy link

yenda commented Jun 29, 2020

Possible announcement: layer 2 solution for Status Pay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants