Problem/Motivation

#2870295: Concerns about beta and RC contrib without security coverage made me think about frequency of contrib module releases in general. Would it be worth adding a contribution credit ranking for 'stable releases created' - this would mean adding the issue credit field (or something similar) to release nodes so they can be attributed. Attribution would be for the actual process of creating the release (pre-release triage, release notes, tagging etc.).

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

catch created an issue. See original summary.

drumm’s picture

drumm
he/him
Location NY, US
commented

A good release is certainly a lot of work. I have seen a couple projects that make a new release almost every new commit, although infrequent releases are more of a problem.

For user pages, maybe the listings of project-related credit need a revamp. We don’t really need a credit number for individuals, we want to summarize their contributions.

For organization attribution, we do have the project’s supporting organizations. Although that doesn’t have any machine-readable details.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented

Duplicate of #2875447: Contribution credits for project releases?

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented
Related issues: +#2875447: Contribution credits for project releases
catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Closed (duplicate)

Marking duplicate of #2875447: Contribution credits for project releases.