My two cents:

Publishing to npm would be a community thing as a convenience not an official 
distribution guaranteeing the bytes for a third party service (ie npmjs.org)

No need to vote on the npmjs.org published, vote should already happened for 
the source code and the tgz source code published. 

Just setup some scripting that publishes the already voted tgz source to 
npmjs.org server. 

- Carlos Santana
@csantanapr

> On Feb 28, 2020, at 11:43 AM, David P Grove <gro...@us.ibm.com> wrote:
> 
> 
> 
> Alexander Klimetschek <aklim...@adobe.com.INVALID> wrote on 02/28/2020
> 01:44:51 AM:
>> 
>>> We own both the @openwhisk and @apache-openwhisk organizations, so
>>> we could choose to use either as a scope for this new package.
>> 
>> I did not see any @openwhisk or @apache-openwhisk scopes on npm (no
>> results for e.g. [1]). Which are you referring to?
> 
> We have not published a package to either one of these scopes, but the
> organizations already exist and are owned by the PMC's "openwhisk-bot"
> functional id.  The existence of the org claims the scope.
> 
> We should be able to publish a package to either one of those scopes at any
> time without additional setup (after we go through the usual voting process
> to actually have content to put there).
> 
> --dave

Reply via email to