polkadot-parachains folder restructuring.

[hbulgarini]

In order to enhance the developer experience and documentation for engineers working with the parachains living under polkadot-parachains, a new folder called parachain-runtimes will be created with the following structure:

• parachain-runtimes
  • chain-specs (formerly known as res)
  • common
    • utilities (common shared code / libraries)
    • tests ( folder containing unit tests for different functionalities ) Moved topolkadot-parachain folder
  • pallets
    • specific pallets for parachains (e.g. collator-selection)
  • src (entry point folder for commands/services etc ) Moved to polkadot-parachain folder
  • starters
    • shell (can be used to launch an "empty" runtime that can be upgraded via a downward message)
    • seedling (runtime with sudo to register prior to migrating a solo-chain into a parachain)
    • scaffold (formerly known as parachain-template, a scaffold/template for teams to start from when developing a runtime) Discussion
  • testing
    • pen-pal (parachain runtime ready with the necessary XCM setup to test interactions with Statemine/Statemint)
    • rococo-parachain (used for creating Tick/Trick/Track parachains). Discussion Is rococo-parachain necessary? #1222
  • assets
    • statemine
    • statemint
  • contracts
    • substrate-contracts
  • governance (as an example of a potential common good parachain dedicated to governance)
    • kusama-gov
    • polkadot-gov
  • etc...

Also based as a result of a diagnostic of the existing parachains on the folder, Wesmint would be removed since we would be deploying the Statemint runtime directly on Westend.

Every parachain runtime should include a rust doc with the purpose of it.

@joepetrowski

[gilescope]

Would like penpal not hyphenated but it's all fine with me.

[bkchr]

starters

* shell (can be used to launch an "empty" runtime that can be upgraded via a downward message)

* seedling (runtime with sudo to register prior to migrating a solo-chain into a parachain)

* scaffold (formerly known as `parachain-template`, a scaffold/template for teams to start from when developing a runtime)

Why should this entire stuff be moved there? I mean I get that shell and seedling are already there as a runtime, but the template is an entire node. Not sure this makes sense.

[hbulgarini]

Why should this entire stuff be moved there? I mean I get that shell and seedling are already there as a runtime, but the template is an entire node. Not sure this makes sense.

OK. Fair enough. We will not move the parachain-template into the polkadot-parachains folder and it can remain as it is with no changes.

[gilescope]

As discussed in the meeting, having the polkadot-parachain collator in the same dir as the runtimes does not lend itself to trying to separate out these two things (which have separate release cycles). The suggestion that seemed to have some backing is to split the contents of polkadot-parachains into polkadot-parachain (the collator) and parachain-runtimes (the runtimes).