As @dirvine has already stated on the forum, we still have a few issues in Vaults and one remaining in Crust that the dev team are focused on; these need to be resolved before the MVP is ready for delivery. So no MVP this week - to paraphrase David: it is all still a wee bit raw for release this week.
It is amazing to see all the app building activity and discussion here on the forum and in github. We all want to keep this momentum going and continue to progress and expand the client side APIs, so later this week we expect to have an RFC for enabling dynamic data handling completed and shared for everyone in the community to discuss, more details about this can be found within the Client section.
##Crust - uTP / API : Vinicius / Andrew / David
We re-enabled the lints and removed code that was implementing functionality that is now available through other crates, so the Crust code is now much simpler. We also discussed design and decided to implement a heartbeat mechanism in Crust as it will make behaviour more consistent across multiple platforms and gets us closer to being able to use TCP without experiencing any problems. The heartbeat will also be used in uTP, as it is also important for Routing churn to have fast notifications regarding LostPeer events.
##Routing - Vault Integration : Andreas / Adam / David
Apart from lots of testing and debugging, we have made some improvements to the algorithm that should enable the network to better handle lots of simultaneously joining and leaving nodes, but there is still plenty of work to do in that area.
##Vaults : Brian / Fraser / Qi
Last week was a designing week to re-examine the data flow for backup / sacrificial copies of immutable data. There are data-flow documents, sequence diagrams, class diagrams, task lists and RFC updates, all of which have been newly created or updated to reflect and document the outcome from these discussions.
It has been agreed that future work within the Vault library will be divided into two phases, with phase one focusing on introducing backup / sacrificial copies in get flow and the second phase focusing on freeing up space in the put flow, together with adjusting the farming rate.
Implementation work has begun based on the task list created for phase one.
This week we aim to complete the newly listed tasks from phase one and to begin work on phase two.
##Client - Launcher : Krishna / Spandan / Shankar
The logging abilities within the maidsafe_utilities library have been improved to enable sending logs to a remote server. The logs from vaults are to be sent to the visualiser server, which will help in debugging and also display real time statistics from the testnet (e.g. how many nodes are running, information on how well network connections are behaving, etc). The components needed for the visualiser were developed last week. @shankar and @krishna_kumar will be putting the pieces together this week to get the log visualiser into a working state.
To the delight of the app devs, an RFC for enabling dynamic data handling is expected to be completed and shared by the end of this week. We expect that this RFC will create a lot of good healthy debate and constructive suggestions that will help mould the final design and implementation. The RFC will detail the APIs that will be exposed from the Launcher and how these can be used to build applications that require to handle dynamic data. We are excited to add this important and much requested functionality to the network.
##UI Design : Scott / Shankar
@shankar and @scott have been working on the roadmap and it is nearing completion. Functionally, it is nearly finished and we’re starting to populate it with some real data. A lot of time this week will be spent collating and parsing data from various places to put into the roadmap. Following this, we will get feedback from the devs and management who will contribute to the data and make sure it properly reflects the company’s endeavours over the next wee while.
Following on from the work @scott did last week on the video, we’ve decided to do a second iteration of this. Time this week will be spent on nailing down the direction we’re planning to take for this (e.g. target audience and objectives covered), writing a script and finally recording the video and voiceover.
Some small changes to the website UX are also planned to be researched and worked on this week by @scott with @shankar implementing these proposed changes following review and critique of the mockups and suggestions.
##Customer Support : Ross
As stated last week, as new releases are rolled out we can close off issues that are fixed by that release, so if you have an open issue, it has not been forgotten and the list of open issues are reviewed every couple of days. Some work has also gone into defining and sharing the known security limitations and this will continue and hopefully be completed at some point this week. The RFC process has also received some long overdue attention with new (and some outstanding) RFC PRs being merged into the Proposed section for discussion and a few being accepted and made Active and implemented.
Thank you for the ongoing support, no transcript this week as this was something Justine used to pull together and Justine has now moved on from MaidSafe to new opportunities. The transcript was originally created from a whole team meeting which no longer happens (replaced by other team catch-ups). I also felt it duplicated a lot of content found here in the weekly dev update, so did not chase people to complete it this week. If there is a huge demand to reinstate the transcript, we can revisit this.
that will make many people (including me) very happy 
