fix: remove all md files introduced in ee298fc commit

SUMMARY.md

@@ -1,104 +0,0 @@
-# Table of contents
-
-* [Joystream](README.md)
-* [README](pioneer/README.md)
-  * [packages](pioneer/packages/README.md)
-    * [@polkadot/apps-routing](pioneer/packages/apps-routing.md)
-    * [@polkadot/app-explorer](pioneer/packages/app-explorer.md)
-    * [@polkadot/app-democracy](pioneer/packages/app-democracy/README.md)
-      * [src](pioneer/packages/app-democracy/src/README.md)
-        * [md](pioneer/packages/app-democracy/src/md/README.md)
-          * [basic](pioneer/packages/app-democracy/src/md/basic.md)
-    * [@polkadot/app-toolbox](pioneer/packages/app-toolbox.md)
-    * [@polkadot/app-address-book](pioneer/packages/app-address-book/README.md)
-      * [src](pioneer/packages/app-address-book/src/README.md)
-        * [md](pioneer/packages/app-address-book/src/md/README.md)
-          * [Address book](pioneer/packages/app-address-book/src/md/basic.md)
-    * [Forum module for Joystream node](pioneer/packages/joy-forum.md)
-    * [Proposals module for Joystream node](pioneer/packages/joy-proposals.md)
-    * [@polkadot/app-123code](pioneer/packages/app-dashboard.md)
-    * [@polkadot/app-treasury](pioneer/packages/app-treasury/README.md)
-      * [src](pioneer/packages/app-treasury/src/README.md)
-        * [md](pioneer/packages/app-treasury/src/md/README.md)
-          * [Treasury](pioneer/packages/app-treasury/src/md/basic.md)
-    * [@polkadot/app-settings](pioneer/packages/app-settings/README.md)
-      * [src](pioneer/packages/app-settings/src/README.md)
-        * [md](pioneer/packages/app-settings/src/md/README.md)
-          * [basics](pioneer/packages/app-settings/src/md/basics.md)
-    * [Media content module for Joystream node](pioneer/packages/joy-media.md)
-    * [@polkadot/app-staking](pioneer/packages/app-staking/README.md)
-      * [src](pioneer/packages/app-staking/src/README.md)
-        * [md](pioneer/packages/app-staking/src/md/README.md)
-          * [basic](pioneer/packages/app-staking/src/md/basic.md)
-    * [Joystream Pages Module](pioneer/packages/joy-pages/README.md)
-      * [src](pioneer/packages/joy-pages/src/README.md)
-        * [md](pioneer/packages/joy-pages/src/md/README.md)
-          * [Terms of Service](pioneer/packages/joy-pages/src/md/tos.md)
-          * [Privacy](pioneer/packages/joy-pages/src/md/privacy.md)
-    * [@polkadot/apps](pioneer/packages/apps.md)
-    * [Election module for Joystream node](pioneer/packages/joy-election.md)
-    * [@polkadot/app-accounts](pioneer/packages/app-accounts/README.md)
-      * [src](pioneer/packages/app-accounts/src/README.md)
-        * [md](pioneer/packages/app-accounts/src/md/README.md)
-          * [basic](pioneer/packages/app-accounts/src/md/basic.md)
-    * [@polkadot/react-api](pioneer/packages/react-api.md)
-    * [@polkadot/app-generic-asset](pioneer/packages/app-generic-asset.md)
-    * [@polkadot/react-params](pioneer/packages/react-params.md)
-    * [@polkadot/app-storage](pioneer/packages/app-storage.md)
-    * [@polkadot/app-js](pioneer/packages/app-js.md)
-    * [@polkadot/app-transfer](pioneer/packages/app-transfer.md)
-    * [@polkadot/react-signer](pioneer/packages/react-signer.md)
-    * [@polkadot/app-123code](pioneer/packages/app-123code.md)
-    * [@polkadot/app-sudo](pioneer/packages/app-sudo.md)
-    * [Help module for Joystream node](pioneer/packages/joy-help.md)
-    * [@polkadot/app-council](pioneer/packages/app-council.md)
-    * [@polkadot/app-contracts](pioneer/packages/app-contracts/README.md)
-      * [src](pioneer/packages/app-contracts/src/README.md)
-        * [md](pioneer/packages/app-contracts/src/md/README.md)
-          * [contracts](pioneer/packages/app-contracts/src/md/intro.md)
-    * [@polkadot/ui-settings](pioneer/packages/joy-settings.md)
-    * [Utils for Joystream node](pioneer/packages/joy-utils.md)
-    * [@polkadot/app-parachains](pioneer/packages/app-parachains.md)
-    * [@polkadot/react-query](pioneer/packages/react-query.md)
-    * [@polkadot/app-claims](pioneer/packages/app-claims.md)
-    * [@polkadot/react-components](pioneer/packages/react-components.md)
-    * [Membership module for Joystream node](pioneer/packages/joy-members.md)
-    * [@polkadot/app-extrinsics](pioneer/packages/app-extrinsics.md)
-    * [@polkadot/joy-actors](pioneer/packages/joy-storage.md)
-    * [@polkadot/joy-roles](pioneer/packages/joy-roles.md)
-  * [CHANGELOG](pioneer/changelog.md)
-  * [Contributing](pioneer/contributing.md)
-  * [Bounties](pioneer/bounties.md)
-* [README](cli/README.md)
-  * [bin](cli/bin/README.md)
-    * [run](cli/bin/run.md)
-* [@joystream/types](types.md)
-* [docs](docs/README.md)
-  * [using-docker](docs/using-docker/README.md)
-    * [Docker](docs/using-docker/building-node-and-runtime.md)
-* [runtime](runtime/README.md)
-  * [CHANGELOG](runtime/changelog.md)
-* [query-node](query-node/README.md)
-  * [Overview](query-node/docs/README.md)
-    * [Install Hydra](query-node/docs/install-hydra.md)
-    * [Architecture](query-node/docs/architecture.md)
-    * [Schema](query-node/docs/schema-spec/README.md)
-      * [Entities](query-node/docs/schema-spec/entities.md)
-      * [The Goodies](query-node/docs/schema-spec/the-query-goodies.md)
-      * [Entity Relationships](query-node/docs/schema-spec/entity-relationship.md)
-      * [Enums](query-node/docs/schema-spec/enums.md)
-      * [Algebraic types](query-node/docs/schema-spec/variant-types.md)
-      * [Interfaces](query-node/docs/schema-spec/interfaces.md)
-      * [Full-text queries](query-node/docs/schema-spec/full-text-queries.md)
-    * [Mappings](query-node/docs/mappings/README.md)
-      * [DatabaseManager](query-node/docs/mappings/databasemanager.md)
-      * [SubstrateEvent](query-node/docs/mappings/substrateevent.md)
-    * [Tutorial](query-node/docs/quick-start.md)
-  * [Substrate Query Node](query-node/substrate-query-framework/README.md)
-    * [cli](query-node/substrate-query-framework/cli/README.md)
-      * [bin](query-node/substrate-query-framework/cli/bin/README.md)
-        * [run](query-node/substrate-query-framework/cli/bin/run.md)
-  * [Joystream Query Node](query-node/joystream-query-node.md)
-  * [examples](query-node/examples/README.md)
-    * [kusama-query-node](query-node/examples/kusama-query-node.md)
-

