Thank you Betrand for the suggestion.
I have created a pull request to update the website. Anyone interested,
please take a look and leave feedback in the pull request or via
response to this mail. There is no preview of the resulting page
available, but we can also iterate via multiple pull
Hi,
> On May 5th 2020 I have opened LEGAL-515 and asked (among other
> questions) how the MXNet PPMC can correctly reference third-party
> distributions on the website. Unfortunately that question was not answered.
It looks answered to me. Your question “Finally, I believe the MXNet project
Hi,
On Thu, Jun 4, 2020 at 8:44 AM Leonard Lausen wrote:
> ...Does adding the following notice pior to any mentioning of a third-party
> binary release work for clearly informing users?...
I haven't followed all the details but IIUC what you are doing is
linking to third-party packages that can
Hi Justin,
as there have been a couple of mails on the dev@ list prior to your mail
to general@ list and your mail contains a dramatic opening, I'd like to
provide some context here.
The problem in the current focus is how to ensure the
http://mxnet.apache.org/get_started page is compliant with
Hi,
> The status quo has been in place since a while. Do you think we have
> time to first discuss the correct solution on the Incubator list, before
> we delete the existing pages?
I’ll ask again. Please remove any releases that are not Apache releases, that
includes any releases that are not
Hi Justin,
Here's an update on the progress of addressing the license issues:
Done:
- Add disclaimer to repo.mxnet.io and dist.mxnet.io to clarify that the
nightly releases there are not intended for public consumption. (changed.
pending cache refresh)
- Remove non-Apache releases in github
Hi,
I'm writing my board report in the next couple of days and just wondering what
progress has been made on this.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands,
Thanks for the reply. Besides the clarification below, we will track and
address here [1] the rest of the comments in this thread.
> > - We will introduce source releases on PyPI and Maven using apache-mxnet
> > name to provide users with the option to have Apache distribution and
allow
> > users
Hi,
> Here are some examples using search:
> - Arrow https://arrow.apache.org/docs/python/cuda.html
"This functionality is optional and must have been enabled at build time. “
So you as a user needs to recompile the code, checking their downloads page
this also seems to be the case and there’s
>
> I’m not aware of any other project that uses CUDU code.
>
I want to point out that most machine learning and analytics related
projects will likely need to involve (and likely distribute) CUDA code,
this would include some of the current TLPs.
Here are some examples using search:
- Arrow
Hi,
> - MXNet publishes only nightly pre-release builds to dist.mxnet.io for the
> verification purpose for projects in the ecosystem and for developers who
> work on the bleeding edge.
IMO Something more needs to be done here, at the very least I would expect to
se a very large disclaimer that
Hi Justin and incubator,
Thank you for the feedback.
1. We fully intend to address the licensing issues in releases and software
distributions as part of our efforts towards graduation.
2. To my knowledge, there was no intention from this PPMC to bypass the
software release policy.
To clarify
12 matches
Mail list logo
