Looking at the linked official release documentation, I think this comment is no longer valid. Moreover, I cannot find an explanation why some projects are allowed to publish on npm and others not.
Cheers, Till On Mon, Jan 24, 2022 at 4:14 PM Chesnay Schepler <ches...@apache.org> wrote: > What is your explanation for the comment in the ticket then? > > On 24/01/2022 16:07, Till Rohrmann wrote: > > I am not sure whether this is really a problem. There are other Apache > > projects that publish their artifacts on npm already [1, 2]. > > > > Also on the official release page [3] there it is written: > > > >> After uploading to the canonical distribution channel, the project (or > > anyone else) MAY redistribute the artifacts in accordance with their > > licensing through other channels. > > > > [1] https://www.npmjs.com/package/echarts > > [2] https://www.npmjs.com/package/cordova-coho > > [3] > https://www.apache.org/legal/release-policy.html#release-distribution > > > > Cheers, > > Till > > > > On Mon, Jan 24, 2022 at 3:54 PM Chesnay Schepler <ches...@apache.org> > wrote: > > > >> I'm concerned about a comment in > >> https://issues.apache.org/jira/browse/INFRA-19733 stating that npm is > >> not an approved release channel. > >> I don't really know what to make of it and neither the current nor past > >> versions of the linked legal page shed some light on it. > >> > >> As such it would be a good idea to double-check whether we are even > >> allowed to publish anything on NPM. > >> > >> On 24/01/2022 15:42, Ingo Bürk wrote: > >>> Hi Till, > >>> > >>> speaking as someone who regularly works with JavaScript/TypeScript, > >>> definitely a +1 from me to providing this on the npm registry to make > >>> it an easy installation for developers. > >>> > >>> > >>> Best > >>> Ingo > >>> > >>> On 24.01.22 15:37, Till Rohrmann wrote: > >>>> Hi everyone, > >>>> > >>>> I would like to start a discussion about hosting > >>>> StatefulFunction's JavaScript SDK [1] on npm. With the upcoming > Statefun > >>>> 3.2.0 release, the JavaScript SDK will be officially supported. In > order > >>>> for users to easily use this SDK, it would be very convenient if we > make > >>>> this dependency available via npm. Therefore, I propose to create a > npm > >>>> account that is governed by the PMC (similar to PyPI). > >>>> > >>>> Do you have any concerns about this? > >>>> > >>>> [1] https://issues.apache.org/jira/browse/FLINK-24256 > >>>> > >>>> Cheers, > >>>> Till > >>>> > >> > >
