Re: Issue with releases / feedback from ASF board
Hi Justin,
Justin Mclean writes:
> It’s quite clear they should not be linked to from an Apache page
> like this as users will think these are Apache releases. Please remove
> them, after that bring it up on the incubator general list and we can
> discuss what needs to be done.
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?
>> Also I notice you referred to the Github Release page. Github will
>> automatically
>> provide a ZIP folder ("Source code (zip)") for the commit tagged as release.
>> PPMC has further uploaded the ASF .tar.gz, .tar.gz.asc and .tar.gz.sha512. Is
>> that what you mean with confusing mix of "Apache and non-Apache releases”?
>
> You need to mark anything that is not an Apache release very clearly
> and if that cannot be done them it needs to be removed.
I'm not sure what you mean. Note that Github automatically creates these
release pages based on the presence of git tags in the version control
history.
I looked at a number of Apache projects and their Github Release pages.
By the very nature of how Github presents the release page, they all
contain links to download a source archive provided by Github. Different
to MXNet, these projects do not in addition provide the ASF source
archives on their Github release page, but only the Github source
archives.
- Apache Arrow: https://github.com/apache/arrow/releases
- Apache Hadoop: https://github.com/apache/hadoop/releases
- Apache Maven: https://github.com/apache/maven/releases
Most closely, the Apache Beam project includes changelog in a similar
manner as MXNet and also tags RC releases on Github:
- Apache Beam https://github.com/apache/beam/releases
So is your recommendation here to take down the ASF source archives, ie.
the .tar.gz, .tar.gz.asz and .tar.gz.sha512 files and only keep the
basic Github functionality? This will make it harder for users to
discover the official ASF releases, but it's certainly something we can
do.
Best regards
Leonard
Re: Issue with releases / feedback from ASF board
Hi,
> this page currently contains some links to third-party binary distributions of
> MXNet (for example at [1]). The question of what the PPMC should recommend
> those
> third-parties to avoid trademarking issues is currently being discussed on
> private@ and trademark@.
It’s quite clear they should not be linked to from an Apache page like this as
users will think these are Apache releases. Please remove them, after that
bring it up on the incubator general list and we can discuss what needs to be
done.
> Also I notice you referred to the Github Release page. Github will
> automatically
> provide a ZIP folder ("Source code (zip)") for the commit tagged as release.
> PPMC has further uploaded the ASF .tar.gz, .tar.gz.asc and .tar.gz.sha512. Is
> that what you mean with confusing mix of "Apache and non-Apache releases”?
You need to mark anything that is not an Apache release very clearly and if
that cannot be done them it needs to be removed.
Thanks,
Justin
Re: Issue with releases / feedback from ASF board
Hi Justin,
this page currently contains some links to third-party binary distributions of
MXNet (for example at [1]). The question of what the PPMC should recommend those
third-parties to avoid trademarking issues is currently being discussed on
private@ and trademark@.
With respect to the MXNet Website linking to third-parties, I haven't been able
to find a policy yet. The current plan is to add a disclaimer and bring this up
with the Incubator for review. Do you think that's sensible? Do you have any
other recommendation?
Also I notice you referred to the Github Release page. Github will automatically
provide a ZIP folder ("Source code (zip)") for the commit tagged as release.
PPMC has further uploaded the ASF .tar.gz, .tar.gz.asc and .tar.gz.sha512. Is
that what you mean with confusing mix of "Apache and non-Apache releases"?
Best regards
Leonard
[1]:
https://mxnet.apache.org/get_started?platform=linux=python=gpu=pip;
;
On Wed, 2020-06-03 at 23:50 +, Justin Mclean wrote:
> Hi,
>
> I don't see what has been done about this [1] which I mentioned above. What is
> the planned action here?
>
> Thanks,
> Justin
>
> 1. https://mxnet.apache.org/get_started?
>
Re: Issue with releases / feedback from ASF board
Hi, I don't see what has been done about this [1] which I mentioned above. What is the planned action here? Thanks, Justin 1. https://mxnet.apache.org/get_started?
