Re: Podling names pre code transfer
Agreed, remove "or pre-code-drop process” would be much more clear. FYI: I always have the wrong impression that podlings are encouraged to call themself Apache Incubator-PodlingName before they graduates. Now, a lesson is learned for me, thanks. Best Regards, York Shen 申远 > 2019年10月17日 22:42，John D. Ament 写道： > > Hi, > > I've always read this as "some code" rather than "all code" since "all > code" is a completely unbounded endpoint which no project could ever reach > until it retires. So as long as some code is in our repos, they must be > called "Apache " > > My $0.02 > > John > > On Thu, Oct 17, 2019 at 8:36 AM Justin Mclean > wrote: > >> Hi, >> >> I was reviewing this page [1] and noticed that what is current states is >> not what happens in practice. Podlings are encouraged to called themselves >> "Apache XXX" fairly early on and it takes some podlings a while to get all >> the code submitted the ASF repositories. In particular some projects with >> multiple repositories would have issues with this. Under a strict >> interpertation some podlings would not even be able to call themselves >> “Apache XXX” on graduation which seems a bit silly. Should it be clarified >> as the first donation? I think it may makes sense to simplify those 3 >> stages as proposal, approved and graduated and remove mention of the code >> drop altogether. Releases can’t be called Apache releases until the code >> moves over obviously. >> >> Thanks, >> Justin >> >> 1. >> https://incubator.apache.org/guides/branding.html#publicity_throughout_the_incubation_process >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: [IP CLEARANCE] Apache NetBeans - dukescript presenters
If my memory was right, you could disclose the link of your reception as individuals without the proper right will not be able to open the link. Everything is safe. Correct me if I am wrong. Best Regards, York Shen 申远 > 2019年10月16日 18:52，Eric Barboni 写道： > > Hi > Not sure if I have to do something. > But secretary give us feedback on our private list for reception of files. > But should not be disclose I guess. > I have no access to secretary ml, so cannot help. > > Best Regards > Eric > -Message d'origine- > De : Matt Sicker > Envoyé : mercredi 16 octobre 2019 06:30 > À : general@incubator.apache.org > Objet : Re: [IP CLEARANCE] Apache NetBeans - dukescript presenters > > There should be an automatic email receipt of the secretary filing the doc. > > On Tue, Oct 15, 2019 at 23:02, 申远 wrote: > >> Not sure SGA is required in this situation as it seems like there is >> an employment in Dukehoff GmbH. >> >> FYI: Add the link about the communication with secretary would be a >> great, which gives an individual to look into what's happening if >> he/she has the privilege in secretary@asf mailing list. >> >> Best Regards, >> YorkShen >> >> 申远 >> >> >> Eric Barboni 于2019年10月15日周二 下午10:49写道： >> >>> Hi community >>> >>> Apache NetBeans received a donation called dukescript presenters. >>> This donation goes in the Apache NetBeans html4j subproject. >>> >>> Form for ip clearance is here : >>> >>> >> https://incubator.apache.org/ip-clearance/netbeans-dukescript-presente >> rs.htm >>> l >>> I had issue to regenerate the page please note that PR link is the >>> following >>> >>> https://github.com/apache/netbeans-html4j/pull/23 >>> Commit id if needed >>> >>> >> https://github.com/apache/netbeans-html4j/commit/383122eb00479d12b8df1 >> 810c26 >>> e7596fa0672d0 >>> < >> https://github.com/apache/netbeans-html4j/commit/383122eb00479d12b8df1 >> 810c26e7596fa0672d0 >>> >>> >>> >>> Please vote to approve this contribution. Lazy consensus applies: If >>> no >> -1, >>> votes are being cast within the next 72 hours, the vote passes. >>> >>> Best Regards >>> Eric >>> >>> >>> >>> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >> > -- > Matt Sicker > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: Open up incubator wiki to all committers
+1 Great idea. It could save everyone’s time in this mailing list, IMO. BTW, I just add RW access to all committers in Weex Wiki space. Best Regards, York Shen 申远 > 2019年10月10日 17:40，Myrle Krantz 写道： > > Hey all, > > I just checked the Weex report for October, and while doing so, I realized > that I do not have edit rights to the incubator wiki. Rather than request > them now, I'd like to make a different suggestion: > > We should add the group "committers" with RW access (but not delete) to the > entire INCUBATOR space. > > We have, historically, spent rather a lot of time granting people access to > our wiki. > > But our recently implemented confluence-LDAP integration makes that > unnecessary. I made the COMDEV confluence space writable for all > committers. So far this has had several advantages and no disadvantages. > It's made it possible for committers of any project to enter themselves for > the ApacheCon EU hackathon without having to ask for permissions, and I > haven't seen any spamming of our spaces from this. > > Do you all see any reason we can't do the same for the incubator confluence > space? > > Best Regards, > Myrle
Re: configure GitBox output to post to our commits@ vs dev@
You can ask the help from Infra in JIRA[1] [1] https://jira.apache.org/jira/secure/Dashboard.jspa <https://jira.apache.org/jira/secure/Dashboard.jspa> Best Regards, York Shen 申远 > 2019年10月9日 07:58，leerho 写道： > > Hi, > > DataSketches podling here, > > How can we configure GitBox so it posts its output to our commits@ list and > not our dev@ list? > > Thanks, > > Lee.
Re: [IP CLEARANCE] Apache Weex - Weex Loader
The hyperlink in the previous mail is somehow wrong, please copy and paste the URL to your browser mannually if you are interested about the IP clearance. Best Regards, York Shen 申远 > 在 2019年9月30日，14:55，申远 写道： > > Hi community, > > Apache Weex received an another donation called Weex Loader soon after Weex > CLI[1] donated to ASF. > > Weex Loader is a loader of webpack that can transform *.vue file into a plain > javascript module for Android and iOS platform. In other words, it's a > compiler for compiling .vue file to .js file. > > The IP clearance form can be found at: > https://incubator.apache.org/ip-clearance/weex_loader.html > <https://incubator.apache.org/ip-clearance/weex_cli.html> once the website > updates. > One can view the xml version at: > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/weex_loader.xml > > <https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/weex_cli.xml> > > > The git commit containing the donation can be found > https://github.com/weexteam/weex-loader/commit/83d3767d419e8ba0d28f3e16cd22ad8543f2cfac > > <https://github.com/weexteam/weex-loader/commit/83d3767d419e8ba0d28f3e16cd22ad8543f2cfac> > . The git repo will be transferred to ASF at the end of the process. > > Please vote to approve this contribution. Lazy consensus applies: > If no -1, votes are being cast within the next 72 hours, the vote passes. > > [1] > https://lists.apache.org/thread.html/97e18ae60f7ae10c8c3a6111bbc64ca9bcac34fc98be90ad0ac4aaf2@%3Cgeneral.incubator.apache.org%3E > > <https://lists.apache.org/thread.html/97e18ae60f7ae10c8c3a6111bbc64ca9bcac34fc98be90ad0ac4aaf2@%3Cgeneral.incubator.apache.org%3E> > > Best Regards, > YorkShen > > 申远
Re: [IP CLEARANCE] Apache Weex - Weex CLI
We got +1 vote in dev@weex and no -1 vote. The vote has passed successfully, I will post another mail thread to announce the result. Best Regards, York Shen 申远 > 在 2019年9月27日，15:21，Jan Piotrowski 写道： > > +1 > > Am Fr., 27. Sept. 2019 um 06:17 Uhr schrieb York Shen : >> >> Hi community, >> >> Apache Weex received a donation of a software called Weex CLI (i.e. Weex >> Toolkit) which is dedicated to standardizing the tool in Weex ecosystem. It >> ensures that various build tools can be seamlessly connected based on smart >> default configuration, so users can focus on writing applications without >> having to spend days tangling configuration issues. >> >> The IP clearance form can be found at: >> https://incubator.apache.org/ip-clearance/weex_cli.html >> <https://incubator.apache.org/ip-clearance/weex_cli.html> once the website >> updates. One can view the xml version at: >> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/weex_cli.xml >> >> <https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/weex_cli.xml> >> >> >> The git commit containing the donation can be found >> https://github.com/weexteam/CLI-for-Apache-Weex/commit/7eadde0efa0982f36cf9b3915adad4b672dc5408 >> >> <https://github.com/weexteam/CLI-for-Apache-Weex/commit/7eadde0efa0982f36cf9b3915adad4b672dc5408> >> . The git repo will be transferred to ASF at the end of the process. >> >> Please vote to approve this contribution. Lazy consensus applies: >> If no -1, votes are being cast within the next 72 hours, the vote passes. >> >> >> Best Regards, >> York Shen >> >> 申远 >>
[IP CLEARANCE] Apache Weex - Weex CLI
Hi community, Apache Weex received a donation of a software called Weex CLI (i.e. Weex Toolkit) which is dedicated to standardizing the tool in Weex ecosystem. It ensures that various build tools can be seamlessly connected based on smart default configuration, so users can focus on writing applications without having to spend days tangling configuration issues. The IP clearance form can be found at: https://incubator.apache.org/ip-clearance/weex_cli.html <https://incubator.apache.org/ip-clearance/weex_cli.html> once the website updates. One can view the xml version at: https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/weex_cli.xml <https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/weex_cli.xml> The git commit containing the donation can be found https://github.com/weexteam/CLI-for-Apache-Weex/commit/7eadde0efa0982f36cf9b3915adad4b672dc5408 <https://github.com/weexteam/CLI-for-Apache-Weex/commit/7eadde0efa0982f36cf9b3915adad4b672dc5408> . The git repo will be transferred to ASF at the end of the process. Please vote to approve this contribution. Lazy consensus applies: If no -1, votes are being cast within the next 72 hours, the vote passes. Best Regards, York Shen 申远
Re: IP Clearance Process for Incubating projects
Thanks, that’s clear enough for me. > 在 2019年9月3日，19:10，Justin Mclean 写道： > > Hi, > >> There is another question during the donation. If some contributors of the >> donated code repo already signed ICLA in other projects, do they have to >> submit ICLA again for the new project? My understanding is that they don’t. > > Correct, they do not, one ICLA for the ASF is enough, it’s not required per > project or per donation. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IP Clearance Process for Incubating projects
Thanks. There is another question during the donation. If some contributors of the donated code repo already signed ICLA in other projects, do they have to submit ICLA again for the new project? My understanding is that they don’t. Best Regards, York Shen 申远 > 在 2019年9月2日，23:54，Matt Sicker 写道： > > Don’t forget to file the forms with the secretary. > > On Mon, Sep 2, 2019 at 04:53, York Shen wrote: > >>> Just to be clear the ICLAs need to be be from all the contributors, not >> just one person. >> >> Understood, that’s why I use plural form of ICLAs. >> >> I shall collected ICLAs/SGAs and send them to the mailing list by the end >> of this weekend if everything is fine. But I’m confused about what I shall >> do next to transfer those Git repo to ASF, maybe creating a JIRA issue to >> INFRA? >> >> Best Regards, >> York Shen >> >> 申远 >> >>> 在 2019年9月2日，17:43，Justin Mclean 写道： >>> >>> Just to be clear the ICLAs need to be be from all the contributors, not >> just one person. >> >> -- > Matt Sicker
Re: IP Clearance Process for Incubating projects
> Just to be clear the ICLAs need to be be from all the contributors, not just > one person. Understood, that’s why I use plural form of ICLAs. I shall collected ICLAs/SGAs and send them to the mailing list by the end of this weekend if everything is fine. But I’m confused about what I shall do next to transfer those Git repo to ASF, maybe creating a JIRA issue to INFRA? Best Regards, York Shen 申远 > 在 2019年9月2日，17:43，Justin Mclean 写道： > > Just to be clear the ICLAs need to be be from all the contributors, not just > one person.
Re: IP Clearance Process for Incubating projects
This is not done yet. The code owner of a third-party tool [1] is willing to give the donation to ASF, and I’m happy to receive the donation. I think I shall get the ICLAs/SGA signed by the code owner and send the result to d...@weex.apache.org <mailto:d...@weex.apache.org> , then I am confused about what to do next. I have also read the mentor-guide[2] , and the section about "Having trouble getting software transferred to ASF." is blank now. A brief introduction about how to continue the donation is really appreciated, and I am happy to fill out the donation section in mentor-guide after donation is done if my experience is needed. [1] https://github.com/weexteam/weex-loader <https://github.com/weexteam/weex-loader> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/Mentor+FAQ#suggested-action <https://cwiki.apache.org/confluence/display/INCUBATOR/Mentor+FAQ#suggested-action> Best Regards, York Shen 申远 > 在 2019年9月2日，17:17，Justin Mclean 写道： > > Hi, > >> Suppose ICLAs / SGAs is already signed and send to a proper mailing list >> (d...@weex.apache.org <mailto:d...@weex.apache.org>), what should I do next ? > > IMO If that already been done, I don’t see any harm in using the standard > process, if that’s the easy path. What's important is that the code have > clear IP provenance and the project has permission to use it and it’s > licensed under an ALv2 compatible license. Perhaps if we had more information > we could provide better guidance? > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: IP Clearance Process for Incubating projects
Thanks for your quick reply. I’m still a little confused about what I should do next. Suppose ICLAs / SGAs is already signed and send to a proper mailing list (d...@weex.apache.org <mailto:d...@weex.apache.org>), what should I do next ? Is there any documentation for make a donation to a project still in Incubator? Best Regards, York Shen 申远 > 在 2019年9月2日，16:20，Justin Mclean 写道： > > Hi, > > IMO there’s no need to go through the standard IP process but you still need > to check the IP of the donation very carefully and make sure that you ICLA > for all people who worked on it and/or a SGA if needed (depending on who owns > the code’s copyright). It best if this is recorded on the mailing list or > somewhere as it can be checked if needed. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
IP Clearance Process for Incubating projects
Hi, community. As a PPMC member of Apache Weex, I found some useful tools developed outside ASF code repo, and I’d like to make those tools donated to Weex PPMC. Is there any necessary to go through the standard IP clearance process considering the fact that Weex is currently in Apache Incubator? We found projects still in incubating might not need to do that[1]. If that’s true, then how shall we continue donation process without the IP clearance process? [1] https://mail-archives.apache.org/mod_mbox/incubator-general/201906.mbox/%3C1721C66C-7C49-4EED-B036-9DBDB04539BA%40gmail.com%3E <https://mail-archives.apache.org/mod_mbox/incubator-general/201906.mbox/%3c1721c66c-7c49-4eed-b036-9dbdb0453...@gmail.com%3E> Best Regards, York Shen 申远
Re: How to update status page after podling status file changed?
You’re welcomed. Just be patient, I remember it takes several hours before it takes effect. > 在 2019年8月30日，17:12，Sheng Wu 写道： > > Thanks. File updated. > > But still need to wait for when the page updated, somehow. > > Sheng Wu 吴晟 > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin > Twitter, wusheng1108 > > > York Shen 于2019年8月30日周五 下午4:58写道： > >> I think it’s generated by >> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml >> < >> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml >>> >> >> Best Regards, >> York Shen >> >> 申远 >> >> >>> 在 2019年8月30日，16:52，Sheng Wu 写道： >>> >>> Hi >>> >>> I just helped Dolphin Scheduler to initialize its dolphinscheduler.xml >>> podling status file. Do I have a way to trigger the website update? >>> >>> And besides this file, is there an index file needs to be changed? For >> this >>> page, https://incubator.apache.org/projects/ >>> >>> Sheng Wu 吴晟 >>> >>> Apache SkyWalking, Apache ShardingSphere(Incubating), Apache Incubator >>> Twitter, wusheng1108 >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: How to update status page after podling status file changed?
I think it’s generated by https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml <https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml> Best Regards, York Shen 申远 > 在 2019年8月30日，16:52，Sheng Wu 写道： > > Hi > > I just helped Dolphin Scheduler to initialize its dolphinscheduler.xml > podling status file. Do I have a way to trigger the website update? > > And besides this file, is there an index file needs to be changed? For this > page, https://incubator.apache.org/projects/ > > Sheng Wu 吴晟 > > Apache SkyWalking, Apache ShardingSphere(Incubating), Apache Incubator > Twitter, wusheng1108
Re: LGPL dependency
Thanks for your supporting. I will bring it to general@incubator when vote passed in weex@dev Best Regards, York Shen 申远 > 在 2019年7月2日，15:20，Myrle Krantz 写道： > > Hey Jim, > > Thank you for asking. : o) Weex is still cutting the release. It's > precisely because this can be time-consuming that they asked before they > started. They'll bring it for a vote once they have it. > > Best, > Myrle > > On Mon, Jul 1, 2019 at 6:19 PM Jim Jagielski wrote: > >> Myrle, did you get all you needed? Enough votes and all to get the release >> unblocked? >> >>> On Jun 28, 2019, at 11:24 AM, Myrle Krantz wrote: >>> >>> I've said it on dev@weex, and on private@incubator, but I wanted to make >>> sure and say it here too. Weex should cut the release. We'll figure out >>> the rest later. The straw poll on private@incubator also confirms: you >>> have my support and the support of many of the mentors in the >> incubator. I >>> apologize for us blocking you for so long. >>> >>> Best Regards, >>> Myrle Krantz >>> PMC Member, Apache Incubator >>> >>> On Thu, Jun 27, 2019 at 6:06 AM 申远 wrote: >>> >>>> It looks like we have got result[1] from Legal VP, I will bring it here >> now >>>> >>>> 1. It's fine if Weex only could include header files under 2-clause >> BSD >>>> license from Webkit at compiling time and has a dynamic link to >>>> Webkit.so >>>> at runtime. >>>> 2. It's recommended that excluding Webkit.so from Weex convenience >>>> library. Users would include the code snippet below to include both >> weex >>>> and webkit. >>>> >>>> >>>> >>>> weex_sdk >>>> >>>> >>>> >>>> >>>> >>>> webkit >>>> >>>> >>>> >>>> >>>> The following is what I need to consult from Incubator: >>>> >>>> Google will ban all apps without 64 bit published in Google Play from >> 1st, >>>> August, 2019 [1]. Though it's a good idea of excluding Webkit.so from >>>> convenience library of Weex, Weex community needs to publish next >> release >>>> with 64-bit support ASAP to give users enough time to upgrade Weex. I'd >>>> like to remain webkit.so in convenience library of Weex only for next >>>> release. >>>> >>>> [1] https://issues.apache.org/jira/browse/LEGAL-464 >>>> [2] >> https://developer.android.com/distribute/best-practices/develop/64-bit >>>> >>>> Best Regards, >>>> YorkShen >>>> >>>> 申远 >>>> >>>> >>>> Roman Shaposhnik 于2019年6月24日周一 上午7:32写道： >>>> >>>>> Lets continue this discussion on >>>>> https://issues.apache.org/jira/browse/LEGAL-464 please >>>>> >>>>> On Sat, Jun 22, 2019 at 2:18 PM Matt Sicker wrote: >>>>>> >>>>>> WebKit dates back to KHTML, an LGPL web engine from KDE. It sounds >> like >>>>>> it’s some WebKit specific files that are BSD licensed. I haven’t >>>>> inspected >>>>>> the individual files, but I suspect that the header files are BSD >>>>> licensed >>>>>> to make linking less of a legal headache. >>>>>> >>>>>> On Sat, Jun 22, 2019 at 07:11, Craig Russell >>>>> wrote: >>>>>> >>>>>>> The Webkit license page https://webkit.org/licensing-webkit/ says >>>>>>> portions licensed under LGPL and BSD licenses. >>>>>>> >>>>>>> Usually this means it's the user's choice which license to use. >>>>>>> >>>>>>> We would choose the BSD License for the components that we use. >>>>>>> >>>>>>> Can you find anywhere a statement that the Webkit.so is licensed only >>>>>>> under LGPL? >>>>>>> >>>>>>> Craig >>>>>>> >>>>>>>> On Jun 14, 2019, at 1:40 AM, 申远 wrote: >>>>>>>> >>>>>>>> As mentioned above, Webkit is under dual License(BSD and LPGL) and >>>>> it's >>>>>>>> almost impossible for us to figure out which function is a pure BSD >>>
Re: Podling expectations and some issues encountered in incubation
Agreed with that, from a poddling’s respective, I think it’s important that the community understand the following issues before it enters the incubator: Governance Model. Projects in Incubator would adopt Meritocracy model, no exception. Ownership of the Projects. Once a project enters the Incubator, ASF owns the project. All trademark/IP around the project belongs to ASF now. Though if they choose retire from Incubator, the incubator would give it back. Best Regards, York Shen 申远 > 在 2019年7月1日，14:32，Geertjan Wielenga 写道： > > Well, I think a lot of frustration with the Apache incubation process could > be avoided simply by very explicitly asking this question to a community > planning to start incubation: “Are you aware that until you complete > incubation you will not be in full control of your project, for example, > please scrap your release schedule until you complete incubation because > your release dates will not be under your control?”
Re: LGPL dependency
It depends on the definition of optional dependency. Weex targets iOS, Android and Browser environment and Webkit header files and shared library are only bundled for Android environment. As for other environments, the OS or browser itself has exposed enough API for Weex. PS: I am pretty sure that the iOS system itself uses almost the same code of Webkit as Weex does to build its WKWebView. It’s really strange that’s ok for Weex iOS and not ok for Weex Android. > 在 2019年6月14日，19:17，Justin Mclean 写道： > > Hi, > >> Well, what if Weex copies some BSD header files in Webkit then run on >> Webkit? IMHO, the Webkit is also an environment for Weex in this case. > > You still didi not answer if this is an optional dependancy? But again either > way I suggest you ask on legal discuss. > > Thanks, > Justin > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: LGPL dependency
Well, what if Weex copies some BSD header files in Webkit then run on Webkit? IMHO, the Webkit is also an environment for Weex in this case. Best Regards, York Shen 申远 > 在 2019年6月14日，18:37，Justin Mclean 写道： > > Hi, > >> So this question may have been seen before. Justin, one of the projects >> which seems to currently be using Webkit is Flex. Given the weird >> part-by-part licensing, how did Flex justify it's decision? Or am I >> misreading, and Webkit is just an environment for Flex? > > It just an environment, there no source code from webkit in Flex to my > knowledge. The other projects I’m not aware of how they used it. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
