>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1275424. --> Reported by: [webchick](https://www.drupal.org/user/24967) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>After making it possible for everyone to edit pages with images/tables on <a href="http://drupal.org/node/528682">another issue</a>, we still have a legacy Documentation input format hanging around on Drupal.org, and a corresponding Docs Admin role that I think only has permission to use that input format and no other special permissions.</p> <p>There are quite a few nodes of various types that have this Documentation input format (see comment #2), and quite a few people with the Documentation role.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>a) Change book nodes and project_project with Documentation format to Filtered HTML. [Some images may break, but since the pages will be editable by anyone (books) or the project owner (projects), they can be fixed as they are noticed.]</p> <p>b) Change other nodes with Documentation format to Full HTML. This will leave the screen shots in them intact, at the cost of them being not very editable.</p> <p>c) Remove the code that generates the Docs Maintainers page in the drupalorg project.</p> <p>d) Remove all permissions for use of the Documentation input format.</p> <p>e) Remove the current Docs Admin role.</p> <p>f) Create a new role "documentation moderator" or "documentation administrator" or whatever it should be called. Give it to about 20 people who have recently been active docs maintainers (list TBD). Give that role these privileges:<br> - publish/unpublish pages -- I guess that means "administer content"?<br> - use the Full HTML format<br> - administer URL aliases and redirects<br> - manage book outline<br> - administer comments</p> <p>g) Rejoice and close this issue.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>With reference to the Proposed Resolution above:</p> <p>1. [DONE] Figure out queries for (a) and (b), and code for (c). Test them on a staging server. Apply to drupal.org.</p> <p>2. Do (d) and (e) in the drupal.org admin interface.</p> <p>3. [IN PROGRESS] Figure out the list of people to be given the new docs admin role. Create the role as described in (f), and grant it to those people. [IN PROGRESS]</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>Documentation input format will be unusable. Fewer pages will be locked to editing. Some pages may have broken images during the transition period. Remove one role and add a new role.</p> <h3 id="summary-api-changes">API changes</h3> <p>None.</p> <h3 id="summary-original-report">Original report by webchick</h3> <p>Coming here from <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/infrastructure/-/work_items/528682" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/infrastructure/-/work_items/528682</a></span>. Relevant comments/discussion:</p> <p><a href="http://drupal.org/node/528682#comment-4972136">http://drupal.org/node/528682#comment-4972136</a><br> Posted by arianek on September 10, 2011 at 10:08pm</p> <p>Was just logging in to test this, and realized that we'll also need to address the already set input formats either with rolling this out or afterwards.</p> <p>eg. <a href="http://issue-summaries-drupal.redesign.devdrupal.org/documentation/modul">http://issue-summaries-drupal.redesign.devdrupal.org/documentation/modul</a>... because it already has images, it has the docs input format, and so can only be edited by docs admins even after this is rolled out.</p> <p>We'd ideally want to somehow make all these existing posts with images accessible to regular users as well (and subsequently probably revoke all the unnecessary docs admin role assignments). My suggestion would be (unless there's something I'm overlooking):</p> <p>1. Change all nodes with docs input format to this new local image input format.<br> 2. Revoke docs admin role from all users.</p> <p>And separately:</p> <p>1. Review and update what docs admin role should actually have permissions for.<br> 2. Add docs admin role back to any users that should have the new permission set.</p> <p>Not ticketing these yet, as it'd be great to have input from y'all.</p> <p>DID I MENTION YOU'RE MAKING MY DREAMS COME TRUE RIGHT NOW? THANK YOU!!! ;)</p> <p><a href="http://drupal.org/node/528682#comment-4972756">http://drupal.org/node/528682#comment-4972756</a><br> Posted by dww on September 11, 2011 at 2:22am</p> <p>@arianek: From what I understand, some of the pages marked needing the "documentation" format are supposed to be "locked" pages that we don't want to behave as wikis (for whatever reason -- perhaps they're contentious, or they're the coding standards and we have a very specific process we go through if we're going to change them, etc). So, I'm slightly concerned about a blanket reset of all posts with that format. Then again, there might be so few pages that need to be locked that it'd be a lot easier to reset everything and handle those special-cases manually.</p> <p>Otherwise, everything you're proposing makes perfect sense and I'd be happy to see tickets for those sub-tasks spawned off so they don't get lost in here.</p> <p>Thanks,<br> -Derek</p>