Alright, I hope that we could resolve all mentioned concerns. If not, then
please speak up. I will try to set up a npm account for the Flink project.
Cheers,
Till
On Mon, Jan 24, 2022 at 4:40 PM Till Rohrmann wrote:
> Reading the description of the ticket again, I think the comment might
> also
Reading the description of the ticket again, I think the comment might also
simply relate to the fact that the ASF does not have its own npm account.
So there is no official npm release channel.
Note that this is not what we would need here.
Cheers,
Till
On Mon, Jan 24, 2022 at 4:37 PM Chesnay S
I looked at the 2018/2020 versions of the page and also couldn't find
anything that relates to the comment.
That's why this is so weird to me; it seems to be based on some
knowledge that isn't written down explicitly.
There aren't any limitations/requirements for (secondary) distribution
chann
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 wrote:
> What is your explanation f
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:
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
+1 for publishing to npm in addition to an official source release, would
be very beneficial.
Looking at other Apache projects that produce js artifacts[1] , it seems
like they also publish to npm.
[1]
https://github.com/orgs/apache/repositories?q=&type=all&language=javascript&sort=
Cheers,
Igal.
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 id
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 abou
