Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify question of Elephant Factor #171

Open
19 tasks
GeorgLink opened this issue Feb 23, 2023 · 0 comments
Open
19 tasks

Clarify question of Elephant Factor #171

GeorgLink opened this issue Feb 23, 2023 · 0 comments

Comments

@GeorgLink
Copy link
Member

Name of Metric

Elephant Factor

Link to Original Metric Release Issue

#15

Specific Metric Details that Require Attention

  • Question: What is the distribution of work in the community?

The Elephant Factor is specifically about "companies" in a project and I suggest adding that to the name.

Question: What is the distribution of work in the community across companies?

Sorry, I already made the change.
I tried to create a PR but accidentally pushed directly to the main branch: ea66a0e

Checklist

Process

  • Create the “revising metric” labeled issue in the authoring WG’s repo for comments during review period
  • Create pull request of revised metric to WG’s repo (after checking Content Quality and Technical Requirements below)
  • Add the metric revision to release notes issue in working group repo
  • Update the Metrics Spreadsheet to indicate that the revised metric is under review
  • Create issue in CHAOSS/Translations repository to kick-off translation to other languages (please use the the translation issue template)
  • "Metric Candidate Release" label added to the metric release candidate issue when fully ready fo release

When above steps are completed:

  • Announce new/updated metric on mailing list, newsletter, community Zoom call, and Twitter. This can be coordinated with the community manager and can be done as a collective of all revised metrics from the CHAOSS community.

Content Quality (check all that apply)

  • Date of last review has been added to the revised metric at the bottom of the markdown file (month/year)
  • Formatting changes have been made
  • Minor editorial changes have been made
  • Major editorial changes have been made
  • Metric adheres to the current metrics template
  • Metric name has changed and necessary updates are made to the WG README table and metrics tracking spreadsheet

Technical Requirements for any Revisions

  • Metric file name is the full metric name and only contains lower case letters and hyphens (“-”) for spaces
  • Images are included using markdown and absolute path links (as described in the metrics template)
  • Images have at least one empty line above and below them
  • Images are placed in image folder and followed naming convention
  • If new a focus area is created, ensure focus area is added to wg repo readme and focus area folder readme
  • There is no HTML code in the metrics markdown file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant