Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-07-17 #732
Comments
|
Based on nodejs/Release#341 (comment), should nodejs/Release#341 be removed from the agenda? If so, then we have a very light agenda, with the only non-standing issue being something that has an active email thread going on. Seems like the meeting could be canceled. |
|
Yes, #341 should have had the tag removed, done that now and removed from agenda. |
|
I'm +1 to canceling this week unless somebody has something to add to the agenda. |
|
👋I'd like to join this meeting and discuss some package namespace concepts the GitHub Package Registry team is considering. We would value your input on the direction we're taking. Single source of truthFor simplicity and security GPR (the GitHub Package Registry) plans to provide a system for "upstreaming NPM" such that our users only need to add a single registry URL to their config. npm login --registry=https://npm.pkg.github.comThrough this single URL users should have access to both NPM packages and those packages which reside on GPR. However we have been running into issues with namespace conflicts with the NPM registry given its global name resolution and separate namespace system. Namespace ProblemsGitHub offers namespaces through organizations (https://github.com/nodejs/), users (https://github.com/clarkbw), and repos (https://github.com/nodejs/TSC/ or https://github.com/clarkbw/jest-localstorage-mock). But our namespaces are often different from those namespaces on NPM and this creates the conflict when trying to use a single source; who is correct if both have an answer. For example our system currently allows you to require a module with a namespace. Without upstream support this isn't a problem but when we combine both our system and NPM you don't know which system namespace "dependencies": {
"@octo-org/octo-app": "1.0.0"
}This namespace conflict is apparent with namespaces URLs as namespaceOur long term plan is to use URLs as a namespace prefix such that The problem we face when trying to use URLs is that the NPM client mostly assumes that a GitHub URL means direct Protocol as namespaceAn alternate version of the URL as namespace is using a protocol instead such that GPR requests are prefixed with Hybrid solutionThe GPR team would like to make progress on the longer term solution, we believe to be something like URL namespaces. At the same time we want to make forward progress on a solution that could work better in the next couple months. We're looking at a number of different solutions for the near term that will allow our users to use GPR as expected while we work toward a more stable namespace solution like URLs. These solutions are purely temporary so we can get up and running without requiring changes to clients that take time to propagate out. Namespace PrefixOne example temporary solution is to use a prefix on namespace like We're humbled to be able to take part in this conversation and appreciate your time, thoughts, and advice on these proposals. |
|
cc @nodejs/modules @clarkbw we have a meeting of the Modules group tomorrow (nodejs/modules#349 (comment)); it might be a better place to have initial conversations? |
Happy to join that one instead and not be on the hook for an 8am meeting 😴 😄 |
|
@clarkbw It may help to copy that write-up into an issue (either in nodejs/node or nodejs/modules) so we can properly tag it and also in case there's additional discussion beforehand. |
|
@clarkbw I was just coming back to this issue to see if we'd cancel for this week. If a good starting point is to start the discussion in the modules team meeting then I'll go ahead and cancel this unless there are objections from @nodejs/tsc |
I'm happy to start there! |
|
Canceling meeting for today. If you are interested in the discussion on namespacing make sure to attend the Modules meeting today. |
Time
UTC Wed 17-Jul-2019 15:00 (03:00 PM):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/Release
nodejs/TSC
Invited
Observers/Guests
Beth Griggs @BethGriggs (guest participant)
Notes
The agenda comes from issues labelled with
tsc-agendaacross all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
Zoom link: https://zoom.us/j/611357642
Regular password
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: