Hi Bruce,

Thanks for your reply.

>  Why do the NOTICE files make note of commons-lang including something
from the Spring Framework?

commons-lang has this in its NOTICE file[1], so we added this to our NOTICE
file.

[1]. https://github.com/apache/commons-lang/blob/master/NOTICE.txt

> What is the policy for pointing users at Stackoverflow and Quora? I don't
think this should be included in the README (In fact, we should create a
users@rocketmq mailing list)

Mainling list is the first place in the section `Learn it & Contact us`,
and if Stackoverflow and Quora shouldn't be here, we will remove it next
release.

> About the file name

The binary file name is a legacy issue, we will unify the source release
and binary release file name in next release.

Regards,
yukon

On Thu, Feb 16, 2017 at 5:46 AM, Justin Mclean <[email protected]>
wrote:

> Hi,
>
> > * It's definitely odd to point to Maven central and Github for
> incubating project releases
>
> It’s more than odd, it’s not in line with policy. You must point to the
> primary source of distribution at Apache, Maven and Github can be mentioned
> as secondary distribution points but should not take prominence over the
> Apache links.
>
> Github releases are misleading as anything that is tagged GitHub assumes
> is a release even though (at that point) it will not have not been voted
> on. For example see [2] Please remove the link to GitHub release form the
> REAME.
>
> > * What is the policy for pointing users at Stackoverflow and Quora? I
> don't
> > think this should be included in the README (In fact, we should create a
> > users@rocketmq mailing list)
>
> Again users should be pointed the mailing lists first, then other places.
> I think the REAMDE is OK here.
>
> > * Why do the NOTICE files make note of commons-lang including something
> > from the Spring Framework?
>
> That’s correct see [1]
>
> > * Shouldn't the release artifact names both be apache-rocketmq-*.zip?
> > ** Also, the binary artifact unzips to a directory named
> > apache-rocketmq-all-* whereas the source artifact unzips to a directory
> > named rocketmq-all-*
>
> There’s no policy on naming, it’s up to the PPMC but having apache in the
> name is good from a branding and legal point of view.
>
> RE the README this is also still an issue with the "Apache RocketMQ
> Community” section. The community is not at https://github.com/rocketmq
> it is here at Apache!
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> 2. https://github.com/apache/incubator-rocketmq/releases

Reply via email to