Decentralized module delivery

[scriptjs]

I am asking that the TSC begin to explore a future of module delivery for node that is decentralized. Along with this, it should assume control of determining future standards around the use of the package.json. A decentralized approach (as opposed to what today is centralized) for module distribution is safest at scale. The Web itself was designed around this philosophy and it is a useful model for the scale of node.

Further, the node community and TSC must retain control over the user experience of node. The future of module delivery can and should involve multiple players that deliver according to standards that are developer driven and in consultation with the TSC that can assure this interest.

The process of moving forward can and should involve the community in determining possible approaches, tests, and be given careful consideration over time since we are now into an LTS approach to releases. This future can evolve with es6 and with the purpose of moving away from the legacy of a single upstream service.

[Fishrock123]

@scriptjs could you move this issue to https://github.com/nodejs/NG? It'l probably be better over there.

[scriptjs]

@Fishrock123 I created nodejs/NG#26 for this but would like this issue to remain since I don't see this as a very long range goal. I rather see this as a priority since alternate approaches can begin to be discussed, considered and tests undertaken well in advance of the fully restructured node of our future.

[ChALkeR]

I guess I should leave this here: https://twitter.com/izs/status/690385503519117312

[bnoordhuis]

Huh, so npm, inc. is acting as moral guardian too, now? What could possibly go wrong?

[defnorep]

@bnoordhuis: I didn't even see any white smoke.

[joshmanders]

While I understand izs made a joke (since deleted it), it still worries me that we put so much reliance on a company who can, and will make such claims.

[joshmanders]

For those wondering, Izs made a joke saying anyone who breaks npm code of conduct on github gets blacklisted from the registry by ip (as if github gives ip addresses of users to a 3rd party like npm anyway)

[ChALkeR]

@joshmanders That didn't look like a joke to me.

See the following threads: one (asking him if he is serious), two (regarding the IP source), three.

[joshmanders]

@ChALkeR wow I didn't see those. I retract my statement and my worrying intensifies.

[jasnell]

While we do need to make sure that any issues are surfaced, we need to make sure we don't jump to conclusions or have a pile on with this. Let's make sure we keep the conversation productive and let's keep in mind that this issue tracker here is to track technical issues with Node core. A more appropriate location for this discussion would likely be the issue tracker in the nodejs/TSC repository (https://github.com/nodejs/TSC).