Skip to content
Snippets Groups Projects

Further define size of member projects for Open Source Partners program

Open Further define size of member projects for Open Source Partners program
nuritzi-update-def-members into master
1 unresolved thread
Open Nuritzi Sanchez requested to merge nuritzi-update-def-members into master
1 unresolved thread

Why is this change being made?

Based on feedback from @c_hupy and @dplanella, it'd help to define with a "large" or "prominent" open source project is. Christina also brought up the point that we may want to reassess using the word "prominent" as it implies a hierarchy.

For now, I've added a definition of at least 10,000 community members or users to qualify for our program. This may still be too small.

Some considerations:

  • Some open source projects do not measure their reach due to privacy concerns around metrics and the logistics around measuring size
  • What do we count as "community members"? Are these contributors + consumers? If we say we are basing it on contributors, how do we define that? e.g. GNOME's core contributor base is on the scale of a couple hundred, but they have thousands of contributions, and their user base is much larger (millions).

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
source/solutions/open-source/partners/index.html.haml
41 41 Participants must:
42 42 %ul
43 43 %li Be a current member of our GitLab for Open Source program or be a user of GitLab's Community Edition
44 %li Have a large community and user base, or be a prominent dependency project
44 %li Have a large community and user base, or be a prominent dependency project. This means having at least 10,000 community members or users
  • Michael Friedrich
    Michael Friedrich @dnsmichi
    Maintainer

    Do you have reference numbers e.g. from GNOME or KDE? Also, keep in mind that a community member number might not be the only measurement. Years in the ecosystem, maturity, vendor usage, etc. could also qualify.

  • Ray Paik
    Ray Paik @rpaik
    Contributor

    I also think this number is difficult to measure/audit. Also one community may have one definition of "community" (e.g. includes users in their count) while another community may have a different way of looking at things.

  • Please register or sign in to reply
  • Danielle Morrill added handbook label

    added handbook label

    • Please register or sign in to reply