{"id":15010535,"url":"https://github.com/nodejs/performance","last_synced_at":"2025-05-16T03:02:17.699Z","repository":{"id":62949054,"uuid":"563495788","full_name":"nodejs/performance","owner":"nodejs","description":"Node.js team focusing on performance","archived":false,"fork":false,"pushed_at":"2025-04-08T11:25:58.000Z","size":44,"stargazers_count":382,"open_issues_count":73,"forks_count":7,"subscribers_count":73,"default_branch":"main","last_synced_at":"2025-05-08T10:28:17.789Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nodejs.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2022-11-08T18:27:38.000Z","updated_at":"2025-04-08T11:25:58.000Z","dependencies_parsed_at":"2023-02-14T03:03:38.138Z","dependency_job_id":"e16e76b6-ed84-404c-b48d-6fe4e942d89a","html_url":"https://github.com/nodejs/performance","commit_stats":{"total_commits":39,"total_committers":13,"mean_commits":3.0,"dds":0.6666666666666667,"last_synced_commit":"a008e840776aacc0f92c2a12f923136c5e0c8589"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2Fperformance","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2Fperformance/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2Fperformance/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2Fperformance/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nodejs","download_url":"https://codeload.github.com/nodejs/performance/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":253815987,"owners_count":21968736,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-09-24T19:34:40.004Z","updated_at":"2025-05-16T03:02:17.641Z","avatar_url":"https://github.com/nodejs.png","language":"Shell","readme":"[![OpenJS Slack Invite](https://img.shields.io/badge/join%20slack%20on-nodejs--core--performance-green.svg)](https://slack-invite.openjsf.org/)\n\n## Performance Team\n\nThe Node.js Performance Team is a place to propose and discuss initiatives\naround improving the performance of Node.js internals.\n\nFor the current list of team members, see the project\n[README.md](./README.md#current-project-team-members).\n\n## Current Project Team Members\n\n\u003c!-- ncu-team-sync.team(nodejs/performance) --\u003e\n\n* [@anonrig](https://github.com/anonrig) - Yagiz Nizipli\n* [@apapirovski](https://github.com/apapirovski) - Anatoli Papirovski\n* [@benjamingr](https://github.com/benjamingr) - Benjamin Gruenbaum\n* [@bmeurer](https://github.com/bmeurer) - Benedikt Meurer\n* [@BridgeAR](https://github.com/BridgeAR) - Ruben Bridgewater\n* [@CanadaHonk](https://github.com/CanadaHonk) - CanadaHonk\n* [@ErickWendel](https://github.com/ErickWendel) - Erick Wendel\n* [@Ethan-Arrowood](https://github.com/Ethan-Arrowood) - Ethan Arrowood\n* [@F3n67u](https://github.com/F3n67u) - Feng Yu\n* [@fhinkel](https://github.com/fhinkel) - F. Hinkelmann\n* [@gareth-ellis](https://github.com/gareth-ellis) - Gareth Ellis\n* [@gibfahn](https://github.com/gibfahn) - Gibson Fahnestock\n* [@H4ad](https://github.com/H4ad) - Vinícius Lourenço\n* [@joyeecheung](https://github.com/joyeecheung) - Joyee Cheung\n* [@mcollina](https://github.com/mcollina) - Matteo Collina\n* [@qard](https://github.com/qard) - Stephen Belanger\n* [@RafaelGSS](https://github.com/RafaelGSS) - Rafael Gonzaga\n* [@rluvaton](https://github.com/rluvaton) - Raz Luvaton\n* [@santigimeno](https://github.com/santigimeno) - Santiago Gimeno\n* [@sheplu](https://github.com/sheplu) - Jean Burellier\n* [@sxa](https://github.com/sxa) - Stewart X Addison\n* [@TimothyGu](https://github.com/TimothyGu) - Timothy Gu\n* [@tniessen](https://github.com/tniessen) - Tobias Nießen\n* [@trevnorris](https://github.com/trevnorris) - Trevor Norris\n* [@UlisesGascon](https://github.com/UlisesGascon) - Ulises Gascón\n* [@uzlopak](https://github.com/uzlopak) - Aras Abbasi\n\n\u003c!-- ncu-team-sync end --\u003e\n\n## Collaborators\n\nThe Performance Team GitHub repository is\nmaintained by the team and additional Collaborators who are added by the\nteam on an ongoing basis.\n\nIndividuals making significant and valuable contributions are made\nCollaborators and given commit-access to the project. These\nindividuals are identified by the team and their addition as\nCollaborators is discussed during the weekly meeting.\n\n_Note:_ If you make a significant contribution and are not considered\nfor commit-access log an issue or contact a team member directly and it\nwill be brought up in the next meeting.\n\nModifications of the contents of the Performance Team repository are made on\na collaborative basis. Anybody with a GitHub account may propose a\nmodification via pull request and it will be considered by the project\nCollaborators. All pull requests must be reviewed and accepted by a\nCollaborator with sufficient expertise who is able to take full\nresponsibility for the change. In the case of pull requests proposed\nby an existing Collaborator, an additional Collaborator is required\nfor sign-off. Consensus should be sought if additional Collaborators\nparticipate and there is disagreement around a particular\nmodification. See _Consensus Seeking Process_ below for further detail\non the consensus model used for governance.\n\nCollaborators may opt to elevate significant or controversial\nmodifications, or modifications that have not found consensus to the\nteam for discussion by assigning the ***performance-agenda*** tag to a pull\nrequest or issue. The team should serve as the final arbiter where\nrequired.\n\nFor the current list of Collaborators, see the project\n[README.md](./README.md#current-project-team-members).\n\n## Team Membership\n\nTeam seats are not time-limited.  There is no fixed size of the team.\nHowever, the expected target is between 6 and 12, to ensure adequate\ncoverage of important areas of expertise, balanced with the ability to\nmake decisions efficiently.\n\nThere is no specific set of requirements or qualifications for the\nmembership beyond these rules.\n\nThe team may add additional members by unanimous consensus.\n\nA team member may be removed from the Performance Team by voluntary \nresignation, or by unanimous consensus of all other team members.\n\nChanges to team membership should be posted in the agenda, and may be\nsuggested as any other agenda item (see \"Team Meetings\" below).\n\nIf an addition or removal is proposed during a meeting, and the full\nteam is not in attendance to participate, then the addition or removal\nis added to the agenda for the subsequent meeting.  This is to ensure\nthat all members are given the opportunity to participate in all\nmembership decisions.  If a team member is unable to attend a meeting\nwhere a planned membership decision is being made, then their consent\nis assumed.\n\nNo more than 1/3 of the team members may be affiliated with the same\nemployer.  If removal or resignation of a team member, or a change of\nemployment by a team member, creates a situation where more than 1/3 of\nthe team membership shares an employer, then the situation must be\nimmediately remedied by the resignation or removal of one or more team\nmembers affiliated with the over-represented employer(s).\n\n## Team Meetings\n\nThe team meets weekly on a Zoom On Air. A designated moderator\napproved by the team runs the meeting. Each meeting should be\npublished to [YouTube](https://www.youtube.com/c/nodejs-foundation/streams).\n\nItems are added to the team agenda that are considered contentious or\nare modifications of governance, contribution policy, team membership,\nor release process.\n\nThe intention of the agenda is not to approve or review all patches;\nthat should happen continuously on GitHub and be handled by the larger\ngroup of Collaborators.\n\nAny community member or contributor can ask that something be added to\nthe next meeting's agenda by logging a GitHub Issue. Any Collaborator,\nteam member or the moderator can add the item to the agenda by adding\nthe ***performance-agenda*** tag to the issue.\n\nPrior to each team meeting the moderator will share the Agenda with\nmembers of the team. Team members can add any items they like to the\nagenda at the beginning of each meeting. The moderator and the team\ncannot veto or remove items.\n\nThe team may invite persons or representatives from certain projects to\nparticipate in a non-voting capacity.\n\nThe moderator is responsible for summarizing the discussion of each\nagenda item and sends it as a pull request after the meeting.\n\n## Consensus Seeking Process\n\nThe Performance Team follows a [Consensus Seeking][] decision-making model.\n\nWhen an agenda item has appeared to reach a consensus the moderator\nwill ask \"Does anyone object?\" as a final call for dissent from the\nconsensus.\n\nIf an agenda item cannot reach a consensus a team member can call for\neither a closing vote or a vote to table the issue to the next\nmeeting. The call for a vote must be seconded by a majority of the team\nor else the discussion will continue. Simple majority wins.\n\nNote that changes to team membership require unanimous consensus.  See\n\"Team Membership\" above.\n\n\u003ca id=\"developers-certificate-of-origin\"\u003e\u003c/a\u003e\n## Developer's Certificate of Origin 1.1\n\nUse of a CLA or DCO is mandatory for all all OpenJS Foundation projects. The Node.js project has chosen to use the DCO 1.1\n\nBy making a contribution to this project, I certify that:\n\n* (a) The contribution was created in whole or in part by me and I\n  have the right to submit it under the open source license\n  indicated in the file; or\n\n* (b) The contribution is based upon previous work that, to the best\n  of my knowledge, is covered under an appropriate open source\n  license and I have the right under that license to submit that\n  work with modifications, whether created in whole or in part\n  by me, under the same open source license (unless I am\n  permitted to submit under a different license), as indicated\n  in the file; or\n\n* (c) The contribution was provided directly to me by some other\n  person who certified (a), (b) or (c) and I have not modified\n  it.\n\n* (d) I understand and agree that this project and the contribution\n  are public and that a record of the contribution (including all\n  personal information I submit with it, including my sign-off) is\n  maintained indefinitely and may be redistributed consistent with\n  this project or the open source license(s) involved.\n\n## Moderation Policy\n\nThe [Node.js Moderation Policy][] applies to this team.\n\n## Code of Conduct\n\nThe [Node.js Code of Conduct][] applies to this team.\n\n[Node.js Code of Conduct]: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md\n[Node.js Moderation Policy]: https://github.com/nodejs/TSC/blob/master/Moderation-Policy.md\n[Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnodejs%2Fperformance","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnodejs%2Fperformance","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnodejs%2Fperformance/lists"}