Revert "Initial Draft of Community Roadmap"

This reverts commit a8579681307296eeaac7f2b443dc13830c68c34f.

community-roadmap/process.md

@@ -1,25 +0,0 @@
-## Community Roadmap Process
-
-This will eventually outline the process by which the Community Roadmap is developed. For now it is a very rough outline and some basic thoughts about aspects that should probably be discussed.
-
-#### Initial thoughts
-- Where to discuss? Should we have a dedicated Discord channel?
-- Where to draft? Community repo and/or Notion?
-	- Should we have a dedicated repo for this?
-- Where to store? Community repo & Notion?
-- We really need something better than .md files on Github, it may be worth looking at a solution like Gitbook or Docusaurus so users can easily navigate and maybe it would make contributing easier.
-- How to agree on phases (`initial rollout`, `stability phase`, `initial growth`)?
-- How to deal with time when planning and structuring things? (blockheights, weeks, months?)
-- How to agree on roles necessary to make governance system work well (i.e. Council Secretary)
-- How do we structure projects and initiatives? (i.e. a specific initiative like Joystreamstats, a custom Atlas fork that supports music)?
-- What are the minimum number of proposals required to get mainnet operational? (This would mean opening/hiring proposals, mint proposals but `not` runtime/system related proposals/sudo actions that JSG would do)
-
-#### Draft Process
-1. Proposal to create initial discussion
-2. Create Draft/Template
-3. Gather community feedback and summarize
-4. Submit to Notion, label to be changed to `Draft Submitted`
-5. Upon discussion timeframe (What time period?) the draft should then be submitted as a PR to the community repo and submitted via a proposal.
-6. If proposal approved by council, label to be changed to `Approved via testnet council` and `community repo` persons to merge PR.
-
-

community-roadmap/readme.md

@@ -1,28 +0,0 @@
-## Community Roadmap
-
-This readme is a basic description of the `Community Roadmap` to get the ball rolling and details will be added over time. Everything in this folder has been written by @tomato with the goal of having the community participate and take full ownership before anything is actually agreed upon.
-
-The idea is still in the process of being drafted, refined and approved by the community before it would proceed fully, but the general idea would be to draft and soft approve on critical early stage proposals by utilizing the councils elected on the testnet by submitting text proposals. Rather than focusing on the addition of new features post-launch, much of it is intended to revolve around governance.
-
-`research.md` contains some examples of other community roadmaps and more critically looks at examples of better ways to store documentation compared to Markdown files within Github.
-
-***
-
-The Community Roadmap is an initiative that will start during the testnet phase of the project and is aimed at pulling together the ideas and ambitions of the community to ensure that mainnet launch is successful and has some coordination and structure.
-
-Goals:
-* Aim for genesis launch to have an involved community who have some cohesion and structure to ensure success of the platform.
-* Get users interested in governance and the testnet councils to start thinking longer term.
-* Create a list of drafted proposals that can be submitted upon genesis launch at appropriate times.
-* Create an initial organizational structure (labels, categories) for drafts of proposals.
-* Create a system so that the council and all platform participants can at any time have a structured, easily accessible overview of governance and minimize time having to be spent manually reading through old proposals.
-* Try to agree upon critical components of communication and reporting so that working groups and the council and governance in general can operate efficiently.
-* Try to develop a range of templates and standardized formatting for regular tasks (such as mint refill requests).
-
-A much fuller description of some aspects of this initiative can be read here: https://github.com/Joystream/community-repo/issues/710
-
-
-
-The plans for this initiative would be stored in two places:
-- The `Community Repo` on Github: https://github.com/Joystream/community-repo
-- The `Community Roadmap` area within Joystream's Notion: https://joystream.notion.site/Community-Roadmap-6aadc1a9e1674b35af27097c1ec6d26d

community-roadmap/research.md

@@ -1,15 +0,0 @@
-## Community Roadmap Research
-
-It would be good to compile a list of community roadmaps from other projects and include links to any associated processes that would be worth of consideration.
-
-#### Documentation Tools
-* Gitbook
-* Docusaurus
-
-#### Web3
-
-#### Web2
-
-#### Real World
-* API for accessing United State's Congress governance information (`including bills, amendments, summaries, Congress, members, the Congressional Record, committee reports, nominations, treaties, and House Communications. Over time we will be adding other Congress.gov collection endpoints, such as hearing transcripts and Senate Communications`)
-	* https://blogs.loc.gov/law/2022/09/introducing-the-congress-gov-api/ / https://api.congress.gov/ - 

community-roadmap/resources.md

@@ -1,9 +0,0 @@
-## Community Roadmap - Resources
-
-This page will list out resources relevant to the Community Roadmap.
-
-Media:
-* It would be nice to have a dedicated logo. 
-
-Database:
-* It would be good to have a .JSON file that can replicate the database within Notion so that the data can be used in multiple places