Repository navigation
PkgJS Org for WG supported tooling #271
Description
As discussed in our meeting and in #263, we will be using the @pkgjs github org as well as npm namespace for publishing our tooling. To kick things off we have a small todo list:
- Change the licenses to MIT for existing repos
- Assemble a list of contributors to grant access
- Define a process for adding new members
- Explicitly adopt the governance structure of the Node org for managing the projects
- get these reviewed/landed pkgjs/* and nodejs/ci-config* repo housekeeping #348
- 2FA Publishing CI Publish with Two-Factor Auth for Teams #244
- Moderation team access
- TSC members as owners
- Add node js foundation account on npm
To start we can post users here who want to be added to that org as well as discuss what processes we need to document so that we are fully in line with the contribution and governance models Node has.
Activity
dominykas commentedon Oct 22, 2019
✋
We need to move on solving that 2FA publishing problem ;)
wesleytodd commentedon Oct 22, 2019
YESS! Added to the todo list!
lholmquist commentedon Oct 24, 2019
/me would like to be added
mhdawson commentedon Oct 24, 2019
I'd like to be added, but will need to wait until the licences are updated and then I can request the ok to contribute.
Eomm commentedon Oct 25, 2019
I should have upgraded the licence to MIT for the 6 repo... great test in production for massive wax 😅
If you need more "broadcast" operation let me know!
Edit: ✋🏻
wesleytodd commentedon Nov 3, 2019
Ok, all the license changes are made and everyone from this thread so far is invited. 🎉
mhdawson commentedon Nov 4, 2019
@wesleytodd thanks, requesting the ok to contribute to that org internally now :)
wesleytodd commentedon Feb 11, 2020
To follow up from our meeting today, the next steps for this is to raise this up to the greater Node community (maybe via the TSC?) and see how others are managing this and how we might make this official without loosing out on the reasons we thought a separate org was a good idea in the first place.
So, does anyone know of other teams/wg's which do this? If so how are they managing it. Also, should we raise an issue on the TSC repo to discuss? It was brought up that @mhdawson probably has the best view of what the next steps should be.
mhdawson commentedon Feb 17, 2020
@wesleytodd do we have a list of those reasons that we can use for the discussions? Most if not all of the teams I know of are using repos under the Node.js org.
Can you also clarify what you mean by "official". I thought one of the concerns that led to a separate org was avoiding the impression of it being official.
wesleytodd commentedon Feb 20, 2020
I think it was burried in an unrelated issue, I will dig for it and pull it into the OP here.
How many of them are producing tools like we want to build? When I look at the repos in the node org I don't see much like what we have currently in
pkgjs.Official in this sense is about governance and ownership, and the thing we wanted to avoid was canonical implementation squashing competitive libraries. I think these are separate meanings of "official".
mhdawson commentedon Feb 20, 2020
@wesleytodd the closest is possibly node-addon-api, and nan. Others repos for tools like https://github.com/nodejs/create-node-meeting-artifacts are more for internal use. Mostly I was saying that other teams are using repos in the org, not that they are doing something similar.
In terms of "official", then what you might be asking is if the Node.js Project can 'own' and additional repo, with the TSC delegating management of it to the Package-maintenance team and ask that things like moderation be extended to this new org. Is that a good way to describe it?
wesleytodd commentedon Feb 20, 2020
Yeah, described very well!
Got it. I think that our differences matter here. Internal tools don't really confer any sense of "official implementation" and things like nan are actually supported official projects.
mhdawson commentedon Feb 21, 2020
Created this issue in the admin repo to start the discussion at the project level: nodejs/admin#470
dominykas commentedon Feb 23, 2020
I think there are two more aspects where the second org makes sense:
nanhave the "backed by foundation" aspect, whereas the tooling that we're experimenting with are somewhat different?8 remaining items
rodion-arr commentedon Jul 23, 2020
Hi all, if you need some help with tooling, please let me know, I will be happy to jump in
wesleytodd commentedon Jul 23, 2020
@rodion-arr Do you have a particular project you would like to work on? Happy to get you setup with on the triage team if you are unsure yet. Let me know.
rodion-arr commentedon Jul 23, 2020
@wesleytodd I did small contribution to
supportand a little bit familiar withwiby. I will be happy do some coding, but it is quite difficult for me to find here specific tasks to work on.Anyway, I ready to spent some time in activities according to your priorities.
wesleytodd commentedon Jul 23, 2020
Invite sent. I think it might be a bit "self guided" right now, but if you have any ideas and want to get team feedback you can always open an issue to discuss what you are thinking.
mhdawson commentedon Jul 23, 2020
PR with suggestion of initial administrative members:
#390
After we agree on the set of administrative members, I think the next step is to make sure we think the pkgjs org/repos meet the requirements we laid out in the governance and then move over the org, add access to the TSC etc.
mhdawson commentedon Aug 25, 2020
Next steps:
dominykas commentedon Aug 28, 2020
Since all members already had that, I enforced 2FA in the pkgjs GH org.
Also updated @BethGriggs, @ljharb, @Eomm to owners and invited @ghinks as outlined in https://github.com/nodejs/package-maintenance/blob/master/ADMINISTRATIVE-MEMBERS.md
helio-frota commentedon Oct 8, 2020
@wesleytodd could I please be added to pkgjs? Planning to work on all repos as long term thing (learning-n-contributing).
helio-frota commentedon Oct 8, 2020
@wesleytodd thank you.
dominykas commentedon Oct 13, 2020
mhdawson commentedon Oct 15, 2020
Landed the on-boarding doc update to add TSC members to the pkgjs org as owners and to a team, and did the required additions for existing TSC members.
Next up do the same for the moderation onboarding documentation.
mhdawson commentedon Oct 19, 2020
Landed updated documentation for moderation onboarding, and updated so moderation team members are owners of the pkgjs org.
mhdawson commentedon Oct 20, 2020
Everything complete, closing