Create governance dcoumentation stored in repo/GitLab Pages

Currently the only documentation available regarding the process to adopt a module are located on D.O. in a location where anyone can edit them. This raises questions about the accuracy of the documents at any given moment.

Is there any edit which defaced the documentation page? For what I recall, that never happened.
It is not necessary to move the documentation to GitLab Pages. All the project moderators have the permissions to use the Full HTML format, which cannot be used from people without specific roles.

Is there any edit which defaced the documentation page? F

Your text provides a key concern I have with these pages. It is being described as a "documentation page' not a 'Policy page".

I'm not aware of any deliberate modification to deface the page, although I am aware of lines that may not be written the best as they could be as they use phrases such as "Must" and "will" in a manner that appears to imply these are mandatory non-discretionary steps when other posts by site moderators appear to imply these are general cases, however not mandatory.

Without a formal policy I am unable to ascertain with certainty which of the two interpretations is correct in order to propose documentation edits.

In the past i have tried quoting from the relevant pages and been told these are not policy.

Offering to become a project owner, maintainer, or co-maintainer is not a policy, nor is a documentation page describing the terms of service. Please stop making false claims.

-- https://www.drupal.org/project/drupalorg/issues/3452333#comment-16094934 📌 Automate the majority of the ownership transfer process (retain human approval) Active
The page links both to

https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

At this point I keep receiving conflicting statement a large part of it may be a language barrier with the involved individuals. Having a well defined policy page with a tracked record of every change linked directly to the discussion involved (where not just the text of the policy but the thought process behind the wording is present) would provide more clear context to both understand the policy and to provide references when communications difficulties may be involved.

It is not necessary to move the documentation to GitLab Pages.
While perhaps not 100% necessary it would provide assertions on authenticity.

Drupal Core governance has done this in 📌 Make gitlab pages for governance.drupal.org Active .
The coding standards group is considering the same in 📌 Convert Coding Standards to GitLab pages Active .

I am a fan of governance policies in repo as well

- Tim Lehnen
CTO of the Drupal Association
https://drupal.slack.com/archives/C5ABFBZ5Z/p1746562504563009?thread_ts=...

Nothing of what you describe changes moving the documentation pages in the repository, to which any project maintainer for the Drupal.org project ownership would have access, especially when they are project moderators or have a higher role.

That documentation page has been created time ago to describe what people who wanted to become co-maintainer/maintainer or project owner should do, such which title give to the issue, how long the issue must be kept in the project issue queue before moving it, who can move the issue, what can be changed in the issue after it was created and from who can be changed. It does not say that a project moderator, finding an issue for an offer to become maintainer created the day before, cannot contact the project maintainers.
What the documentation page says does not change moving it to a repository, nor does the nature of that documentation page change because it is moved to a repository.

Nothing of what you describe changes moving the documentation pages in the repository,

My understanding from previous conversations is that the pages are editable by even average users today (I can open the edit page, I have not tried saving to confirm), if so that would change as moving it to the repository.

to which any project maintainer for the Drupal.org project ownership would have access, especially when they are project moderators or have a higher role.

Are you saying we do not have a policy for when the document is allowed to be updated or are you saying that we can't trust the Project Ownership Queue admins to not make make nu-approved changes?

That documentation page has been created time ago to describe

If we do not think the current page as-is is useful I'm willing to help write something more governance like based on the current documentation published.