/
Project Planning Jan 11, 2018

Project Planning Jan 11, 2018

Jan 12, 2018

Date

Attendees

Goals

  • Map out objectives for the coming weeks - and how pieces come together for a release.
  • Decide the cadence of this meeting.  The 'leads' need to speak with each other about what we are building, what the detailed statuses are for each area, and what the integration points are.  Propose every 2 weeks on Thursdays.

Discussion items

TimeItemWhoNotes
10 minSDK Relese
Medha Parlikar (Unlicensed)
  • What is the user experience for the SDK Release?
  • UX to complete the following use case:
    • Pull an example Rholang contract, compile and run.
    • Author a new Rholang contract, compile and run.
    • Debug a compile problem
    • Debug an execution problem
    • View output of a running program
  • Who is going to do the work to create the SDK package and make sure that the UX is good?
  • Kyle Butt - as a tech preview he is fine with the web compiler.
  • Michael Stay (Unlicensed) - don't see any reason to have any glue code.  Author the code in editor and then compiler, and then run it in rosette.
  • Kyle Butt - will make it more accessible for more people.
  • Chris Kirkwood-Watts - Will it feel more like a compiler if they get all the separate pieces.  
 10 min Node Code Chris Kirkwood-Watts
  • How will node operators interact with their nodes?  RSON or ReST?
  • Geth in ETH uses Javascript, which is Untyped.  What will we use?  Do we provide something like Geth, or do we provide just the API for Node management, and let others build the tools?
  • Who will design the interface (API) & write the specification?
  • What are the verbs that are needed?
  • Nash Foster isn't crazy about JSON, prefers protbufs but he isn't too opposed to JSON.  Chris Kirkwood-Watts believes most everyone is expecting to interface with the node using Javascript.
  • Chris can start out with communications stuff, and as more things become more accessible, we can roll more in. 
  • Chris will resurrect his old code and start building out the front of the node. 
10 minWhat's Next for Node
  • What comes after Node.Hello?  Node.Void originally was defined as integrating Storage, VM and Networking.  This doesn't make sense now.
  • JSON for communication stuff by Chris.
  • Possibly storage in the February time frame as an independent release.
  • Does it make sense to put Roscala into the node?  If there is anything end to end at all it makes sense to put it into the node.
  • Can we write a primitive to send a message across the comms layer - and could the VM execute it - As soon as Transition is done, we could do something.  Possibly done by end by March.
  • Up next VM into the Node - write programs using opcodes that does something interesting and demonstrates the use of the comms and storage layer.  
  • Implement more Primitives - If we have primitives that can be invoked using ApplyPrim() - we can demonstrate many primitives even without boot.rbl.

Action items

  •