Announcing Acropolis
Announcing our next testnet, Acropolis
blog.joystream.org/announcing-acropolis/
After the launch Athens on mid April, we have fully shifted our attention to our next testnet - Acropolis.
As the name might suggest, our intention is for Acropolis to build and improve on some of the issues we encountered with the launch of Athens. Perhaps the most interesting change for most users, is the introduction of the first "half" of the platforms integrated communication system - the on-chain forum.
This is the first step in providing users, platform role participants, council members and future stakeholders a way to communicate and coordinate. Hopefully, this method of interaction will further help develop a strong community around Joystream.
Both in the short, medium and long term, we need a way to onboard developers in an efficient way. The longevity of the project relies on a sufficient set of contributors that can write new features, and test and verify the code.
We have identified some problems with the current product, and have decided to attempt to improve and simplify the system. As a sidenote, the new product released with Acropolis will be shipped with tranches, allowing Storage Providers not to have to store the entire Content Directory as it grows.
In line with the project goals of openness and transparency, we are releasing public Release Plans for each testnet. More on this in an upcoming blog post. Perhaps the most tangible output of the Release Plan process, is the the Release OKR:
Get 75 posts on forum (limits, not Jsg)Forum (runtime), storage (runtime and P2P) fully specdHave 4x replication for all 2 tranches on storage node95% uptime Storage ProviderNo PRs merged to master (excluding bugfixes and "pioneer") after "Sub-system Test"
Although Joystream is currently controlled by us at Jsgenesis, our goal has been, and still is, to withdraw and leave it in the hands of our community to own, operate and govern. In order for that transition to work smoothly, we need contributors at all levels. Just participating on our testnets is helping us immensely (hence why we pay monero for doing so), but we need help in other ways as well.
Both detailed specing and opening our project management and planning process on GitHub at an early stage, are steps we hope will attract both technical and managerial talent.
Developers and testers can report issues or make PRs to our repos, following our standard rules. In addition to the small bounties we promise for small "patches" or bug discoveries, feel free to contact us anywhere if you have something larger in mind.
All forward looking statements, estimates and commitments found in this blog post should be understood to be highly uncertain, not binding and for which no guarantees of accuracy or reliability can be provided. To the fullest extent permitted by law, in no event shall Joystream, Jsgenesis or our affiliates, or any of our directors, employees, contractors, service providers or agents have any liability whatsoever to any person for any direct or indirect loss, liability, cost, claim, expense or damage of any kind, whether in contract or in tort, including negligence, or otherwise, arising out of or related to the use of all or part of this post, or any links to third party websites.
Our next testnet, Acropolis, will introduce an on-chain forum!
After the launch Athens on mid April, we have fully shifted our attention to our next testnet - Acropolis.