I don't see the need for this to cherry pick a few project and push them with the Linux brand. The JS landscape is fragmented for a good reason and I don't see that as problem in fact, rather as a feature. With NPM and YARN we already have a good enough package management system and their platform can help me evaluate if a package is community supported enough. I'm talking about the stats that I can just check: numbe…
How can you find the js fragmentation a feature and not a stinking pile of shit? Seriously.
The Linux Foundation Unites the JavaScript Community for Open Web Development
21–30 of 134 posts
Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#22Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#23From my perspective the main benefit of this is there is now a non profit that can take over administration of JS projects the community values but the original developers want to abandon.
Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#24Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#25From my perspective the main benefit of this is there is now a non profit that can take over administration of JS projects the community values but the original developers want to abandon.
Has such an argangment ever worked in practice? I have read here on HN about how the Apache brand is used as a dumping ground for zombie projects. Why would it be different for the Linux Foundation?
Seems to me like it get's updated
Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#26Does anyone know if this will affect the licensing of these projects? Linux uses GPL, but I believe most of these projects use MIT.
Also the JS Foundation already announced that they're adopting the Apache 2.0 license as the default license but that existing projects will keep their MIT/etc licenses. Their open source licensing policy is hidden in the "IP Policy" PDF linked in the footer: https://js.foundation/pdf/ip-policy.pdf
Quote:
> The technical governing body of each Project is free to choose, [..] the Apache License, Version 2.0 [..]. If an alternative inbound or outbound license is required [..], the Board of Directors of the JS Foundation (the “Board”) may approve the use of an alternative license for inbound or outbound contributions on an exception basis.
Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#27Does anyone know if this will affect the licensing of these projects? Linux uses GPL, but I believe most of these projects use MIT.
The Linux Foundation already has a wide variety of projects besides Linux which are covered by a number of different licenses depending upon the project. https://www.linuxfoundation.org/projects
Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#28As confusing as this appears (are they going to handle new ECMAScript specifications? I am so confused), I am glad that they're supporting Moment.js. It has become one of my default libs, like jQuery, when working on a new project.
The JS Foundation is not related to TC39, the organization in charge of new ECMAScript editions. I guess they might sponsor a TC39 member eventually and engage in JS advocacy beyond merely supporting JS open source projects -- similar to what the PSF and its affiliates do for Python.
Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#29I don't see the need for this to cherry pick a few project and push them with the Linux brand. The JS landscape is fragmented for a good reason and I don't see that as problem in fact, rather as a feature. With NPM and YARN we already have a good enough package management system and their platform can help me evaluate if a package is community supported enough. I'm talking about the stats that I can just check: numbe…
Re: The Linux Foundation Unites the JavaScript Community for Open Web Development
#30Interested to hear - what kind of effect will this have on the fragmentation we see in the JavaScript ecosystem?
Case in point: https://medium.com/webpack/sustaining-webpack-for-the-future...