This repository has been archived by the owner on Apr 13, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 299
Sprint 2
QuiqueGL edited this page Nov 29, 2018
·
8 revisions
Sprint 1 has just been completed. The sprint planning presented in sprint 1 has been faithfully followed and most of the user stories have been accomplished. The main highlights during these two weeks are:
- Team: a new member with a devops profile has been onboarded in Alastria core and is already working in automation, security tasks. Sync meetings have been started with Latam Alastria team and it has been agreed to share backlog for next Sprint #2 so that we join forces, share knowledge and work towards the same goals.
- Network: the most important advances done were:
- Telsius testnet has been deployed in a closed environment for the core team.
- RPC filter Access Point has been developed and tested in a native environment.
- Netstats and Block explorer have been released for both Arrakis and Telsius testnets for its monitoring and visualization
- Community issues and pull requests have been attended as soon as possible highlighting the addition of new requested nodes and dealing with problems detected in the network. (reinitialization of nodes, update of certificates etc.)
- Documentation: The wiki documentation has been extended and updated, now including a private smart contracts creation step by step guide. Gitlab internal documentation has been created to share ADRs and approaches as well as to keep step by step guides of repetitive tasks such as adding a new node, so that any member of the core team can do it.
1. How to set up:
- A regular node in Red T using Docker
- A validator node in Red T using Docker
- A bootnode in Red T using Docker
- Private Smart Contracts in Red T
- Deployment of Smart Contracts in Red T
2. F.A.Q.
3. Netstats and Block explorers