Project Planning March 7th, 2018

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
10 minCompiler / Interpreter status - what features will be ready for 3/29
  • Open work items - what will happen next sprint.
  • Joe is going on vacation
  • Progress being made on the matching algorithm. Parallel matching is tricky. 
  • Scala Protobuf will allow you to serialize and de-serialize to custom classes, so we were able to get a bitset and serialize it to bytes. 
    • we will do the same thing for maps and sets, allowing us to avoid the non-determinstic corners of protobuf (at the expense of lang interop)
  • Storage tier is progressing fine.  In memory version is in flight, LMDB version is in flight as well. 
  • Locking story is a WIP.  Competing writes is an issue we will need to look at.  
  • Highest risk for 3/29 is the Evaluator - Joe's holiday was a surprise.  Fallback, halt matching work (it's done enough for 3/29) and ensure evaluator is solid
    • Enlist Kent's help as well.
5 minNode Status - what features will be ready by 3/15 Chris Kirkwood-Watts / Kelly Foster
  • 3/15 is in excellent shape. Stretch goals - clearer by end of week
  • Encryption and Handshake is moving along nicely.
  • Talk about how much 'splash' we want for the 3/15 release, or do we defer in favor of 3/29
    • Blog post about release.
    • Demo?  Kelly and Medha to meet.  It's a small incremental improvement over the last release.  
5 minVM - Status.Timm Schäuble
  • Plan for testing Transition function. 
    • We need to analyze the code coverage reports /tests and validate that the system is being properly tested.
  • Compiler extraction plan - Keith to test this out starting next sprint.
  • Primitives plan 
10 minLast meeting rolled over itemsChris Kirkwood-Watts
  • Compiler extraction plan - dive into details.
    • Will we run it in 32 bit mode?  It doesn't run particularly well in a modern Linux system.
      • Plan - Test that we can extract the environment literals, the compiler sets the VM environment.  That dependency needs to be broken.
        • Keith and Nash are working on this.
        • Need to include the 64 bit port of the compiler as part of the work items.
5 minDepencies Discussion
  • Lay out any dependencies that you may have on other teams work.
    • Node team will need to know how to integrate with Interpreter.  CLI and REPL are not done yet.  Kent is working on those pieces
      • Rholang team to deliver a REPL.  Node team will want to look at the main function and do the same thing. 
      • To integrate the Node and Interpreter, the file parser will look very similar to the current compiler. 
      • Read in a file → parse it → pass to Normalizer → pass to Interpreter.
10 min

Releases / Roadmap

Whats next.

Everyone
  • Medha reviews Roadmap
  • Medha needs to work with Mike to get the interface for the powerbox documented
    • Understand how the authority for the powerbox is bundled up and exposed.  We need more specificity so we can implement. 
    • Can Mike write the powerbox code to lay down an initial pattern and interfaces that the teams need to write code adhering to.
    • Get a pattern in place for the system contracts.

Action items

From Last meeting

  • Henry Till: Follow up with Kyle to on Storage.  Walk through the API.
  • Kyle Butt: Update the Interpreter specification to outline what the interfaces is for Node to call the Interpreter.
  •  

New action items

  • Henry Till: Write up LMDB locking story for Kyle ButtNash Foster to provide input and feedback on how to resolve.  Not critical for 3/29, but we need to have a story.