Stats about new contributors

Open
#190 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, python
Domain
analytics

Research direction

Start with the aggregated metrics table described in this issue and review the linked Orchard Core issues 14585 and 15073 for the existing action and metric format. Done means adding a reliable “Number of items opened by new contributors” metric, with the contributor definition and calculation agreed and reflected in the output.

Written by the indexing model from the issue text.

Description

enhancement keep

During our community meeting at Orchard Core on the topic of integrating this action (https://github.com/OrchardCMS/OrchardCore/issues/14585) it came up that it would be nice to have stats about new contributors as well.

I.e., in an issue like https://github.com/OrchardCMS/OrchardCore/issues/15073, we'd also have a "Number of items opened by new contributors" line in the aggregated metrics table. A new contributor can be defined as somebody who GitHub indicates as a first-time contributor like this:

296902235-32f27aad-2c5a-4f0d-963b-722af1caedb2

I'm not sure how this is calculated. In any case, this would be a user who didn't yet author a contribution of that type (e.g., didn't open an issue before and thus they're a new contributor for issues) or didn't create any issues/discussions/PRs before in the project (whichever is easier to compute).

What do you think?

Dominant language
Python
Stars
542
Forks
94
Avg merge
10h 3m
Merged PRs (30d)
9

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github-community-projects/issue-metrics

All issues in github-community-projects/issue-metrics

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.