Set up repository for UIPs

[cornelius]

As decided in ADR-23 we will move design documents to its own repository dtr-org/uips as UIPs.

To do:

• [x] Create repo
• [x] Create UIP-1 to document the UIP process (https://github.com/dtr-org/uips/pull/1)
• [x] Move ADRs to UIP repo as described in ADR-23 (https://github.com/dtr-org/uips/pull/2 and https://github.com/dtr-org/unit-e-docs/pull/91)
• [x] Link uips repo from ADR-1 (https://github.com/dtr-org/unit-e-docs/pull/91)
• [x] Add license information (https://github.com/dtr-org/uips/pull/3)
• [x] Create table of content of UIPs in the README.md (https://github.com/dtr-org/uips/pull/4)
• [x] Add standard files (https://github.com/dtr-org/uips/pull/3)
  • [x] CODE_OF_CONDUCT.md (https://github.com/dtr-org/uips/pull/3)
  • [x] CONTRIBUTING.md (https://github.com/dtr-org/uips/pull/3)
  • [x] PULL_REQUEST_TEMPLATE.md (https://github.com/dtr-org/uips/pull/3)
• [x] Add DCO (https://github.com/dtr-org/uips/pull/3)

[mergeable[bot]]

Mergeable has found some problems

• The issue is not categorized using any label.

  ---

  Please address these problems to adhere to the repo's guidelines. Thank you!

[cornelius]

I'm wondering if we also should require the DCO for the UIPs. On one hand it would be consistent with the other repos, on the other hand it might add a barrier for people to contribute. The kind of material and its license is different here as well as it's not primarily about code but more about ideas and designs.

Opinions?

[scravy]

I say make the DCO part of it.

Anything could be ruled out on the grounds of "might be a barrier for people to contribute".

[scravy]

Also, If someone does not get it done, the DCO check can still be bypassed by the one merging it and the merger can then sign off himself.

[cornelius]

Ok, let's add the DCO and see how it goes.

[cornelius]

Done