[meta] Improve issue management

Open on Drupal.org →

Created on 1 April 2023, over 1 year ago

Updated 22 April 2024, 8 months ago

Problem/Motivation

A recent Slack discussion indicated that there isn't a single solution for improving the way we work on issues. This issue is to gather all the core issues about that. I hope it will provide one place to see the big picture of what problems people are having and the existing range of possible solutions.

The intention of most of these issues is to make it easier and faster to get an issue resolved and committed. In, other words to remove blockers that are slowing us down. Also included are issues about the Core Gates because they define what must be done for a commit.

I have included any issue I found related to 'issue management'. They do not have to be addressed in this meta but I think it helps to provide the big picture. An example, is the issues in the Coding Standards project about reducing boilerplate documentation.

The issue(s) currently being worked on

🌱 [Plan] Simplify core component list Needs review
🌱 [policy] Decide on format of commit message Active

This issue is waiting for various manager review and subsystem maintainer review

Related wiki ocumentation

Getting an issue addressed sooner →

The issues

🌱 [Plan] Simplify core component list Needs review
#2438267: Create an "EntityReference system" component →

#3199887: [meta] Tools to improve issue triage →

Suggested improvements from other issues

From 🌱 [Policy, no patch] Add special tag to identify issues ready for a high level only review Fixed

Do more self-RTBCs and keeping issues RTBC after posting changes
Another options, 'E' Add status 'In progress' with tag 'Needs architectural review'
An approval process (apparantly GitLab has this).
More room for 'fixed on commit' from committers.
Add a baseline for phpcs.
Ignore non automated nitpicks, possible followup. These followup can be good for new contributors. However, there is concern about this due to the credit farming behaviors. Also, longer time to get stable state for new features (from #85).
If you find nit-pick standard reviews, then update the patch yourself.
Coding standards - remove boilerplate no longer needed

From 🌱 [policy, no patch] Policy to help less interested Patch move forward. Closed: outdated

Allowing self signing patched, with restrictions. See the issue summary for details.
#3 🌱 [policy, no patch] Policy to help less interested Patch move forward. Closed: outdated . Create a review swap area on d.o. A formal place to establish connections to do swaps.
Wish Drupal has https://github.com/facebook/mention-bot. (also @see: https://code.facebook.com/posts/597378980427792/). See #5 🌱 [policy, no patch] Policy to help less interested Patch move forward. Closed: outdated
In general all stuff in https://github.com/servo/highfive/tree/master/handlers would be just amazing. See #9 🌱 [policy, no patch] Policy to help less interested Patch move forward. Closed: outdated
What we need here is a mark that "I think this is a change limited to its own namespace".. See #12 🌱 [policy, no patch] Policy to help less interested Patch move forward. Closed: outdated

From 🌱 [policy, no patch] Better scoping for bug fix test coverage RTBC

Allow trivial bug reports to be committed without test coverage, when generic test coverage scoped at a wider level, or CS/rector rules would be more appropriate.
For non-trivial or low level bugfixes, continue to require test coverage on the issue since in these cases we need be able to demonstrate the bug is fixed without manual testing.

Proposed resolution

As a community work on one of these issues at a time to make incremental improvements. Although, the coding standards issues have a separate process, independent of this meta. They are listed for reference.

Completed

🌱 [policy, no patch] Better scoping for bug fix test coverage RTBC

📌 Strategies for far-reaching core patches Closed: outdated
🌱 [Policy, no patch] Add special tag to identify issues ready for a high level only review Fixed
🌱 [policy, no patch] Policy to help less interested Patch move forward. Closed: outdated
🌱 [policy, no patch] Agile process for bigger changes in core (Part B: Implementation) Fixed
📌 [Meta] Run tests with phpcs fail Closed: duplicate

🌱 [policy, no patch] Core review bonus Closed: outdated
🌱 [policy, no patch] Adopt a set of guidelines for closing stale bug reports Fixed
🌱 Proposal: consolidation period for D10.0.0 Fixed

📌 Sort values of "Component" field for core issues alphabetically Closed: won't fix
🌱 [Plan] Update core components Fixed

🌱 Plan

Status

Active

Version

11.0 🔥

Component

Last updated about 4 hours ago

Created by

🇳🇿New Zealand quietone

Live updates comments and jobs are added and updated live.

Incomplete comments

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Issue created by @quietone
Comment over 1 year ago →
cilefen
A feature that would tend to prevent duplicate issue submissions would be nice.
Comment over 1 year ago →
🇩🇪Germany FeyP
A feature that would tend to prevent duplicate issue submissions would be nice.

We'll get such a feature once 📌 Migrate drupal.org issues to gitlab issues Needs review is completed. When you file a new issue, GitLab will suggest up to 5 similar issues based on what you enter as the issue title. It is then suggested that it might be better to comment there instead of filing a new issue. To find similar issues, GitLab will search title and description fields of existing issues you have access to.
Comment over 1 year ago →
🇳🇿New Zealand quietone
In Slack, catch pointed out the Git related issues which I chose not to include. But since it has been asked for, and that I think about it again, it makes sense. Added a section for Git.
Comment over 1 year ago →
🇳🇿New Zealand quietone
Comment over 1 year ago →
🇳🇿New Zealand quietone
Add 🌱 [policy, no patch] Core review bonus Closed: outdated
Comment over 1 year ago →
🇳🇿New Zealand quietone
Found some more issues to add to the IS.
Comment over 1 year ago →
🇳🇿New Zealand quietone
Add issues as related so that this issue can be found.
Comment over 1 year ago →
🇳🇿New Zealand quietone
Comment over 1 year ago →
🇳🇿New Zealand quietone
Add 📌 [Meta] Run tests with phpcs fail Closed: duplicate to the issue summary.
Comment over 1 year ago →
🇳🇿New Zealand quietone
Comment over 1 year ago →
🇳🇿New Zealand quietone
Comment 9 months ago →
🇳🇿New Zealand quietone
Comment 9 months ago →
🇳🇿New Zealand quietone
Comment 8 months ago →
🇸🇰Slovakia poker10
Updating completed issues in Git/Components sections, as there were issues which are still active.
Comment 8 months ago →
🇳🇿New Zealand quietone

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024