Structure for our tsc and project management documents

[hendrikebbers]

Today, many informal documents are stored as markdown files in the root of the https://github.com/hiero-ledger repo. Next, the latest version of the charter (including its date) is stored in the https://github.com/hiero-ledger/governance repo. While that was ok for the start, we should define a better structure for all those documents.

Technical Charter

LFDT defines the charter as part of the governance repository. The problem with the current file is that it includes the date in the filename (Hiero Technical Charter Final 9-16-2024.md), making it impossible to link to the latest / active charter. Therefore, I suggest creating a hiero-technical-charter.md file directly in the root of the governance repo that always contains the latest version. Next to that, we can make a folder called charter-history that includes all versions (like Hiero Technical Charter Final 9-16-2024.md).

Other official documents

We have created some documents that define rules and criteria for the project onboarding (https://github.com/hiero-ledger/hiero/blob/main/howto-transfer.md + #54). Since the TSC voted on those documents, I suggest moving them to the governance repository in a project-onboarding folder.

General structure

In the future, we should place all information on that the TSC voted on as markdown files in the governance repository and create a meaningful folder structure. We could even create a webpage out of that in a future step.

[jwagantall]

In other communities we recommend using Wikis for non-technical contributions. It is easy to collaborate to and will be a better option to visualize documentation for the repo.
I am doing a test here on how this will look like but I am checking if Wikis have a way to organizing a tree structure-like directory.
https://github.com/jwagantall/hiero-governance/wiki

Let me know what do you think

[jwagantall]

This is updated in hiero-ledger/governance#288 similarly to how we do it in other communities