HI,
> Users should run `npm install xxx`, `pip install xxx`, or `cargo add xxx`
> to include our library in their dependency list. Users should write code
> in their own libraries or applications using statements such as `use xxx`
> or `import xxx`. Adding the prefixes `apache-` or `asf-`
For the platforms npm, PyPI, crates.io, and NuGet, the situation is somewhat
different: We deliver libraries instead binaries.
Users should run `npm install xxx`, `pip install xxx`, or `cargo add xxx`
to include our library in their dependency list. Users should write code
in their own
Hi,
> The proposal here is to improve the expression on NPM / PyPI for the
> package name to be either:
>
> 1. apache-projectname
> 2. projectname
Existing ASF policy has this to say:
- "All PMCs must to comply with the Apache Project Branding Requirements.” [1]
- “PMCs are directly responsible
Hi,
I’ll note these guidelines were discussed and voted on by the IPMC a while
back. Legal and trademarks also reviewed them and had input, and the work is
based on existing policy and years of discussion. They, however, have only had
minor updates since being formed.
Kind Regards,
Justin
I found the original discussion for this guideline[1], and I respect
that the Incubator did such pioneer works to provide a base to discuss
and evolve.
The proposal here is to improve the expression on NPM / PyPI for the
package name to be either:
1. apache-projectname
2. projectname
or loosely
Hi,
The Distribution Guidelines[1] in ASF Incubator website wrote:
* Artifacts show up on https://www.npmjs.com/package/apache-;
version page.
* Artifacts need to be placed in
https://pypi.org/project/apache-;. To comply with ASF release
and distributions please ensure the following:
Both
