Just sometime back we saw the end of a great rust-2 sprint and had some exciting stuff coming out of it which we hope was as exciting to the community as it was to us :).
We are now just about to start Sprint-3. We not only had a good planning week, which ended yesterday, but also very important RFC discussions. These RFCs are going to impart solid technical finesse to the core concepts of SAFE Network. To start with, the implementation of the RFCs will reduce the amount of code considerably. This in turn has far reaching implications, the smaller the code the less complex the system. Reducing complexity also reduces the number of bugs and is therefore a big step towards ensuring even more security. Now that the RFC discussions are finalised and agreed upon, most of the crates are going to benefit from these changes. However, the beauty of this simplification is that not only will it benefit the development of the modules by the MaidSafe team directly, but it will also have a positive impact on future developers and users of these libraries.
Unified StructuredData for instance adds a significant amount of flexibility. As mentioned in the RFC description, it will aid defining new data types and ability to link such data. We might even see a crate or two greatly slimmed down if not completely removed as a result. Hopefully, by the end of the sprint, developers will be able to code a nice demo to show some cool features that are now made possible as a result of these RFCs, fingers crossed!
So, this sprint will see the implementation of these RFCs as its main objectives and is therefore going to be an important one, simplicity and future-scalability has always been our focus. Additionally, by the end of this sprint, we might see some interface lock-downs so that app developers and other users of these libraries can get an idea of public-interfaces and APIs. Either during, or at the end of the sprint, QAs also anticipate the delivery of binary installers that will run the examples with ease while also connecting to the network of droplets, enabling further testing of the examples. That will hopefully make running these examples much less gruesome for those who aren’t really interested, or able, to clone and manually compile the code. The sprint starts this week and will run for between 3 and 4 weeks. Beyond that many goodies like the App Launcher, messaging…etc…are in the pipeline for the next sprint.
Wish us luck and stay tuned
The RFCs and objectives for this sprint:
Unified Structured Data - Reduced network traffic, increased scalability and reduced complexity
Public Key ID for all messages - Enables the client to be recognised by its public key via a signed secret key
Name Service - The SAFE Networks indexing mechanism locating data to a name (DNS Lookup)
Reserved Names - Outline and maintain type tags for Unified Structured Data. Anyone is free to choose the tags not reserved for their own customised types.
Here’s the dev-transcript.