cli/bin/README.md

@@ -1,2 +0,0 @@
-# bin
-

cli/bin/run.md

@@ -1,6 +0,0 @@
-# run
-
-@echo off
-
-node "%~dp0\run" %\*
-

docs/README.md

@@ -1,2 +0,0 @@
-# docs
-

docs/using-docker/README.md

@@ -1,2 +0,0 @@
-# using-docker
-

pioneer/BOUNTIES.md

@@ -1,19 +0,0 @@
-# Bounties
-
-From time-to-time we will add bounties for features.
-
-These are generously provided by the [Web3 Foundation](https://web3.foundation/) and as such employees of Parity or those of the W3F are ineligible for them. (This includes people being by either Party for development or community work, related or un-related to polkadot-js).
-
-The idea is that these bounties should be left open to community participation, so only if there is no outside interest for a specific issue, should those directly or indirectly paid by the W3F for work, attempt to close an issue. (in which case it will be "un-bountied")
-
-Current bounties are tracked by the [!bounty](https://github.com/polkadot-js/apps/labels/%21bounty) label.
-
-## Process
-
-Once listed, the normal [Gitcoin](https://gitcoin.co/) process kicks in. This means application, work and payment is managed by this tool. The values for bounties are determined by the size estimation done by the team.
-
-## Some small requests
-
-Please don't start work on an issue until you have been approved via the gitcoin interface. We generally love enthusiasm and code in the repo, however short-cutting the process does create some issues for the management of the bounties. We certainly don't want to be playing favorites if 2 PRs for the same issue are created at the same time. And in cases where somebody else has been approved and an unapproved PR comes in... well, it gets really murky.
-
-When making changes, please do not force push in your PRs, especially not after a review has been started. We will clone your repo and work from that, doing a simple `pull` on a force-pushed branch ends up being, well, less than simple. We squash merge all PRs, so you do not clutter up the history by using stock-standard pushes to your branch.

pioneer/CHANGELOG.md

@@ -1,124 +0,0 @@
-# 0.36.1
-
-- Api 0.95.1, Util 1.6.1, Extension 0.13.1
-- Support latest contracts ABI (via API), incl. rework of contracts UI
-- Support for Kusama CC2
-- Support for Edgeware mainnet
-- Experimental Ledger support
-- Display forks on explorer (limited to Babe)
-- Change settings to have Save as well as Save & Reload (depending on changes made)
-- Updates to struct & enum rendering (as per extrinsic app)
-- Backup, Password change & Delete don't show for built-in dev accounts
-- Add commissions to the staking overview
-- UI theme update
-- A large number of components refactored for React functional components
-- Allow dismiss of all notifications (via bounty)
-- Migrate all buttons to have icons (via bounty)
-- Proposal submission via modal (via bounty)
-- i18n string extraction (via bounty)
-- adjust signature validity (via bounty)
-- Make the network selection clickable on network name (via bounty)
-- ... and a number of cleanups all around
-
-# 0.35.1
-
-- Api 0.91.1, Util 1.2.1, Extension 0.10.1
-- Support for accounts added via Qr (for instance, the Parity Signer)
-- Support for accounts tied to specific chains (instead of just available to all)
-- GenericAsset app transfers
-- Support for Edgeware with default types
-- Display received heartbeats for validators
-- Allow optional params (really as optional) in RPC toolbox
-- Add Polkascan for Kusama
-- Fix account derivation with `///password`
-- Lots of component & maintainability cleanups
-
-# 0.34.1
-
-- Kusama support
-- Full support for Substrate 2.x & Polkadot 0.5.0 networks
-- Lots of UI updated to support both Substrate 1.x & 2.x chains
-- Add of claims app for Kusama (and Polkadot)
-- Basic Council, Parachains & Treasury apps
-- Moved ui-* packages to react-*
-
-# 0.33.1
-
-- Allow for externally injected accounts (i.e. via extension, polkadot-js & SingleSource)
-- Links to extrnisics & addresses on Polkascan
-- Rework Account & Address layouts with cards
-- Transfer can happen from any point (via Transfer modal)
-- Use new api.derive functions
-- Introduce multi support (most via api.derive.*)
-- Update all account and address modals
-- Add seconding of proposals
-- Staking updates, including un-bonding & withdrawals
-- Update explorer with global query on hash/blocks
-- Add filters on the staking page
-- Vanitygen now supports sr25519 as well
-- Fixes for importing of old JSON
-- Latest @polkadot/util & @polkadot/api
-- A large number of optimizations and smaller fixes
-
-# 0.32.1
-
-- Support for Substrate 1.0 release & metadata v4
-- @polkadot/api 0.77.1
-
-# 0.31.1
-
-- Cleanups, fixes and features around the poc-4 staking module
-- Number of UI enhancements
-
-# 0.30.1
-
-- Staking page indicator for offline nodes (count & block)
-- Rework page tabs and content layouts
-- Cleanup of all UI summary headers
-- Emberic Elem support (replaces Dried Danta)
-
-# 0.29.1
-
-- @polkadot/util & @polkadot/api 0.75.1
-
-# 0.28.1
-
-- Support for substrate 1.0-rc
-
-# 0.27.1
-
-- Bring in new staking & nominating functions
-- Swap default keyring accounts (on creation) to sr25519
-- New faster crypto algorithms
-- Misc. bug fixes all around
-
-# 0.26.1
-
-- Swap keyring to HDKD derivation, mnemonic keys are now not backwards compatible with those created earlier. (Defaults are still for ed25519)
-- Swap crypto to new WASM-backed version (and remove libsodium dependency)
-- UI to allow for derived keys for ed25519 and sr25519
-- New mobile-friendly sidebar
-- Fix issues with nominating (old non-bonds interface)
-
-# 0.25.1
-
-- Swap to publishing -beta.x on merge (non-breaking testing)
-
- # 0.24.1
-
- Storage now handles Option type properly
-
- # 0.23.1
-
- JavaScript console introduced
-
-# 0.22.1
-
-- Use new Compact<Index> transaction format - this requires the latest binaries from either Polkadot or Substrate
-
-# 0.21.1
-
-- PoC-3 support with latest Substrate master & Polkadot master
-- Add support for Charred Cherry (Substrate) and Alexander (Polkadot) testnets
-- Too many changes to mention, master now only supports latest PoC-3 iteration
-- Use https://poc-2.polkadot.io if access is required to PoC-2 era networks

pioneer/CONTRIBUTING.md

@@ -1,45 +0,0 @@
-# Contributing
-
-## What?
-
-Individuals making significant and valuable contributions are given commit-access to a project to contribute as they see fit.
-A project is more like an open wiki than a standard guarded open source project.
-
-## Rules
-
-There are a few basic ground-rules for contributors (including the maintainer(s) of the project):
-
-1. **No `--force` pushes** or modifying the Git history in any way. If you need to rebase, ensure you do it in your own repo.
-2. **Non-master branches**, prefixed with a short name moniker (e.g. `<initials>-<feature>`) must be used for ongoing work.
-3. **All modifications** must be made in a **pull-request** to solicit feedback from other contributors.
-4. A pull-request *must not be merged until CI* has finished successfully.
-
-#### Merging pull requests once CI is successful:
-- A pull request with no large change to logic that is an urgent fix may be merged after a non-author contributor has reviewed it well.
-- No PR should be merged until all reviews' comments are addressed.
-
-#### Reviewing pull requests:
-When reviewing a pull request, the end-goal is to suggest useful changes to the author. Reviews should finish with approval unless there are issues that would result in:
-
-- Buggy behaviour.
-- Undue maintenance burden.
-- Breaking with house coding style.
-- Pessimisation (i.e. reduction of speed as measured in the projects benchmarks).
-- Feature reduction (i.e. it removes some aspect of functionality that a significant minority of users rely on).
-- Uselessness (i.e. it does not strictly add a feature or fix a known issue).
-
-#### Reviews may not be used as an effective veto for a PR because:
-- There exists a somewhat cleaner/better/faster way of accomplishing the same feature/fix.
-- It does not fit well with some other contributors' longer-term vision for the project.
-
-## Releases
-
-Declaring formal releases remains the prerogative of the project maintainer(s).
-
-## Changes to this arrangement
-
-This is an experiment and feedback is welcome! This document may also be subject to pull-requests or changes by contributors where you believe you have something valuable to add or change.
-
-## Heritage
-
-These contributing guidelines are modified from the "OPEN Open Source Project" guidelines for the Level project: [https://github.com/Level/community/blob/master/CONTRIBUTING.md](https://github.com/Level/community/blob/master/CONTRIBUTING.md)

pioneer/packages/README.md

@@ -1,2 +0,0 @@
-# packages
-

pioneer/packages/app-123code.md

@@ -1,23 +0,0 @@
-# @polkadot/app-123code
-
-A simple template to get started with adding an "app" to this UI. It contains the bare minimum for a nicely hackable app \(if you just want to code _somewhere_\) and the steps needed to create, add and register an new app that appears in the UI.
-
-## adding an app
-
-If you want to add a new app to the UI, this is the place to start.
-
-1. Duplicate this `app-123code` folder and give it an appropriate name, in this case we will select `app-example` to keep things clear.
-2. Edit the `apps-example/package.json` app description, i.e. the name, author and relevant overview.
-
-And we have the basic app source setup, time to get the tooling correct.
-
-1. Add the new app to the TypeScript config in root, `tsconfig.json`, i.e. an entry such as `"@polkadot/app-example/*": [ "packages/app-example/src/*" ],`
-
-At this point the app should be buildable, but not quite reachable. The final step is to add it to the actual sidebar in `apps`.
-
-1. In `apps-routing/src` duplicate the `123code.ts` file to `example.ts` and edit it with the appropriate information, including the hash link, name and icon \(any icon name from semantic-ui-react/font-awesome 4 should be appropriate\).
-2. In the above description file, the `isHidden` field needs to be toggled to make it appear - the base template is hidden by default.
-3. Finally add the `template` to the `apps-routing/src/index.ts` file at the appropriate place for both full and light mode \(either optional\)
-
-Yes. After all that we have things hooked up. Run `yarn start` and your new app \(non-coded\) should show up. Now start having fun and building something great.
-

pioneer/packages/app-accounts/src/README.md

@@ -1,2 +0,0 @@
-# src
-

pioneer/packages/app-accounts/src/md/README.md

@@ -1,2 +0,0 @@
-# md
-

pioneer/packages/app-address-book/src/README.md

@@ -1,2 +0,0 @@
-# src
-

pioneer/packages/app-address-book/src/md/README.md

@@ -1,2 +0,0 @@
-# md
-

pioneer/packages/app-claims.md

@@ -1,2 +0,0 @@
-# @polkadot/app-claims
-

pioneer/packages/app-contracts/src/README.md

@@ -1,2 +0,0 @@
-# src
-

pioneer/packages/app-contracts/src/md/README.md

@@ -1,2 +0,0 @@
-# md
-

pioneer/packages/app-council.md

@@ -1,2 +0,0 @@
-# @polkadot/app-council
-

pioneer/packages/app-dashboard.md

@@ -1,23 +0,0 @@
-# @polkadot/app-123code
-
-A simple template to get started with adding an "app" to this UI. It contains the bare minimum for a nicely hackable app \(if you just want to code _somewhere_\) and the steps needed to create, add and register an new app that appears in the UI.
-
-## adding an app
-
-If you want to add a new app to the UI, this is the place to start.
-
-1. Duplicate this `app-123code` folder and give it an appropriate name, in this case we will select `app-example` to keep things clear.
-2. Edit the `apps-example/package.json` app description, i.e. the name, author and relevant overview.
-
-And we have the basic app source setup, time to get the tooling correct.
-
-1. Add the new app to the TypeScript config in root, `tsconfig.json`, i.e. an entry such as `"@polkadot/app-example/*": [ "packages/app-example/src/*" ],`
-
-At this point the app should be buildable, but not quite reachable. The final step is to add it to the actual sidebar in `apps`.
-
-1. In `apps/src/routing/` duplicate the `123code.ts` file to `example.ts` and edit it with the appropriate information, including the hash link, name and icon \(any icon name from semantic-ui-react/font-awesome 4 should be appropriate\).
-2. In the above description file, the `isHidden` field needs to be toggled to make it appear - the base template is hidden by default.
-3. Finally add the `template` to the `apps/src/routing/index.ts` file at the appropriate place for both full and light mode \(either optional\)
-
-Yes. After all that we have things hooked up. Run `yarn start` and your new app \(non-coded\) should show up. Now start having fun and building something great.
-

pioneer/packages/app-democracy/src/README.md

@@ -1,2 +0,0 @@
-# src
-

pioneer/packages/app-democracy/src/md/README.md

@@ -1,2 +0,0 @@
-# md
-

pioneer/packages/app-explorer.md

@@ -1,2 +0,0 @@
-# @polkadot/app-explorer
-

pioneer/packages/app-extrinsics.md

@@ -1,2 +0,0 @@
-# @polkadot/app-extrinsics
-

pioneer/packages/app-generic-asset.md

@@ -1,4 +0,0 @@
-# @polkadot/app-generic-asset
-
-A basic GenericAsset transfer application, allowing the movement of funds from one account to another.
-

pioneer/packages/app-js.md

@@ -1,2 +0,0 @@
-# @polkadot/app-js
-

pioneer/packages/app-parachains.md

@@ -1,2 +0,0 @@
-# @polkadot/app-parachains
-

pioneer/packages/app-settings/src/README.md

@@ -1,2 +0,0 @@
-# src
-

pioneer/packages/app-settings/src/md/README.md

@@ -1,2 +0,0 @@
-# md
-

pioneer/packages/app-staking/src/README.md

@@ -1,2 +0,0 @@
-# src
-

pioneer/packages/app-staking/src/md/README.md

@@ -1,2 +0,0 @@
-# md
-

pioneer/packages/app-storage.md

@@ -1,2 +0,0 @@
-# @polkadot/app-storage
-

pioneer/packages/app-sudo.md

@@ -1,2 +0,0 @@
-# @polkadot/app-sudo
-

pioneer/packages/app-toolbox.md

@@ -1,2 +0,0 @@
-# @polkadot/app-toolbox
-

pioneer/packages/app-transfer.md

@@ -1,4 +0,0 @@
-# @polkadot/app-transfer
-
-A basic DOT transfer application, allowing the movement of funds from one account to another.
-

pioneer/packages/app-treasury/src/README.md

@@ -1,2 +0,0 @@
-# src
-

pioneer/packages/app-treasury/src/md/README.md

@@ -1,2 +0,0 @@
-# md
-

pioneer/packages/apps-routing.md

@@ -1,4 +0,0 @@
-# @polkadot/apps-routing
-
-The routing config for the application
-

pioneer/packages/apps.md

@@ -1,2 +0,0 @@
-# @polkadot/apps
-

pioneer/packages/joy-election.md

@@ -1,2 +0,0 @@
-# Election module for Joystream node
-

pioneer/packages/joy-forum.md

@@ -1,4 +0,0 @@
-# Forum module for Joystream node
-
-Forum allows to create categories and subcategories, start discussion threads and reply to others.
-

pioneer/packages/joy-help.md

@@ -1,4 +0,0 @@
-# Help module for Joystream node
-
-Here you can find a help and the latest news related to Joystream community and software.
-

pioneer/packages/joy-media.md

@@ -1,4 +0,0 @@
-# Media content module for Joystream node
-
-This module works with multi-media content such as audio and video.
-

pioneer/packages/joy-members.md

@@ -1,2 +0,0 @@
-# Membership module for Joystream node
-

pioneer/packages/joy-pages/src/README.md

@@ -1,2 +0,0 @@
-# src
-

pioneer/packages/joy-pages/src/md/Privacy.md

@@ -1,52 +1,58 @@
-# Privacy and Cookies
+# Privacy
+
+## Privacy and Cookies
+
 **Last updated on the 17th of April 2019**
 
 Jsgenesis values your privacy.
 
-This Privacy Policy ("Privacy Policy") and Cookie Policy ("Cookie Policy") explains how Jsgenesis AS ("Jsgenesis", "Company", "We", "Us", "Our") collect and use data and information when you ("User) use on or any of the Joystream products, developed in the GitHub organization [Joystream](https://github.com/JoyStream). These products (collectively "Software") include, but are not limited to, [all pages under the joystream.org domain](https://www.joystream.org/) ("Website"), the [Joyful node](https://github.com/Joystream/substrate-node-joystream) ("Full Node"), the [Colossus Storage Node](https://github.com/Joystream/storage-node-joystream) ("Storage node"), and the Pioneer User Interface, either [self hosted](https://github.com/Joystream/apps) or [hosted by Us](http://testnet.joystream.org/) ("App").
+This Privacy Policy \("Privacy Policy"\) and Cookie Policy \("Cookie Policy"\) explains how Jsgenesis AS \("Jsgenesis", "Company", "We", "Us", "Our"\) collect and use data and information when you \("User\) use on or any of the Joystream products, developed in the GitHub organization [Joystream](https://github.com/JoyStream). These products \(collectively "Software"\) include, but are not limited to, [all pages under the joystream.org domain](https://www.joystream.org/) \("Website"\), the [Joyful node](https://github.com/Joystream/substrate-node-joystream) \("Full Node"\), the [Colossus Storage Node](https://github.com/Joystream/storage-node-joystream) \("Storage node"\), and the Pioneer User Interface, either [self hosted](https://github.com/Joystream/apps) or [hosted by Us](http://testnet.joystream.org/) \("App"\).
 
 Relevant to the Privacy Policy and Cookie Policy are the following terms:
-* The term "Blockchain" refers to the blockchain(s) assembled by the Full Node.
+
+* The term "Blockchain" refers to the blockchain\(s\) assembled by the Full Node.
 * The term "Content" refers to media files accessible through our Software.
-* The term "Keys" refers to a private/public cryptographic keypair, that Users can generate in order to write (and decrypt data) on the Blockchain.
+* The term "Keys" refers to a private/public cryptographic keypair, that Users can generate in order to write \(and decrypt data\) on the Blockchain.
 * The term "Membership" refers to tying your Keys to a public profile, allowing users to access Content and interact with the Blockchain.
 * The term "Memo" refers to a markdown enabled text field, where users can input data tied to their Keys.
 
+## Privacy Policy
 
-# Privacy Policy
 **Last updated on the 19th of May 2020**
 
-## 1. Agreement to the Policy
+### 1. Agreement to the Policy
+
 By using any of Our Software, the User are accepting this Privacy Policy. If you are acting on behalf of another company or an employer, you must have the rights to act on their behalf. The Privacy Policy is not extended to any of our newsletters, where Users are bound by the [privacy policy](https://mailchimp.com/legal/privacy/) of [Mailchimp](https://mailchimp.com/).
 
 The Privacy Policy does not apply to any other third party services including, but not limited to, applications, websites, tools or software, even if accessible through links or guides in our Software.
 
-## 2. Changes to Policy
+### 2. Changes to Policy
+
 This Privacy Policy may be changed at the sole discretion of Company. If any material changes are made, the User will be notified in the Service that is used. Note that adding new products to be included in the term Software , e.g. a new User facing product replacing the App or a new tool for uploading Content, is not considered material as it will not affect Users unless they adopt the new product. Changing softare names, terminology used in this Privacy Policy, and changin link locations are aslo examples of non-material changes.
 
-## 3. Information Collected
-All data written to the Blockchain, is implicitly collected not only by Company, but also anyone else in the world that is running the Full Node locally, or accessed via the App or a third party.
-This includes, but is not limited to, Content hashes, Membership profile, Memo field, and any other way a User can record data on the Blockchain.
+### 3. Information Collected
+
+All data written to the Blockchain, is implicitly collected not only by Company, but also anyone else in the world that is running the Full Node locally, or accessed via the App or a third party. This includes, but is not limited to, Content hashes, Membership profile, Memo field, and any other way a User can record data on the Blockchain.
 
 Company uses [Google Analytics](https://marketingplatform.google.com/about/analytics/), with IP anonymization, to collect statistics on Website and the version of App hosted by us. All customizable data sharing settings are turned off to improve the privacy of Users.
 
 Company will not sell your data for advertising, or other purposes.
 
+## Cookie Policy
 
-# Cookie Policy
 **Last updated on the 17th of April 2019**
 
-Company uses cookies on Website and App when hosted by Us (collectively "Service"). By using the Service, you consent to the use of cookies.
+Company uses cookies on Website and App when hosted by Us \(collectively "Service"\). By using the Service, you consent to the use of cookies.
 
 Our Cookies Policy explains what cookies are, how we use cookies, how third-parties we partner with may use cookies on the Service, your choices regarding cookies and further information about cookies.
 
-## 1. What are Cookies?
+### 1. What are Cookies?
 
 Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the Service or a third-party to recognize you and make your next visit easier and the Service more useful to you.
 
-Cookies can be *persistent* or *session* cookies.
+Cookies can be _persistent_ or _session_ cookies.
 
-## 2. How we use Cookies
+### 2. How we use Cookies
 
 We use cookies for the following purposes our Service:
 
@@ -54,26 +60,26 @@ We use cookies for the following purposes our Service:
 * Store preferences
 * Persistant local storage of Keys and Membership.
 
-## 3. Third-party Cookies
+### 3. Third-party Cookies
 
 In addition to our own cookies, we also use various third-party cookies to report usage statistics of the Service, deliver advertisements on and through the Service, and so on. They include:
 
 * Google Analytics
-* Mailchimp (Only when signing up for any of our newsletters)
+* Mailchimp \(Only when signing up for any of our newsletters\)
 * Godaddy
 
 Please see Item 3. of the Privacy Policy for more information on the extent of these providers.
 
-## Your Regarding Cookies
+### Your Regarding Cookies
 
 If you would like to delete cookies or instruct your web browser to delete or refuse cookies, please visit the help pages of your web browser.
 
 Please note, however, that if you delete cookies or refuse to accept them, you might not be able to use all of the features we offer, you may not be able to store your preferences, and some of our pages might not display properly.
 
-
 MORE INFORMATION About Cookies
 
 You can learn more about cookies and the following third-party websites:
 
 * [AllAboutCookies](http://www.allaboutcookies.org/)
 * [Network Advertising Initiative](http://www.networkadvertising.org/)
+

pioneer/packages/joy-pages/src/md/README.md

@@ -1,2 +0,0 @@
-# md
-

pioneer/packages/joy-pages/src/md/ToS.md

@@ -1,40 +1,40 @@
 # Terms of Service
+
 **Last updated on the 17th of April 2019**
 
-The Terms of Service ("Agreement") is a binding obligation between you ("User") and Jsgenesis AS ("Company", "We", "Us", "Our") for use of our Products. These products (collectively "Software") include [all pages under the joystream.org domain](https://www.joystream.org/) ("Website"), the [Joyful node](https://github.com/Joystream/substrate-node-joystream) ("Full node"), the [Colossus Storage Node](https://github.com/Joystream/storage-node-joystream) ("Storage node"), and the Pioneer User Interface, either [self hosted ](https://github.com/Joystream/apps) or [hosted by Us](http://testnet.joystream.org/) ("App").
+The Terms of Service \("Agreement"\) is a binding obligation between you \("User"\) and Jsgenesis AS \("Company", "We", "Us", "Our"\) for use of our Products. These products \(collectively "Software"\) include [all pages under the joystream.org domain](https://www.joystream.org/) \("Website"\), the [Joyful node](https://github.com/Joystream/substrate-node-joystream) \("Full node"\), the [Colossus Storage Node](https://github.com/Joystream/storage-node-joystream) \("Storage node"\), and the Pioneer User Interface, either [self hosted ](https://github.com/Joystream/apps) or [hosted by Us](http://testnet.joystream.org/) \("App"\).
 
 ## 1. Agreement to Terms
+
 By using this Software, the User are agreeing to be bound by this Agreement. If you are acting on behalf of another company or an employer, you must have the rights to act on their behalf.
 
 ## 2. Changes to Terms
+
 This Agreement may be changed at the sole discretion of Company without notice. Your continued use of our Software is a confirmation of Users acceptance of the newest Agreement.
 
 ## 3. Privacy Policy
-Please see our [privacy policy](https://joystream.org/privacy-cookies) ("Privacy Policy") for information regarding privacy.
+
+Please see our [privacy policy](https://joystream.org/privacy-cookies) \("Privacy Policy"\) for information regarding privacy.
 
 ## 4. Membership
-By generating private/public cryptographic keys ("Keys") or applying for a membership account ("Membershp"), you accept the risk of losing access to your Keys and Membership. Reasons include, but is not limited to:
-  1. Losing passwords
-  2. Losing recovery seeds or mnemonics
-  3. Deleting accounts and backups
-  4. Security breaches
-   
+
+By generating private/public cryptographic keys \("Keys"\) or applying for a membership account \("Membershp"\), you accept the risk of losing access to your Keys and Membership. Reasons include, but is not limited to: 1. Losing passwords 2. Losing recovery seeds or mnemonics 3. Deleting accounts and backups 4. Security breaches
+
 Under no circumstance will Company take any responsiblity for loss resulting of losing access to Membership or Keys.
 
 ## 5. User Conduct
 
-By using any of Our Software, you agree to not state, write, link to, download, distribute, share or encourage other users to state, write, link to, download, distribute, share or encourage anything that:
-1. breach or infringe any copyright or intellectual property of any third party.
-2. is abusive, malicious, threatening or unlawful in any way.
+By using any of Our Software, you agree to not state, write, link to, download, distribute, share or encourage other users to state, write, link to, download, distribute, share or encourage anything that: 1. breach or infringe any copyright or intellectual property of any third party. 2. is abusive, malicious, threatening or unlawful in any way.
 
-Company has not reviewed all content of this website, and is not responsible for content submitted or provided by individuals or groups not directly tied to them. 
+Company has not reviewed all content of this website, and is not responsible for content submitted or provided by individuals or groups not directly tied to them.
 
 ## 6. Responsibilites and Risks
 
-In no event shall Company, its contractors, employees or owners be liable for any damage or loss of any kind to User arising out of the use or inability to use any Software made by Company. 
+In no event shall Company, its contractors, employees or owners be liable for any damage or loss of any kind to User arising out of the use or inability to use any Software made by Company.
 
 In no event shall Company, its contractors, employees or owners be liable for any damage or loss of any kind to User resulting of clicking links, following guides, using software or doing anything else recommended by Company.
 
 ## 7. Governing Law
 
-These terms and conditions are governed by and construed in accordance with the laws of Norway.
+These terms and conditions are governed by and construed in accordance with the laws of Norway.
+

pioneer/packages/joy-pages/src/md/privacy.md

@@ -1,85 +0,0 @@
-# Privacy
-
-## Privacy and Cookies
-
-**Last updated on the 17th of April 2019**
-
-Jsgenesis values your privacy.
-
-This Privacy Policy \("Privacy Policy"\) and Cookie Policy \("Cookie Policy"\) explains how Jsgenesis AS \("Jsgenesis", "Company", "We", "Us", "Our"\) collect and use data and information when you \("User\) use on or any of the Joystream products, developed in the GitHub organization [Joystream](https://github.com/JoyStream). These products \(collectively "Software"\) include, but are not limited to, [all pages under the joystream.org domain](https://www.joystream.org/) \("Website"\), the [Joyful node](https://github.com/Joystream/substrate-node-joystream) \("Full Node"\), the [Colossus Storage Node](https://github.com/Joystream/storage-node-joystream) \("Storage node"\), and the Pioneer User Interface, either [self hosted](https://github.com/Joystream/apps) or [hosted by Us](http://testnet.joystream.org/) \("App"\).
-
-Relevant to the Privacy Policy and Cookie Policy are the following terms:
-
-* The term "Blockchain" refers to the blockchain\(s\) assembled by the Full Node.
-* The term "Content" refers to media files accessible through our Software.
-* The term "Keys" refers to a private/public cryptographic keypair, that Users can generate in order to write \(and decrypt data\) on the Blockchain.
-* The term "Membership" refers to tying your Keys to a public profile, allowing users to access Content and interact with the Blockchain.
-* The term "Memo" refers to a markdown enabled text field, where users can input data tied to their Keys.
-
-## Privacy Policy
-
-**Last updated on the 19th of May 2020**
-
-### 1. Agreement to the Policy
-
-By using any of Our Software, the User are accepting this Privacy Policy. If you are acting on behalf of another company or an employer, you must have the rights to act on their behalf. The Privacy Policy is not extended to any of our newsletters, where Users are bound by the [privacy policy](https://mailchimp.com/legal/privacy/) of [Mailchimp](https://mailchimp.com/).
-
-The Privacy Policy does not apply to any other third party services including, but not limited to, applications, websites, tools or software, even if accessible through links or guides in our Software.
-
-### 2. Changes to Policy
-
-This Privacy Policy may be changed at the sole discretion of Company. If any material changes are made, the User will be notified in the Service that is used. Note that adding new products to be included in the term Software , e.g. a new User facing product replacing the App or a new tool for uploading Content, is not considered material as it will not affect Users unless they adopt the new product. Changing softare names, terminology used in this Privacy Policy, and changin link locations are aslo examples of non-material changes.
-
-### 3. Information Collected
-
-All data written to the Blockchain, is implicitly collected not only by Company, but also anyone else in the world that is running the Full Node locally, or accessed via the App or a third party. This includes, but is not limited to, Content hashes, Membership profile, Memo field, and any other way a User can record data on the Blockchain.
-
-Company uses [Google Analytics](https://marketingplatform.google.com/about/analytics/), with IP anonymization, to collect statistics on Website and the version of App hosted by us. All customizable data sharing settings are turned off to improve the privacy of Users.
-
-Company will not sell your data for advertising, or other purposes.
-
-## Cookie Policy
-
-**Last updated on the 17th of April 2019**
-
-Company uses cookies on Website and App when hosted by Us \(collectively "Service"\). By using the Service, you consent to the use of cookies.
-
-Our Cookies Policy explains what cookies are, how we use cookies, how third-parties we partner with may use cookies on the Service, your choices regarding cookies and further information about cookies.
-
-### 1. What are Cookies?
-
-Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the Service or a third-party to recognize you and make your next visit easier and the Service more useful to you.
-
-Cookies can be _persistent_ or _session_ cookies.
-
-### 2. How we use Cookies
-
-We use cookies for the following purposes our Service:
-
-* Provide Analytics
-* Store preferences
-* Persistant local storage of Keys and Membership.
-
-### 3. Third-party Cookies
-
-In addition to our own cookies, we also use various third-party cookies to report usage statistics of the Service, deliver advertisements on and through the Service, and so on. They include:
-
-* Google Analytics
-* Mailchimp \(Only when signing up for any of our newsletters\)
-* Godaddy
-
-Please see Item 3. of the Privacy Policy for more information on the extent of these providers.
-
-### Your Regarding Cookies
-
-If you would like to delete cookies or instruct your web browser to delete or refuse cookies, please visit the help pages of your web browser.
-
-Please note, however, that if you delete cookies or refuse to accept them, you might not be able to use all of the features we offer, you may not be able to store your preferences, and some of our pages might not display properly.
-
-MORE INFORMATION About Cookies
-
-You can learn more about cookies and the following third-party websites:
-
-* [AllAboutCookies](http://www.allaboutcookies.org/)
-* [Network Advertising Initiative](http://www.networkadvertising.org/)
-

pioneer/packages/joy-pages/src/md/tos.md

@@ -1,40 +0,0 @@
-# Terms of Service
-
-**Last updated on the 17th of April 2019**
-
-The Terms of Service \("Agreement"\) is a binding obligation between you \("User"\) and Jsgenesis AS \("Company", "We", "Us", "Our"\) for use of our Products. These products \(collectively "Software"\) include [all pages under the joystream.org domain](https://www.joystream.org/) \("Website"\), the [Joyful node](https://github.com/Joystream/substrate-node-joystream) \("Full node"\), the [Colossus Storage Node](https://github.com/Joystream/storage-node-joystream) \("Storage node"\), and the Pioneer User Interface, either [self hosted ](https://github.com/Joystream/apps) or [hosted by Us](http://testnet.joystream.org/) \("App"\).
-
-## 1. Agreement to Terms
-
-By using this Software, the User are agreeing to be bound by this Agreement. If you are acting on behalf of another company or an employer, you must have the rights to act on their behalf.
-
-## 2. Changes to Terms
-
-This Agreement may be changed at the sole discretion of Company without notice. Your continued use of our Software is a confirmation of Users acceptance of the newest Agreement.
-
-## 3. Privacy Policy
-
-Please see our [privacy policy](https://joystream.org/privacy-cookies) \("Privacy Policy"\) for information regarding privacy.
-
-## 4. Membership
-
-By generating private/public cryptographic keys \("Keys"\) or applying for a membership account \("Membershp"\), you accept the risk of losing access to your Keys and Membership. Reasons include, but is not limited to: 1. Losing passwords 2. Losing recovery seeds or mnemonics 3. Deleting accounts and backups 4. Security breaches
-
-Under no circumstance will Company take any responsiblity for loss resulting of losing access to Membership or Keys.
-
-## 5. User Conduct
-
-By using any of Our Software, you agree to not state, write, link to, download, distribute, share or encourage other users to state, write, link to, download, distribute, share or encourage anything that: 1. breach or infringe any copyright or intellectual property of any third party. 2. is abusive, malicious, threatening or unlawful in any way.
-
-Company has not reviewed all content of this website, and is not responsible for content submitted or provided by individuals or groups not directly tied to them.
-
-## 6. Responsibilites and Risks
-
-In no event shall Company, its contractors, employees or owners be liable for any damage or loss of any kind to User arising out of the use or inability to use any Software made by Company.
-
-In no event shall Company, its contractors, employees or owners be liable for any damage or loss of any kind to User resulting of clicking links, following guides, using software or doing anything else recommended by Company.
-
-## 7. Governing Law
-
-These terms and conditions are governed by and construed in accordance with the laws of Norway.
-

pioneer/packages/joy-proposals.md

@@ -1,2 +0,0 @@
-# Proposals module for Joystream node
-

pioneer/packages/joy-roles.md

@@ -1,2 +0,0 @@
-# @polkadot/joy-roles
-

pioneer/packages/joy-settings.md

@@ -1,41 +0,0 @@
-# @polkadot/ui-settings
-
-Manages app settings including endpoints, themes and prefixes
-
-## Usage Example
-
-User preferences are set as a settings object in the browser's local storage.
-
-```text
-import settings from '@polkadot/ui-settings';
-
-render () {
-  // get api endpoint for the selected chain
-  const WS_URL = settings.apiUrl();
-
-  // get the selected il8n language
-  const language = settings.il8nLang();
-
-  // get all available il8n languages
-  const languages = settings.availableLanguages();
-
-  // update settings
-  const updatedSettings = {
-    ...settings,
-    i18nLang: 'Arabic'
-  }
-  settings.set(updatedSettings);
-
-  // NOTE: API currently does not handle hot reconnecting properly,
-  so you need to manually reload the page after updating settings.
-  window.location.reload();
-}
-```
-
-## Used by
-
-Apps that currently use the settings package
-
-* \[polkadot-js/apps\]\('[https://www.github.com/polkadot-js/apps](https://www.github.com/polkadot-js/apps)'\)
-* [paritytech/substrate-light-ui](https://github.com/paritytech/substrate-light-ui)
-

pioneer/packages/joy-storage.md

@@ -1,2 +0,0 @@
-# @polkadot/joy-actors
-

pioneer/packages/joy-utils.md

@@ -1,2 +0,0 @@
-# Utils for Joystream node
-

pioneer/packages/react-api.md

@@ -1,6 +0,0 @@
-# @polkadot/react-api
-
-WARNING: This is is not deemed stable yet for external use in React-based apps and still included in the [polkadot-js/apps](https://github.com/polkadot-js/apps) repo. Since these are generic HOC components for React, they will move to the [polkadot-js/ui](https://github.com/polkadot-js/ui) repo once deemed stable and usable by external projects.
-
-For the existing sharable components usable in external React-based projects, take a look at the [polkadot-js/ui documentation](https://polkadot.js.org/ui/)
-

pioneer/packages/react-components.md

@@ -1,6 +0,0 @@
-# @polkadot/react-components
-
-WARNING: This is an internal package to [polkadot-js/apps](https://github.com/polkadot-js/apps) so is not inteded \(yet\) for broad use.
-
-For the existing sharable components usable in external React-based projects, take a look at the [polkadot-js/ui documentation](https://polkadot.js.org/ui/)
-

pioneer/packages/react-params.md

@@ -1,6 +0,0 @@
-# @polkadot/react-params
-
-WARNING: This is an internal package to [polkadot-js/apps](https://github.com/polkadot-js/apps) so is not inteded \(yet\) for broad use.
-
-For the existing sharable components usable in external React-based projects, take a look at the [polkadot-js/ui documentation](https://polkadot.js.org/ui/)
-

pioneer/packages/react-query.md

@@ -1,43 +0,0 @@
-# @polkadot/react-query
-
-WARNING: This is an internal package to [polkadot-js/apps](https://github.com/polkadot-js/apps) so is not inteded \(yet\) for broad use. Since these are generic components, they will move to the [polkadot-js/ui](https://github.com/polkadot-js/ui) repo once deemed stable and usable.
-
-For the existing sharable components usable in external React-based projects, take a look at the [polkadot-js/ui documentation](https://polkadot.js.org/ui/)
-
-## Overview
-
-A collection of RxJS enabled React components that operate with the [@polkadot/api-rx](https://github.com/polkadot-js/api) library. It automatically manages subscriptions on behalf of the developer, providing a number of unstyled components that can be used to construct UIs.
-
-## Usage
-
-Basic usage entails creating a `ContextProvider` and just using the components. For instance, to display the current node time,
-
-```javascript
-import React from 'react';
-import ReactDOM from 'react-dom';
-
-import { Api, NodeTime } from '@polkadot/react-query';
-
-...
-ReactDOM.render(
-  <Api>
-    <NodeTime />
-  </Api>,
-  document.querySelector('#container')
-);
-...
-```
-
-All components are provided unstyled making no assumptions on the actual use, however they all support \(optionally\) the `label`, `className` and `style` attributes, that can be used to style to component.
-
-```javascript
-...
-ReactDOM.render(
-  <Api>
-    <NodeTime className='rx-time' label='current node time:' />
-  </Api>,
-  document.querySelector('#container')
-);
-...
-```
-

pioneer/packages/react-signer.md

@@ -1,6 +0,0 @@
-# @polkadot/react-signer
-
-WARNING: This is an internal package to [polkadot-js/apps](https://github.com/polkadot-js/apps) so is not inteded \(yet\) for broad use.
-
-For the existing sharable components usable in external React-based projects, take a look at the [polkadot-js/ui documentation](https://polkadot.js.org/ui/)
-

runtime/CHANGELOG.md

@@ -1,43 +1,57 @@
-### Version 6.15.0 - Constantinople runtime upgrade A - June 2020
-- Updated runtime to sort out type name clashes between the proposal discussion module
-and forum module, in preparing to roll out proposal discussion system in pioneer.
-- Increased ROLE_PARAMETERS_REWARD_MAX_VALUE to 100,000
-
-### Version 6.13.0 - (Constantinople) runtime upgrade - May 20th 2020
-- New proposal system that strengthens the governance structure of the platform
-- Adjusted inflation curve to better reflect a new realistic economic system for the platform
-
-### Version 6.8.0 (Rome release - new chain) - March 9th 2020
-- New versioned and permissioned content mangement system that powers a new media experience.
-- Content Working Group - introduces staked content curator roles to maintain quality of content and ensure that is meets the platform's terms of service.
-- Update of core substrate to pre-release of version 2.0 - [c37bb08](https://github.com/paritytech/substrate/commit/c37bb08535c49a12320af7facfd555ce05cce2e8)
-
-### Version 5.4.0 (Acropolis) - Athens testnet update 3 - June 22n 2019
-- New Forum - v1.0.0
-- Discovery Service to support new Storage Provider implementation.
-- Removing all previously uploaded content
-
-### Version 5.3.0 - Athens testnet update 2 - April 27th 2019
-- Fix to configure an onchain primary storage provider liason to work around incomplete storage server implementation.
-
-### Version 5.2.0 - Athens testnet update 1 - April 17th 2019
-- Fix account locking for staked roles to allow storage providers to submit transaction
-- Update substrate version to `6dfc3e8b057bb00322136251a0f10305fbb1ad8f` from v1 branch
-
-### Version 5.1.0 - Athens testnet release - April 14th 2019
-- Storage Role
-- Update to substrate version at `89bbb7b6d0e076f0eda736b330f5f792aa2e2991`
-
-### Version 4 - Bug Fixes - March 4th 2019 - `9941dd`
- - Allow illiquid accounts to pay transaction fees. Fixes unstaking and setting memo, by permitting extrinsics which do not require more than a transaction fee to be accepted into mempool.
- - Updated Cargo dependencies to use forked substrate repo `github.com/joystream/substrate`
-
- On-chain runtime upgrade performed with sudo `consensus::setCode()`
-
-### Version 3 - Sparta - March 1st 2019 - `1ca4cc`
-  - Basic substrate node - based on substrate `1ca4cc0a16a357782bb1028bb57376594ca232a0`
-  - Block Authoring - only Aura (enabling GRANDPA in future release)
-  - Council Elections
-  - Council Runtime upgrade proposal
-  - Simple PoS validator staking
-  - Memo (account status message)
+# CHANGELOG
+
+## Version 6.15.0 - Constantinople runtime upgrade A - June 2020
+
+* Updated runtime to sort out type name clashes between the proposal discussion module
+
+  and forum module, in preparing to roll out proposal discussion system in pioneer.
+
+* Increased ROLE\_PARAMETERS\_REWARD\_MAX\_VALUE to 100,000
+
+## Version 6.13.0 - \(Constantinople\) runtime upgrade - May 20th 2020
+
+* New proposal system that strengthens the governance structure of the platform
+* Adjusted inflation curve to better reflect a new realistic economic system for the platform
+
+## Version 6.8.0 \(Rome release - new chain\) - March 9th 2020
+
+* New versioned and permissioned content mangement system that powers a new media experience.
+* Content Working Group - introduces staked content curator roles to maintain quality of content and ensure that is meets the platform's terms of service.
+* Update of core substrate to pre-release of version 2.0 - [c37bb08](https://github.com/paritytech/substrate/commit/c37bb08535c49a12320af7facfd555ce05cce2e8)
+
+## Version 5.4.0 \(Acropolis\) - Athens testnet update 3 - June 22n 2019
+
+* New Forum - v1.0.0
+* Discovery Service to support new Storage Provider implementation.
+* Removing all previously uploaded content
+
+## Version 5.3.0 - Athens testnet update 2 - April 27th 2019
+
+* Fix to configure an onchain primary storage provider liason to work around incomplete storage server implementation.
+
+## Version 5.2.0 - Athens testnet update 1 - April 17th 2019
+
+* Fix account locking for staked roles to allow storage providers to submit transaction
+* Update substrate version to `6dfc3e8b057bb00322136251a0f10305fbb1ad8f` from v1 branch
+
+## Version 5.1.0 - Athens testnet release - April 14th 2019
+
+* Storage Role
+* Update to substrate version at `89bbb7b6d0e076f0eda736b330f5f792aa2e2991`
+
+## Version 4 - Bug Fixes - March 4th 2019 - `9941dd`
+
+* Allow illiquid accounts to pay transaction fees. Fixes unstaking and setting memo, by permitting extrinsics which do not require more than a transaction fee to be accepted into mempool.
+* Updated Cargo dependencies to use forked substrate repo `github.com/joystream/substrate`
+
+  On-chain runtime upgrade performed with sudo `consensus::setCode()`
+
+## Version 3 - Sparta - March 1st 2019 - `1ca4cc`
+
+* Basic substrate node - based on substrate `1ca4cc0a16a357782bb1028bb57376594ca232a0`
+* Block Authoring - only Aura \(enabling GRANDPA in future release\)
+* Council Elections
+* Council Runtime upgrade proposal
+* Simple PoS validator staking
+* Memo \(account status message\)
+

runtime/README.md

@@ -1,2 +0,0 @@
-# runtime
-

runtime/changelog.md

@@ -1,57 +0,0 @@
-# CHANGELOG
-
-## Version 6.15.0 - Constantinople runtime upgrade A - June 2020
-
-* Updated runtime to sort out type name clashes between the proposal discussion module
-
-  and forum module, in preparing to roll out proposal discussion system in pioneer.
-
-* Increased ROLE\_PARAMETERS\_REWARD\_MAX\_VALUE to 100,000
-
-## Version 6.13.0 - \(Constantinople\) runtime upgrade - May 20th 2020
-
-* New proposal system that strengthens the governance structure of the platform
-* Adjusted inflation curve to better reflect a new realistic economic system for the platform
-
-## Version 6.8.0 \(Rome release - new chain\) - March 9th 2020
-
-* New versioned and permissioned content mangement system that powers a new media experience.
-* Content Working Group - introduces staked content curator roles to maintain quality of content and ensure that is meets the platform's terms of service.
-* Update of core substrate to pre-release of version 2.0 - [c37bb08](https://github.com/paritytech/substrate/commit/c37bb08535c49a12320af7facfd555ce05cce2e8)
-
-## Version 5.4.0 \(Acropolis\) - Athens testnet update 3 - June 22n 2019
-
-* New Forum - v1.0.0
-* Discovery Service to support new Storage Provider implementation.
-* Removing all previously uploaded content
-
-## Version 5.3.0 - Athens testnet update 2 - April 27th 2019
-
-* Fix to configure an onchain primary storage provider liason to work around incomplete storage server implementation.
-
-## Version 5.2.0 - Athens testnet update 1 - April 17th 2019
-
-* Fix account locking for staked roles to allow storage providers to submit transaction
-* Update substrate version to `6dfc3e8b057bb00322136251a0f10305fbb1ad8f` from v1 branch
-
-## Version 5.1.0 - Athens testnet release - April 14th 2019
-
-* Storage Role
-* Update to substrate version at `89bbb7b6d0e076f0eda736b330f5f792aa2e2991`
-
-## Version 4 - Bug Fixes - March 4th 2019 - `9941dd`
-
-* Allow illiquid accounts to pay transaction fees. Fixes unstaking and setting memo, by permitting extrinsics which do not require more than a transaction fee to be accepted into mempool.
-* Updated Cargo dependencies to use forked substrate repo `github.com/joystream/substrate`
-
-  On-chain runtime upgrade performed with sudo `consensus::setCode()`
-
-## Version 3 - Sparta - March 1st 2019 - `1ca4cc`
-
-* Basic substrate node - based on substrate `1ca4cc0a16a357782bb1028bb57376594ca232a0`
-* Block Authoring - only Aura \(enabling GRANDPA in future release\)
-* Council Elections
-* Council Runtime upgrade proposal
-* Simple PoS validator staking
-* Memo \(account status message\)
-

types.md

@@ -1,59 +0,0 @@
-# @joystream/types
-
-The types package is required to register the custom Substrate runtime types when working with [`@polkadot/api`](https://www.npmjs.com/package/@polkadot/api#registering-custom-types) to communicate with a Joystream full node.
-
-## Installation
-
-Add the package as a dependency in your project.
-
-```text
-yarn add @joystream/types
-
-# or
-
-npm install --save @joystream/types
-```
-
-## Registering the types
-
-Call `registerJoystreamTypes()` before creating a Polkadot API client.
-
-```javascript
-import { registerJoystreamTypes } from '@joystream/types';
-import { ApiPromise, WsProvider } from '@polkadot/api';
-
-async function main () {
-  // Initialise the provider to connect to the local node
-  const provider = new WsProvider('ws://127.0.0.1:9944');
-
-  // Register types before creating the API
-  registerJoystreamTypes();
-
-  // Create the API and wait until ready
-  const api = await ApiPromise.create(provider);
-
-  // Retrieve the chain & node information information via RPC calls
-  const [chain, nodeName, nodeVersion] = await Promise.all([
-    api.rpc.system.chain(),
-    api.rpc.system.name(),
-    api.rpc.system.version()
-  ]);
-
-  console.log(`Chain ${chain} using ${nodeName} v${nodeVersion}`);
-}
-
-main();
-```
-
-## Publishing Instructions
-
-The package is published with typescipt sources pre-compiled, automated with prepublish hook in package.json
-
-```text
-npm publish
-```
-
-## Users
-
-See [joystream-api-examples](https://github.com/Joystream/joystream-api-examples) for some additional examples on usage.
-