List view
- No due date•3/3 issues closed
This milestone tracks the creation of how to guides and content for the ISC documentation.
No due date•2/2 issues closed- No due date•1/1 issues closed
This milestones tracks our progress towards making the SDK 2.0 ready.
No due date•4/4 issues closedThis milestone indicates that we've successfully added all the relevant 2.0 content in an organized manner that is accesible to all user levels.
No due date•4/4 issues closedIdentify "Discover", "Play", "Build" and "Ship" content lists for both Shimmer and ShimmerEVM
Due by April 10, 2023•2/2 issues closed## Goal Successfully launch the IOTA 2.0 education campaign and part of this will include descriptions of IOTA 2.0 on the wiki ## Objective Create the technical content and have DevX create introductory/ELI5 content around IOTA 2.0 on wiki For existing generated contents: - Create a PR. Depending on where in the wiki in which repo; - Assuming it's for GoShimmer, they need to add to [this folder](https://github.com/iotaledger/goshimmer/tree/develop/documentation/docs) and update [this file](https://github.com/iotaledger/goshimmer/blob/develop/documentation/sidebars.js) to include their new files - We will be creating a new repo for this. - Once it is merged it should get published at midnight Items that need to confirm: - What contents need an update to the wiki? Or just a protocol overview - Check if the research team wants to update the 2.0 specification docs? We should commit to one section **- We will be creating a new repository for this.** - Put some more thought into how we handle versioning in the wiki (The idea is that Stardust changes eventually go into IOTA, to prepare it for the GoShimmer changes to be merged?) Alternatives: Share the contents/technical docs with Lucas and write a summary based on that ## Tasks ### Create ELI5 content **Design Principles:** - [ ] The 5 IOTA 2.0 Principles and how we achieve them. **Anatomy of the Protocol:** - [ ] Data flow: how all the components fit together. - [ ] Networking, Autopeering, how the network comes to be. - [ ] Data structures: TX, branch IDs, [multiverse reality], epoch commitments, etc. - [ ] Mana, accounts, tokenomics and staking - [ ] Consensus, commitee, approval weight, finality gadget - [ ] Validators, their selection and rotation - [ ] Communication layer: congestion control, scheduler, tip selection. - [ ] https://v2.iota.org/
Due by May 26, 2023•5/5 issues closed# Goal Since iota.rs, wallet.rs and iota.js will be merged into the iota-sdk, we need to prepare the repository and documentation in a way to minimizes the learning curve and maximizes adoption. To do so, we must: 1. Organize the documentation in a sensible manner. 2. Ensure all getting started documentation is clear, concise and has the least amount of steps possible. 3. Prepare and organize code examples that showcase the sdk's functionalities in the exact same way for all the available languages. 4. Create or adapt current tutorials to follow a logical development path to facilitate developer onboarding and retention. ## Tasks (to do: confirm after meeting with the team lead for the iota-sdk project)
Due by May 1, 2023•8/8 issues closed# Goal To launch the `iota-sdk` with comprehensive, accessible documentation which is easy to use from the simplest use cases to the most complex. ## Acceptance Criteria The following tasks
Due by May 1, 2023•1/1 issues closed## Goal Successfully launch the IOTA 2.0 education campaign and part of this will include descriptions of IOTA 2.0 on the wiki ## Objective Create the technical content and have DevX create introductory/ELI5 content around IOTA 2.0 on wiki For existing generated contents: - Create a PR. Depending on where in the wiki in which repo; - Assuming it's for GoShimmer, they need to add to [this folder](https://github.com/iotaledger/goshimmer/tree/develop/documentation/docs) and update [this file](https://github.com/iotaledger/goshimmer/blob/develop/documentation/sidebars.js) to include their new files - We will be creating a new repo for this. - Once it is merged it should get published at midnight Items that need to confirm: - What contents need an update to the wiki? Or just a protocol overview - Check if the research team wants to update the 2.0 specification docs? We should commit to one section **- We will be creating a new repository for this.** - Put some more thought into how we handle versioning in the wiki (The idea is that Stardust changes eventually go into IOTA, to prepare it for the GoShimmer changes to be merged?) Alternatives: Share the contents/technical docs with Lucas and write a summary based on that ## Tasks ### Add technical content provided by Darcy **Design Principles:** - [ ] The 5 IOTA 2.0 Principles and how we achieve them. **Anatomy of the Protocol:** - [ ] Data flow: how all the components fit together. - [ ] Networking, Autopeering, how the network comes to be. - [ ] Data structures: TX, branch IDs, [multiverse reality], epoch commitments, etc. - [ ] Mana, accounts, tokenomics and staking - [ ] Consensus, commitee, approval weight, finality gadget - [ ] Validators, their selection and rotation - [ ] Communication layer: congestion control, scheduler, tip selection. **The 2 high level releases are:** - [ ] introduction on digital autonomy + principles. - [ ] Development and integration of Mana calculator.
Due by May 12, 2023•7/7 issues closed