Re: [VOTE] Release Apache TubeMQ (Incubating) 0.3.0-incubating RC0
> > I can’t compile from source as I have a newer version of protobuf installed > (3.6) and it looks like the build expects 2.5. Perhaps you should consider > updating to a newer version? > > With your LICENSE I think you have included far too many things. You only > need to mention something if it is bundled in the release you don’t have to > mention licenses of all dependancies. I can see data tables and jQuery but > not much else is bundled in your source release. There's also no need to have > multiple copies of the ALv2 license text. Hi justin, Thank you very much for your suggestions, these problems will be solved one by one in the next version. Thanks - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Mentors needed for Superset and Samoa
It is time for me to step down from the Incubator PMC. Before I officially depart I'd like to help the podlings I am currently mentoring, Superset and Samoa, find new mentors. If anyone has time and interest in mentoring these projects I would greatly appreciate their stepping in to replace me. "Superset is an enterprise-ready web application for data exploration, data visualization and dashboarding." The project has been growing the community and making regular releases and is nearing graduation. >From Samoa's self description: "SAMOA provides a collection of distributed streaming algorithms for the most common data mining and machine learning tasks such as classification, clustering, and regression, as well as programming abstractions to develop new algorithms that run on top of distributed stream processing engines (DSPEs). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Storm, Apache S4, and Apache Samza." The project has been in incubation for 5 years now and has at times struggled to keep momentum, though it has recently added a new committer and made a release. Alan.
Re: [MENTORS] Podling reports due today
Hi, The reporting deadline has come and gone and these podlings will be asked to report next month: - Hivemall - Spot - Warble Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-251) IP clearance for ShardingSphere ElasticJob
[ https://issues.apache.org/jira/browse/INCUBATOR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125700#comment-17125700 ] Liang Zhang commented on INCUBATOR-251: --- IP clearance vote passed[1]. [1] [https://lists.apache.org/thread.html/r750880f7295c1a8c31c99e7a40f3466c177bd714254d0c98a506dede%40%3Cgeneral.incubator.apache.org%3E] > IP clearance for ShardingSphere ElasticJob > -- > > Key: INCUBATOR-251 > URL: https://issues.apache.org/jira/browse/INCUBATOR-251 > Project: Incubator > Issue Type: Task >Reporter: Liang Zhang >Priority: Major > Attachments: elastic-job-cloud-master.zip, > elastic-job-doc-master.zip, elastic-job-example-master.zip, > elastic-job-lite-dev.zip > > > Liang Zhang(ShardingSphere VP) is contributing the ElasticJob to Apache > ShardingSphere. > > The clearance tasks are in progress and recorded at: > [http://incubator.apache.org/ip-clearance/shardingsphere-elasticjob.html]. > > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as elastic-job-lite-dev.zip, elastic-job-cloud-master.zip, > elastic-job-doc-master.zip and elastic-job-example-master.zip > > % md5 elastic-job-lite-dev.zip > MD5 (elastic-job-lite-dev.zip) = f4a5ca33c85ab7385a0c04e5c5f0cc56 > > % md5 elastic-job-cloud-master.zip > MD5 (elastic-job-cloud-master.zip) = 26555807a1db7cd232f77dfd2aad71a4 > > % md5 elastic-job-doc-master.zip > MD5 (elastic-job-doc-master.zip) = 8f100778334402724e1af2e996590e2e > > % md5 elastic-job-example-master.zip > MD5 (elastic-job-example-master.zip) = 008dc57833babcb10e34cad8151c61e5 > > IP clearance is: > [http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/shardingsphere-elasticjob.xml?view=markup] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-251) IP clearance for ShardingSphere ElasticJob
[ https://issues.apache.org/jira/browse/INCUBATOR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang Zhang closed INCUBATOR-251. - Resolution: Fixed > IP clearance for ShardingSphere ElasticJob > -- > > Key: INCUBATOR-251 > URL: https://issues.apache.org/jira/browse/INCUBATOR-251 > Project: Incubator > Issue Type: Task >Reporter: Liang Zhang >Priority: Major > Attachments: elastic-job-cloud-master.zip, > elastic-job-doc-master.zip, elastic-job-example-master.zip, > elastic-job-lite-dev.zip > > > Liang Zhang(ShardingSphere VP) is contributing the ElasticJob to Apache > ShardingSphere. > > The clearance tasks are in progress and recorded at: > [http://incubator.apache.org/ip-clearance/shardingsphere-elasticjob.html]. > > This issue is partly to track that and primarily to provide an official > record of the code drop contribution. The contributed code is attached to > this issue as elastic-job-lite-dev.zip, elastic-job-cloud-master.zip, > elastic-job-doc-master.zip and elastic-job-example-master.zip > > % md5 elastic-job-lite-dev.zip > MD5 (elastic-job-lite-dev.zip) = f4a5ca33c85ab7385a0c04e5c5f0cc56 > > % md5 elastic-job-cloud-master.zip > MD5 (elastic-job-cloud-master.zip) = 26555807a1db7cd232f77dfd2aad71a4 > > % md5 elastic-job-doc-master.zip > MD5 (elastic-job-doc-master.zip) = 8f100778334402724e1af2e996590e2e > > % md5 elastic-job-example-master.zip > MD5 (elastic-job-example-master.zip) = 008dc57833babcb10e34cad8151c61e5 > > IP clearance is: > [http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/shardingsphere-elasticjob.xml?view=markup] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] ShardingSphere ElasticJob project contribution
72 hours passed. We got +1 binding from Sheng Wu. Based on lazy consensus, this vote passed. Thanks. -- Liang Zhang (John) Apache ShardingSphere & Dubbo Sheng Wu 于2020年5月31日周日 下午4:12写道： > +1 binding. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > zhangli...@apache.org 于2020年5月31日周日 下午1:42写道： > > > Hi Incubator PMC, > > > > The TLP Apache ShardingSphere has been donated code for a scheduler > > framework, being > > referred to as `shardingsphere elasticjob`[1][2][3][4], old hostsd at > > [5][6][7][8]. > > > > Please notice, at this moment, GitHub repo has not been updated. > > > > The donated code can be found at [9] (*) > > > > Please see > > http://incubator.apache.org/ip-clearance/shardingsphere-elasticjob.html > > > > The PMC has voted and passed to accept this donation. > > The ICLA of major contributors, Liang Zhang, Hao Cao, Hongtao Gao and > > Guangyun Li have been filed > > before, as they are already ShardingSphere PMC and contributor. > > The SGA from Dangdang has been filed. > > The reason that Dangdang should submit SGA, because, in the old day, this > > project announced powered by Dangdang. Such as the latest release > > https://github.com/elasticjob/elastic-job-lite/releases/tag/2.1.5 > > > > Please vote to approve this contribution. > > > > This majority vote is open for at least 72 hours and as usual lazy > > consensus applies. > > > > [1] https://github.com/apache/shardingsphere-elastic-job-lite > > [2] https://github.com/apache/shardingsphere-elastic-job-cloud > > [3] https://github.com/apache/shardingsphere-elastic-job-doc > > [4] https://github.com/apache/shardingsphere-elastic-job-example > > [5] https://github.com/elasticjob/elastic-job-lite > > [6] https://github.com/elasticjob/elastic-job-cloud > > [7] https://github.com/elasticjob/elastic-job-doc > > [8] https://github.com/elasticjob/elastic-job-example > > [9] https://issues.apache.org/jira/browse/INCUBATOR-251 > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere > > >
Re: Issue with releases / feedback from ASF board
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 website would need to be updated to clarify that such binaries are provided by third parties and not associated with the ASF. Is that correct?” was answered as “correct" on the 5th May. > In response I have asked you, if it wouldn't be possible to first decide > how to properly disclaim links to third-parties on the website, It quite straight forward put a big disclaimer there saying these are not Apache releases. This as it has been discussed before here and examples easily found. e.g [1] >> WARNING: The following binary release is not provided by the Apache >> Software Foundation and third-party members of the MXNet community. >> They may contain closed-source components with restrictive licenses. >> You may want to download the official Apache MXNet (incubating) source >> release instead and build from source instead. Why say “may" when you know it to be incompatible with the Apache license? Be clear about the situation, your users deserve that. But something like this would be a good start. Making the source download more prominent would be another. Addressing any naming and trademark issues (also needed) can come later. > And in either case, if the Incubator prefers the route of updating the > website multiple times It's not hard to update the text on a website (or shouldn’t be). The incubator would prefer that the podlings follow ASF policy and when something serious is pointed out correct it in a reasonable amount of time. Yes some things may take time to discuss but you can still act in the meantime. In this case the right course of action should have been to clearly inform your users of the issue(s) while you were working out what to do. Adding a disclaimer is a good first step and could have been done before now. > But given your response, I now believe you may be referring to git tags > that were made prior to MXNet joining the incubator on 2017-01-23 / on > which no vote by the PPMC took place? Correct. Be sure to clearly label these are not ASF releases. Also be clear to clearly label any release that is not compatible with the Apache license. Basically a user should not be surprised to find out what they have been using is not an Apache release or is not compatible with the Apache license. Thanks, Justin 1. https://nuttx.apache.org/download/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Issue with releases / feedback from ASF board
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 help people get started with MXNet but are not provided by the ASF. If that's correct, I would phrase your disclaimer a bit differently. > > > WARNING: The following binary release is not provided by the Apache > > Software Foundation and third-party members of the MXNet community. > > They may contain closed-source components with restrictive licenses. > > You may want to download the official Apache MXNet (incubating) source > > release instead and build from source instead WARNING: the following links are provided for your convenience but they point to packages that are *not* provided nor endorsed by the Apache Software Foundation. As such, they might contain software components with more restrictive licenses than the Apache License and you'll need to decide whether they are appropriate for your usage. Like all Apache Releases, the official Apache MXNet (incubating) releases consist of source code only and are found at . -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Issue with releases / feedback from ASF board
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 ASF policies. The page currently provides names of third-party binary distributions not controlled by the PPMC which may confuse some users. Let's take a look at the timeline first: 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. In fact the majority of questions in LEGAL-515 remained unanswered throughout May (starting May 8th). Note that prior to my question in LEGAL-515, the MXNet website has been mentioning the names of third-party distributions already. You just now stated: > You were asked to do something about this a few weeks ago and as far > as I can see have not done so. Please do so as soon as you can. That's not entirely correct. I note that there a two different requests. On May 24th you have contacted the PPMC, requesting the PPMC to (among other things) improve the clarity of the Getting Started page: > It also needs to be clear what a user is installed from this install > page [http://mxnet.incubator.apache.org/get_started] PPMC has been working on resolving this question in LEGAL-515 since May 5th and has also requested guidance from the trademark@ team. This was still ongoing at the time of your email today. Today you have contacted the PPMC with a different request about the Getting Started page: > 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. In response I have asked you, if it wouldn't be possible to first decide how to properly disclaim links to third-parties on the website, before removing the links and then potentially adding them back with a disclaimer later. This is a very simple question. It's quite late in my timezone and updating the website will take some time. Why not udpate the website once correctly instead of taking a route that requires multiple updates? To resolve the situation, I suggest we start from your statement here: > No Apache project should be distributing 3rd party releases from their > web site without clearly informing the users of what they are getting. Does adding the following notice pior to any mentioning of a third-party binary release work for clearly informing users? > WARNING: The following binary release is not provided by the Apache > Software Foundation and third-party members of the MXNet community. > They may contain closed-source components with restrictive licenses. > You may want to download the official Apache MXNet (incubating) source > release instead and build from source instead. If so, PPMC can initiate the process of adding this statement to the website tomorrow. If not, do you have a better suggestion? And in either case, if the Incubator prefers the route of updating the website multiple times and leaves a partially empty website in the intermediate time, then let it be that way and PPMC may initiate that process tomorrow. >> 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. > > Yes they do but they consists of Apache releases it looks like you > have non Apache releases there. Other projects tag these add notes to > make it very clear they are not Apache releases. The context here is that I requested you to clarify on your mail from May 24th in which you stated: > The GitHub download page [2] is also confusing as it contains a mix of > Apache and non-Apache releases My understanding of your statement was that you refer to the source archives created by Github, which are not the official ASF source archives. MXNet project uploaded the ASF source archives in addition to the Github source archives to ensure users can easily discover them. But it appears this is not what you meant with "confusing" . But given your response, I now believe you may be referring to git tags that were made prior to MXNet joining the incubator on 2017-01-23 / on which no vote by the PPMC took place? Adding notes to those releases can be done easily if that is what you request. Best regards Leonard - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
