Skip to content

invite prior contributors to the nodejs org #3802

Closed

Description

@mikeal

With the launch of individual membership in the foundation we offer free member registration in the Node.js Foundation to members of the nodejs with the understanding that these are people who have contributed to the project and therefor should be offered membership free of charge.

While this accurately accounts for most of the recent contributors to the project this does not account for people who have contributed in the past prior to this org and our liberal contribution agreement. It may then be prudent to invite these people to the nodejs GitHub org (this would not give them commit privileges in any repository and the only team they would be in would be "members").

There are 671 contributors to the nodejs project who are not org members. Only 232 of those contributors have more than a single commit. Our options are:

  • Invite nobody.
  • Invite above a certain threshold.
  • Invite everyone who has successfully landed a commit in node.

Here's the list, apologies in advance for its length.

Activity

  1. jasnell commented on Nov 12, 2015

    @jasnell
    Member

    As opposed to inviting them to the github organization and granting free membership, an alternative would be to offer a discount code for membership to these individuals who, quite likely, are not actively involved in Node development efforts. In other words, if they wish to become more actively involved again, then by all means take join the organization as an active contributor and receive the associated benefits, but alternatively, here is a discount as a thank you for your prior contributions...

  2. mikeal commented on Nov 12, 2015

    @mikeal
    ContributorAuthor

    @jasnell I thought about that but then once I had the list I realized how silly it would be at some level. Some of the top historic contributors ever to node.js are on that list, sending Ryan Dahl a "discount" on Node.js seems either laughable or insulting on some level :(

  3. added
    metaIssues and PRs related to the general management of the project.
    on Nov 12, 2015
  4. jas- commented on Nov 13, 2015

    @jas-
    Contributor

    I would like to make more contributions but want to ensure any future work on the crypto.Certificate object (such as CSR, x.509, PKCS#7, PKCS#12 and CA) functionality would be welcomed. Someone mentioned in the #3761 issue that there is a crypto wg? I recently attempted to ask some core maintainers in IRC but its always hit and miss due to timezones, work etc.

  5. creationix commented on Nov 13, 2015

    @creationix
    Contributor

    How much is membership? Maybe discount a dollar per commit landed?

  6. mikeal commented on Nov 13, 2015

    @mikeal
    ContributorAuthor

    past prior to this org and our liberal contribution agreement. It may Did you change the CLA for something leaner? I signed the CLA out of neccesity, but I did not like it (nor do I like them now).

    Sorry for the confusion here, I'm not talking about the CLA (although we no longer have it) I'm talking about our new policy of on-boarding new contributors as committers much earlier than we did prior.

    As to the CLA, that no longer exists, we now use the DCO which is a notice in the CONTRIBUTING file and effectively provides the same protection.

    My last commit is from Feb 2015 ... does it make me historic? ;-)

    "Historic" in the sense that the contribution fell shortly before we were on-boarding committers the way we are now.

  7. mikeal commented on Nov 13, 2015

    @mikeal
    ContributorAuthor

    How much is membership? Maybe discount a dollar per commit landed?

    That isn't feasible :)

  8. mikeal commented on Nov 13, 2015

    @mikeal
    ContributorAuthor

    @jas- there isn't so much a crypto "working group" as there is a "crypto team." Working groups tend to be lead by someone and take on some additional organization but hasn't happened, instead there's a GitHub team that we @ in any crypto issue to get them onboard. I believe you are on the list for the next committer onboarding, once you are a committer we can easily add you to that team.

  9. rsms commented on Nov 13, 2015

    @rsms
    Contributor

    When you posted this issue, I received an email notifying me of being mentioned — one option could be to do some sort of "action needed" where contributors (like myself) who are still interested in Node can chime in to get a discount code, membership or whatever you're planning. I suspect a majority of the people mentioned above are no longer involved in node, or was never involved (but just helped fix some bug.)

  10. jasnell commented on Nov 13, 2015

    @jasnell
    Member

    @mikeal ... perhaps this:

    • users with commits > 1 and < 100 who have committed within the past year = 50% discount
    • any user with >=100 commits = 100% discount
    • @ry should simply be granted a permanent membership for life.

    (we can play with that threshold a bit, 100 commits may be too high)

  11. rsms commented on Nov 13, 2015

    @rsms
    Contributor

    @jasnell 100 commits = 2 people (not including ry.) Also, contribution within the last year doesn't make that much sense, does it — a lot of the foundational "dirty work" happened early (2010-2013 ish) in Node's life. Just my 5¢ :)

  12. jasnell commented on Nov 13, 2015

    @jasnell
    Member

    As I said we can play with that threshold a bit ;-)

  13. saper commented on Nov 14, 2015

    @saper

    Even if only 10% of 600 will stay a high-yield committers, $60k/year is a bargain.

  14. jasnell commented on Nov 14, 2015

    @jasnell
    Member

    My main concern is that the free membership for organization members is a benefit. I'd like it to be one of the incentives that encourage more contributions in the future. I'll defer to @mikeal's judgement on it tho.

  15. mikeal commented on Nov 14, 2015

    @mikeal
    ContributorAuthor

    So, the board created the Individual Membership program to try and broaden
    the perspective of the board and bring in more input from the broader
    community. The current seat for the TSC on the board does a good job of
    representing the interests of those actively engaged in core (for now, if
    the TSC grows and has less overlap with the CTC that could change).

    Free membership is actually org wide, so most of the people eligible aren't
    active in core but in other WGs. As such it's a poor incentive for core
    contributions.

    I guess the main question would be: does this bring in more of the user
    community? Do we think this list is representative of people who may have
    once used node but are now dissengaged or is it a list of people who
    contributed to core early on until it was sufficient for them to spend all
    their time up the stack?

    On Friday, November 13, 2015, James M Snell notifications@github.com
    wrote:

    My main concern is that the free membership for organization members is a
    benefit. I'd like it to be one of the incentives that encourage more
    contributions in the future. I'll defer to @mikeal
    https://github.com/mikeal's judgement on it tho.

    —
    Reply to this email directly or view it on GitHub
    #3802 (comment).

  16. jas- commented on Nov 14, 2015

    @jas-
    Contributor

    What ever happened to doing it for the glory?

  17. aheckmann commented on Nov 14, 2015

    @aheckmann
    Contributor

    Doesn't matter too much to me either way. I still use node everywhere and
    lurk to stay aware of changes which potentially affect my team but this
    probably won't increase or decrease my contribution level.

    Kind thought though <3
    On Nov 13, 2015 8:04 PM, "Jason Gerfen" notifications@github.com wrote:

    What ever happened to doing it for the glory?

    —
    Reply to this email directly or view it on GitHub
    #3802 (comment).

  18. zimbatm commented on Nov 14, 2015

    @zimbatm

    You can remove me from the list, I am not an active contributor anymore. In
    fact I would suggest to ignore any contribution older that X months to keep
    the board with interested people.

    On Sat, 14 Nov 2015 06:15 Aaron Heckmann notifications@github.com wrote:

    Doesn't matter too much to me either way. I still use node everywhere and
    lurk to stay aware of changes which potentially affect my team but this
    probably won't increase or decrease my contribution level.

    Kind thought though <3
    On Nov 13, 2015 8:04 PM, "Jason Gerfen" notifications@github.com wrote:

    What ever happened to doing it for the glory?

    —
    Reply to this email directly or view it on GitHub
    #3802 (comment).

    —
    Reply to this email directly or view it on GitHub
    #3802 (comment).

  19. tyleranton commented on Nov 16, 2015

    @tyleranton

    I only have one commit, but am definitely wanting to contribute more. I actively follow and use Node. I wouldn't say I'm deserving of discounts or anything. 1 commit isn't a big deal.

  20. seebees commented on Nov 16, 2015

    @seebees
    Contributor

    I'm not sure what the cost/benefit of all this is, but I would do something like: any commit that lands gets you a 1 year subscription. Give all the people on this list a 1 year sub, and then if they stay active great, if they don't, then great.

    Anything that is forever is a bad idea, so how do you plan to cull your current list of "members"? Activity seems like a good proxy to me...

    This also has the advantage of not only incentivizing past activity, but also incentivizing future activity.

  21. coolaj86 commented on Nov 20, 2015

    @coolaj86

    Just saw the announcement about individual members. https://nodejs.org/en/blog/community/individual-membership/

    Was there any resolution as to discount for membership based on commits? I'm in a scrappy startup right now and being very discriminate about how and where I spend money, but would love to join.

    I'm still active in the node.js community, but as of late node.js has been so awesome that I haven't been plagued by very many bugs in the code or shortcomings in the docs except for a few that were outside of my technical capability to fix by myself (thanks @indutny) and hence haven't been an active committer to core.

  22. mikeal commented on Jan 7, 2016

    @mikeal
    ContributorAuthor

    Talked about this today in the TSC meeting.

    The consensus seemed to be that we should invite everyone with 3 or more commits to the GitHub org. After a few days (enough time for people to accept their invites) I can run the script that adds every org member to the "members" group. At that point I'll log a new issue in the members repo about adding these people, the CoC, and what the moderation repo is (since they'll be subscribed).

    To re-iterate, we are not giving commit bits on anything, only adding them as org members. The only things they have access to which they did not before:

    • members and moderation repo
    • Free individual membership in the foundation.

    If there aren't any objections I'll get to this in the next few days.

  23. jasnell commented on Mar 22, 2016

    @jasnell
    Member

    @mikeal ... I assume there's no reason to keep this open?

  24. seebees commented on Mar 23, 2016

    @seebees
    Contributor

    I'm curious what ever happened with this. Was I supposed to get an email? Or did this go off and never happen. Just wondering.

  25. mikeal commented on Mar 23, 2016

    @mikeal
    ContributorAuthor

    It didn't happen because the CTC/TSC never agreed on a threshold.

  26. jasnell commented on Apr 22, 2016

    @jasnell
    Member

    Closing. Doesn't appear to be anything further on this. @mikeal, if this gets revisited, perhaps opening an issue over in the TSC repo is better. Can reopen this if necessary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    metaIssues and PRs related to the general management of the project.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions