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: Development, Dec 27 #29

Closed
lehnberg opened this Issue Dec 16, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@lehnberg
Copy link
Collaborator

lehnberg commented Dec 16, 2018

Solicit suggestions for agenda items for the Development meeting to be held on Thursday Dec 27 @ 15:00 UTC in Grin/Dev Gitter. Please comment to provide topics or suggestions.

Proposed agenda

  1. Igno's Retrospective
  2. Agenda review
  3. Action point follow ups from previous meetings
  4. PoW general item
  5. Results from libsecp audit
    1. Related: mimblewimble/grin#2218
  6. Mainnet planning
    1. Betanet status
    2. Genesis status
  7. Post-mainnet release planning.
    1. How do we plan releases?
    2. How do we decide what features go into each release?
  8. Other questions
@yeastplume

This comment has been minimized.

Copy link
Member

yeastplume commented Dec 22, 2018

I do think we need to start thinking about post-mainnet release planning. Specifically, how we plan releases and how we decide what features go into each release. This topic probably crosses over with governance

@lehnberg lehnberg changed the title Agenda: Development, Dec 25 Agenda: Development, Dec 27 Dec 24, 2018

@lehnberg

This comment has been minimized.

Copy link
Collaborator

lehnberg commented Dec 24, 2018

Agenda updated, added this point. I think it makes sense to have it be development driven.

@ignopeverell

This comment has been minimized.

Copy link
Member

ignopeverell commented Dec 24, 2018

We should also discuss current results from the code review of libsecp and its use in Grin.

@lehnberg

This comment has been minimized.

Copy link
Collaborator

lehnberg commented Dec 27, 2018

Makes sense, updated

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