Drupal.org/GitLab Tooling Requirements for Decoupled Menus Inititaive

Problem/Motivation

Using this issue to prioritize the tooling improvements to Drupal.org that are needed to properly support JavaScript development using Drupal.org issues and our GitLab integration.

• Choosing to put it in this queue rather than the Drupalorg Customizations queue so that it is easily visible to the initiative team.
• We want frequent touch-points to ensure we're working on the most critical priorities first.
• Child issues may live in the drupalorg customizations project.

Tooling Gaps and Prioritization

These gaps have been identified in this example GitHub repository: https://github.com/jsdrupal/js-client/wiki/d.o-Wishlist

Critical/Blocker priorities

• Done: Project type on Drupal.org for 'libraries/components' #2474007: Add a “General” project type to Drupal.org
  • WebIDE - Just comes with GitLab
  • Follow-up: #3195258: Provide a way of identifying projects that are part of core
• Done: Enable GitLabCI for pipelines
• Integrated Workflow and Build Pipelines
• Configure initial 'instance size' for GitLabCI runners/k8s cluster
• Reserve this for *just* the decoupled initiative project for now, so we can make changes quickly
• Test: Secrets management
• Test: Publishing to NPM
• Follow-up: Verify additional configuration/bugs found when configured for the first project.

Major priorities

• Merge request pipeline testing - check whether this is a config option
• Static page documentation publishing? Scope and determine core policies

Normal priorities

• Credit work on official @drupal projects as if it were work on core
• Discuss at Initiative Meeting Jan 26th - Ensure that configuration of the following types of CI jobs is possible:
  • Automated dependency updates/CI
  • CodeQL or other scanning and alerts
  • Automated dependency scanning(and updates?)/CI
• Automatic publishing of documentation changes to api.drupal.org?
  • Current pattern: Parsing doc-comments from code and displaying on api.drupal.org
  • Related conversation: In-place api docs in Drupal admin interface?
  • Related conversation: Drupal's core apis vs apis added in libraries/modules?
  • Related conversation: documentation in code?

Nice to have

• Pending further feedback: Improved project management tools (Kanban? Milestones? Issue moderation? Code owner delegation? Easier commenting/image upload
• Complete(Pending further feedback):Gitlab and Drupal.org Integration: Managing code review comments/annotations in issue.