Coding Standards issues are not being addressed

Created on 9 December 2020, about 4 years ago
Updated 21 June 2023, over 1 year ago

Problem/Motivation

The topic of πŸ“Œ Document cases where it's appropriate to use global \Drupal calls as opposed to DI Active was brought up in Slack and somebody noted that the committee responsible for reviewing/approving updates to our Coding Standards doesn't seem to be active any more. Indeed, of the 115 open standards issues β†’ , only 11 have had any activity in the last 6 months. Two issues are RTBTC and tagged as Core Committer Approved, but have not had any activity in roughly 6 months and 4 years, respectively.

This is problematic, as keeping standards up to date is important to the ongoing health of the community and our code.

Proposed resolution

I'm not sure of the right way to fix this, but the desired outcome would be to get that queue pared down and into the official standards docs. If there is indeed a committee that is meant to be responsible for this, but is currently inactive, I'd ask that they become more active.

Somebody with more intimate knowledge of the process could probably propose a more specific pathway to resolution.

🌱 Plan
Status

Closed: duplicate

Component

Policies

Created by

πŸ‡ΊπŸ‡ΈUnited States mrweiner

Live updates comments and jobs are added and updated live.
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.

Production build 0.71.5 2024