2018-04-05 Engineering Meeting Notes
Attendees
Yannis De Cleene
Ben Longstaff
Jack Zampolin
Aaron Blankstein
Shankar Ganesh
Jude Nelson
Vsund
Jeff Domke
Larry Salibra
Chase Wackerfuss
Mario Ceballos
Versioning And Specs
- Larry:
- We should separate developer toolkits from the user-facing product
- Iterate quickly on the user-facing product
- Developer toolkits go more life-cycle focused, where you have a year-long period of development interfaces that change often
- The trade-off is that we’re not necessarily at a point where everything is very stable, and we know what a platform “is”.
- Breaking changes only quarterly — non-breaking changes allowed in more frequent releases
- Documentation and specification:
- interfaces of blockstack.js
- interfaces between blockstack.js and core
- Action item: binding json schemas and documentation for core.blockstack (and similar deployments)
- Specification ask:
- Single location for specs?
- Specs update if code updates
- Use json schemas for interfaces
- Tie specs onto unit tests — we need a framework for enforcing specs
- Next sprint: have someone assigned to working on this
- Release schedule is also important (somewhat orthogonal to the specs)
Browser
- Progressive on-boarding?
- If we’re committing to browser.blockstack.org — then what options do we really have for storing information?
- Where do we store information if we want the transition to be seamless?
- Redux state cleanup
- Can we make this a concrete goal for next sprint?
- Core-less Browser Build
- Do we want this to block on the redux state cleanup?