Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi Branding issues should be improved now. No concern for that. But, I have a question, which also needs the Dubbo community to clear. In the Dubbo incubator proposal[1], there are several repositories in Initial Source - https://github.com/chickenlj/dubbo-dev-book-en [archieved in chickenlj[2] personal repo] - https://github.com/chickenlj/dubbo-admin-book-en [archieved in chickenlj personal repo] - https://github.com/dubbo/dubbo-docker-sample [404] - https://github.com/dubbo/dubbo-http-demo [404] ...(and several others repos) Also, chickenlj[3] can't be found in Dubbo team[4]. Maybe really 'can't`, but I can't find a match by name(ken or ken.lj). Could someone tell me what is going on? Are these being included in the Dubbo website document, already? Or the proposal changed. Thanks. [1] https://wiki.apache.org/incubator/DubboProposal [2] https://github.com/chickenlj/dubbo-dev-book-en [3] https://github.com/chickenlj [4] http://dubbo.apache.org/en-us/docs/developers/developers_dev.html Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Huxing Zhang 于2019年4月28日周日 下午11:05写道： > Hi, > > I am wrapping the latest update from Dubbo community. > > - The avator of dubbo[1] group has been deleted > - The description of dubbo group has been rename as Eco System For Apache > Dubbo > - A new group called thubbo[2] has been created > - All projects under dubbo group are renamed in xxx-for-apache-dubbo > format in compliance with the policies > - For the 19 projects remaining in dubbo group, the Dubbo community > has contacted all the project owners, and got response from 18 > projects[3]. Among them, > * 14 projects will be transferred to ASF (13 of them will be > transferred by May 31st, 1 project will be transferred by June 30th) > * 3 projects will be transferred outside dubbo group, with all > branding issues cleared. > * 1 project (dubbo.github.io) will be deleted by May 31st. (redirect > dubbo.io to dubbo.apache.org via dns) > * The remaining 1 project (intellij-idea-plugin) will be transferred > to thubbo group if no response is received. > * The detailed status has been summarized here[4]. > * If any project failed to be transferred before ETA, it will be > transferred to thubbo group instead. > > Given that all project has given ETA to be transferred to ASF/outside > dubbo, a suggestion is given that there is no need to move the > projects to thubbo group unless they are not transferred before ETA. > > The Dubbo community is seeking comments from the IPMC that whether > this proposal is OK or not. Any feedback will be appreciated. Hope > this could clear the concern from IPMC. > > [1] https://github.com/dubbo > [2] https://github.com/thubbo > [3] > https://lists.apache.org/thread.html/c8dc772242181517e3159d583c6aa7d1fcf5ce6f321ebb9e882ab6ad@%3Cdev.dubbo.apache.org%3E > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > On Thu, Apr 25, 2019 at 2:46 PM Huxing Zhang wrote: > > > > Hi, > > > > On Thu, Apr 25, 2019 at 2:10 PM Ian Luo wrote: > > > > > > Dave & Others, > > > > > > This "3rd party" site (https://github.com/dubbo) is used for building > > > Dubbo's eco-system. Just as you said, It contains both the projects > which > > > will be donated and which may not, so the final goal for this "3rd > party" > > > site is pretty clear: it will contain and only contain projects won't > > > donate, and if there's no project left eventually, this site does not > > > necessarily exist. > > > > > > What we're doing now is to solve the potential branding issues, in > order to > > > answer the challenges from whom wearing the trademark committee hat. > It is > > > an ad-hoc actions since we need to solve this particular issue as > quickly > > > as possible. Here're what we are doing as short-term actions: > > > > > > 1. Rename dubbo group to other name. - not yet > > > > Or create a new group and move all the projects to it, left dubbo as > > an empty group. (The purpose is just to ensure nobody is trying to > > abuse it) > > > > > 2. Stop using Dubbo logo as group's avatar - done > > > 3. Rename all project names in compliance with the policies - ongoing > > > > +1 > > > > > > > > > > > At the same time, I strongly agree with what Dave suggested for the > long > > > run plan. Here's what I propose (certainly this plan needs to be vote > in > > > dubbo's mailing list): > > > > > > 1. All projects will be transferred to Apache group with ETA > > > > I will try
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi Sorry, I copy the wrong link. > - https://github.com/chickenlj/dubbo-dev-book-en [archieved in chickenlj[2] personal repo] In the proposal, it is https://github.com/dubbo/dubbo-dev-book-en >- https://github.com/chickenlj/dubbo-admin-book-en [archieved in chickenlj personal repo] In the proposal, it is https://github.com/dubbo/dubbo-admin-book-en Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Sheng Wu 于2019年4月29日周一 下午2:22写道： > Hi > Branding issues should be improved now. No concern for that. > > But, I have a question, which also needs the Dubbo community to clear. > > In the Dubbo incubator proposal[1], there are several repositories > in Initial Source > - https://github.com/chickenlj/dubbo-dev-book-en [archieved in > chickenlj[2] personal repo] > - https://github.com/chickenlj/dubbo-admin-book-en [archieved in > chickenlj personal repo] > - https://github.com/dubbo/dubbo-docker-sample [404] > - https://github.com/dubbo/dubbo-http-demo [404] > ...(and several others repos) > > Also, chickenlj[3] can't be found in Dubbo team[4]. Maybe really 'can't`, > but I can't find a match by name(ken or ken.lj). > > Could someone tell me what is going on? > Are these being included in the Dubbo website document, already? Or the > proposal changed. > > Thanks. > > [1] https://wiki.apache.org/incubator/DubboProposal > [2] https://github.com/chickenlj/dubbo-dev-book-en > [3] https://github.com/chickenlj > [4] http://dubbo.apache.org/en-us/docs/developers/developers_dev.html > > Sheng Wu 吴晟 > > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > Huxing Zhang 于2019年4月28日周日 下午11:05写道： > >> Hi, >> >> I am wrapping the latest update from Dubbo community. >> >> - The avator of dubbo[1] group has been deleted >> - The description of dubbo group has been rename as Eco System For Apache >> Dubbo >> - A new group called thubbo[2] has been created >> - All projects under dubbo group are renamed in xxx-for-apache-dubbo >> format in compliance with the policies >> - For the 19 projects remaining in dubbo group, the Dubbo community >> has contacted all the project owners, and got response from 18 >> projects[3]. Among them, >> * 14 projects will be transferred to ASF (13 of them will be >> transferred by May 31st, 1 project will be transferred by June 30th) >> * 3 projects will be transferred outside dubbo group, with all >> branding issues cleared. >> * 1 project (dubbo.github.io) will be deleted by May 31st. (redirect >> dubbo.io to dubbo.apache.org via dns) >> * The remaining 1 project (intellij-idea-plugin) will be transferred >> to thubbo group if no response is received. >> * The detailed status has been summarized here[4]. >> * If any project failed to be transferred before ETA, it will be >> transferred to thubbo group instead. >> >> Given that all project has given ETA to be transferred to ASF/outside >> dubbo, a suggestion is given that there is no need to move the >> projects to thubbo group unless they are not transferred before ETA. >> >> The Dubbo community is seeking comments from the IPMC that whether >> this proposal is OK or not. Any feedback will be appreciated. Hope >> this could clear the concern from IPMC. >> >> [1] https://github.com/dubbo >> [2] https://github.com/thubbo >> [3] >> https://lists.apache.org/thread.html/c8dc772242181517e3159d583c6aa7d1fcf5ce6f321ebb9e882ab6ad@%3Cdev.dubbo.apache.org%3E >> [4] >> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status >> >> On Thu, Apr 25, 2019 at 2:46 PM Huxing Zhang wrote: >> > >> > Hi, >> > >> > On Thu, Apr 25, 2019 at 2:10 PM Ian Luo wrote: >> > > >> > > Dave & Others, >> > > >> > > This "3rd party" site (https://github.com/dubbo) is used for building >> > > Dubbo's eco-system. Just as you said, It contains both the projects >> which >> > > will be donated and which may not, so the final goal for this "3rd >> party" >> > > site is pretty clear: it will contain and only contain projects won't >> > > donate, and if there's no project left eventually, this site does not >> > > necessarily exist. >> > > >> > > What we're doing now is to solve the potential branding issues, in >> order to >> > > answer the challenges from whom wearing the trademark committee hat. >> It is >> > > an ad-hoc actions since we need to solve this particular issue as >> quickly >&g
[jira] [Closed] (INCUBATOR-237) IP clearance for SkyWalking RocketBot UI
[ https://issues.apache.org/jira/browse/INCUBATOR-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Wu closed INCUBATOR-237. -- > IP clearance for SkyWalking RocketBot UI > > > Key: INCUBATOR-237 > URL: https://issues.apache.org/jira/browse/INCUBATOR-237 > Project: Incubator > Issue Type: Task > Reporter: Sheng Wu >Priority: Major > Attachments: skywalking-rocketbot-ui.zip > > > Yao Wang(SkyWalking committer) is contributing the RocketBot UI to Apache > SkyWalking. > > The clearance tasks are in progress and recorded at: > [http://incubator.apache.org/ip-clearance/skywalking-rocketbot-ui.html|http://incubator.apache.org/ip-clearance/brooklyn-ui-angular.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 skywalking-rocketbot-ui.zip > > % md5 skywalking-rocketbot-ui.zip > MD5 (skywalking-rocketbot-ui.zip) = fd05ed7e5ffae52ac1b9763cbe0e9d71 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Resolved] (INCUBATOR-237) IP clearance for SkyWalking RocketBot UI
[ https://issues.apache.org/jira/browse/INCUBATOR-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Wu resolved INCUBATOR-237. Resolution: Fixed IP clearance vote passed. > IP clearance for SkyWalking RocketBot UI > > > Key: INCUBATOR-237 > URL: https://issues.apache.org/jira/browse/INCUBATOR-237 > Project: Incubator > Issue Type: Task > Reporter: Sheng Wu >Priority: Major > Attachments: skywalking-rocketbot-ui.zip > > > Yao Wang(SkyWalking committer) is contributing the RocketBot UI to Apache > SkyWalking. > > The clearance tasks are in progress and recorded at: > [http://incubator.apache.org/ip-clearance/skywalking-rocketbot-ui.html|http://incubator.apache.org/ip-clearance/brooklyn-ui-angular.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 skywalking-rocketbot-ui.zip > > % md5 skywalking-rocketbot-ui.zip > MD5 (skywalking-rocketbot-ui.zip) = fd05ed7e5ffae52ac1b9763cbe0e9d71 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-237) IP clearance for SkyWalking RocketBot UI
[ https://issues.apache.org/jira/browse/INCUBATOR-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827837#comment-16827837 ] Sheng Wu commented on INCUBATOR-237: Vote: [https://lists.apache.org/thread.html/8360e530a4c1af90e29796aef8ee4cc9800bf17af18ea7bb7d6af7f8@%3Cgeneral.incubator.apache.org%3E] Vote Result[PASS]: [https://lists.apache.org/thread.html/ab51c11060047e6a93a861f40e4afacdacae6f98ef88620dd4b38c58@%3Cgeneral.incubator.apache.org%3E] > IP clearance for SkyWalking RocketBot UI > > > Key: INCUBATOR-237 > URL: https://issues.apache.org/jira/browse/INCUBATOR-237 > Project: Incubator > Issue Type: Task > Reporter: Sheng Wu >Priority: Major > Attachments: skywalking-rocketbot-ui.zip > > > Yao Wang(SkyWalking committer) is contributing the RocketBot UI to Apache > SkyWalking. > > The clearance tasks are in progress and recorded at: > [http://incubator.apache.org/ip-clearance/skywalking-rocketbot-ui.html|http://incubator.apache.org/ip-clearance/brooklyn-ui-angular.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 skywalking-rocketbot-ui.zip > > % md5 skywalking-rocketbot-ui.zip > MD5 (skywalking-rocketbot-ui.zip) = fd05ed7e5ffae52ac1b9763cbe0e9d71 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][IP CLEARANCE] SkyWalking RocketBot UI project contribution
72 hours passed. We got +1 binding from Matt Sicker. Based on lazy consensus, this vote passed. Thanks. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Matt Sicker 于2019年4月26日周五 上午12:00写道： > +1 > > On Thu, 25 Apr 2019 at 00:53, Sheng Wu wrote: > > > > Hi Incubator PMC, > > > > The TLP Apache SkyWalking has been donated code for a new ui, being > > referred to as `skywalking-rocketbot-ui`[1], old hostsd at Yao Wang's > > personal repo[2]. > > I am sorry to submit this late. > > > > This is the formal request for IP clearance to be checked as per [3]. > > The donated code can be found at [4] (*) > > > > See > > http://incubator.apache.org/ip-clearance/skywalking-rocketbot-ui.html > > Notice, at this moment, HTML has not been updated, the raw XML is here > > > http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/skywalking-rocketbot-ui.xml?revision=1858082=markup > > > > The PMC has voted and passed to accept this donation. > > The ICLA of major contributors, Wang Yao and Tan Jian. have been filed > > before, as they are already SkyWalking PMC. > > The SGA from DaoCloud has been filed. > > The reason that DaoCloud should submit SGA, because, in the old day, this > > project announced powered by DaoCloud. Such as the latest release > > https://github.com/TinyAllen/rocketbot/tree/v1.0.3#introduction > > > > 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/skywalking-rocketbot-ui > > [2] https://github.com/TinyAllen/rocketbot > > [3] > > > https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling > > [4] https://issues.apache.org/jira/browse/INCUBATOR-237 > > > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > -- > Matt Sicker > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi Justin I mean these two are very important and should be fixed. Sorry for not clear enough. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Justin Mclean 于2019年4月26日周五 下午12:16写道： > Hi, > > It a little unclear to me if your are commenting on the release check list > or the Superset release here. > > > 1. Missing licensing information > > Well IMO it depends on the serenity IMO missing one or two MIT or BSD > licenses in a podling release is generally a fix next release type of issue > as they are permissive licenses and often the license is included (as a > header) just not clearly indicated that’s it’s included, so it’s more an > ASF policy issue than an actual licensing issue. > > > 2. Source release may contained compiled code > > I’m still not sure it can. In the past I’ve alway voted -1 on this issue, > but it's recently been suggested, that we go easier on podlings releases > particularly their first one. It is still however unknown if the board (who > are responsible for release policy) or infra (who are responsible for > distribution policy) would actually allow this. So far that exact situation > has not come and I not been able to get a clear answer from others on this. > The incubator (and its PMC) don’t set those policies. [1][2] > > Thanks, > Justin > > 1. http://www.apache.org/legal/release-policy.html > 2. https://www.apache.org/dev/release-distribution > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi In Justin's checked list, you hope the community to confirm at least for this first release. 1. Missing licensing information 2. Source release may contained compiled code And add `incubating` in the name. Please make sure doesn't include the license against Apache 2.0, Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Justin Mclean 于2019年4月26日周五 上午10:49写道： > Hi, > > Normally I would be -1 binding as there’s a number of issues here, however > the most serious one for a first release is that you are missing incubating > from the artefact name. The artefacts can be renamed without changing the > hash or anything else, if you rename I’ll change my vote to +1. Other IPMC > members may think the issue are more serious and may also vote -1. You may > need to check with legal if it OK to distribute this release given the font > licensing issue. > > The PPMC could also decide to not release this and cancel the vote because > of the issues below and instead fix them and make another RC to vote on. > > Using a checklist like this [2] when voting on releases might help, you > can also ask the IPMC to take a look at a release before putting it up for > vote here.That’s probably a good thing to do for a first release. > > I checked: > - incubating is missing from name > - signatures and hashes good > - DISCLAIMER exists > - LICENSE is missing a few licenses (see below) > - NOTICE should not include LICENSE information e.g The line about CC 4.0. > This may need to be removed. Also this content may be Category X and this > can’t included in a source release. [11] > - Some 3rd party code have headers with "[LICENSE TBD]” [4][5][6][7][9] > which seems odd > - The ASF headers on a number of files are not correct e.g the file [13] > and other under that directory (search for COPYRIGHT 2016 and and COPYRIGHT > 2017 and COPYRIGHT 2018) Or are these files not actually licensed to the > ASF? > - Source release may contained compiled code e.g [20] my understanding is > that a .mo file is compiled from the .po file. I not sure if it could be > classified as code however, but even if that is so it may be best to remove > them from the source release. > > There is a few bits of missing licensing information: > - How is the map date here licensed? [3] Is it from > http://www.diva-gis.org/Data? I can see there is a credit in the code > that has a link to https://bl.ocks.org/john-guerra. How is that code > licensed? > - This file [7] is missing from LICENSE I assume it’s public domain? [8] > - This file [9] is licensed how? It seems to come from here [10] which > says to contact the author for a license. > - How is this image [14] licensed? (One reference I found said it could > only be used for personal use [21]) > - LICENSE is missing license information for these fonts > [15][16][17][18][19] The license for Glyphicons Halflings is complex and in > this context (outside of bootstrap) a commercial license may be needed [22] > and so it can’t be included. > > Some other improvements that could be made: > - The LICENSE fieldworker is a little odd with headings like BSD 2-Clause > licenses with noting under them, people (or tools) may incorrectly assume > that it does contain BSD 2-Clause licensed code. > - Make vote link link in future emails to lists.apache,org > - Sign release with an apache.org email address > - This [12] has copyright 2018 when it shovel be 2019 > > Thanks, > Justin > > 1. https://incubator.apache.org/policy/incubation.html#releases > 2. > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > 3. > apache-superset-0.32.0rc2/superset/assets/src/visualizations/CountryMap/* > 4. > apache-superset-0.32.0rc2/superset/assets/vendor/cal-heatmap/cal-heatmap.js > / .css > 5 > apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/d3.parcoords.js > / .css > 6. > apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/divgrid.js > 7 apache-superset-0.32.0rc2/superset/assets/vendor/pygments.css > 8. https://github.com/richleland/pygments-css/blob/master/UNLICENSE.txt > 9. > ./apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/divgrid.js > 10. http://bl.ocks.org/syntagmatic/3687826 > 11. http://www.tavfrna.incubator.apache.org/legal/resolved.html#cc-sa > 12. ./apache-superset-0.32.0rc2/docs/conf.py > 13. ./apache-superset-0.32.0rc2/superset/translations/messages.pot > 14. ./apache-superset-0.32.0rc2/superset/assets/images/babytux.jpg > 15. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/Roboto-Regular.woff > 16. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/Roboto-Regular.woff2 > 17. > apache-superset-0.32.0rc2/s
Re: incubator website guide transferring
Hi Eric Are you trying to rename repo? I think the new V.P. should have received a mail from Matt Sicker, which guide you to do other things, besides repo rename. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Eric Barboni 于2019年4月25日周四 下午8:13写道： > Hi incubator, > > As we progress to graduate Apache NetBeans we try to follow the guide in > the > incubator transferring > (https://incubator.apache.org/guides/transferring.html) pages we found > the > following: > > Graduating as New Top Level Project > Work with the Apache Infrastructure team to set up the top level project > infrastructure. Setting up the TLP request can be done by anyone on the new > PMC, and should be done via Infra Service Desk > https://issues.apache.org/jira/servicedesk/customer/portal/1/create/10 is > 404 > > This can be done by any PMC but it's under the PMC chair subsection. But > this is anyway a deadlink. > > Later in the document you have the paragraph that link to > http://www.apache.org/dev/infra-contact#requesting-graduation which is > working. > First Steps Outside the Incubator > > Although the below checklist is still generally useful, the infrastructure > process has been streamlined, see requesting graduation. You might also > want > to check JIRA checklist tickets for projects that graduated in the last > month or two. This process is known as "TLP Parent Request" > > Are the two sections aim to resolve the same objective? Would it be > possible > to clarify ? > > Best Regards > Eric (skygo) > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[IP CLEARANCE] SkyWalking RocketBot UI project contribution
Hi Incubator PMC, The TLP Apache SkyWalking has been donated code for a new ui, being referred to as `skywalking-rocketbot-ui`[1], old hostsd at Yao Wang's personal repo[2]. I am sorry to submit this late. This is the formal request for IP clearance to be checked as per [3]. The donated code can be found at [4] (*) See http://incubator.apache.org/ip-clearance/skywalking-rocketbot-ui.html Notice, at this moment, HTML has not been updated, the raw XML is here http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/skywalking-rocketbot-ui.xml?revision=1858082=markup The PMC has voted and passed to accept this donation. The ICLA of major contributors, Wang Yao and Tan Jian. have been filed before, as they are already SkyWalking PMC. The SGA from DaoCloud has been filed. The reason that DaoCloud should submit SGA, because, in the old day, this project announced powered by DaoCloud. Such as the latest release https://github.com/TinyAllen/rocketbot/tree/v1.0.3#introduction 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/skywalking-rocketbot-ui [2] https://github.com/TinyAllen/rocketbot [3] https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling [4] https://issues.apache.org/jira/browse/INCUBATOR-237 Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108
[jira] [Commented] (INCUBATOR-237) IP clearance for SkyWalking RocketBot UI
[ https://issues.apache.org/jira/browse/INCUBATOR-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825695#comment-16825695 ] Sheng Wu commented on INCUBATOR-237: IP clearance is [http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/skywalking-rocketbot-ui.xml?revision=1858082=markup] > IP clearance for SkyWalking RocketBot UI > > > Key: INCUBATOR-237 > URL: https://issues.apache.org/jira/browse/INCUBATOR-237 > Project: Incubator > Issue Type: Task > Reporter: Sheng Wu >Priority: Major > Attachments: skywalking-rocketbot-ui.zip > > > Yao Wang(SkyWalking committer) is contributing the RocketBot UI to Apache > SkyWalking. > > The clearance tasks are in progress and recorded at: > [http://incubator.apache.org/ip-clearance/skywalking-rocketbot-ui.html|http://incubator.apache.org/ip-clearance/brooklyn-ui-angular.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 skywalking-rocketbot-ui.zip > > % md5 skywalking-rocketbot-ui.zip > MD5 (skywalking-rocketbot-ui.zip) = fd05ed7e5ffae52ac1b9763cbe0e9d71 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Ask for help] Can't commit IP-CLEARANCE, Ask Incubator Karma grant.
John Thanks. That is the case. :) HTTPS works. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 John D. Ament 于2019年4月25日周四 上午11:23写道： > Sheng, > > You are in fact a committer on incubator, so you have that permission. > Please check that you are using HTTPS URL to commit rather than HTTP. > > John > > On Wed, Apr 24, 2019 at 10:25 PM Sheng Wu > wrote: > > > Hi Incubator > > > > SkyWalking PMC recently accepts the RocketBot UI project. ICLA, SGA filed > > and License checked. I am trying to finish the IP-CLEARANCE by following > > this[1]. > > > > But the svn forbids me to submit files in to here[1], as by the > document, I > > as SkyWalking officer, should be able to do this. > > > > > Incubator karma is also required. Please request karma from the > incubator > > pmc if you do not have it. > > > > I think I lack the grant of this. Could someone grant me? > > > > Thanks. > > > > [1] https://incubator.apache.org/ip-clearance/ > > [3] > > > > > https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling > > > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > >
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
> I think that rather than quickly responding by fixing various issues in an ad hoc manner it would be good to present the long term plan and then agree on the needed language on the “3rd party site” Agree with Dave. Dubbo community has time to discuss, fix and catch up the next meeting. Most of my concerns have been addressed, and I think the Dubbo team have some solutions. Please make sense the community agree about them. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Dave Fisher 于2019年4月25日周四 上午12:29写道： > Hi - > > (With trademark committee hat) > > Trademark resources can all be found from here: > Trademark resources sitemap: > http://www.apache.org/foundation/marks/resources > PMC responsibility: http://www.apache.org/foundation/marks/responsibility > Improper third party uses: > http://www.apache.org/foundation/marks/responsibility#police > Formal policy: http://www.apache.org/foundation/marks/ > > I don’t think that there is a formal policy to handle the situation where > a transitional, "3rd party” site controlled by the PMC exists that will be > phased out. Generally trademarks is looking for that PMC to be working with > and engaging 3rd parties to fix any branding issues. > > I think it is important to know what the goal is for the "3rd party" site > is and when that will be achieved. > > (Dubbo mentor hat) > > I think that rather than quickly responding by fixing various issues in an > ad hoc manner it would be good to present the long term plan and then agree > on the needed language on the “3rd party site” > > For example, the treatment of “product” that will be donated into the > project codebase differs from “product” that won’t be. The “for Apache > Dubbo” makes no sense for product that will be moved into Dubbo. > > The next board meeting is May 15th and there is time to carefully address > the plan to the satisfaction of the IPMC. > > Regards, > Dave > > > On Apr 24, 2019, at 8:51 AM, Sheng Wu wrote: > > > > Hi > > > >> Could somebody point me to Apache documentation that indicates that > > such use of names of Apache projects is not ok? I might need that > > information soon-ish myself, thanks. > > > > I used to read this from incubator discussions. Zipkin and SkyWalking > were > > facing that question. Could someone help about this? > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > Jan Piotrowski 于2019年4月24日周三 下午11:29写道： > > > >> Semi OT: > >> Could somebody point me to Apache documentation that indicates that > >> such use of names of Apache projects is not ok? I might need that > >> information soon-ish myself, thanks. > >> > >> -J > >> > >> Am Mi., 24. Apr. 2019 um 17:07 Uhr schrieb Sheng Wu < > >> wu.sheng.841...@gmail.com>: > >>> > >>> Hi, > >>> > >>> 4. We plan to rename all projects in this organization to > >>>> xxx-for-apache-dubbo > >>> > >>> The rename makes sense for ecosystem projects, especially for these > >> three. > >>> I also used to see the traditional rename to xxx-for-apache-project > >>> 1. js, https://github.com/dubbo/dubbo2.js > >>> 2. python, https://github.com/dubbo/dubbo-client-py > >>> 3. php, https://github.com/dubbo/dubbo-php-framework > >>> > >>> Also, please pay attention to this[1]. This is a release repo(npm), the > >>> description in Chinese, I assume it related to [2]. Right? > >>> If yes, this release dist should be renamed. SkyWalking used to be > asked > >>> stop in the same case. > >>> Because it misguides user this is Apache release, which isn't. > >>> > >>> [1] https://www.npmjs.com/package/dubbo2.js > >>> [2] https://github.com/dubbo/dubbo2.js > >>> > >>> Sheng Wu 吴晟 > >>> > >>> Apache SkyWalking, ShardingSphere, Zipkin > >>> Twitter, wusheng1108 > >>> > >>> > >>> Sheng Wu 于2019年4月24日周三 下午10:46写道： > >>> > >>>> Hi > >>>> > >>>>> 1. We will remove the organization avatar > >>>>> 2. We are ready to rename organization name from 'dubbo' to other > >> name > >>>>> 3. Because of action 2, we will also lose the domain name > >>>> dubbo.github.io, > >>>>> but it also makes things easier, since we don't need to keep website > >> in > &
[Ask for help] Can't commit IP-CLEARANCE, Ask Incubator Karma grant.
Hi Incubator SkyWalking PMC recently accepts the RocketBot UI project. ICLA, SGA filed and License checked. I am trying to finish the IP-CLEARANCE by following this[1]. But the svn forbids me to submit files in to here[1], as by the document, I as SkyWalking officer, should be able to do this. > Incubator karma is also required. Please request karma from the incubator pmc if you do not have it. I think I lack the grant of this. Could someone grant me? Thanks. [1] https://incubator.apache.org/ip-clearance/ [3] https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108
[jira] [Created] (INCUBATOR-237) IP clearance for SkyWalking RocketBot UI
Sheng Wu created INCUBATOR-237: -- Summary: IP clearance for SkyWalking RocketBot UI Key: INCUBATOR-237 URL: https://issues.apache.org/jira/browse/INCUBATOR-237 Project: Incubator Issue Type: Task Reporter: Sheng Wu Attachments: skywalking-rocketbot-ui.zip Yao Wang(SkyWalking committer) is contributing the RocketBot UI to Apache SkyWalking. The clearance tasks are in progress and recorded at: [http://incubator.apache.org/ip-clearance/skywalking-rocketbot-ui.html|http://incubator.apache.org/ip-clearance/brooklyn-ui-angular.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 skywalking-rocketbot-ui.zip % md5 skywalking-rocketbot-ui.zip MD5 (skywalking-rocketbot-ui.zip) = fd05ed7e5ffae52ac1b9763cbe0e9d71 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi > Could somebody point me to Apache documentation that indicates that such use of names of Apache projects is not ok? I might need that information soon-ish myself, thanks. I used to read this from incubator discussions. Zipkin and SkyWalking were facing that question. Could someone help about this? Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Jan Piotrowski 于2019年4月24日周三 下午11:29写道： > Semi OT: > Could somebody point me to Apache documentation that indicates that > such use of names of Apache projects is not ok? I might need that > information soon-ish myself, thanks. > > -J > > Am Mi., 24. Apr. 2019 um 17:07 Uhr schrieb Sheng Wu < > wu.sheng.841...@gmail.com>: > > > > Hi, > > > > 4. We plan to rename all projects in this organization to > > > xxx-for-apache-dubbo > > > > The rename makes sense for ecosystem projects, especially for these > three. > > I also used to see the traditional rename to xxx-for-apache-project > > 1. js, https://github.com/dubbo/dubbo2.js > > 2. python, https://github.com/dubbo/dubbo-client-py > > 3. php, https://github.com/dubbo/dubbo-php-framework > > > > Also, please pay attention to this[1]. This is a release repo(npm), the > > description in Chinese, I assume it related to [2]. Right? > > If yes, this release dist should be renamed. SkyWalking used to be asked > > stop in the same case. > > Because it misguides user this is Apache release, which isn't. > > > > [1] https://www.npmjs.com/package/dubbo2.js > > [2] https://github.com/dubbo/dubbo2.js > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > Sheng Wu 于2019年4月24日周三 下午10:46写道： > > > > > Hi > > > > > > > 1. We will remove the organization avatar > > > > 2. We are ready to rename organization name from 'dubbo' to other > name > > > > 3. Because of action 2, we will also lose the domain name > > > dubbo.github.io, > > > > but it also makes things easier, since we don't need to keep website > in > > > > this group > > > > 4. We plan to rename all projects in this organization to > > > > xxx-for-apache-dubbo > > > > > > Please discuss with your community, then make the decision. I just > reply > > > the Huxing's. Transfer the repos in the org(except the dubbo.github.io > , > > > if the community wants), is also a good idea. > > > > > > I think both you and Huxing have been clear about my concern. I trust > the > > > Dubbo community could make it right. > > > > > > Thanks. > > > > > > Sheng Wu 吴晟 > > > > > > Apache SkyWalking, ShardingSphere, Zipkin > > > Twitter, wusheng1108 > > > > > > > > > Ian Luo 于2019年4月24日周三 下午10:16写道： > > > > > >> > > > >> > Those two are good options. Please read my prev reply[1], which > > >> concerns me > > >> > more are > > >> > 1. Website codebase. > > >> > 2. GitHub org name and logo. > > >> > > >> > > >> Sheng, If your concerns here are confirmed to be disallowed, we will > do > > >> the > > >> following things against dubbo group: > > >> 1. We will remove the organization avatar > > >> 2. We are ready to rename organization name from 'dubbo' to other name > > >> 3. Because of action 2, we will also lose the domain name > dubbo.github.io > > >> , > > >> but it also makes things easier, since we don't need to keep website > in > > >> this group > > >> 4. We plan to rename all projects in this organization to > > >> xxx-for-apache-dubbo > > >> > > >> Let me know if your concerns will be completely addressed once the > actions > > >> above are made. Before it, I'd like to confirm with our mentors and > > >> hopefully get back to you soon. > > >> > > >> Regards, > > >> -Ian. > > >> > > >> > > >> On Wed, Apr 24, 2019 at 7:56 PM Huxing Zhang > wrote: > > >> > > >> > Hi, > > >> > > > >> > On Wed, Apr 24, 2019 at 11:01 AM Sheng Wu < > wu.sheng.841...@gmail.com> > > >> > wrote: > > >> > > > > >> > > Hi. > > >> > > > > >> > > > As Justin mentioned above, the translation is under going. W
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi, 4. We plan to rename all projects in this organization to > xxx-for-apache-dubbo The rename makes sense for ecosystem projects, especially for these three. I also used to see the traditional rename to xxx-for-apache-project 1. js, https://github.com/dubbo/dubbo2.js 2. python, https://github.com/dubbo/dubbo-client-py 3. php, https://github.com/dubbo/dubbo-php-framework Also, please pay attention to this[1]. This is a release repo(npm), the description in Chinese, I assume it related to [2]. Right? If yes, this release dist should be renamed. SkyWalking used to be asked stop in the same case. Because it misguides user this is Apache release, which isn't. [1] https://www.npmjs.com/package/dubbo2.js [2] https://github.com/dubbo/dubbo2.js Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Sheng Wu 于2019年4月24日周三 下午10:46写道： > Hi > > > 1. We will remove the organization avatar > > 2. We are ready to rename organization name from 'dubbo' to other name > > 3. Because of action 2, we will also lose the domain name > dubbo.github.io, > > but it also makes things easier, since we don't need to keep website in > > this group > > 4. We plan to rename all projects in this organization to > > xxx-for-apache-dubbo > > Please discuss with your community, then make the decision. I just reply > the Huxing's. Transfer the repos in the org(except the dubbo.github.io, > if the community wants), is also a good idea. > > I think both you and Huxing have been clear about my concern. I trust the > Dubbo community could make it right. > > Thanks. > > Sheng Wu 吴晟 > > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > Ian Luo 于2019年4月24日周三 下午10:16写道： > >> > >> > Those two are good options. Please read my prev reply[1], which >> concerns me >> > more are >> > 1. Website codebase. >> > 2. GitHub org name and logo. >> >> >> Sheng, If your concerns here are confirmed to be disallowed, we will do >> the >> following things against dubbo group: >> 1. We will remove the organization avatar >> 2. We are ready to rename organization name from 'dubbo' to other name >> 3. Because of action 2, we will also lose the domain name dubbo.github.io >> , >> but it also makes things easier, since we don't need to keep website in >> this group >> 4. We plan to rename all projects in this organization to >> xxx-for-apache-dubbo >> >> Let me know if your concerns will be completely addressed once the actions >> above are made. Before it, I'd like to confirm with our mentors and >> hopefully get back to you soon. >> >> Regards, >> -Ian. >> >> >> On Wed, Apr 24, 2019 at 7:56 PM Huxing Zhang wrote: >> >> > Hi, >> > >> > On Wed, Apr 24, 2019 at 11:01 AM Sheng Wu >> > wrote: >> > > >> > > Hi. >> > > >> > > > As Justin mentioned above, the translation is under going. We cannot >> > do it >> > > for all because we need to examine the license and make sure ICLA for >> > each >> > > projects are signed, >> > > >> > > I am not asking to move all repo related to Dubbo, which is decided by >> > the >> > > project owner or Dubbo community. >> > > >> > > > eventually we hope to move everything into Apache group except for >> the >> > > repo [1] which serves redirection dubbo.io to dubbo.apache.org. >> > > >> > > As you mentioned, which make me concern more. Especially you say >> > > `eventually` and `hope`. Are these optional? >> > >> > No. The redirection has been completed. >> > You can test with: curl -i http://dubbo.io >> > The only effective file is index.html, possibly CNAME. >> > Other files are archive for the old website before joining ASF. >> > To make it better understandable, I think it is better to move them to >> > other place (e.g. a new branch) for archive purpose. >> > I update the description and readme, removing the word "eventually". >> > >> > > Please read your own Incubator Proposal[1], section Initial Source, >> "Home >> > > Page: https://github.com/dubbo/dubbo.github.io; >> > > If the transfer has not been finished, you should wait for that before >> > > graduation. >> > >> > IMO, the transfer has been finished. Requests to dubbo.io has been >> > redirected to dubbo.apache.org. >> > >> > > >> > > Why not just set the `redirect` on the
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi > 1. We will remove the organization avatar > 2. We are ready to rename organization name from 'dubbo' to other name > 3. Because of action 2, we will also lose the domain name dubbo.github.io, > but it also makes things easier, since we don't need to keep website in > this group > 4. We plan to rename all projects in this organization to > xxx-for-apache-dubbo Please discuss with your community, then make the decision. I just reply the Huxing's. Transfer the repos in the org(except the dubbo.github.io, if the community wants), is also a good idea. I think both you and Huxing have been clear about my concern. I trust the Dubbo community could make it right. Thanks. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Ian Luo 于2019年4月24日周三 下午10:16写道： > > > > Those two are good options. Please read my prev reply[1], which concerns > me > > more are > > 1. Website codebase. > > 2. GitHub org name and logo. > > > Sheng, If your concerns here are confirmed to be disallowed, we will do the > following things against dubbo group: > 1. We will remove the organization avatar > 2. We are ready to rename organization name from 'dubbo' to other name > 3. Because of action 2, we will also lose the domain name dubbo.github.io, > but it also makes things easier, since we don't need to keep website in > this group > 4. We plan to rename all projects in this organization to > xxx-for-apache-dubbo > > Let me know if your concerns will be completely addressed once the actions > above are made. Before it, I'd like to confirm with our mentors and > hopefully get back to you soon. > > Regards, > -Ian. > > > On Wed, Apr 24, 2019 at 7:56 PM Huxing Zhang wrote: > > > Hi, > > > > On Wed, Apr 24, 2019 at 11:01 AM Sheng Wu > > wrote: > > > > > > Hi. > > > > > > > As Justin mentioned above, the translation is under going. We cannot > > do it > > > for all because we need to examine the license and make sure ICLA for > > each > > > projects are signed, > > > > > > I am not asking to move all repo related to Dubbo, which is decided by > > the > > > project owner or Dubbo community. > > > > > > > eventually we hope to move everything into Apache group except for > the > > > repo [1] which serves redirection dubbo.io to dubbo.apache.org. > > > > > > As you mentioned, which make me concern more. Especially you say > > > `eventually` and `hope`. Are these optional? > > > > No. The redirection has been completed. > > You can test with: curl -i http://dubbo.io > > The only effective file is index.html, possibly CNAME. > > Other files are archive for the old website before joining ASF. > > To make it better understandable, I think it is better to move them to > > other place (e.g. a new branch) for archive purpose. > > I update the description and readme, removing the word "eventually". > > > > > Please read your own Incubator Proposal[1], section Initial Source, > "Home > > > Page: https://github.com/dubbo/dubbo.github.io; > > > If the transfer has not been finished, you should wait for that before > > > graduation. > > > > IMO, the transfer has been finished. Requests to dubbo.io has been > > redirected to dubbo.apache.org. > > > > > > > > Why not just set the `redirect` on the DNS level, and host all in > > > http://dubbo.apache.org. If the two are the same. If not, which is > > harder > > > to understand for me. > > > > Because the ownership of dubbo.io did not belong to either Apache or > > Alibaba when Dubbo joined ASF. > > The Dubbo community do not have access to change the DNS record. > > The easiest way is to redirect dubbo.io to dubbo.apache.org. > > > > > > > > This is a block for me. > > > > > > > Now I have changed the title and the profile for dubbo group like > this: > > > > > > You changed some. But if you look clearly about the logo(GitHub org > > > avatar), also the name, you will see they[2][3] are the same, which > both > > of > > > them belong to ASF. > > > Which makes me think the branding has not been cleared. Especially, I > > think > > > Dubbo team has the full access to that GitHub org, so this should be > able > > > to be fixed. > > > > I have no objection to rename the organization if this is an issue. > > I see some TLP keep an empty group. I think it is useful just for > > defensive purpose, in case someone abuse it. > &
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi > No. The redirection has been completed. > You can test with: curl -i http://dubbo.io Checked, it is good now. And repo[1] of website description is clear. Thanks. > Because the ownership of dubbo.io did not belong to either Apache or > Alibaba when Dubbo joined ASF. > The Dubbo community do not have access to change the DNS record. > The easiest way is to redirect dubbo.io to dubbo.apache.org. Based on the redirect works, this is not an issue, no matter who owns the domain, but only remind, the community have trusted the one, who owns it. I assume YES. > I have no objection to rename the organization if this is an issue. > I see some TLP keep an empty group. I think it is useful just for > defensive purpose, in case someone abuse it. > Another way is to create another group with something other than > dubbo, can transfer all the projects under it. Totally understand and make sense. I prefer `reate another group with something other than dubbo, can transfer all the projects under it.`. My only concern is the misguidance of the repos in that org. [1] https://github.com/dubbo/dubbo.github.io Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Huxing Zhang 于2019年4月24日周三 下午7:56写道： > Hi, > > On Wed, Apr 24, 2019 at 11:01 AM Sheng Wu > wrote: > > > > Hi. > > > > > As Justin mentioned above, the translation is under going. We cannot > do it > > for all because we need to examine the license and make sure ICLA for > each > > projects are signed, > > > > I am not asking to move all repo related to Dubbo, which is decided by > the > > project owner or Dubbo community. > > > > > eventually we hope to move everything into Apache group except for the > > repo [1] which serves redirection dubbo.io to dubbo.apache.org. > > > > As you mentioned, which make me concern more. Especially you say > > `eventually` and `hope`. Are these optional? > > No. The redirection has been completed. > You can test with: curl -i http://dubbo.io > The only effective file is index.html, possibly CNAME. > Other files are archive for the old website before joining ASF. > To make it better understandable, I think it is better to move them to > other place (e.g. a new branch) for archive purpose. > I update the description and readme, removing the word "eventually". > > > Please read your own Incubator Proposal[1], section Initial Source, "Home > > Page: https://github.com/dubbo/dubbo.github.io; > > If the transfer has not been finished, you should wait for that before > > graduation. > > IMO, the transfer has been finished. Requests to dubbo.io has been > redirected to dubbo.apache.org. > > > > > Why not just set the `redirect` on the DNS level, and host all in > > http://dubbo.apache.org. If the two are the same. If not, which is > harder > > to understand for me. > > Because the ownership of dubbo.io did not belong to either Apache or > Alibaba when Dubbo joined ASF. > The Dubbo community do not have access to change the DNS record. > The easiest way is to redirect dubbo.io to dubbo.apache.org. > > > > > This is a block for me. > > > > > Now I have changed the title and the profile for dubbo group like this: > > > > You changed some. But if you look clearly about the logo(GitHub org > > avatar), also the name, you will see they[2][3] are the same, which both > of > > them belong to ASF. > > Which makes me think the branding has not been cleared. Especially, I > think > > Dubbo team has the full access to that GitHub org, so this should be able > > to be fixed. > > I have no objection to rename the organization if this is an issue. > I see some TLP keep an empty group. I think it is useful just for > defensive purpose, in case someone abuse it. > Another way is to create another group with something other than > dubbo, can transfer all the projects under it. > > > > > > Dubbo is now incubated in ASF: > https://github.com/apache/incubator-dubbo, > > this group is for hosting dubbo eco-system temporarily before the > > transition finishes. > > > > The temporarily needs to be defined, as you are going to be a TLP, the > > PPMC(potentail PMC) have to make the decision, what do you want about > your > > own repo. > > Notice, I am not saying all repo in GitHub, but the specific ones in the > > initial org, https://github.com/dubbo > > > > > > [1] https://wiki.apache.org/incubator/DubboProposal > > [2] http://dubbo.apache.org/en-us/ > > [3] https://github.com/dubbo > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking, ShardingSphere,
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi > The metrics project just plays as a third party dependency to Apache Dubbo, IMO there is no branding issue against Dubbo. The mailing list can be removed, I have already removed it. 3rd party dependency is ok, I think. If ml has been removed, which should be good. > t was discussed here[1]. Possible further actions include: > - contact the authors where they would like to donate to Dubbo, if > they are willing to, cleanup the IP issues such as license and etc. > - if not, change the name to avoid potential branding issue, for > eample, dubbo-go can be changed to go-client-for-apache-dubbo Those two are good options. Please read my prev reply[1], which concerns me more are 1. Website codebase. 2. GitHub org name and logo. [1] https://lists.apache.org/thread.html/b22abd44e0532822053b757b1bb7781cbbd3b556f1b05d60548e5b53@%3Cgeneral.incubator.apache.org%3E Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Huxing Zhang 于2019年4月24日周三 上午10:54写道： > Hi, > > On Wed, Apr 24, 2019 at 7:19 AM Justin Mclean > wrote: > > > > Hi, > > > > > 1. If graduation happens, Dubbo should be Apache branding, then why > > > dubbo GitHub org[1] is still used. Especially the exact name and logo. > > > > Part of the repo was used to host dubbo.io which now redirects to > http://dubbo.apache.org/en-us/. Re the other projects it may be that a > little clean up still needs to be done but action is being taken. The > existence of this extra repo has been discussed a number of times in the > project and projects are being moved off it. e.g. [1][2] and more recently > [3][4]. > > > > This document probably best describes what is happening [5]. > > > > > 2. Most star project[2] in dubbo org is using Apache mail list[3]. But > > > groupId[4] says it belongs Alibaba > > > > I would guess this is just an oversight, but if someone from the PPMC > can comment on this that would be good. > > The metrics project just plays as a third party dependency to Apache > Dubbo, IMO there is no branding issue against Dubbo. The mailing list > can be removed, I have already removed it. > > > > > > 3. Dubbo-go[5] project exists, and also use the Dubbo name. > > > > See [5]. > > It was discussed here[1]. Possible further actions include: > - contact the authors where they would like to donate to Dubbo, if > they are willing to, cleanup the IP issues such as license and etc. > - if not, change the name to avoid potential branding issue, for > eample, dubbo-go can be changed to go-client-for-apache-dubbo > > [1] > https://lists.apache.org/thread.html/2fbe0a4653908ac287c874fe265ac0e0c6481a94573114d70984ecde@%3Cdev.dubbo.apache.org%3E > > > > > > Also, in the last Dubbo vote `[VOTE]: Release Apache Dubbo > > > Admin(Incubating) 0.2.0 [RC3]`. License issue hasn't been addressed > inside > > > the PPMC(dev vote), I know LGPL is uncertain thing(maybe), but at this > > > moment, it should not be included. > > > > This issue is is being addressed (vote has been canceled, the dependancy > removed, documentation updated and there’s a discussion started on legal > discuss on if it might in future be allowed). I also note it was the PPMC > who first noticed this issue not the IPMC. > > > > Thanks, > > Justin > > > > 1. > https://lists.apache.org/thread.html/aae8787244959aeaab0e3e83dd79036482df9e8006f0fb83e5173d87@%3Cdev.dubbo.apache.org%3E > > 2. > https://lists.apache.org/thread.html/f272b30bd9bb09dc605088504f8ed643bd9a3b2434c9e7ef59b6b7fe@%3Cdev.dubbo.apache.org%3E > > 3. > https://lists.apache.org/thread.html/1987617abc1d4989476beda9dfc9a79eb0e4750050317803b113288c@%3Cdev.dubbo.apache.org%3E > > 4. > https://lists.apache.org/thread.html/ec7995d2c42bafcb8f2778b1d0c6ee94bcbbc2dae11d23c41cad82d6@%3Cdev.dubbo.apache.org%3E > > 5. > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- > Best Regards！ > Huxing > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi. > As Justin mentioned above, the translation is under going. We cannot do it for all because we need to examine the license and make sure ICLA for each projects are signed, I am not asking to move all repo related to Dubbo, which is decided by the project owner or Dubbo community. > eventually we hope to move everything into Apache group except for the repo [1] which serves redirection dubbo.io to dubbo.apache.org. As you mentioned, which make me concern more. Especially you say `eventually` and `hope`. Are these optional? Please read your own Incubator Proposal[1], section Initial Source, "Home Page: https://github.com/dubbo/dubbo.github.io; If the transfer has not been finished, you should wait for that before graduation. Why not just set the `redirect` on the DNS level, and host all in http://dubbo.apache.org. If the two are the same. If not, which is harder to understand for me. This is a block for me. > Now I have changed the title and the profile for dubbo group like this: You changed some. But if you look clearly about the logo(GitHub org avatar), also the name, you will see they[2][3] are the same, which both of them belong to ASF. Which makes me think the branding has not been cleared. Especially, I think Dubbo team has the full access to that GitHub org, so this should be able to be fixed. > Dubbo is now incubated in ASF: https://github.com/apache/incubator-dubbo, this group is for hosting dubbo eco-system temporarily before the transition finishes. The temporarily needs to be defined, as you are going to be a TLP, the PPMC(potentail PMC) have to make the decision, what do you want about your own repo. Notice, I am not saying all repo in GitHub, but the specific ones in the initial org, https://github.com/dubbo [1] https://wiki.apache.org/incubator/DubboProposal [2] http://dubbo.apache.org/en-us/ [3] https://github.com/dubbo Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Ian Luo 于2019年4月24日周三 上午10:29写道： > > > > Glad to see the actions are ongoing, and many projects are done. Could > the > > Dubbo community consider to make sure the Dubbo GitHub[1] org to be > > processed well? Such as, > > 1. Stop using the Dubbo logo. > > 2. Statement clear, this org will be renamed or some other way(community > > prefers) to avoid the branding concern. > > I think the clear status of Dubbo ecosystem is very important. > > > As Justin mentioned above, the translation is under going. We cannot do it > for all because we need to examine the license and make sure ICLA for each > projects are signed, but, eventually we hope to move everything into Apache > group except for the repo [1] which serves redirection dubbo.io to > dubbo.apache.org. > > Now I have changed the title and the profile for dubbo group like this: > > Title: Apache Dubbo Ecosystem > Profile: Dubbo is now incubated in ASF: > https://github.com/apache/incubator-dubbo, this group is for hosting dubbo > eco-system temporaryly before the transition finishes. > > I hope this can answer your concerns. > > Regards, > -Ian. > > > 1. https://github.com/dubbo/dubbo.github.io > > > On Wed, Apr 24, 2019 at 8:13 AM Sheng Wu > wrote: > > > > Part of the repo was used to host dubbo.io which now redirects to > > http://dubbo.apache.org/en-us/. Re the other projects it may be that a > > little clean up still needs to be done but action is being taken. The > > existence of this extra repo has been discussed a number of times in the > > project and projects are being moved off it. e.g. [1][2] and more > recently > > [3][4]. > > > This document probably best describes what is happening [5]. > > > > Glad to see the actions are ongoing, and many projects are done. Could > the > > Dubbo community consider to make sure the Dubbo GitHub[1] org to be > > processed well? Such as, > > 1. Stop using the Dubbo logo. > > 2. Statement clear, this org will be renamed or some other way(community > > prefers) to avoid the branding concern. > > I think the clear status of Dubbo ecosystem is very important. > > > > Dubbo has a very wide community and connected many projects/developers, > so > > please consider to make sure the branding is clear before graduation. > > > > > This issue is is being addressed (vote has been canceled, the > dependancy > > removed, documentation updated and there’s a discussion started on legal > > discuss on if it might in future be allowed). I also note it was the PPMC > > who first noticed this issue not the IPMC. > > > > This is not a blocker, this comes from the same reason I asked about > > branding. > > Dubbo is too widely used as they said in many media(s), many > >
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
> Part of the repo was used to host dubbo.io which now redirects to http://dubbo.apache.org/en-us/. Re the other projects it may be that a little clean up still needs to be done but action is being taken. The existence of this extra repo has been discussed a number of times in the project and projects are being moved off it. e.g. [1][2] and more recently [3][4]. > This document probably best describes what is happening [5]. Glad to see the actions are ongoing, and many projects are done. Could the Dubbo community consider to make sure the Dubbo GitHub[1] org to be processed well? Such as, 1. Stop using the Dubbo logo. 2. Statement clear, this org will be renamed or some other way(community prefers) to avoid the branding concern. I think the clear status of Dubbo ecosystem is very important. Dubbo has a very wide community and connected many projects/developers, so please consider to make sure the branding is clear before graduation. > This issue is is being addressed (vote has been canceled, the dependancy removed, documentation updated and there’s a discussion started on legal discuss on if it might in future be allowed). I also note it was the PPMC who first noticed this issue not the IPMC. This is not a blocker, this comes from the same reason I asked about branding. Dubbo is too widely used as they said in many media(s), many watcher(s)/star(s) in GitHub. I am hoping it will be a good example of ASF project, and the PMC is ready to find the license issue in first place. Thanks. [1] https://github.com/dubbo Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Justin Mclean 于2019年4月24日周三 上午7:19写道： > Hi, > > > 1. If graduation happens, Dubbo should be Apache branding, then why > > dubbo GitHub org[1] is still used. Especially the exact name and logo. > > Part of the repo was used to host dubbo.io which now redirects to > http://dubbo.apache.org/en-us/. Re the other projects it may be that a > little clean up still needs to be done but action is being taken. The > existence of this extra repo has been discussed a number of times in the > project and projects are being moved off it. e.g. [1][2] and more recently > [3][4]. > > This document probably best describes what is happening [5]. > > > 2. Most star project[2] in dubbo org is using Apache mail list[3]. But > > groupId[4] says it belongs Alibaba > > I would guess this is just an oversight, but if someone from the PPMC can > comment on this that would be good. > > > 3. Dubbo-go[5] project exists, and also use the Dubbo name. > > See [5]. > > > Also, in the last Dubbo vote `[VOTE]: Release Apache Dubbo > > Admin(Incubating) 0.2.0 [RC3]`. License issue hasn't been addressed > inside > > the PPMC(dev vote), I know LGPL is uncertain thing(maybe), but at this > > moment, it should not be included. > > This issue is is being addressed (vote has been canceled, the dependancy > removed, documentation updated and there’s a discussion started on legal > discuss on if it might in future be allowed). I also note it was the PPMC > who first noticed this issue not the IPMC. > > Thanks, > Justin > > 1. > https://lists.apache.org/thread.html/aae8787244959aeaab0e3e83dd79036482df9e8006f0fb83e5173d87@%3Cdev.dubbo.apache.org%3E > 2. > https://lists.apache.org/thread.html/f272b30bd9bb09dc605088504f8ed643bd9a3b2434c9e7ef59b6b7fe@%3Cdev.dubbo.apache.org%3E > 3. > https://lists.apache.org/thread.html/1987617abc1d4989476beda9dfc9a79eb0e4750050317803b113288c@%3Cdev.dubbo.apache.org%3E > 4. > https://lists.apache.org/thread.html/ec7995d2c42bafcb8f2778b1d0c6ee94bcbbc2dae11d23c41cad82d6@%3Cdev.dubbo.apache.org%3E > 5. > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi I have no doubt about the activity level of Dubbo community, as I have seen a lot of events and users around the project. So most cases, I think Dubbo is nearly to graduate. But I want to remind the incubator and Dubbo community, please pay attention to other things, besides codes and adoptors. Because they are as same as codes and users. 1. If graduation happens, Dubbo should be Apache branding, then why dubbo GitHub org[1] is still used. Especially the exact name and logo 2. Most star project[2] in dubbo org is using Apache mail list[3]. But groupId[4] says it belongs Alibaba 3. Dubbo-go[5] project exists, and also use the Dubbo name. Also, in the last Dubbo vote `[VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]`. License issue hasn't been addressed inside the PPMC(dev vote), I know LGPL is uncertain thing(maybe), but at this moment, it should not be included. I have concerns about whether the PPMC is ready about branding and license. [1] https://github.com/dubbo [2] https://github.com/dubbo/metrics [3] https://github.com/dubbo/metrics/blob/master/pom.xml#L439-L444 [4] https://github.com/dubbo/metrics/blob/master/pom.xml#L34 [5] https://github.com/dubbo/dubbo-go Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Huxing Zhang 于2019年4月23日周二 下午5:42写道： > Hi All, > > Since Apache Dubbo (incubating) entered the Apache incubator in > February 2018, the Dubbo community has been growing in a fast and > healthy way. Thanks to all the mentors, the community has learned a > lot about how to collaborate in Apache way. > > During incubation, we have: > - successfully made 11 releases with 7 different release managers. > - 6 new PPMC members are added since incubation(17 in total, excluding > mentors). The PPMC members varies from Alibaba, Jingdong, Youzan, > Weidian, Netease, Meituan-Dianping, Qunar. [0] > - 15 new committers are added since incubation. The committers varies > from Alibaba, Weidian, Jingdong, Qunar, Youzan, Netease, > Meituan-Dianping, Rongguan, Handuyishe, Didi, NetsUnion, Caocaokeji, > Huawei, GomeFinance, Asiainfo-sec, iFlytek, Keep and etc. [0] > - The number of contributors has grown from 70+ to 192 for the > incubator-dubbo repository. > - 1401 issues and 1168 pull requests are closed since incubation. > - 140+ companies are using Dubbo in production since incubation. > - 383 subscriber for the dev@ mailing list. Below is some stats in > recent few months: > * March 2019: 386 emails sent by 56 people, divided into 76 topics > * Feb 2019: 260 emails sent by 45 people, divided into 61 topics > * Jan 2019: 448 emails sent by 62 people, divided into 83 topics > * Dec 2018: 427 emails sent by 48 people, divided into 78 topics > * Nov 2018: 235 emails sent by 38 people, divided into 44 topics > * Oct 2018: 154 emails sent by 31 people, divided into 32 topics > > After a discussion in the Apache Dubbo community on the dev mailing > list[1], choosing PMC chair[2], forming the PMC members[3], completing > the maturity model[4], discussing the resolution proposal[5], and > voting for the graduation[6], the Dubbo community would like to > continue the graduation process and hereby ask the incubator community > for your opinion on this. > > Please see the resolution below and any comments, corrections, > suggestions, and feedback is welcome. > > The discussion is open for 72 hours. > > - > Establish the Apache Dubbo Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to a high-performance, lightweight, java based RPC framework. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Dubbo Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Dubbo Project be and hereby is responsible for > the creation and maintenance of software related to a high-performance, > lightweight, java based RPC framework; and be it further > > RESOLVED, that the office of "Vice President, Apache Dubbo" be and > hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the Apache Dubbo > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache Dubbo Project; > and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache Dubbo Project:
Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]
Hi > That option is based on my understanding that linking to > "hibernate-core" does not create a derivative work of > "hibernate-core". > Yes, when compiling the source code and run the incubator-dubbo-admin > code, the hibernate-core binary will be included, this > will create a derivative work of "hibernate-core". As long as user do > not distribute it, I think it is fine to use it. > This is the same case as using "spring-boot-starter-data-jpa". > However, it becomes a problem when user want to distributed the > incubator-dubbo-admin binary, it must not be licensed as Apache > license, but should only be GPL/LGPL licensed. > This creates a risk that some user won't use this software because of > the potential license issue, which is not what we want. > So as long as an Apache project does not distribute the binary, IMO it is fine. > That is my understanding of why this is an option. It is not a good > option, but I think it is an option. As an Apache project, we should make sure re-distribution friendly, no matter what the user intends to do. So I still think only keep them optional, and the user could download and use them if they want by themselves. For the license part, I am not an expert, even not close, but I prefer to follow the Apache suggestion at this moment. Unless the board or legal team change that. As it belongs to Catalog X[1] now and also supported by your answer, LGPL is not friendly to re-distribution. I still consider this a license issue. Also, you could bring this discussion to legal ml, I think. [1] https://apache.org/legal/resolved.html#category-x Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Huxing Zhang 于2019年4月22日周一 上午10:18写道： > Hi, > > On Sun, Apr 21, 2019 at 11:11 PM Sheng Wu > wrote: > > > > Hi. > > > > > 1. Stop distribute the binary of incubator-dubbo-admin > > > > I think "stop distribute the binary" would NOT change the fact the source > > release could lead users to use `hiberante-core`. I doubt this is an > option. > > That option is based on my understanding that linking to > "hibernate-core" does not create a derivative work of > "hibernate-core". > Yes, when compiling the source code and run the incubator-dubbo-admin > code, the hibernate-core binary will be included, this > will create a derivative work of "hibernate-core". As long as user do > not distribute it, I think it is fine to use it. > This is the same case as using "spring-boot-starter-data-jpa". > However, it becomes a problem when user want to distributed the > incubator-dubbo-admin binary, it must not be licensed as Apache > license, but should only be GPL/LGPL licensed. > This creates a risk that some user won't use this software because of > the potential license issue, which is not what we want. > So as long as an Apache project does not distribute the binary, IMO it is > fine. > That is my understanding of why this is an option. It is not a good > option, but I think it is an option. > > > > > Also based on the license issue, you should consider canceling this vote, > > and move the further discussion to dev ml. > > I agree that cancel this vote is the safest way for now, before > everything is cleared. > > > > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > Huxing Zhang 于2019年4月21日周日 下午11:02写道： > > > > > Hi, > > > > > > I am thinking why spring-boot-starter-data-jpa depends on LGPL > > > licensed library "hibernate-core", and can still be Apache 2.0 > > > licensed. > > > I am reading [1]. In section 5 it says: > > > > > > A program that contains no derivative of any portion of the Library, > > > but is designed to work with the Library by being compiled or linked > > > with it, is called a "work that uses the Library". Such a work, in > > > isolation, is not a derivative work of the Library, and therefore > > > falls outside the scope of this License. > > > > > > I think spring-boot-starter-data-jpa falls in to this case. It is a > > > "work that uses the Library". > > > > > > The source code of incubator-dubbo-admin should also falls into this > > > case, because it does not contain any portion of the hibernate-core. > > > Based on it and explanation here[2], I think the source code can be > > > released anyway. Is my understanding correct? > > > > > > Next, the LGPL license says: > > > > > > However, linking a "
Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]
Hi. > 1. Stop distribute the binary of incubator-dubbo-admin I think "stop distribute the binary" would NOT change the fact the source release could lead users to use `hiberante-core`. I doubt this is an option. Also based on the license issue, you should consider canceling this vote, and move the further discussion to dev ml. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Huxing Zhang 于2019年4月21日周日 下午11:02写道： > Hi, > > I am thinking why spring-boot-starter-data-jpa depends on LGPL > licensed library "hibernate-core", and can still be Apache 2.0 > licensed. > I am reading [1]. In section 5 it says: > > A program that contains no derivative of any portion of the Library, > but is designed to work with the Library by being compiled or linked > with it, is called a "work that uses the Library". Such a work, in > isolation, is not a derivative work of the Library, and therefore > falls outside the scope of this License. > > I think spring-boot-starter-data-jpa falls in to this case. It is a > "work that uses the Library". > > The source code of incubator-dubbo-admin should also falls into this > case, because it does not contain any portion of the hibernate-core. > Based on it and explanation here[2], I think the source code can be > released anyway. Is my understanding correct? > > Next, the LGPL license says: > > However, linking a "work that uses the Library" with the Library > creates an executable that is a derivative of the Library (because it > contains portions of the Library), rather than a "work that uses the > library". The executable is therefore covered by this License. > > The binary distribution of incuabator-dubbo-admin falls into this case > because it creates an executable that contains binary of > hibernate-core. Therefore it is a "work based on the library". As a > derivative of hibernate-core, it must be licensed with LGPL/GPL, which > is not allowed as an Apache product, and eventually causes the > incompatibility. > > If my understanding is correct, there are at least 4 ways to solve this > issue: > 1. Stop distribute the binary of incubator-dubbo-admin > 2. Make the feature optional, as explained here[3] > 3. Stop depending on hiberante-core > 4. Choose other Apache compatible equivalent > > I recommend to go with number 3 in my last thread. > > > [1] https://opensource.org/licenses/LGPL-2.1 > [2] https://www.apache.org/legal/resolved.html#prohibited > [3] https://www.apache.org/legal/resolved.html#optional > > On Sun, Apr 21, 2019 at 10:40 AM Huxing Zhang wrote: > > > > Hi, > > > > ccing dev@dubbo > > > > On Fri, Apr 19, 2019 at 8:24 AM Willem Jiang > wrote: > > > > > > Hi， > > > > > > I just checked the binary release kit, it has the third party > > > dependency of LGPL (Hibernate core) which is belonged to Cataloge > > > X[1], it cannot be included in Apache Product. > > > I had to vote -1 for it. We can change the ORM lib to Eclipse Link to > > > fix this issue, I just fill an issue here[2]. > > > > I did some dig for this issue and confirm that this is introduced by > > this pull request[1]. > > The purpose of this pull request is to introduce the pagination to > > service query. > > In this pull request a dependency to spring-boot-starter-data-jpa was > added, > > which introduce the LGPL licensed dependency hibernate-core. > > The detailed dependency tree is shown below: > > > > [INFO] +- > org.springframework.boot:spring-boot-starter-data-jpa:jar:2.0.2.RELEASE:compile > > [INFO] | +- > org.springframework.boot:spring-boot-starter-aop:jar:2.0.2.RELEASE:compile > > [INFO] | | \- org.aspectj:aspectjweaver:jar:1.8.13:compile > > [INFO] | +- > org.springframework.boot:spring-boot-starter-jdbc:jar:2.0.2.RELEASE:compile > > [INFO] | | +- com.zaxxer:HikariCP:jar:2.7.9:compile > > [INFO] | | \- org.springframework:spring-jdbc:jar:5.0.6.RELEASE:compile > > [INFO] | +- org.hibernate:hibernate-core:jar:5.2.17.Final:compile > > [INFO] | | +- > > > org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final:compile > > [INFO] | | +- antlr:antlr:jar:2.7.7:compile > > [INFO] | | +- org.jboss:jandex:jar:2.0.3.Final:compile > > [INFO] | | +- dom4j:dom4j:jar:1.6.1:compile > > [INFO] | | \- > > > org.hibernate.common:hibernate-commons-annotations:jar:5.0.1.Final:compile > > [INFO] | +- javax.transaction:javax.transaction-api:jar:1.2:compile > > [INFO] | +- > org.springframework.data:spring-data-jpa:jar:2.0.7.RELEASE:compile
Re: [ANNOUNCE] Apache ShardingSphere 4.0.0-RC1 available
Hi Liang The introduction is a little too long. One or two sentences for project description is good and clear for everyone. And be good for clear project landscape. Let's start a discussion in dev mail. zhangli...@apache.org 于2019年4月21日 周日下午6:52写道： > Hi all, > > Apache ShardingSphere (incubating) Team is glad to announce the first > release of Apache ShardingSphere Incubating 4.0.0-RC1. > > ShardingSphere is an open-source ecosystem consisted of a set of > distributed database middleware solutions, including 2 independent > products, Sharding-JDBC & Sharding-Proxy. > They both provide functions of data sharding, distributed transaction and > database orchestration, applicable in a variety of situations such as Java > isomorphism, heterogeneous language. > Aiming at reasonably making full use of the computation and storage > capacity of database in distributed system, ShardingSphere defines itself > as a middleware, rather than a totally new type of database. > As the cornerstone of many enterprises, relational database still takes a > huge market share. > Therefore, at current stage, we prefer to focus on its increment instead of > a total overturn. > > Sharding-JDBC defines itself as a lightweight Java framework that provides > extra service at Java JDBC layer. > With client end connecting directly to the database, it provides service in > the form of jar and requires no extra deployment and dependence. > It can be considered as an enhanced JDBC driver, which is fully compatible > with JDBC and all kinds of ORM frameworks. > > * Applicable in any ORM framework based on Java, such as JPA, Hibernate, > Mybatis, Spring JDBC Template or direct use of JDBC. > * Based on any third-party database connection pool, such as DBCP, C3P0, > BoneCP, Druid, HikariCP. > * Support any kind of database that conforms to JDBC standard: MySQL, > Oracle, SQLServer and PostgreSQL for now. > > Sharding-Proxy defines itself as a transparent database proxy, providing a > database server that encapsulates database binary protocol to support > heterogeneous languages. > Friendlier to DBA, the MySQL/PostgreSQL version provided now can use any > kind of client access (such as MySQL Command Client, MySQL Workbench, > Navicat etc.) that is compatible of MySQL/PostgreSQL protocol to operate > data. > > * Totally transparent to applications, it can be used directly as MySQL and > PostgreSQL. > > * Applicable to any kind of compatible of client end that is compatible of > MySQL and PostgreSQL protocol. > > > Vote Thread: > > https://lists.apache.org/thread.html/25c11b46dd3a58d4048dd35be71d21f86db6f5278480eb7083149af1@%3Cgeneral.incubator.apache.org%3E > > Download Links: > > https://dist.apache.org/repos/dist/release/incubator/shardingsphere/4.0.0-RC1/ > > Release Notes: > https://github.com/apache/incubator-shardingsphere/releases/tag/4.0.0-RC1/ > > Website: https://shardingsphere.apache.org/ > > ShardingSphere Resources: > > - Issue: https://github.com/apache/incubator-shardingsphere/issues > - Mailing list: d...@shardingsphere.apache.org > - Documents: https://shardingsphere.apache.org/document/current > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
Re: [VOTE]: Release Apache ShardingSphere (Incubating) 4.0.0-RC1
Hi Justin Yes. You are right. Sorry, my misread. I saw the following mail from Willem, but this mail goes to dev@. My mail achieved them in the same thread(maybe because of the title). ``` +1 (binding) Forward my VOTE from dev@ list ``` Hi Liang Zhang Please notice this, if face this again, please manually forward the +1 from dev to incubator, or remind the mentor to do that. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Justin Mclean 于2019年4月21日周日 下午5:24写道： > Hi, > > > I saw three +1 votes, including two mentors, Willem and Gosling, and I > > gave +1 too. > > AFACS Willem's vote didn’t end up in this thread [1] but ended up on your > dev list [2]. I think this confusion happed as you sent the initial vote > email to both lists. > > Thanks, > Justin > > 1. > https://lists.apache.org/thread.html/25c11b46dd3a58d4048dd35be71d21f86db6f5278480eb7083149af1@%3Cgeneral.incubator.apache.org%3E > 2. > https://lists.apache.org/thread.html/445bf1e41648b042e14a6b77d8bc2364eb9a0406764f59a5fb0231c5@%3Cdev.shardingsphere.apache.org%3E > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE]: Release Apache ShardingSphere (Incubating) 4.0.0-RC1
Hi Justin I saw three +1 votes, including two mentors, Willem and Gosling, and I gave +1 too. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Justin Mclean 于2019年4月21日周日 下午4:54写道： > Hi, > > > The vote has already opened for at least 72 hours and necessary number of > > votes are reached. > > There’s only 2 +1 votes I count here and you need 3 for a vote to pass. > Did you have the rIPMC member vote on your dev list? > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]
Hi If the LGPL lib is delivering inside final binary tar, I agree this causes a license issue, which should be fixed. Sheng Willem Jiang 于2019年4月19日 周五下午9:11写道： > If you extract the dubbo-admin-0.2.0.jar from the > apache-dubbo-admin-incubating-0.2.0-bin.zip, you can find the > hibernate-core-5.2.17.Final.jar in the BOOT-INF/lib directory. > I found this issue by going through the License file of the bin.zip > file, it lists the LGPL library of Hibernate. > Event you just have the dependency of spring-boot-jpa, you still need > to check final dependencies of spring-boot application. > > [1] > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/apache-dubbo-admin-incubating-0.2.0-bin.zip > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Apr 19, 2019 at 1:36 PM Minxuan Zhuang > wrote: > > > > hi Craig: > >we do not depend hibernate directly, they are imported by spring boot > web > > > > On Fri, Apr 19, 2019 at 11:31 AM Craig Russell > wrote: > > > > > I don't know if it helps, but there are Apache Projects for both > > > relational database (Derby) and ORM (OpenJPA) that can be included in > > > binary releases. > > > > > > So we should never need to bundle LGPL or Category X projects with > binary > > > releases. > > > > > > Craig > > > > > > > On Apr 18, 2019, at 5:23 PM, Willem Jiang > > > wrote: > > > > > > > > Hi， > > > > > > > > I just checked the binary release kit, it has the third party > > > > dependency of LGPL (Hibernate core) which is belonged to Cataloge > > > > X[1], it cannot be included in Apache Product. > > > > I had to vote -1 for it. We can change the ORM lib to Eclipse Link to > > > > fix this issue, I just fill an issue here[2]. > > > > > > > > [1]https://www.apache.org/legal/resolved.html#category-x > > > > [2]https://github.com/apache/incubator-dubbo-admin/issues/366 > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Mon, Apr 15, 2019 at 10:24 AM Minxuan Zhuang > > > > wrote: > > > >> > > > >> Hello Incubator Community, > > > >> > > > >> The Apache Dubbo community has voted on and approved a proposal to > > > release > > > >> Apache Dubbo Admin (Incubating) version 0.2.0. > > > >> > > > >> We now kindly request the Incubator PMC members review and vote on > this > > > >> incubator release. > > > >> > > > >> Apache Dubbo™ (incubating) is a high-performance, java based, open > > > source > > > >> RPC framework. Dubbo offers three key functionalities, which include > > > >> interface based remote call, fault tolerance & load balancing, and > > > >> automatic service registration & discovery. > > > >> > > > >> > > > >> Dubbo community vote and result thread: > > > >> > > > > https://lists.apache.org/thread.html/fc71a5f8c93b8c3606338b97a08c044af64ca3165e226aed37295a45@%3Cdev.dubbo.apache.org%3E > > > >> > > > >> The release candidates (RC3): > > > >> * > > > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0 > > > >> < > > > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/ > > > >/* > > > >> > > > >> > > > >> Git tag for the release (RC3): > > > >> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0 > > > >> > > > >> Hash for the release tag: > > > >> 37e23a7354e3da50914e075eb4676c7c2875ffa7 > > > >> > > > >> Release Notes: > > > >> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0 > > > >> > > > >> > > > >> The artifacts have been signed with Key : > > > >> DA2108479B0C1E71, which can be > > > >> found in the keys file: > > > >> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > > >> <https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS>* > > > >> > > > >> The vote will be open for at least 72 hours or until necessary > number of > > > >> votes are reached. > > > >> > > > >> Please vote accordingly: > > > >> > > > >> [ ] +1 approve > > > >> [ ] +0 no opinion > > > >> [ ] -1 disapprove with the reason > > > >> > > > >> Thanks, > > > >> The Apache Dubbo (Incubating) Team > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > Craig L Russell > > > c...@apache.org > > > > > > > > > - > > > 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 > > -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]
Hi, Do you deliver it in your binary tar? And do you need it at runtime? Sheng Minxuan Zhuang 于2019年4月19日 周五下午1:36写道： > hi Craig: >we do not depend hibernate directly, they are imported by spring boot > web > > On Fri, Apr 19, 2019 at 11:31 AM Craig Russell > wrote: > > > I don't know if it helps, but there are Apache Projects for both > > relational database (Derby) and ORM (OpenJPA) that can be included in > > binary releases. > > > > So we should never need to bundle LGPL or Category X projects with binary > > releases. > > > > Craig > > > > > On Apr 18, 2019, at 5:23 PM, Willem Jiang > > wrote: > > > > > > Hi， > > > > > > I just checked the binary release kit, it has the third party > > > dependency of LGPL (Hibernate core) which is belonged to Cataloge > > > X[1], it cannot be included in Apache Product. > > > I had to vote -1 for it. We can change the ORM lib to Eclipse Link to > > > fix this issue, I just fill an issue here[2]. > > > > > > [1]https://www.apache.org/legal/resolved.html#category-x > > > [2]https://github.com/apache/incubator-dubbo-admin/issues/366 > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Mon, Apr 15, 2019 at 10:24 AM Minxuan Zhuang > > wrote: > > >> > > >> Hello Incubator Community, > > >> > > >> The Apache Dubbo community has voted on and approved a proposal to > > release > > >> Apache Dubbo Admin (Incubating) version 0.2.0. > > >> > > >> We now kindly request the Incubator PMC members review and vote on > this > > >> incubator release. > > >> > > >> Apache Dubbo™ (incubating) is a high-performance, java based, open > > source > > >> RPC framework. Dubbo offers three key functionalities, which include > > >> interface based remote call, fault tolerance & load balancing, and > > >> automatic service registration & discovery. > > >> > > >> > > >> Dubbo community vote and result thread: > > >> > > > https://lists.apache.org/thread.html/fc71a5f8c93b8c3606338b97a08c044af64ca3165e226aed37295a45@%3Cdev.dubbo.apache.org%3E > > >> > > >> The release candidates (RC3): > > >> * > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0 > > >> < > > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-admin/0.2.0/ > > >/* > > >> > > >> > > >> Git tag for the release (RC3): > > >> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0 > > >> > > >> Hash for the release tag: > > >> 37e23a7354e3da50914e075eb4676c7c2875ffa7 > > >> > > >> Release Notes: > > >> https://github.com/apache/incubator-dubbo-admin/releases/tag/0.2.0 > > >> > > >> > > >> The artifacts have been signed with Key : > > >> DA2108479B0C1E71, which can be > > >> found in the keys file: > > >> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > >> <https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS>* > > >> > > >> The vote will be open for at least 72 hours or until necessary number > of > > >> votes are reached. > > >> > > >> Please vote accordingly: > > >> > > >> [ ] +1 approve > > >> [ ] +0 no opinion > > >> [ ] -1 disapprove with the reason > > >> > > >> Thanks, > > >> The Apache Dubbo (Incubating) Team > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > Craig L Russell > > c...@apache.org > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
Re: [VOTE]: Release Apache ShardingSphere (Incubating) 4.0.0-RC1
+1 binding checked 1. acs exist and checked 2. LICENSE and NOTICE exist in the source tar 3. DISCLAIMER exists 4. sha512 exist 5. source compile passed. 6. rat exclusions look right, no special. Rat passed. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Willem Jiang 于2019年4月16日周二 下午6:45写道： > +1 (binding) > > Forward my VOTE from dev@ list > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > On Tue, Apr 16, 2019 at 4:33 PM zhangli...@apache.org > wrote: > > > > Hello all, > > > > This is a call for vote to release Apache ShardingSphere (Incubating) > > version 4.0.0-RC1. > > > > The Apache ShardingSphere community has voted on and approved a proposal > to > > release > > Apache ShardingSphere (Incubating) version 4.0.0-RC1. > > > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > > ShardingSphere is an open-source ecosystem consisted of a set of > > distributed database middleware solutions, including 2 independent > > products, Sharding-JDBC & Sharding-Proxy. > > They both provide functions of data sharding, distributed transaction and > > database orchestration, applicable in a variety of situations such as > Java > > isomorphism, heterogeneous language. > > Aiming at reasonably making full use of the computation and storage > > capacity of database in distributed system, ShardingSphere defines itself > > as a middleware, rather than a totally new type of database. > > As the cornerstone of many enterprises, relational database still takes a > > huge market share. > > Therefore, at current stage, we prefer to focus on its increment instead > of > > a total overturn. > > > > Sharding-JDBC defines itself as a lightweight Java framework that > provides > > extra service at Java JDBC layer. > > With client end connecting directly to the database, it provides service > in > > the form of jar and requires no extra deployment and dependence. > > It can be considered as an enhanced JDBC driver, which is fully > compatible > > with JDBC and all kinds of ORM frameworks. > > > > * Applicable in any ORM framework based on Java, such as JPA, Hibernate, > > Mybatis, Spring JDBC Template or direct use of JDBC. > > * Based on any third-party database connection pool, such as DBCP, C3P0, > > BoneCP, Druid, HikariCP. > > * Support any kind of database that conforms to JDBC standard: MySQL, > > Oracle, SQLServer and PostgreSQL for now. > > > > Sharding-Proxy defines itself as a transparent database proxy, providing > a > > database server that encapsulates database binary protocol to support > > heterogeneous languages. > > Friendlier to DBA, the MySQL/PostgreSQL version provided now can use any > > kind of client access (such as MySQL Command Client, MySQL Workbench, > > Navicat etc.) that is compatible of MySQL/PostgreSQL protocol to operate > > data. > > > > * Totally transparent to applications, it can be used directly as MySQL > and > > PostgreSQL. > > > > * Applicable to any kind of compatible of client end that is compatible > of > > MySQL and PostgreSQL protocol. > > > > > > ShardingSphere community vote and result thread: > > > https://lists.apache.org/thread.html/7818fb3400ca4404d4d9c47407f4589281ba4a499e0a798b7d714c32@%3Cdev.shardingsphere.apache.org%3E > > > > Release notes: > > > https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-d5d2dc137c82994bbaac > > > > The release candidates: > > > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC1/ > > > > Maven 2 staging repository: > > > https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ > > > > Git tag for the release: > > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC1 > > > > Release Commit ID: > > > https://github.com/apache/incubator-shardingsphere/commit/2c1d23f9569e5cbe74074a578931c77dfa800800 > > > > Keys to verify the Release Candidate: > > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS > > > > Look at here for how to verify this release candidate: > > https://shardingsphere.apache.org/community/en/contribute/release/ > > > > The vote will be open for at least 72 hours or until necessary number of > > votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > Checklist for reference: > > > > [ ] Download links are valid. > > > > [ ] Checksums and PGP signatures are valid. > > > > [ ] DISCLAIMER is included. > > > > [ ] Source code artifacts have correct names matching the current > release. > > > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > > > [ ] All files have license headers if necessary. > > > > [ ] No compiled archives bundled in source archive. > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo >
Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to askingIPMC to vote
Have enough mentor votes in dev vote, and carry them to incubator vote, really could make the IPMC vote more flexible. IPMC member could help on recheck from different view, which sometimes is necessary. Fresh eyes are good to the community and assist the project speed up to graduate, in my perspective. Even one or two IPMC vote -1, but the project mentors think still good enough to release, then the release wouldn't be blocked. From my experiences, in SkyWalking as very new in ASF, in ShardingSphere as a member of PPMC goes through incubator journey again, and in Zipkin as a project mentor, all these project PPMC team explicitly hope that, they could have this kind of help from mentors. I am +1 for Craig's suggestion, and hope the mentors could have time to take part in the release checks. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Ross Gardler"; Date: Mon, Apr 1, 2019 12:14 PM To: "general@incubator.apache.org"; Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to askingIPMC to vote Just like so many things, this is how it used to be. In fact, back in the day the only time the IPMC was asked to vote was when there were not enough mentor votes. If you look at all the podlinga I've mentored I have only ever asked for an IPMC vote on two occasions (that I recall). One because I had absent mentors (the project never graduated due to lack of success as a community) and one because it was a very large and complex code base and we asked for extra eyes on the first release. Every other time the community worked with mentors. Once we had the votes we notified the IPMC that the vote had passed and moved on. Requiring an IPMC vote is akin to the board voting on all TLP releases. It should be stopped. The IPMC are facilitators not gate keepers. Individual IPMC members can join the podling communities if they wish to participate. Why are podlings and mentors answering to the IPMC by default? I know the standard answer is because mentors sometimes get too busy. Sure. If it happens every release is a problem and having to ask for an IPMC vote highlights the problem. I realize this proposal does not go this far, I'm +0 for the proposal as a step in the right direction, but it doesn't go far enough in my opinion. Ross Get Outlook for Android<https://aka.ms/ghei36> From: Craig Russell Sent: Sunday, March 31, 2019 8:30:35 PM To: Incubator Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote This is a proposal to recommend that all Mentors SHOULD vote on podling releases prior to sending the release for a vote to the IPMC. This is not a MUST, since there are many good reasons why a mentor might be unable to perform the checks needed to vote. We are volunteers after all. But if this proposal is adopted, it will minimize the occurrences of a podling desperately asking for someone, anyone, on the IPMC to please vote. It should also minimize the number of podling releases that are shot down in the full IPMC vote because of something that a Mentor is likely to catch. Thanks for your consideration, Craig Craig L Russell c...@apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator wiki being deprecated
Hi, I guess the issue caused by my wiki username as same as Apache id before ldap integrated. Look like it is not working. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Willem Jiang Date: Sun,Mar 24,2019 5:34 PM To: general Subject: Re: Incubator wiki being deprecated Hi WuSheng, cwiki is LDAP enabled, you should have the access right if you login with your Apache ID. Willem Jiang Twitter: willemjiang Weibo: willem On Sun, Mar 24, 2019 at 9:26 AM Sheng Wu wrote: > > Hi Justin > > > Besides the contents, I think we need to grant access again. I just use my > username(wusheng) to login, no right to edit page. > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "justin"; > Date: Sun, Mar 24, 2019 09:02 AM > To: "general"; > > Subject: Incubator wiki being deprecated > > > > Hi, > > If you didn??t know the wiki.apache.org system using Moin software is being > decommissioned in May 2019. Currently how incubator reports are being created > depend on this system and this will need to change. > > I??ve created an incubator space [1] and we shovel think about mobbing the > content over. There??s a self help migration tool, but given the size of the > incubator wiki I??m not 100% sure if that??a a good idea to run. > > Thanks, > Justin > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR > - > 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: Incubator wiki being deprecated
Hi Justin Besides the contents, I think we need to grant access again. I just use my username(wusheng) to login, no right to edit page. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "justin"; Date: Sun, Mar 24, 2019 09:02 AM To: "general"; Subject: Incubator wiki being deprecated Hi, If you didn??t know the wiki.apache.org system using Moin software is being decommissioned in May 2019. Currently how incubator reports are being created depend on this system and this will need to change. I??ve created an incubator space [1] and we shovel think about mobbing the content over. There??s a self help migration tool, but given the size of the incubator wiki I??m not 100% sure if that??a a good idea to run. Thanks, Justin 1. https://cwiki.apache.org/confluence/display/INCUBATOR - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Recommend 'Apache SkyWalking graduation to TopLevelProject' resolution to board
Hi Sebb > r32183 | wusheng | 2019-01-29 08:19:22 + (Tue, 29 Jan 2019) | 2 lines Changed paths: D /dev/incubator/skywalking/6.0.0-GA A /release/incubator/skywalking/6.0.0-GA (from /dev/incubator/skywalking/6.0.0-GA:32182) Fixed. Log and last change time have been reset to 2019-01-21 06:24[1] > Also the hash and sig links on the download page should use HTTPS when referencing the archive site, same as for www.apache.org. Fixed. Website updated. [1] https://www.apache.org/dist/incubator/skywalking/6.0.0-GA/ -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "sebb"; Date: Sat, Mar 23, 2019 08:24 AM To: "general"; Subject: Re: [VOTE] Recommend 'Apache SkyWalking graduation to TopLevelProject' resolution to board On Sat, 23 Mar 2019 at 00:06, Sheng Wu wrote: > > Hi Sebb, Deva, Kevin > > > Status update, > I added the 6.0.0-GA back. And all links in website updated to > http://archive.apache.org/ > Thanks. However the SVN history has been lost; the files look brand new as far as the history is concerned. I think there are ways to copy the files from previous versions in SVN which preserve the history. It should be possible to get them from this commit: r32183 | wusheng | 2019-01-29 08:19:22 + (Tue, 29 Jan 2019) | 2 lines Changed paths: D /dev/incubator/skywalking/6.0.0-GA A /release/incubator/skywalking/6.0.0-GA (from /dev/incubator/skywalking/6.0.0-GA:32182) In the above commit one can clearly see the provenance of the release/ files from the dev/ files Also the hash and sig links on the download page should use HTTPS when referencing the archive site, same as for www.apache.org. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board
Hi Sebb, Deva, Kevin Status update, I added the 6.0.0-GA back. And all links in website updated to http://archive.apache.org/ Thanks for your helps. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "wush...@apache.org"; Date: Sat, Mar 23, 2019 07:43 AM To: "general"; Subject: Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board Hi Sebb > Did you really intend to remove the current release as well? > > That does not seem right; the current release is normally left until > the TLP makes its first release. The latest release, 6.0.0-GA, is back. > Also the download page needs to be updated to use the archive server > for the *old* releases (6.0.0-beta and 6.0.0-alpha). > [These should already have been removed from dist and the links > changed to point to the archive server when 6.0.0-GA was released] The old links look like still working. Such as the removed 6.0.0-beta[1]. Do we still need to change all the links? [1] http://www.apache.org/dyn/closer.cgi/incubator/skywalking/6.0.0-beta/apache-skywalking-apm-incubating-6.0.0-beta-src.tgz On 2019/03/22 22:44:19, sebb wrote: > On Fri, 22 Mar 2019 at 16:41, Sheng Wu wrote: > > > > Hi Dave > > > > > > Thanks for the remind. > > I just removed all releases from a.o/dist[1], and checked all of them exist > > in archive.a.o[2]. > > Did you really intend to remove the current release as well? > > That does not seem right; the current release is normally left until > the TLP makes its first release. > > Also the download page needs to be updated to use the archive server > for the *old* releases (6.0.0-beta and 6.0.0-alpha). > [These should already have been removed from dist and the links > changed to point to the archive server when 6.0.0-GA was released] > > > > > [1] https://www.apache.org/dist/incubator/skywalking/ > > [2] http://archive.apache.org/dist/incubator/skywalking/ > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "Dave Fisher"; > > Date: Fri, Mar 22, 2019 07:55 AM > > To: "general"; > > > > Subject: Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top > > LevelProject' resolution to board > > > > > > > > +1 (binding) > > > > If you look at the new https://incubator.apache.org/clutch/skywalking.html > > <https://incubator.apache.org/clutch/skywalking.html> analysis you will see > > activity in all repositories and that > > https://skywalking.apache.org/downloads/ > > <https://skywalking.apache.org/downloads/> corresponds to the list on the > > clutch analysis. > > > > I??ll note that only current releases on supported versions should be on > > the distribution area. Older releases should be referenced from > > archives.apache.org <http://archives.apache.org/> - here I am referring to > > the RC, Beta, and Alpha releases. Please take care of this. > > > > I don??t view this as blocking since as a TLP the policy is the same. > > > > Regards, > > Dave > > > > > On Mar 18, 2019, at 10:21 PM, Mick Semb Wever wrote: > > > > > > > > > > > > After the latest discussion amongst this dev community on this dev > > > mailing list[1], presenting Sheng Wu as the PMC Chair and the maturity > > > model[2], and then the discussion again on the incubator list[3], a vote > > > for Apache SkyWalking graduating to a top level project was called and > > > has passed[4]. From the past incubator discussions the PPMC altered the > > > draft graduation proposal, specifically the proposed PMC list: removing > > > some inactive people and adding all the podling Committers. > > > > > > > > > Apache SkyWalking entered the incubator on December of 2017. SkyWalking > > > has delivered 8 releases so far in total, and now shows a good cadence of > > > successful releases. > > > > > > During the podling's time in the Apache Incubator there has been > > > 3200+ commits on development of the project, > > > 378 Issues tagged as question in GitHub created, 373 resolved, > > > 850+ Pull request created and resolved, > > > 97 different contributors, > > >9 elected new committers, and > > &
Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board
Hi Sebb > Did you really intend to remove the current release as well? > > That does not seem right; the current release is normally left until > the TLP makes its first release. The latest release, 6.0.0-GA, is back. > Also the download page needs to be updated to use the archive server > for the *old* releases (6.0.0-beta and 6.0.0-alpha). > [These should already have been removed from dist and the links > changed to point to the archive server when 6.0.0-GA was released] The old links look like still working. Such as the removed 6.0.0-beta[1]. Do we still need to change all the links? [1] http://www.apache.org/dyn/closer.cgi/incubator/skywalking/6.0.0-beta/apache-skywalking-apm-incubating-6.0.0-beta-src.tgz On 2019/03/22 22:44:19, sebb wrote: > On Fri, 22 Mar 2019 at 16:41, 吴晟 Sheng Wu wrote: > > > > Hi Dave > > > > > > Thanks for the remind. > > I just removed all releases from a.o/dist[1], and checked all of them exist > > in archive.a.o[2]. > > Did you really intend to remove the current release as well? > > That does not seem right; the current release is normally left until > the TLP makes its first release. > > Also the download page needs to be updated to use the archive server > for the *old* releases (6.0.0-beta and 6.0.0-alpha). > [These should already have been removed from dist and the links > changed to point to the archive server when 6.0.0-GA was released] > > > > > [1] https://www.apache.org/dist/incubator/skywalking/ > > [2] http://archive.apache.org/dist/incubator/skywalking/ > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "Dave Fisher"; > > Date: Fri, Mar 22, 2019 07:55 AM > > To: "general"; > > > > Subject: Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top > > LevelProject' resolution to board > > > > > > > > +1 (binding) > > > > If you look at the new https://incubator.apache.org/clutch/skywalking.html > > <https://incubator.apache.org/clutch/skywalking.html> analysis you will see > > activity in all repositories and that > > https://skywalking.apache.org/downloads/ > > <https://skywalking.apache.org/downloads/> corresponds to the list on the > > clutch analysis. > > > > I’ll note that only current releases on supported versions should be on the > > distribution area. Older releases should be referenced from > > archives.apache.org <http://archives.apache.org/> - here I am referring to > > the RC, Beta, and Alpha releases. Please take care of this. > > > > I don’t view this as blocking since as a TLP the policy is the same. > > > > Regards, > > Dave > > > > > On Mar 18, 2019, at 10:21 PM, Mick Semb Wever wrote: > > > > > > > > > > > > After the latest discussion amongst this dev community on this dev > > > mailing list[1], presenting Sheng Wu as the PMC Chair and the maturity > > > model[2], and then the discussion again on the incubator list[3], a vote > > > for Apache SkyWalking graduating to a top level project was called and > > > has passed[4]. From the past incubator discussions the PPMC altered the > > > draft graduation proposal, specifically the proposed PMC list: removing > > > some inactive people and adding all the podling Committers. > > > > > > > > > Apache SkyWalking entered the incubator on December of 2017. SkyWalking > > > has delivered 8 releases so far in total, and now shows a good cadence of > > > successful releases. > > > > > > During the podling's time in the Apache Incubator there has been > > > 3200+ commits on development of the project, > > > 378 Issues tagged as question in GitHub created, 373 resolved, > > > 850+ Pull request created and resolved, > > > 97 different contributors, > > >9 elected new committers, and > > >3 elected new PPMC members. > > > > > > And the dev ML has had 72 participants: > > > https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019 > > > > > > Attached is the draft Resolution for the PPMC and IPMC to vote upon. > > > > > > Please take a minute to vote on whether or not Apache SkyWalking should > > > graduate to a Top Level Project by responding with one of the following: > > > > > > [ ]
Re: [VOTE] Recommend 'Apache SkyWalking graduation to TopLevelProject' resolution to board
Hi Kevin The current release, 6.0.0-GA[1] is back. And I think the old releases have been pointing to archive.a.o automatically. Like 6.0.0-beta[2] I think the current status is right. [1] https://www.apache.org/dist/incubator/skywalking/6.0.0-GA/ [2] http://www.apache.org/dyn/closer.cgi/incubator/skywalking/6.0.0-beta/apache-skywalking-apm-incubating-6.0.0-beta-src.tgz -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Kevin A. McGrail"; Date: Sat, Mar 23, 2019 06:50 AM To: "general"; Subject: Re: [VOTE] Recommend 'Apache SkyWalking graduation to TopLevelProject' resolution to board I am +1 (binding) contingent on the current release being added back and Dave/Sebb are happy with your incorrect releases being removed. -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Fri, Mar 22, 2019 at 6:44 PM sebb wrote: > On Fri, 22 Mar 2019 at 16:41, Sheng Wu wrote: > > > > Hi Dave > > > > > > Thanks for the remind. > > I just removed all releases from a.o/dist[1], and checked all of them > exist in archive.a.o[2]. > > Did you really intend to remove the current release as well? > > That does not seem right; the current release is normally left until > the TLP makes its first release. > > Also the download page needs to be updated to use the archive server > for the *old* releases (6.0.0-beta and 6.0.0-alpha). > [These should already have been removed from dist and the links > changed to point to the archive server when 6.0.0-GA was released] > > > > > [1] https://www.apache.org/dist/incubator/skywalking/ > > [2] http://archive.apache.org/dist/incubator/skywalking/ > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "Dave Fisher"; > > Date: Fri, Mar 22, 2019 07:55 AM > > To: "general"; > > > > Subject: Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top > LevelProject' resolution to board > > > > > > > > +1 (binding) > > > > If you look at the new > https://incubator.apache.org/clutch/skywalking.html < > https://incubator.apache.org/clutch/skywalking.html> analysis you will > see activity in all repositories and that > https://skywalking.apache.org/downloads/ < > https://skywalking.apache.org/downloads/> corresponds to the list on the > clutch analysis. > > > > I??ll note that only current releases on supported versions should be on > the distribution area. Older releases should be referenced from > archives.apache.org <http://archives.apache.org/> - here I am referring > to the RC, Beta, and Alpha releases. Please take care of this. > > > > I don??t view this as blocking since as a TLP the policy is the same. > > > > Regards, > > Dave > > > > > On Mar 18, 2019, at 10:21 PM, Mick Semb Wever wrote: > > > > > > > > > > > > After the latest discussion amongst this dev community on this dev > mailing list[1], presenting Sheng Wu as the PMC Chair and the maturity > model[2], and then the discussion again on the incubator list[3], a vote > for Apache SkyWalking graduating to a top level project was called and has > passed[4]. From the past incubator discussions the PPMC altered the draft > graduation proposal, specifically the proposed PMC list: removing some > inactive people and adding all the podling Committers. > > > > > > > > > Apache SkyWalking entered the incubator on December of 2017. > SkyWalking has delivered 8 releases so far in total, and now shows a good > cadence of successful releases. > > > > > > During the podling's time in the Apache Incubator there has been > > > 3200+ commits on development of the project, > > > 378 Issues tagged as question in GitHub created, 373 resolved, > > > 850+ Pull request created and resolved, > > > 97 different contributors, > > >9 elected new committers, and > > >3 elected new PPMC members. > > > > > > And the dev ML has had 72 participants: > https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019 > > > > > > Attached is the draft Resolution for the PPMC and IPMC to vote upon. > > > > > > Please take a minute to vote on whether or not Apache
Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board
+ 1 (binding) as a member of IPMC. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "willem.jiang"; Date: Thu, Mar 21, 2019 02:21 PM To: "general"; Subject: Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board +1 ??binding?? It's good to see SkyWalking is growing up. Willem Jiang Twitter: willemjiang Weibo: willem On Tue, Mar 19, 2019 at 1:21 PM Mick Semb Wever wrote: > > > > After the latest discussion amongst this dev community on this dev mailing > list[1], presenting Sheng Wu as the PMC Chair and the maturity model[2], and > then the discussion again on the incubator list[3], a vote for Apache > SkyWalking graduating to a top level project was called and has passed[4]. > From the past incubator discussions the PPMC altered the draft graduation > proposal, specifically the proposed PMC list: removing some inactive people > and adding all the podling Committers. > > > Apache SkyWalking entered the incubator on December of 2017. SkyWalking has > delivered 8 releases so far in total, and now shows a good cadence of > successful releases. > > During the podling's time in the Apache Incubator there has been > 3200+ commits on development of the project, > 378 Issues tagged as question in GitHub created, 373 resolved, > 850+ Pull request created and resolved, > 97 different contributors, > 9 elected new committers, and > 3 elected new PPMC members. > > And the dev ML has had 72 participants: > https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019 > > Attached is the draft Resolution for the PPMC and IPMC to vote upon. > > Please take a minute to vote on whether or not Apache SkyWalking should > graduate to a Top Level Project by responding with one of the following: > > [ ] +1 Apache SkyWalking should graduate. > [ ] +0 No opinion > [ ] -1 Apache SkyWalking should not graduate (please provide the reason) > > The VOTE is open for a minimum of 72 hours. As there has been previous > discussions on past versions of this proposal, I have not preluded the vote > with a DISCUSS email. If feedback arises the vote period will be extended in > good faith. > > regards, > Mick > > > [1] > https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E > [2] > https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking > [3] > https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E > [4] > https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E > > > > > Establish the Apache SkyWalking Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to application performance management and monitoring (APM). > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache SkyWalking Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache SkyWalking Project be and hereby is > responsible for the creation and maintenance of software related to > application performance management and monitoring (APM); and > be it further > > RESOLVED, that the office of "Vice President, Apache SkyWalking" be and > hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the Apache > SkyWalking Project, and to have primary responsibility for management of > the projects within the scope of responsibility of the Apache SkyWalking > Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache SkyWalking > Project: > > * Haoyang Liu (??) > * Hongtao Gao (??) > * Ignasi Barrera > * Mick Semb Wever > * Sheng Wu () > * Shinn Zhang () > * Willem Ning Jiang () > * Yongsheng Peng (??) > * DongXue Si (??) > * Jian Tan ()
Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board
Hi Dave Thanks for the remind. I just removed all releases from a.o/dist[1], and checked all of them exist in archive.a.o[2]. [1] https://www.apache.org/dist/incubator/skywalking/ [2] http://archive.apache.org/dist/incubator/skywalking/ -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Dave Fisher"; Date: Fri, Mar 22, 2019 07:55 AM To: "general"; Subject: Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board +1 (binding) If you look at the new https://incubator.apache.org/clutch/skywalking.html <https://incubator.apache.org/clutch/skywalking.html> analysis you will see activity in all repositories and that https://skywalking.apache.org/downloads/ <https://skywalking.apache.org/downloads/> corresponds to the list on the clutch analysis. I??ll note that only current releases on supported versions should be on the distribution area. Older releases should be referenced from archives.apache.org <http://archives.apache.org/> - here I am referring to the RC, Beta, and Alpha releases. Please take care of this. I don??t view this as blocking since as a TLP the policy is the same. Regards, Dave > On Mar 18, 2019, at 10:21 PM, Mick Semb Wever wrote: > > > > After the latest discussion amongst this dev community on this dev mailing > list[1], presenting Sheng Wu as the PMC Chair and the maturity model[2], and > then the discussion again on the incubator list[3], a vote for Apache > SkyWalking graduating to a top level project was called and has passed[4]. > From the past incubator discussions the PPMC altered the draft graduation > proposal, specifically the proposed PMC list: removing some inactive people > and adding all the podling Committers. > > > Apache SkyWalking entered the incubator on December of 2017. SkyWalking has > delivered 8 releases so far in total, and now shows a good cadence of > successful releases. > > During the podling's time in the Apache Incubator there has been > 3200+ commits on development of the project, > 378 Issues tagged as question in GitHub created, 373 resolved, > 850+ Pull request created and resolved, > 97 different contributors, >9 elected new committers, and >3 elected new PPMC members. > > And the dev ML has had 72 participants: > https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019 > > Attached is the draft Resolution for the PPMC and IPMC to vote upon. > > Please take a minute to vote on whether or not Apache SkyWalking should > graduate to a Top Level Project by responding with one of the following: > > [ ] +1 Apache SkyWalking should graduate. > [ ] +0 No opinion > [ ] -1 Apache SkyWalking should not graduate (please provide the reason) > > The VOTE is open for a minimum of 72 hours. As there has been previous > discussions on past versions of this proposal, I have not preluded the vote > with a DISCUSS email. If feedback arises the vote period will be extended in > good faith. > > regards, > Mick > > > [1] > https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E > [2] > https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking > [3] > https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E > [4] > https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E > > > > > Establish the Apache SkyWalking Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to application performance management and monitoring (APM). > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache SkyWalking Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache SkyWalking Project be and hereby is > responsible for the creation and maintenance of software related to > application performance management and monitoring (APM); and > be it further > > RESOLVED, that the office of "Vice President, Apache SkyWalking" be and > hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the Apac
Re: [VOTE] Release Apache ECharts (incubating) 4.2.1 (releasecandidate 3)
+1 binding
checked
1. incubating in name
2. asc checked
3. sha512 checked
4. compile passed
5. DISCLAIMER, LICENSE, NOTICE exist
One question, when I run
> shasum -c apache-echarts-4.2.1-rc.3-incubating-src.zip.sha512
Result is
> shasum: apache-echarts-4.2.1-rc.3-incubating-src.zip.sha512: no properly
> formatted SHA1 checksum lines found
But when I do manually checking, it is literally matched. Do you create this
sha512 file manually instead of using script? If so, could you consider to use
command like this?
> shasum -a 512 ${PRODUCT_NAME}-src.tgz > ${PRODUCT_NAME}-src.tgz.sha512
------
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108
-- Original --
From: "willem.jiang";
Date: Sat, Mar 16, 2019 10:37 AM
To: "general";
Subject: Re: [VOTE] Release Apache ECharts (incubating) 4.2.1
(releasecandidate 3)
+1 (binding)
I checked
Verified the signature and sha512
DISCLAIMER
LICENSE
NOTICE
Can build the key from source.
Willem Jiang
Twitter: willemjiang
Weibo: willem
On Wed, Mar 6, 2019 at 2:58 PM SHUANG SU wrote:
>
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.2.1 (release candidate 3).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/6f555bdb3bdc23ac9e260116738af779d4dff7b7e21f77c0a3369905@%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/54a63e2208330dd68c39bdcb5bd444301d0eb8580d433d1ac3fe4500@%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=1a2e990
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/RELEASE_NOTE.txt
>
> Some shell commands for validating the release:
>
> ```shell
> # Download the release:
> curl
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/apache-echarts-4.2.1-rc.3-incubating-src.zip
> -o apache-echarts-4.2.1-rc.3-incubating-src.zip
> unzip apache-echarts-4.2.1-rc.3-incubating-src.zip -d
> apache-echarts-4.2.1-rc.3-incubating-src > /dev/null
>
> # Rebuild the project (Node.js environment is required):
> cd "apache-echarts-4.2.1-rc.3-incubating-src" && npm install && cd ..
> node "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --release
> # (See help: `node
> "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --help`)
> ```
>
>
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.2.1 (release candidate 3)
> by "2019-03-09T07:42:38.040Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
>
> --
> Su Shuang (100pah)
> --
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept DataSketches into the Apache Incubator
+1 binding -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Paul King"; Date: Sat, Mar 16, 2019 06:47 PM To: "general"; Subject: Re: [VOTE] Accept DataSketches into the Apache Incubator +1 (binding) On Sat, Mar 16, 2019 at 4:30 PM Liang Chen wrote: > Hi > > +1(binding) > > Regards > Liang > > > Kenneth Knowles wrote > > Hi all, > > > > We've discussed the proposal for the DataSketches project in [1] and [2]. > > The > > proposal itself has been put on the wiki [3]. > > > > Per incubator rules [4] I'd like to call a vote to accept the new > > "DataSketches" project as a podling in the Apache Incubator. > > > > A vote for accepting a new Apache Incubator podling is a majority vote. > > Everyone is welcome to vote, only Incubator PMC member votes are binding. > > It would be helpful (but not required) if you could add a comment stating > > whether your vote is binding or non-binding. > > > > This vote will run for at least 72 hours (but I expect to keep it open > for > > longer). Please VOTE as follows: > > > > [ ] +1 Accept DataSketches into the Apache Incubator > > [ ] +0 Abstain > > [ ] -1 Do not accept DataSketches into the Apache Incubator because ... > > > > Thanks to everyone who contributed to the proposal and discussions. > > > > Kenn > > > > [1] > > > https://lists.apache.org/thread.html/329354bd6a463dab56c2539972cfa2d6c6da7c75900216d785db4e3b@%3Cgeneral.incubator.apache.org%3E > > [2] > > > https://lists.apache.org/thread.html/c9873cd4fcdc6367bcf530d8fa1ef09f3035f38e7c435e1a79a93885@%3Cgeneral.incubator.apache.org%3E > > [3] https://wiki.apache.org/incubator/DataSketchesProposal > > [4] https://incubator.apache.org/guides/proposal.html#the_vote > > > > > > -- > Sent from: http://apache-incubator-general.996316.n3.nabble.com/ > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] introduce "[DISCUSS]" threads for podling releases
> Amendment: > "A non-ASF release > * May or may not be staged on ASF infrastructure for the purposes of a > vote, but it is distributed via non-ASF infrastructure, AND > * Is either not linked from a podling's website, or is linked but clearly > marked as a non-ASF release.?? +1 (binding) from me. Make sense. ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "justin"; Date: Wed, Mar 13, 2019 04:41 PM To: "general"; Subject: Re: [VOTE] introduce "[DISCUSS]" threads for podling releases Hi, +1 (binding) > Amendment: > "A non-ASF release > * May or may not be staged on ASF infrastructure for the purposes of a > vote, but it is distributed via non-ASF infrastructure, AND > * Is either not linked from a podling's website, or is linked but clearly > marked as a non-ASF release.?? Sounds reasonable to me, thanks for updating it. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A smaller IPMC
+1 for #4 From I known, member of Incubator PMC is either already Apache Member or People already are/were active and helpful for other incubator project. Even they are not active today, removing them from IPMC could have negative effects when they want to be back in some day. Of course, we could consider to send mail to the IPMC members, who haven't subscribed the private ml, and ask them to do so. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "roman"; Date: Fri, Mar 8, 2019 07:39 AM To: "general"; Subject: Re: A smaller IPMC On Thu, Mar 7, 2019 at 3:33 PM Justin Mclean wrote: > > Hi, > > It??s been suggested that the IPMC is too large, what do other IPMC members > think might be a way to address this? Personally, I believe that "IPMC is too large" argument is only applicable to how quickly/easily consensus can be built. That's literally the only situation when the size of IPMC gets in the way (sometimes). Is anyone aware of any other situations where "IPMC is too large" argument is actually legit? At any rate, the rest of my feedback will be from that single perspective: > Please discuss and indicate +1 what you would think would help, you can vote > for more than one. > > Some suggestions: > 1. Ask all inactive IPMC if they want to continue being on the IPMC and see > who steps down. Being inactive they are probably not following this list so > we need to identify and send each one email them personally. > 2. There were some questions around merit raised, remove all IPMC members who > were not on the initial proposal and who were voted in. Those left on the > IPMC vote back in those who are currently active. > 3. Get rid of all IPMC members, and vote (with ASF members vote being binding > - not sure how else it could be done?) currently active ones back in. > 4. Do nothing as this is not actually a problem but instead address other > underlying issues. e.g. lack of mentor engagement. I would like to suggest a 5th alternative (again this is from the above's perspective): * Don't change anything, but for any situation that requires consensus building just be a tad more formal with how we close loops and track if we really get as many obstructionists as we thing that the size of the IPMC allows. If not -- we don't have a problem. > Also re point 2 do you think we should drop that ASF members can > automatically get IPMC membership and change it to requiring a vote by the > IPMC? It??s has always seem odd to me that this is the case. We??ve recently > voted more people in that we??ve had requests from ASF members. > > Any other sugestions? > > Options 2 and 3 may cause some issues around mentors, but if they were not > active then I guess it??s no big loss. > > And any suggestions on level of activity? Such as: > - Emailed the list in the last year. > - Reviewed at least one release in that time. > > It??s already been determined that some (about 15%) of the less than active > PMC members (out of the 100 odd that are not signed up to the IPMC private > list) do help out infrequently but that help is very useful. That may also > apply to other inactive IPMC members, so I would suggest the bar for what > consider active be kept low. I honestly don't see how all of these options of getting people in and out of IPMC can actually help with this consensus building thing. So yeah -- I'd say #5. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2]
Hi Strange thing. I noticed my +1 binding mail didn't arrive the ML, but I do send. Anyway, here is My +1 binding - asc checked - sha512 checked - incubating in name - maven compile passed - notice and license exist -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "吴晟 Sheng Wu"; Date: Thu, Mar 7, 2019 06:07 PM To: "Incubator General";"general"; Subject: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2] Hi Thanks for clear that, you have discussed this before. My +1 binding - asc checked - sha512 checked - incubating in name - maven compile passed - notice and license exist Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Minxuan Zhuang Date: Thu,Mar 7,2019 5:54 PM To: general Subject: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2] Hi, there is a discuss about the NOTICE file here: https://lists.apache.org/thread.html/9c26cb1750bc72c5cc3fd6ff1620721f4160ec20250c9328fb102e11@%3Cdev.dubbo.apache.org%3E , I think it's fine not to include the whole netty NOTICE file. On Thu, Mar 7, 2019 at 5:09 PM 吴晟 Sheng Wu wrote: > Hi > > > From my understanding, there is a possible issue in your source release > and bin. > > > I found a very simple NOTICE > > > -- > Apache Dubbo (incubating) > Copyright 2018-2019 The Apache Software Foundation > > > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > > > This product contains code form the Netty Project: > > > The Netty Project > = > Please visit the Netty web site for more information: > * http://netty.io/ > > > Copyright 2014 The Netty Project > > -- > > > But I checked the NOTICE in Netty project[1]. It includes more. > > > Could you clear why don't you include the whole netty's NOTICE file? > Do I miss something? > > > > > [1] https://github.com/netty/netty > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "hux...@apache.org"; > Date: Thu, Mar 7, 2019 03:53 PM > To: "Incubator General"; > > Subject: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2] > > > > +1 (non-binding) > > Still need one more binding vote here... > > On Mon, Mar 4, 2019 at 7:35 PM Minxuan Zhuang wrote: > > > > Hello Incubator Community, > > > > The Apache Dubbo community has voted on and approved a proposal to > release > > Apache Dubbo (Incubating) version 2.6.6. > > > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > > Apache Dubbo™ (incubating) is a high-performance, java based, open source > > RPC framework. Dubbo offers three key functionalities, which include > > interface based remote call, fault tolerance & load balancing, and > > automatic service registration & discovery. > > > > Dubbo community vote and result thread: > > > https://lists.apache.org/thread.html/c1cff6eb1ec9ce2877a38a16145cf41a6ab3f2a6989a0f276da2226a@%3Cdev.dubbo.apache.org%3E > > > > The release candidates (RC2): > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.6 > > > > Git tag for the release (RC2): > > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.6 > > > > Hash for the release tag: > > ba7f6f38c36675268ba64f21e97d02bda7a731dc > > > > Release Notes: > > https://github.com/apache/incubator-dubbo/blob/dubbo-2.6.6/CHANGES.md > > > > The artifacts have been signed with Key : DA2108479B0C1E71, which can be > > found in the keys file: > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > > > The vote will be open for at least 72 hours or until necessary number of > > votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > The Apache Dubbo (Incubating) Team > > > > -- > Best Regards！ > Huxing > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2]
Hi Justin I have read the discussion. Make sense to me. Thanks. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Justin Mclean Date: Thu,Mar 7,2019 7:00 PM To: general Subject: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2] Hi, > Could you clear why don't you include the whole netty's NOTICE file? > Do I miss something? Only parts of the NOTICE file that are relevant need to be included, some projects find analysis of that difficult and include the whole file to be on the safe side, some with only small parts of other projects included decide to only include the pieces they think are relevant. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2]
Hi Thanks for clear that, you have discussed this before. My +1 binding - asc checked - sha512 checked - incubating in name - maven compile passed - notice and license exist Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Minxuan Zhuang Date: Thu,Mar 7,2019 5:54 PM To: general Subject: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2] Hi, there is a discuss about the NOTICE file here: https://lists.apache.org/thread.html/9c26cb1750bc72c5cc3fd6ff1620721f4160ec20250c9328fb102e11@%3Cdev.dubbo.apache.org%3E , I think it's fine not to include the whole netty NOTICE file. On Thu, Mar 7, 2019 at 5:09 PM Sheng Wu wrote: > Hi > > > From my understanding, there is a possible issue in your source release > and bin. > > > I found a very simple NOTICE > > > -- > Apache Dubbo (incubating) > Copyright 2018-2019 The Apache Software Foundation > > > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > > > This product contains code form the Netty Project: > > > The Netty Project > = > Please visit the Netty web site for more information: > * http://netty.io/ > > > Copyright 2014 The Netty Project > > -- > > > But I checked the NOTICE in Netty project[1]. It includes more. > > > Could you clear why don't you include the whole netty's NOTICE file? > Do I miss something? > > > > > [1] https://github.com/netty/netty > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "hux...@apache.org"; > Date: Thu, Mar 7, 2019 03:53 PM > To: "Incubator General"; > > Subject: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2] > > > > +1 (non-binding) > > Still need one more binding vote here... > > On Mon, Mar 4, 2019 at 7:35 PM Minxuan Zhuang wrote: > > > > Hello Incubator Community, > > > > The Apache Dubbo community has voted on and approved a proposal to > release > > Apache Dubbo (Incubating) version 2.6.6. > > > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > > Apache Dubbo?6?4 (incubating) is a high-performance, java based, open source > > RPC framework. Dubbo offers three key functionalities, which include > > interface based remote call, fault tolerance & load balancing, and > > automatic service registration & discovery. > > > > Dubbo community vote and result thread: > > > https://lists.apache.org/thread.html/c1cff6eb1ec9ce2877a38a16145cf41a6ab3f2a6989a0f276da2226a@%3Cdev.dubbo.apache.org%3E > > > > The release candidates (RC2): > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.6 > > > > Git tag for the release (RC2): > > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.6 > > > > Hash for the release tag: > > ba7f6f38c36675268ba64f21e97d02bda7a731dc > > > > Release Notes: > > https://github.com/apache/incubator-dubbo/blob/dubbo-2.6.6/CHANGES.md > > > > The artifacts have been signed with Key : DA2108479B0C1E71, which can be > > found in the keys file: > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > > > The vote will be open for at least 72 hours or until necessary number of > > votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > The Apache Dubbo (Incubating) Team > > > > -- > Best Regards?? > Huxing > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2]
Hi From my understanding, there is a possible issue in your source release and bin. I found a very simple NOTICE -- Apache Dubbo (incubating) Copyright 2018-2019 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). This product contains code form the Netty Project: The Netty Project = Please visit the Netty web site for more information: * http://netty.io/ Copyright 2014 The Netty Project -- But I checked the NOTICE in Netty project[1]. It includes more. Could you clear why don't you include the whole netty's NOTICE file? Do I miss something? [1] https://github.com/netty/netty -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "hux...@apache.org"; Date: Thu, Mar 7, 2019 03:53 PM To: "Incubator General"; Subject: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.6 [RC2] +1 (non-binding) Still need one more binding vote here... On Mon, Mar 4, 2019 at 7:35 PM Minxuan Zhuang wrote: > > Hello Incubator Community, > > The Apache Dubbo community has voted on and approved a proposal to release > Apache Dubbo (Incubating) version 2.6.6. > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Apache Dubbo™ (incubating) is a high-performance, java based, open source > RPC framework. Dubbo offers three key functionalities, which include > interface based remote call, fault tolerance & load balancing, and > automatic service registration & discovery. > > Dubbo community vote and result thread: > https://lists.apache.org/thread.html/c1cff6eb1ec9ce2877a38a16145cf41a6ab3f2a6989a0f276da2226a@%3Cdev.dubbo.apache.org%3E > > The release candidates (RC2): > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.6 > > Git tag for the release (RC2): > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.6 > > Hash for the release tag: > ba7f6f38c36675268ba64f21e97d02bda7a731dc > > Release Notes: > https://github.com/apache/incubator-dubbo/blob/dubbo-2.6.6/CHANGES.md > > The artifacts have been signed with Key : DA2108479B0C1E71, which can be > found in the keys file: > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache Dubbo (Incubating) Team -- Best Regards！ Huxing - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
Hi SkyWalking received all feedbacks from our mentors and committers. 1. Luke Han(mentor) asked for `step down`. 2. All committers accept the `Invitation with condition`[1] As the result, the new initial PMC members are. * Haoyang Liu (??) * Hongtao Gao (??) * Ignasi Barrera * Mick Semb Wever * Sheng Wu () * Shinn Zhang () * Willem Ning Jiang () * Yongsheng Peng (??) * DongXue Si (??) * Jian Tan () * Kai Wang () * Sheng Wang () * Yang Bai () * Yao Wang () * Yuntao Li (??) * Zhang Kewei (??) * Can Li () [*] * Jiaqi Lin (??) [*] * Jinlin Fu (??) [*] * Lang Li () [*] * Wenbin Wang (??)[*] * Yixiong Cao (??)[*] [*] means, they are committers of SkyWalking, and have accepted the PMC invitation with condition. [1] https://lists.apache.org/thread.html/8a63bf68fc2f80c3bdb76414c57b8d79f517310cd5adb7904b23dca2@%3Cprivate.skywalking.apache.org%3E -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: " Sheng Wu"; Date: Wed, Mar 6, 2019 11:58 AM To: "general"; Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) Hi > My understanding, with discussions with Sheng, is that they presumed (2) was > possible and currently are following that approach. The confirmation by each > of the current Committers that they are happy to become PMC should be cc'd to > the private@skywalking ML. Yes. I will send the invitations with conditions to them. We have the supports from current PPMC to invite them in. > Sheng, can you also get confirmation from the mentors that they wish to be > part of the graduated PMC. You have that confirmation from me. I will ask for their confirmation. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "mck"; Date: Wed, Mar 6, 2019 11:34 AM To: "general"; Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) > > > That can only be done if the committers have agreed to becoming > > > members, > > > > That is correct, they need to be offered and they need to agree. > > > > > in which case you might as well add them to the PPMC before > > > graduation. > > > > Since PPMC is an artificial construct that isn't recognized by the > > foundation -- this part is moot. IOW, after these individuals agree > > they may as well be put on the resolution straight away. > > Yes, and LDAP will need to be adjusted in Whimsy after graduation. > > I think there are two choices: > 1) follow the normal route to add committers to the PPMC and copy the > final list to the proposal. > This means sending a NOTICE to the IPMC, etc. > > 2) Conditionally invite the committers (proposal could fail), and add > them to the proposal. > Don't add them to the PPMC (because there has been no IPMC NOTICE) > If the proposal succeeds, then Whimsy can be used to update LDAP membership. Thanks for the clarification. I was becoming quite confused and unhelpful as a mentor at one point there :-) My understanding, with discussions with Sheng, is that they presumed (2) was possible and currently are following that approach. The confirmation by each of the current Committers that they are happy to become PMC should be cc'd to the private@skywalking ML. Sheng, can you also get confirmation from the mentors that they wish to be part of the graduated PMC. You have that confirmation from me. cheers, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
Hi > My understanding, with discussions with Sheng, is that they presumed (2) was > possible and currently are following that approach. The confirmation by each > of the current Committers that they are happy to become PMC should be cc'd to > the private@skywalking ML. Yes. I will send the invitations with conditions to them. We have the supports from current PPMC to invite them in. > Sheng, can you also get confirmation from the mentors that they wish to be > part of the graduated PMC. You have that confirmation from me. I will ask for their confirmation. ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "mck"; Date: Wed, Mar 6, 2019 11:34 AM To: "general"; Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) > > > That can only be done if the committers have agreed to becoming > > > members, > > > > That is correct, they need to be offered and they need to agree. > > > > > in which case you might as well add them to the PPMC before > > > graduation. > > > > Since PPMC is an artificial construct that isn't recognized by the > > foundation -- this part is moot. IOW, after these individuals agree > > they may as well be put on the resolution straight away. > > Yes, and LDAP will need to be adjusted in Whimsy after graduation. > > I think there are two choices: > 1) follow the normal route to add committers to the PPMC and copy the > final list to the proposal. > This means sending a NOTICE to the IPMC, etc. > > 2) Conditionally invite the committers (proposal could fail), and add > them to the proposal. > Don't add them to the PPMC (because there has been no IPMC NOTICE) > If the proposal succeeds, then Whimsy can be used to update LDAP membership. Thanks for the clarification. I was becoming quite confused and unhelpful as a mentor at one point there :-) My understanding, with discussions with Sheng, is that they presumed (2) was possible and currently are following that approach. The confirmation by each of the current Committers that they are happy to become PMC should be cc'd to the private@skywalking ML. Sheng, can you also get confirmation from the mentors that they wish to be part of the graduated PMC. You have that confirmation from me. cheers, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
Dave > Just put them all on the graduation proposal (the IPMC and board??s approval > is equal to NOTICE) and (unless Infra does it) add them to the PMC in Whimsy > once you have graduated and infrastructure has moved the project LDAP. Make sense. Thanks for help. ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Dave Fisher"; Date: Wed, Mar 6, 2019 08:17 AM To: "general"; Cc: "roman"; Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) Hi - > On Mar 5, 2019, at 3:55 PM, Sheng Wu wrote: > > Hi Roman > > > In the discussion, I started about inviting committers to PMC when > graduation, shows the most PPMC members support this. We will wait another 2 > days, in case someone may say others. > > > In case PPMC agree, I want to ask the process steps of this. From committer > to PMC, I think each one should be invited and accept to be one. Then, when > should the invitation happens? > Do we need to send invitation and get confirmation before change the > graduation PMC list? > Or we could change the PMC list first, after our graduation proposal is > accepted, we send the invitation. Just put them all on the graduation proposal (the IPMC and board??s approval is equal to NOTICE) and (unless Infra does it) add them to the PMC in Whimsy once you have graduated and infrastructure has moved the project LDAP. Regards, Dave > > > Thanks. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > -- Original -- > From: roman > Date: Tue,Mar 5,2019 0:50 PM > To: general > Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) > > > > On Mon, Mar 4, 2019 at 12:42 PM Craig Russell wrote: >> >> >> >>> On Mar 4, 2019, at 3:12 AM, Mick Semb Wever wrote: >>>> The cookies in the moderator mails expire after a few days. >>> >>> This example was all done today. Numerous attempts have been made. >>>> It also means that the person is aware that the private@ list is >>>> something they need to follow. >>> >> As noted else-thread, there is an alternate method to subscribing to the >> email lists, by sending email to >> private-subscribe-EMAIL.ADDRESS=domain@skywalking.apache.org >> >>> Not getting any response at all is not an indication of whether the list >>> exist of not, unfortunately. >>> >>> Anyway?? to the thread's discussion: every PPMC received an invitation (per >>> Apache template) that requested subscription to both dev and private ML. >>> Reading the ASF guidelines here: >>> https://apache.org/foundation/governance/pmcs.html#communication ; I >>> interpret it as they SHOULD be subscribed rather than MUST, and I'm curious >>> as to whether how many of the TLPs are actually enforcing this among their >>> pmc, if any. It's an interesting discussion?? but I'm not entirely >>> convinced it's an accurate shortcoming to whether the podling is ready for >>> graduation or not. >> >> I think the question is not "Is SkyWalking ready to graduate" but "Is the >> proposed PMC list accurate". >> >> The PMC members are responsible for governing the TLP and as such need to be >> familiar with what is expected of them. Governance activities are conducted >> on the PPMC private list. If a PPMC member has not participated in any >> governance activities during incubation, it's unclear that they belong on >> the PMC. >> >> Reviewing the last several months of private@skywalking list, most of the >> discussion of new committers has had only four or five participants, who are >> clearly involved in governance of the project. > > From a peanut gallery: has the podling considered PMC == committers at > the graduation point? > The two lists look very close to each other. > > Thanks, > Roman. > > - > 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: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
Hi Roman In the discussion, I started about inviting committers to PMC when graduation, shows the most PPMC members support this. We will wait another 2 days, in case someone may say others. In case PPMC agree, I want to ask the process steps of this. From committer to PMC, I think each one should be invited and accept to be one. Then, when should the invitation happens? Do we need to send invitation and get confirmation before change the graduation PMC list? Or we could change the PMC list first, after our graduation proposal is accepted, we send the invitation. Thanks. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: roman Date: Tue,Mar 5,2019 0:50 PM To: general Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) On Mon, Mar 4, 2019 at 12:42 PM Craig Russell wrote: > > > > > On Mar 4, 2019, at 3:12 AM, Mick Semb Wever wrote: > >> The cookies in the moderator mails expire after a few days. > > > > This example was all done today. Numerous attempts have been made. > >> It also means that the person is aware that the private@ list is > >> something they need to follow. > > > As noted else-thread, there is an alternate method to subscribing to the > email lists, by sending email to > private-subscribe-EMAIL.ADDRESS=domain@skywalking.apache.org > > > Not getting any response at all is not an indication of whether the list > > exist of not, unfortunately. > > > > Anyway?? to the thread's discussion: every PPMC received an invitation (per > > Apache template) that requested subscription to both dev and private ML. > > Reading the ASF guidelines here: > > https://apache.org/foundation/governance/pmcs.html#communication ; I > > interpret it as they SHOULD be subscribed rather than MUST, and I'm curious > > as to whether how many of the TLPs are actually enforcing this among their > > pmc, if any. It's an interesting discussion?? but I'm not entirely > > convinced it's an accurate shortcoming to whether the podling is ready for > > graduation or not. > > I think the question is not "Is SkyWalking ready to graduate" but "Is the > proposed PMC list accurate". > > The PMC members are responsible for governing the TLP and as such need to be > familiar with what is expected of them. Governance activities are conducted > on the PPMC private list. If a PPMC member has not participated in any > governance activities during incubation, it's unclear that they belong on the > PMC. > > Reviewing the last several months of private@skywalking list, most of the > discussion of new committers has had only four or five participants, who are > clearly involved in governance of the project. From a peanut gallery: has the podling considered PMC == committers at the graduation point? The two lists look very close to each other. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
Hi Roman > From a peanut gallery: has the podling considered PMC == committers at > the graduation point? > The two lists look very close to each other. Good suggestion. I have started a discussion[1] in skywalking private. I will feedback the conclusion later. [1] https://lists.apache.org/thread.html/077eea102d7b678ae8dc22c46019fd88b0d7e1d839e523c3595071f9@%3Cprivate.skywalking.apache.org%3E ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "roman"; Date: Tue, Mar 5, 2019 12:49 PM To: "general"; Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) On Mon, Mar 4, 2019 at 12:42 PM Craig Russell wrote: > > > > > On Mar 4, 2019, at 3:12 AM, Mick Semb Wever wrote: > >> The cookies in the moderator mails expire after a few days. > > > > This example was all done today. Numerous attempts have been made. > >> It also means that the person is aware that the private@ list is > >> something they need to follow. > > > As noted else-thread, there is an alternate method to subscribing to the > email lists, by sending email to > private-subscribe-EMAIL.ADDRESS=domain@skywalking.apache.org > > > Not getting any response at all is not an indication of whether the list > > exist of not, unfortunately. > > > > Anyway?? to the thread's discussion: every PPMC received an invitation (per > > Apache template) that requested subscription to both dev and private ML. > > Reading the ASF guidelines here: > > https://apache.org/foundation/governance/pmcs.html#communication ; I > > interpret it as they SHOULD be subscribed rather than MUST, and I'm curious > > as to whether how many of the TLPs are actually enforcing this among their > > pmc, if any. It's an interesting discussion?? but I'm not entirely > > convinced it's an accurate shortcoming to whether the podling is ready for > > graduation or not. > > I think the question is not "Is SkyWalking ready to graduate" but "Is the > proposed PMC list accurate". > > The PMC members are responsible for governing the TLP and as such need to be > familiar with what is expected of them. Governance activities are conducted > on the PPMC private list. If a PPMC member has not participated in any > governance activities during incubation, it's unclear that they belong on the > PMC. > > Reviewing the last several months of private@skywalking list, most of the > discussion of new committers has had only four or five participants, who are > clearly involved in governance of the project. From a peanut gallery: has the podling considered PMC == committers at the graduation point? The two lists look very close to each other. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Re: Withdraw from Incubator or TLP status?
> Hi Sheng, Thanks. Yes, It does mean the original contributor team (or > company). I guess the questions were to understand all possible scenarios and > options before they actually move forward to donating. Yes. Even I don't want to see leave, no matter retire or original team leave. But that is an option. Please don't feel the ASF or Incubator would lock-in. They act as individuals, they could choose. ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Liu Ted"; Date: Tue, Mar 5, 2019 02:49 PM To: " Sheng Wu";"general"; Subject: ??Re: Withdraw from Incubator or TLP status? Hi Sheng, Thanks. Yes, It does mean the original contributor team (or company). I guess the questions were to understand all possible scenarios and options before they actually move forward to donating. Best regards, Ted Liu, ASF Member & Sponsor Ambassador 2019 ?? 3 ?? 5 ?? 14:36?? Sheng Wu ?? Hi > 1. In the incubation period, because of some special matters, is it also > entitled to voluntarily withdraw? I think it could be. But I hope this would not happen.Such as the community doesn't think the ASF fits their requirements(not common case), or retire from incubator because of leaking activities for a long time. > After becoming a TLP, can this TLP still have the right to voluntarily > withdraw? I assume you said TLP has right, it means the original contributor team(or company) has right. Correct me if I am wrong.During the incubator and graduate successfully, the PMC of TLP should be diversity,new PMC/committer should join the community because of it is open sourced, some may because trusting ASF.If your withdraw means close sources, even it just means open out of ASF,I doubt it will success from the PMC vote. Just my thought:) It is really rare to have this, except retirement, which happens sometimes, sadly. --Sheng WuApache SkyWalking, ShardingSphere, ZipkinTwitter, wusheng1108 -- Original --From: "Liu Ted";Date: Tue, Mar 5, 2019 02:12 PMTo: "Incubator General";Subject: Withdraw from Incubator or TLP status? Hi, A couple of questions are raised from a project who is interested in donating to ASF and entering the ASF Incubator: 1. In the incubation period, because of some special matters, is it also entitled to voluntarily withdraw? 2. After becoming a TLP, can this TLP still have the right to voluntarily withdraw? I searched thru the policies and guidances but cannot find the answers. Could anyone shed some light here? Best regards, Ted Liu, ASF Member & Sponsor Ambassador
Re: Withdraw from Incubator or TLP status?
Hi > 1. In the incubation period, because of some special matters, is it also > entitled to voluntarily withdraw? I think it could be. But I hope this would not happen. Such as the community doesn't think the ASF fits their requirements(not common case), or retire from incubator because of leaking activities for a long time. > After becoming a TLP, can this TLP still have the right to voluntarily > withdraw? I assume you said TLP has right, it means the original contributor team(or company) has right. Correct me if I am wrong. During the incubator and graduate successfully, the PMC of TLP should be diversity, new PMC/committer should join the community because of it is open sourced, some may because trusting ASF. If your withdraw means close sources, even it just means open out of ASF, I doubt it will success from the PMC vote. Just my thought:) It is really rare to have this, except retirement, which happens sometimes, sadly. ---------- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Liu Ted"; Date: Tue, Mar 5, 2019 02:12 PM To: "Incubator General"; Subject: Withdraw from Incubator or TLP status? Hi, A couple of questions are raised from a project who is interested in donating to ASF and entering the ASF Incubator: 1. In the incubation period, because of some special matters, is it also entitled to voluntarily withdraw? 2. After becoming a TLP, can this TLP still have the right to voluntarily withdraw? I searched thru the policies and guidances but cannot find the answers. Could anyone shed some light here? Best regards, Ted Liu, ASF Member & Sponsor Ambassador
??????????: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2))
Hi Sebb, John Look like both of them solved this issue by whimsy portal. Even still need mutiple tries. I don't know why, it occasionally work. Most are not. Anyway, thanks all for helps. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- -- ??: Kai Wang : 2019??3??5?? 11:00 ??: general : private , dev , sebb : ??: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) HI, AllThe problem of subscribing to the private list has been resolved, thanks Kai Wang ??2019??3??5?? 10:20?? Hi All: I used https://whimsy.apache.org/committers/subscribe to subscribe priv...@skywalking.apache.org failed, my gmail mailbox did not receive any mail IluckySi <1151262...@qq.com> ??2019??3??5?? 9:36?? Hi, All: I user https://whimsy.apache.org/committers/subscribe to subscribe priv...@skywalking.apache.org successfully~ Thank you~ -- -- ??: "John D. Ament"; : 2019??3??4??(??) 11:37 ??: "general"; : "dev"; "sebb"; : Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) Hi There is another option to try if the email subscription isn't working. You can access the whimsy portal (login using your ASF username/password) https://whimsy.apache.org/committers/subscribe and from here you can subscribe yourself to the private list if you're on the PPMC. At least in theory this should work. Feel free to reply if it doesn't. John On Mon, Mar 4, 2019 at 10:26 AM Sheng Wu wrote: > Hi Sebb > > > I just send mail in dev@skywalking, just realize you may be not there. > This is my reply. > > > > I just replied, and it worked fine; they are shown as being on the list. > > Have no clue why :(. Tried multiple times, always fail. But for some, > success. > > > Can you forward some example failure mails directly to me please? > > Sent two examples to your personal mail. > > > Who gets nothing? > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail > to private-subscr...@skywalking.apache.org. > But nothing comes back to him, I remember, there should be a confirm mail > to subscriber, right? > or moderators like me. I assume you don't get them too. > > > > > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: " Sheng Wu"; > Date: Mon, Mar 4, 2019 11:21 PM > To: "sebb"; > > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > > I just replied, and it worked fine; they are shown as being on the list. > > > Have no clue why :(. Tried multiple times, always fail. But for some, > success. > > > > Can you forward some example failure mails directly to me please? > > > Sent two examples to your personal mail. > > > > Who gets nothing? > > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail > to private-subscr...@skywalking.apache.org. > But nothing comes back to him, I remember, there should be a confirm mail > to subscriber, right? > or moderators like me. I assume you don't get them too. > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "sebb"; > Date: Mon, Mar 4, 2019 10:49 PM > To: "general"; > Cc: "dev"; > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > On Mon, 4 Mar 2019 at 12:11, Sheng Wu wrote: > > > > Hi Sebb > > > > > > I just sent confirm > `private-tc.1551700751.baimfhedlialniklhnho-Allen.Wang.123= > outlook@skywalking.apache.org` requested by Yao Wang again. > > Still fail, 6 times just today > > I just replied, and it worked fine; they are shown as being on the list. > > By the way, the email address such as the confirmation mail above > contains a cookie which means it can be sent by anyone (not just > moderators), so is best not shared on a public list. > > Can you forward some example failure mails directly to me please? > > > > > And for other two PPMC members, Dongxue(1151262...@qq.com) and Kai( > oracle...@g
Re: [VOTE] Release Apache NetBeans (incubating) parent 1
+1 binding Checked 1. name includes INCUBATING 2. sha512 exists and checked 3. asc exists and checked 4. source LICENSE, NOTICE and DISCLAIMER exist 5. pom with Apache header Also, I spend some time to guess out where[1] the KEY file is. :) I suggest you could put the link in vote ml, thanks. Hi Eric You have enough binding votes now. Sorry for haven't helped you on vote earlier. Have a good time. [1] https://www.apache.org/dist/incubator/netbeans/KEYS -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "mck"; Date: Fri, Mar 1, 2019 11:41 AM To: "general"; Subject: Re: [VOTE] Release Apache NetBeans (incubating) parent 1 > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason +1 Hi Eric, I'm a long time user of NetBeans, my involvement the past decade has been minimal, but I am very excited about seeing Apache NetBeans. I was keen to try out the little tool that the Zipkin podling community wrote to help verify the basics on staged releases: https://github.com/openzipkin-contrib/apache-release-verification Unfortunately the tool isn't 100% for use on different projects due to little things like folder layouts and naming. But in the process a few things were unclear to me are: - what's the git sha to this release? - what's the gpg key used to sign? I had to go hunt and figure them out. I have no idea if the Incubator wishes/enforces that this information is provided in the vote email? regards, Mick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
??????????: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2))
I re-tried several times. For foxmail web tool, I am using, only reply directly works. But the link always fail. But just for some ones Strange mail web tool. I am happy this resolved. Thanks for helping. Hope the other two could find out why... Tomorrow. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- -- ??: sebb : 2019??3??5?? 00:02 ??: general , dev : ??: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) On Mon, 4 Mar 2019 at 15:53, Sheng Wu wrote: > > > Maybe their mailers are also adding spurious characters to the To: address. > > > That is really hard to know. Not really, you just have to look at the headers of the mail. These may be available in their mail client in the Sent folder; GMail seems to show them. Otherwise, if they copy themselves (*) or someone else on the mail, they can look at the raw email to see what was sent. (*) This won't work with GMail as it hides duplicates - in this case the incoming mail. > > Dongxue and Kai > > > Could you try to type the private-subscr...@skywalking.apache.org manually, > and try again? Tomorrow. > Also, > You could try John's option, https://whimsy.apache.org/committers/subscribe . > Just not work to me. > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original ------ > From: "sebb"; > Date: Mon, Mar 4, 2019 11:47 PM > To: " Sheng Wu"; > Cc: "dev"; > "general"; > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > On Mon, 4 Mar 2019 at 15:26, Sheng Wu wrote: > > > > Hi Sebb > > > > I just send mail in dev@skywalking, just realize you may be not there. This > > is my reply. > > > > > I just replied, and it worked fine; they are shown as being on the list. > > > > Have no clue why :(. Tried multiple times, always fail. But for some, > > success. > > > > > Can you forward some example failure mails directly to me please? > > > > Sent two examples to your personal mail. > > Thanks > I replied already in the thread. > Your emailer is adding some extra text to the To: address which I > think is confusing ezmlm. > > > > Who gets nothing? > > > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail to > > private-subscr...@skywalking.apache.org. > > But nothing comes back to him, I remember, there should be a confirm mail > > to subscriber, right? > > or moderators like me. I assume you don't get them too. > > Yes, there should be a confirmation mail. > I have so far only seen mod requests for Allen.Wang > > Maybe their mailers are also adding spurious characters to the To: address. > > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > -- Original -- > > From: " Sheng Wu"; > > Date: Mon, Mar 4, 2019 11:21 PM > > To: "sebb"; > > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > > I just replied, and it worked fine; they are shown as being on the list. > > > > > > Have no clue why :(. Tried multiple times, always fail. But for some, > > success. > > > > > > > Can you forward some example failure mails directly to me please? > > > > > > Sent two examples to your personal mail. > > > > > > > Who gets nothing? > > > > > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail to > > private-subscr...@skywalking.apache.org. > > But nothing comes back to him, I remember, there should be a confirm mail > > to subscriber, right? > > or moderators like me. I assume you don't get them too. > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "sebb"; > > Date: Mon, Mar 4, 2019 10:49 PM > > To: "general"; > > Cc: "dev"; > > Subject: Re: : Problems subscribing to SkyWalk
Re: ????: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2))
Yes, I guess so. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "sebb"; Date: Mon, Mar 4, 2019 11:53 PM To: " Sheng Wu"; Cc: "John D. Ament"; "general"; Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) On Mon, 4 Mar 2019 at 15:45, Sheng Wu wrote: > > Hi John > > I just try on that page, don't find skywalking-private in `Subscribe` or > `UnSubscribe` lists. > I am already PPMC, no skywalking, zipkin, shardingsphere private, which I am > already there. > But I could find incubator-private, since I am IPMC. > > Do I miss anything? The page description only refers to PMC subscriptions in the context of private lists. I suspect it does not automatically handle PPMC (podling) subscriptions yet. > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > -- Original -- > From: "John D. Ament"; > Date: Mon, Mar 4, 2019 11:37 PM > To: "general"; > Cc: "dev"; "sebb"; > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > Hi > > There is another option to try if the email subscription isn't working. > You can access the whimsy portal (login using your ASF username/password) > https://whimsy.apache.org/committers/subscribe and from here you can > subscribe yourself to the private list if you're on the PPMC. > > At least in theory this should work. Feel free to reply if it doesn't. > > John > > On Mon, Mar 4, 2019 at 10:26 AM Sheng Wu wrote: > > > Hi Sebb > > > > > > I just send mail in dev@skywalking, just realize you may be not there. > > This is my reply. > > > > > > > I just replied, and it worked fine; they are shown as being on the list. > > > > Have no clue why :(. Tried multiple times, always fail. But for some, > > success. > > > > > Can you forward some example failure mails directly to me please? > > > > Sent two examples to your personal mail. > > > > > Who gets nothing? > > > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail > > to private-subscr...@skywalking.apache.org. > > But nothing comes back to him, I remember, there should be a confirm mail > > to subscriber, right? > > or moderators like me. I assume you don't get them too. > > > > > > > > > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: " Sheng Wu"; > > Date: Mon, Mar 4, 2019 11:21 PM > > To: "sebb"; > > > > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > > > > > > I just replied, and it worked fine; they are shown as being on the list. > > > > > > Have no clue why :(. Tried multiple times, always fail. But for some, > > success. > > > > > > > Can you forward some example failure mails directly to me please? > > > > > > Sent two examples to your personal mail. > > > > > > > Who gets nothing? > > > > > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail > > to private-subscr...@skywalking.apache.org. > > But nothing comes back to him, I remember, there should be a confirm mail > > to subscriber, right? > > or moderators like me. I assume you don't get them too. > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "sebb"; > > Date: Mon, Mar 4, 2019 10:49 PM > > To: "general"; > > Cc: "dev"; > > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > > > > > On Mon, 4 Mar 2019 at 12:11, Sheng Wu wrote: > > > > > > Hi Sebb > > > > > > > > > I just sent confirm &
Re: ????: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2))
> Maybe their mailers are also adding spurious characters to the To: address. That is really hard to know. Dongxue and Kai Could you try to type the private-subscr...@skywalking.apache.org manually, and try again? Tomorrow. Also, You could try John's option, https://whimsy.apache.org/committers/subscribe . Just not work to me. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "sebb"; Date: Mon, Mar 4, 2019 11:47 PM To: " Sheng Wu"; Cc: "dev"; "general"; Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) On Mon, 4 Mar 2019 at 15:26, Sheng Wu wrote: > > Hi Sebb > > I just send mail in dev@skywalking, just realize you may be not there. This > is my reply. > > > I just replied, and it worked fine; they are shown as being on the list. > > Have no clue why :(. Tried multiple times, always fail. But for some, success. > > > Can you forward some example failure mails directly to me please? > > Sent two examples to your personal mail. Thanks I replied already in the thread. Your emailer is adding some extra text to the To: address which I think is confusing ezmlm. > > Who gets nothing? > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail to > private-subscr...@skywalking.apache.org. > But nothing comes back to him, I remember, there should be a confirm mail to > subscriber, right? > or moderators like me. I assume you don't get them too. Yes, there should be a confirmation mail. I have so far only seen mod requests for Allen.Wang Maybe their mailers are also adding spurious characters to the To: address. > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > -- Original -- > From: " Sheng Wu"; > Date: Mon, Mar 4, 2019 11:21 PM > To: "sebb"; > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > I just replied, and it worked fine; they are shown as being on the list. > > > Have no clue why :(. Tried multiple times, always fail. But for some, success. > > > > Can you forward some example failure mails directly to me please? > > > Sent two examples to your personal mail. > > > > Who gets nothing? > > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail to > private-subscr...@skywalking.apache.org. > But nothing comes back to him, I remember, there should be a confirm mail to > subscriber, right? > or moderators like me. I assume you don't get them too. > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "sebb"; > Date: Mon, Mar 4, 2019 10:49 PM > To: "general"; > Cc: "dev"; > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > On Mon, 4 Mar 2019 at 12:11, Sheng Wu wrote: > > > > Hi Sebb > > > > > > I just sent confirm > > `private-tc.1551700751.baimfhedlialniklhnho-Allen.Wang.123=outlook@skywalking.apache.org` > > requested by Yao Wang again. > > Still fail, 6 times just today > > I just replied, and it worked fine; they are shown as being on the list. > > By the way, the email address such as the confirmation mail above > contains a cookie which means it can be sent by anyone (not just > moderators), so is best not shared on a public list. > > Can you forward some example failure mails directly to me please? > > > > > And for other two PPMC members, Dongxue(1151262...@qq.com) and > > Kai(oracle...@gmail.com) > > Get nothing. > > Who gets nothing? > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "wang yao"; > > Date: Mon, Mar 4, 2019 07:39 PM > > To: > > "general";"d...@skywalking.apache.org"; > > > > Subject: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate > > Apache SkyWalking (incubating) as a TLP(take2)) > > > > > > > > Ok, trying to subscribing again. > >
Re: ????: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2))
Hi John I just try on that page, don't find skywalking-private in `Subscribe` or `UnSubscribe` lists. I am already PPMC, no skywalking, zipkin, shardingsphere private, which I am already there. But I could find incubator-private, since I am IPMC. Do I miss anything? -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "John D. Ament"; Date: Mon, Mar 4, 2019 11:37 PM To: "general"; Cc: "dev"; "sebb"; Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) Hi There is another option to try if the email subscription isn't working. You can access the whimsy portal (login using your ASF username/password) https://whimsy.apache.org/committers/subscribe and from here you can subscribe yourself to the private list if you're on the PPMC. At least in theory this should work. Feel free to reply if it doesn't. John On Mon, Mar 4, 2019 at 10:26 AM Sheng Wu wrote: > Hi Sebb > > > I just send mail in dev@skywalking, just realize you may be not there. > This is my reply. > > > > I just replied, and it worked fine; they are shown as being on the list. > > Have no clue why :(. Tried multiple times, always fail. But for some, > success. > > > Can you forward some example failure mails directly to me please? > > Sent two examples to your personal mail. > > > Who gets nothing? > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail > to private-subscr...@skywalking.apache.org. > But nothing comes back to him, I remember, there should be a confirm mail > to subscriber, right? > or moderators like me. I assume you don't get them too. > > > > > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: " Sheng Wu"; > Date: Mon, Mar 4, 2019 11:21 PM > To: "sebb"; > > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > > I just replied, and it worked fine; they are shown as being on the list. > > > Have no clue why :(. Tried multiple times, always fail. But for some, > success. > > > > Can you forward some example failure mails directly to me please? > > > Sent two examples to your personal mail. > > > > Who gets nothing? > > > They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail > to private-subscr...@skywalking.apache.org. > But nothing comes back to him, I remember, there should be a confirm mail > to subscriber, right? > or moderators like me. I assume you don't get them too. > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "sebb"; > Date: Mon, Mar 4, 2019 10:49 PM > To: "general"; > Cc: "dev"; > Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] > Graduate Apache SkyWalking (incubating) as a TLP(take2)) > > > > On Mon, 4 Mar 2019 at 12:11, Sheng Wu wrote: > > > > Hi Sebb > > > > > > I just sent confirm > `private-tc.1551700751.baimfhedlialniklhnho-Allen.Wang.123= > outlook@skywalking.apache.org` requested by Yao Wang again. > > Still fail, 6 times just today > > I just replied, and it worked fine; they are shown as being on the list. > > By the way, the email address such as the confirmation mail above > contains a cookie which means it can be sent by anyone (not just > moderators), so is best not shared on a public list. > > Can you forward some example failure mails directly to me please? > > > > > And for other two PPMC members, Dongxue(1151262...@qq.com) and Kai( > oracle...@gmail.com) > > Get nothing. > > Who gets nothing? > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "wang yao"; > > Date: Mon, Mar 4, 2019 07:39 PM > > To: "general";"d...@skywalking.apache.org > "; > > > > Subject: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate > Apache SkyWalking (incubating) as a TLP(take2)) > > > > > > > > Ok, tryin
Re: ????: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2))
Hi Sebb I just send mail in dev@skywalking, just realize you may be not there. This is my reply. > I just replied, and it worked fine; they are shown as being on the list. Have no clue why :(. Tried multiple times, always fail. But for some, success. > Can you forward some example failure mails directly to me please? Sent two examples to your personal mail. > Who gets nothing? They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail to private-subscr...@skywalking.apache.org. But nothing comes back to him, I remember, there should be a confirm mail to subscriber, right? or moderators like me. I assume you don't get them too. ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: " Sheng Wu"; Date: Mon, Mar 4, 2019 11:21 PM To: "sebb"; Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) > I just replied, and it worked fine; they are shown as being on the list. Have no clue why :(. Tried multiple times, always fail. But for some, success. > Can you forward some example failure mails directly to me please? Sent two examples to your personal mail. > Who gets nothing? They, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com), sent mail to private-subscr...@skywalking.apache.org. But nothing comes back to him, I remember, there should be a confirm mail to subscriber, right? or moderators like me. I assume you don't get them too. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "sebb"; Date: Mon, Mar 4, 2019 10:49 PM To: "general"; Cc: "dev"; Subject: Re: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) On Mon, 4 Mar 2019 at 12:11, Sheng Wu wrote: > > Hi Sebb > > > I just sent confirm > `private-tc.1551700751.baimfhedlialniklhnho-Allen.Wang.123=outlook@skywalking.apache.org` > requested by Yao Wang again. > Still fail, 6 times just today I just replied, and it worked fine; they are shown as being on the list. By the way, the email address such as the confirmation mail above contains a cookie which means it can be sent by anyone (not just moderators), so is best not shared on a public list. Can you forward some example failure mails directly to me please? > > And for other two PPMC members, Dongxue(1151262...@qq.com) and > Kai(oracle...@gmail.com) > Get nothing. Who gets nothing? > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "wang yao"; > Date: Mon, Mar 4, 2019 07:39 PM > To: > "general";"d...@skywalking.apache.org"; > > Subject: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate > Apache SkyWalking (incubating) as a TLP(take2)) > > > > Ok, trying to subscribing again. > > ?? > Yao Wang > Apache SkyWalking Committer, DaoCloud Labs > Twitter, @tinyallen16 > > > ??: Sheng Wu > : 2019??3??4?? 19:26 > ??: Incubator General; general; dev > : Re: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache > SkyWalking (incubating) as a TLP(take2)) > > Hi Yao Wang > > > Could you try to subscribe priv...@skywalking.apache.org again. Let's see > whether we could pass this time. > > > Sebb > Appreciate very much. > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > -- Original -- > From: sebb > Date: Mon,Mar 4,2019 7:24 PM > To: general > Subject: Re: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate > Apache SkyWalking (incubating) as a TLP(take2)) > > > > On Mon, 4 Mar 2019 at 11:12, Mick Semb Wever wrote: > > > > > > > > > > The cookies in the moderator mails expire after a few days. > > > > > > > This example was all done today. Numerous attempts have been made. > > I see another person has subscribed to private, so it is possible to > subscribe, but it may depend on the email provider (they used gmail). > > I have added myself as a moderator to private@ > > Perhaps one of the people who failed earlier can try again? > > S. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org
Re: ????: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2))
Hi Sebb I just sent confirm `private-tc.1551700751.baimfhedlialniklhnho-Allen.Wang.123=outlook@skywalking.apache.org` requested by Yao Wang again. Still fail, 6 times just today. And for other two PPMC members, Dongxue(1151262...@qq.com) and Kai(oracle...@gmail.com) Get nothing. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "wang yao"; Date: Mon, Mar 4, 2019 07:39 PM To: "general";"d...@skywalking.apache.org"; Subject: : Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) Ok, trying to subscribing again. ?? Yao Wang Apache SkyWalking Committer, DaoCloud Labs Twitter, @tinyallen16 ____ ??: Sheng Wu : 2019??3??4?? 19:26 ??: Incubator General; general; dev : Re: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) Hi Yao Wang Could you try to subscribe priv...@skywalking.apache.org again. Let's see whether we could pass this time. Sebb Appreciate very much. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: sebb Date: Mon,Mar 4,2019 7:24 PM To: general Subject: Re: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) On Mon, 4 Mar 2019 at 11:12, Mick Semb Wever wrote: > > > > > > The cookies in the moderator mails expire after a few days. > > > > This example was all done today. Numerous attempts have been made. I see another person has subscribed to private, so it is possible to subscribe, but it may depend on the email provider (they used gmail). I have added myself as a moderator to private@ Perhaps one of the people who failed earlier can try again? S. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2))
Hi Yao Wang Could you try to subscribe priv...@skywalking.apache.org again. Let's see whether we could pass this time. Sebb Appreciate very much. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: sebb Date: Mon,Mar 4,2019 7:24 PM To: general Subject: Re: Problems subscribing to SkyWalking (Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)) On Mon, 4 Mar 2019 at 11:12, Mick Semb Wever wrote: > > > > > > The cookies in the moderator mails expire after a few days. > > > > This example was all done today. Numerous attempts have been made. I see another person has subscribed to private, so it is possible to subscribe, but it may depend on the email provider (they used gmail). I have added myself as a moderator to private@ Perhaps one of the people who failed earlier can try again? S. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache TVM into the incubator
+1 binding -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Mohammad Asif Siddiqui"; Date: Mon, Mar 4, 2019 02:13 PM To: "general"; Subject: Re: [VOTE] Accept Apache TVM into the incubator +1 (binding) Regards Asif On 2019/02/28 04:44:13, Markus Weimer wrote: > Hi everyone, > > we've discussed the proposal for the TVM project in [1]. The proposal itself > can > be found on the wiki [2]. > > According to the Incubator rules[3] I'd like to call a vote to accept the new > TVM project as a podling in the Apache Incubator. > > A vote for accepting a new Apache Incubator podling is a majority vote. > Everyone > is welcome to vote, only Incubator PMC member votes are binding. It would be > helpful (but not required) if you could add a comment stating whether your > vote > is binding or non-binding. > > This vote will run for at least 72 hours (but I expect to keep it open for > longer). Please VOTE as follows: > > [ ] +1 Accept TVM into the Apache Incubator > [ ] +0 Abstain > [ ] -1 Do not accept TVM into the Apache Incubator because ... > > Thank you for everyone who decided to join in in the past discussions! > > Markus > > [1]: > https://lists.apache.org/thread.html/e2b1fe9ca76422ec80b146a6b120091f2419e2f1c27d57080f39cf6f@%3Cgeneral.incubator.apache.org%3E > > [2]: https://wiki.apache.org/incubator/TVMProposal > > [3]: https://incubator.apache.org/guides/proposal.html#the_vote > > - > 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: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
Hi I do the following changes. 1. Committer and PPMC number updated, in CO40 2. Releases and bugs updated, in QU50 3. Contributor updated, in IN10 Thanks. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Justin Mclean"; Date: Mon, Mar 4, 2019 09:49 AM To: "general"; Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) Hi, Yes and thanks for pointing this out. > I have updated the document[1]. > Have any other changes been made since last time? Thanks., Justin >
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2)
Hi Justin > I assume the maturity documentation linked to in the discussion is slightly > out of date? [1] as it states "The community has elected 1 new committer and > 1 PPMC member during incubation, based on meritocracy.??. Yes and thanks for pointing this out. I have updated the document[1]. Now it states "YES. The community has elected 9 new committers, 3 of them also as PPMC members, during incubation, based on meritocracy." [1] https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "justin"; Date: Mon, Mar 4, 2019 04:56 AM To: "general"; Cc: "dev"; Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP(take2) Hi, >> SkyWalking is making more consensus decisions via the ML, including >> discussions and decisions on issue, test, release, new committer and >> branding issues. Since the last graduation discussion, the community has >> voted in 9 new committers, 3 of them also as PPMC members. I assume the maturity documentation linked to in the discussion is slightly out of date? [1] as it states "The community has elected 1 new committer and 1 PPMC member during incubation, based on meritocracy.??. >> RESOLVED, that the initial Apache SkyWalking PMC be and hereby is tasked >> with the creation of a set of bylaws intended to encourage open >> development and increased participation in the Apache SkyWalking >> Project; and be it further I suggest you remove this section, bylaws are not required. Thanks, Justin 1. https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking
Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP (take2)
Hi Sebb > Seems to me this is a bit too specific (and long) - can the example > target systems be left out? > e.g. it could perhaps be rephrased as: > related to application performance monitoring (aka a distributed tracing > system) Thanks for noticing this. Short version, we could say, SkyWalking is an open source application performance management/monitoring system, APM. We join the incubator as an APM based on distributed tracing system, with our journey in incubator and the community grows, we become more than that (huge exciting about this, the charms of being a part of ASF). We could support observing/monitoring service mesh ecosystem, such as Envoy(on developing) and Istio, others are trying to propose more, not formally yet. Anyway, APM is good, well known, and easy enough. ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "sebb"; Date: Sun, Mar 3, 2019 10:04 PM To: "general"; Cc: "dev"; Subject: Re: [DISCUSS] Graduate Apache SkyWalking (incubating) as a TLP (take2) On Sun, 3 Mar 2019 at 12:08, Mick Semb Wever wrote: > > > Apache SkyWalking entered incubation in December of 2017. The SkyWalking > community has learnt a lot about how to do things in The Apache Way. > > The first time graduation was raised for discussion, five months ago, the > IPMC thought SkyWalking was not yet ready because of issues around "Community > growth and in particular how merit is recognised". > > That pushback has been helpful, the community has become a more open and > engaged community. > > SkyWalking is making more consensus decisions via the ML, including > discussions and decisions on issue, test, release, new committer and branding > issues. Since the last graduation discussion, the community has voted in 9 > new committers, 3 of them also as PPMC members. > > SkyWalking has also helped Zipkin with podling learnings. And having a Zipkin > mentor involved in the recent discussions about the role and mechanisms of > the IPMC and the board, and any possible improvements that could be made to > the Incubator, it's witnessed and had a positive experience on the importance > of being involved in the broader Apache community. > > > After discussion in the podling's community on the dev ML > https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E > > ??and no objections, I'm raising the thread here for further discussion. > > Some stats and the proposed resolution is below, but let us know if there's > any other information we can provide to re-assure that the podling is ready > for graduation. > > > A few stats to help with the discussion: > > SkyWalking has delivered 8 releases so far in total, and appears now to have > a good cadence of successful releases. > > During the podling's time in the Apache Incubator there has been > 3200+ commits on development of the project, > 378 Issues tagged as question in GitHub created, 373 resolved, > 850+ Pull request created and resolved, and >97 different contributors. > > The dev ML has had 72 participants. > https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019 > > Also please check out Apache Maturity Model Assessment for SkyWalking > > https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking > > > regards, > Mick Semb Wever (SkyWalking mentor) > > == > > > Establish the Apache SkyWalking Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to application performance monitoring: especially for > microservice, Cloud Native and container-based architecture systems; > also known as a distributed tracing system. . Seems to me this is a bit too specific (and long) - can the example target systems be left out? e.g. it could perhaps be rephrased as: related to application performance monitoring (aka a distributed tracing system) > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache SkyWalking Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache SkyWalking Project be and hereby is > responsible for the creation and maintenance of software related to > application performance monitoring: especially for microservice, Cloud > Nat
Re: Incubator release votes
Hi Dave I offered my helps at your thread. Sorry you wait such long time. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "David P Grove"; Date: Tue, Feb 26, 2019 09:20 PM To: "general"; Subject: Re: Incubator release votes Craig Russell wrote on 02/25/2019 09:15:56 PM: > > To me, the biggest issue with incubating releases has been lack of > engagement by mentors for release voting. Many examples from history > have podlings begging for someone, anyone, to review a release that > has already received review in the podling dev list but has failed > to attract three +1 votes from Incubator PMC members. > > This is really sad, because in most of these cases the mentors have > not voted. And so it fell to the rest of the IPMC members to pay > attention enough to take time to vote. > Or in the case of the current OpenWhisk podling voting thread [1], our only mentor has already voted +1, but after a week we still need two more IPMC votes to be able to proceed. Please help --dave [1] https://lists.apache.org/thread.html/be62f7d373bef9a6729f62faf672ae39951159a0ed2ecc9e196cfb96@%3Cgeneral.incubator.apache.org%3E
Re: [VOTE] Release Apache OpenWhisk Composer (incubating) 0.10.0
Sorry, I only could provide +0. I checked 1. Download source tar. 2. LICENSE, NOTICE and DISCLAIMER exists. 3. acs checked. 4. sha512 exist but check failure. The reason I only provide +0 is, Bertrand Delacretaz shows the right sha512, but the file in release folder is not correct. If you could update the sha512 file, I think I could change my vote to +1 binding. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Dave Grove"; Date: Sat, Feb 23, 2019 00:38 AM To: "general"; Subject: Re: [VOTE] Release Apache OpenWhisk Composer (incubating) 0.10.0 A gentle reminder to IPMC members to please consider voting on this proposed podling release. OpenWhisk's only mentor (Bertrand) has voted +1, but we need two more binding votes to be able to proceed. thanks, --dave On 2019/02/18 22:14:47, "David P Grove" wrote: > > > The Apache OpenWhisk community has voted to release Apache OpenWhisk > Composer (incubating) version 0.10.0. The voting thread can be found here: > https://lists.apache.org/thread.html/801edac7a4d58436a5411fc1fbca523f24056195bdb149f9c2cdc2b8@%3Cdev.openwhisk.apache.org%3E > > We request that IPMC Members please review and vote on this incubator > release. > > This release comprises of source code distribution only. There is only one > module within this release number 0.10.0. The artifact were built from the > following Git commit IDs: > * openwhisk-composer: 96ccab9c5cfab6f98ce564166f63f22b244a47fd > > The source code artifact of openwhisk composer can be found at: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-composer-0.10.0-incubating-sources.tar.gz > > > > The SHA-512 checksum for the artifact of openwhisk composer is > openwhisk-composer-0.10.0-incubating-sources.tar.gz: > B81C71F4 7BF01403 28D5FC80 888FC76D 59A24AB1 59C0FADC 097B0909 BD76AEB9 > BFA309D3 > C2C443AE 2EC3DC50 0474B607 E9A20B73 8D993F51 4DEFEE5A 05C1AE00 > > which can can be found via: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-composer-0.10.0-incubating-sources.tar.gz.sha512 > > > > The signature of the artifact of openwhisk composer can be found via: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-composer-0.10.0-incubating-sources.tar.gz.asc > > > KEYS file is available here: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS > > Please vote on releasing this package as Apache OpenWhisk > 0.10.0-incubating: > OpenWhisk Composer > > The vote will be open for at least 72 hours. > [ ] +1 Release as Apache OpenWhisk 0.10.0-incubating: openwhisk composer > [ ] +0 no opinion > [ ] -1 Do not release and the reason > > Checklist for reference: > [ ] Download links are valid. > [ ] Checksums and PGP signatures are valid. > [ ] DISCLAIMER is included. > [ ] Source code artifacts have correct names matching the current release. > [ ] LICENSE and NOTICE files are correct for each OpenWhisk repository. > [ ] All files have license headers if necessary. > [ ] No compiled archives bundled in source archive. > > regards, > > --dave > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1
Hi Steve Here is my +1 binding. Sorry doesn't take part the vote earlier. Look like you have wait one week. You should be good to continue release process. Good luck. Checked 1. Compile passed. 2. sha256 and sha512 existed and checked. 3. NOTICE, DISCLAIMER, LICENSE exist and look like right. 4. sbt ratCheck passed. 5. incubating in name. 6. asc sign checked. And I just sign and publish your KEY. For sha256 and sha512, I think just keeping sha512 is good enough, but truely sha256 is not asked to remove for now. If you need my help on vote, you could send mail to me(wusheng@a.o). -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "Steve Lawrence"; Date: Tue, Feb 26, 2019 08:09 PM To: "general";"Christofer Dutz"; Subject: Re: [VOTE] Release Apache Daffodil (incubating) 2.3.0-rc1 Thanks Chris. The Daffodil devs agree that the issues you found are not blockers and will be fixed for the next release. As a reminder to the IPMC, Daffodil really only has 1 active mentor so will likely need another vote from a non-mentor for the VOTE to pass. We would greatly appreciate it if the IPMC could take a look. Thanks, - Steve On 2/26/19 2:26 AM, Christofer Dutz wrote: > Changing my vote to +1 (binding) > > I found the reason for the failing tests on Mac and Windows ... the root > cause was the different locale and the way numeric values are encoded. > In Germany we separate the 1000s with "." and the decimal part with "," and > in the US it's the opposite way. If I enforce the locale en_US and increase > the memory, then all except one test succeed. > The one failing test is still related to this locale thing, so I guess this > is something that has to be documented and should not qualify for blocking > this release. > > So I would request to add suggested settings of "SBT_OPTS" to the readme for > further releases as with the current documentation it's impossible to build. > > Haven't tested the binary distributions though ... however with some help of > the community I have successfully updated my PLC4X dynamic drivers that > greatly utilize Daffodil to the maven artifacts of 2.3.0 > > Chris > > > Am 23.02.19, 17:11 schrieb "Steve Lawrence" : > > That's for all the response from everyone so far. We'll make sure to fix > the KEYS issue for the next release. DAFFODIL-2070 [1] was created to > track that issue, and we plan to fix it in the next release. Other > comments inline. > > On 2/22/19 3:45 PM, Christofer Dutz wrote: > > Hi all, > > > > I have started verifying this release ... however this is the first > time I am validating a project I'm not directly involved in. > > So I found some things that are different than with the other projects > (Not sure if this is bad or good though) > > > > So here goes: > > 1) No KEYS file (Think this has been reported) > > Ticket mentioned above, we plan to fix this for the next release. > > > 2) No README and RELEASE_NOTES in the RC directory > > We have a REAMDE.md in the root directory of the source release and the > convenience binaries. And we've been maintaining releases notes on our > website. For example, the release for this are at > https://daffodil.apache.org/releases/2.3.0/ > > Looking at a few other random incubator release candidates, I don't see > a README or RELEASE_NOTES in their directories, so maybe this isn't > required, and the readme in the source and release notes on the webpage > is sufficient? > > > 3) There are sha256 and 512 files ... is it OK to have the sha256 ones? > I remember us having to remove less "save" signature files > > We've recently removed md5 and sha1 for this reason. I haven't yet heard > the need to remove sha256, but I'm fine doing that if that's the right > thing to do. > > > 4) Is there a reason, why the "RPM" file is "2.3.0.incubating" instead > of "2.3.0-incubating" (dot instead of a dash). > > The tool we use to build RPMs is very particular about versios and > filenames RPM standards. Those standards require the dot instead of the > dash. It also requires the -1 at the end as well. > > > 5) It was impossible to import the GPG Key from pgp.mit.edu or any of > my known key servers (did it manually) > > I've had a lot of troubles getting keys from pgp.mit.edu, always seems > to be down for me. I have uploaded it in the past for previous rele
Re: Dubbo's documentation on preparing for an Apache release
Thanks for sharing. This document could help a lot. I think Zipkin learn from it. SkyWalking has similar one. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Huxing Zhang Date: Tue,Feb 26,2019 5:53 PM To: Incubator General Subject: Re: Dubbo's documentation on preparing for an Apache release Hi community, Recently the Dubbo project has summarized a document[1] of how to prepare for an Apache release. Given the recent discussion happening on the list, I think it might be helpful for other projects to get some knowledge about how to prepare for an Apache release. Until now the Dubbo projects has made 8 releases, by 5 different release managers. The documentation did a lot of help. As projects may be different so the documentation may not be applied to all the projects. Please correct me if anything is wrong in the documentation. [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html -- Best Regards?? Huxing - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Zipkin Brave (incubating) for Apache Karafversion 0.1.2
+1 binding Checked 1. LICENSE, DISCLAIMER, NOTICE exist. 2. Apache rat check passed. 3. asc checked. 4. Maven compile passed. 5. No wrapper jar (recheck because of last release failure) 6. sha512 exists and checked. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "willem.jiang"; Date: Sun, Feb 24, 2019 11:31 AM To: "general"; Subject: Re: [VOTE] Release Apache Zipkin Brave (incubating) for Apache Karafversion 0.1.2 Hi, Just forwarding my +1 bind from dev list. Willem Jiang Twitter: willemjiang Weibo: willem On Sat, Feb 23, 2019 at 8:54 AM Adrian Cole wrote: > > Hello All, > > This is a call for vote to release Apache Zipkin Brave (incubating) > for Apache Karaf version 0.1.2 > > The Apache Zipkin community has voted on and approved a proposal to > release Apache Zipkin Brave (incubating) for Apache Karaf version > 0.1.2. > > We now kindly request the Incubator PMC members review and vote on > this incubator release. > > Apache Zipkin Brave (incubating) for Apache Karaf sets up tracing > components such that tools built Karaf needn't configure these > explicitly. > > Zipkin community vote and result thread: > https://lists.apache.org/thread.html/32baf4b4b65644dd1dd8e2bf0cb360c94f8f939d61c5444b8f4ef45b@%3Cdev.zipkin.apache.org%3E > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/zipkin/brave-karaf/0.1.2/ > > Git tag for the release: > https://github.com/apache/incubator-zipkin-brave-karaf/tree/v0.1.2 > > Hash for the release tag: > 3cf4ac6577eb0d4775d20f24814e7a0852fa1635 > > Release Notes: > https://github.com/apache/incubator-zipkin-brave-karaf/releases/tag/v0.1.2 > > The artifacts have been signed with Key : BB67A050, which can be found > in the keys file: > https://dist.apache.org/repos/dist/dev/incubator/zipkin/KEYS > > Verification Hints: > For your convenience, the below includes detailed how-to on verifying > a source release. Please note that this document is a work-in-progress > https://cwiki.apache.org/confluence/display/ZIPKIN/Verifying+a+Source+Release > > The vote will be open for at least 72 hours or until necessary number > of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache Zipkin (Incubating) Team > > - > 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: Fwd: [DISCUSS] can we use weex.io as the short domainnamefortheapache project
Thanks for the feedback. Sadly, It looks like really get the network issue. In my mind, hosting `weex.io` site out ASF is not right. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: ""; Date: Mon, Feb 18, 2019 09:02 PM To: "general"; Subject: Re: Fwd: [DISCUSS] can we use weex.io as the short domainnamefortheapache project Actually, with the tool provided by https://ping.chinaz.com/, there is huge difference of network speed between https://weex.apache.org/ and https://weex.io/ , though their content is totally the same. The average speed for https://weex.io/ is 65ms from 142 different IP address, while it is 271ms for https://weex.apache.org/ But if using another domain is against the rule of Apache, I think I can live with it and redirect https://weex.io/ to https://weex.apache.org/ Best Regards, YorkShen ???? Sheng Wu ??2019??2??18?? 5:16?? > weex.apache.org is fast too from my network environment now. The Chinese network status is strange, we all know. :) Right? > We had received several complaint years ago from Chinese users that weex.apache.org is slow, so we launched weex-project.io with the same content of weex.apache.org. If this is against rules, I think we can make it redirect to weex.apache.org, not sure whether we would receive complaint again. In my mind, redirect is better. You could try, and listen to the community. If really need some another, I suggest you to talk with Brand Management Committee.[1] Maybe publish an website, but don't use `weex` in name and say clearly, this is not Apache Weex official documents, just documents maintained by volunteers. This is not so cool, I know. [1] https://www.apache.org/foundation/marks/#whoweare -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: ""; Date: Mon, Feb 18, 2019 05:07 PM To: "general"; Subject: Re: Fwd: [DISCUSS] can we use weex.io as the short domain namefortheapache project weex.apache.org is fast too from my network environment now. We had received several complaint years ago from Chinese users that weex.apache.org is slow, so we launched weex-project.io with the same content of weex.apache.org. If this is against rules, I think we can make it redirect to weex.apache.org, not sure whether we would receive complaint again. Best Regards, YorkShen Sheng Wu ??2019??2??18?? 4:56?? > Hi > > > I don't know why it is slow, I just tried, very quickly. > > > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: ""; > Date: Mon, Feb 18, 2019 04:33 PM > To: "general"; > > Subject: Re: Fwd: [DISCUSS] can we use weex.io as the short domain name > fortheapache project > > > > > > > 3. I don't think ASF websites are facing GFW issue. > > ASF website is quite slow when accessing from China, I am not sure whether > this is a GFW issue or simply the server is on another continent without a > CDN. > > We received complains about weex.apache.org from China mainland years ago, > so we deploy website to weex-project.io for fast access in China, as many > of our users are from China and there is CDN for weex-project.io . If > there is a solution for this issue, please let me know. > > Best Regards, > YorkShen > > > > > Sheng Wu ??2019??2??18?? 3:52?? > > > Hi YorkShen > > > > > > From my understanding, weex project, including branding and logo, should > > be donated to ASF(at least before Graduation). > > The basic policy is, weex.apache.org should be the only official website > > for the project. > > And project's website should be hosted in Apache Infra. > > > > > > If you have others, let's say weex.io and weex-project.io, and run by > > your committers team, I suggest > > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user > > convenience. > > 2. For the Chinese documents, if your committers/contributors maintain > > this, put it in `http://weex.apache.org/cn/`makes > <http://weex.apache.org/cn/makes> > > <http://weex.apache.org/cn/makes> sense. > > 3. I don't think ASF websites are facing GFW issue. > > > > > > If you want to publish another domain/website for ecosystem, you should > > avoid
Re: Fwd: [DISCUSS] can we use weex.io as the short domain namefortheapache project
> weex.apache.org is fast too from my network environment now. The Chinese network status is strange, we all know. :) Right? > We had received several complaint years ago from Chinese users that weex.apache.org is slow, so we launched weex-project.io with the same content of weex.apache.org. If this is against rules, I think we can make it redirect to weex.apache.org, not sure whether we would receive complaint again. In my mind, redirect is better. You could try, and listen to the community. If really need some another, I suggest you to talk with Brand Management Committee.[1] Maybe publish an website, but don't use `weex` in name and say clearly, this is not Apache Weex official documents, just documents maintained by volunteers. This is not so cool, I know. [1] https://www.apache.org/foundation/marks/#whoweare -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "申远"; Date: Mon, Feb 18, 2019 05:07 PM To: "general"; Subject: Re: Fwd: [DISCUSS] can we use weex.io as the short domain namefortheapache project weex.apache.org is fast too from my network environment now. We had received several complaint years ago from Chinese users that weex.apache.org is slow, so we launched weex-project.io with the same content of weex.apache.org. If this is against rules, I think we can make it redirect to weex.apache.org, not sure whether we would receive complaint again. Best Regards, YorkShen 申远 吴晟 Sheng Wu 于2019年2月18日周一 下午4:56写道： > Hi > > > I don't know why it is slow, I just tried, very quickly. > > > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "申远"; > Date: Mon, Feb 18, 2019 04:33 PM > To: "general"; > > Subject: Re: Fwd: [DISCUSS] can we use weex.io as the short domain name > fortheapache project > > > > > > > 3. I don't think ASF websites are facing GFW issue. > > ASF website is quite slow when accessing from China, I am not sure whether > this is a GFW issue or simply the server is on another continent without a > CDN. > > We received complains about weex.apache.org from China mainland years ago, > so we deploy website to weex-project.io for fast access in China, as many > of our users are from China and there is CDN for weex-project.io . If > there is a solution for this issue, please let me know. > > Best Regards, > YorkShen > > 申远 > > > 吴晟 Sheng Wu 于2019年2月18日周一 下午3:52写道： > > > Hi YorkShen > > > > > > From my understanding, weex project, including branding and logo, should > > be donated to ASF(at least before Graduation). > > The basic policy is, weex.apache.org should be the only official website > > for the project. > > And project's website should be hosted in Apache Infra. > > > > > > If you have others, let's say weex.io and weex-project.io, and run by > > your committers team, I suggest > > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user > > convenience. > > 2. For the Chinese documents, if your committers/contributors maintain > > this, put it in `http://weex.apache.org/cn/`makes > <http://weex.apache.org/cn/makes> > > <http://weex.apache.org/cn/makes> sense. > > 3. I don't think ASF websites are facing GFW issue. > > > > > > If you want to publish another domain/website for ecosystem, you should > > avoid using `weex-`, `weex.`, to avoid branding issues. > > And I suggest you don't do that, because the community will be split. > > > > > > The following are just suggestions from my experiences. > > Blog(cn/en) post are popular in many Apache project, which could be > easily > > supported by our CI hook in GitHub, also have post control and review. > > If you want helps from this, ping me or `d...@skywalking.apache.org`, we > > have done something. > > > > > > For Q robots, if you are running that on GitHub issue, a Robot account > > with project subscription should be good enough. > > If you want to do that at Website, I think it will be more complex. > > > > > > -- > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > -- Original -- > > From: "申远"; > > Date: Mon, Feb 18, 2019 03:07 PM > > To: "general"; > > > > Subject: Fwd: [DISCUSS] can we use weex.io as
Re: Fwd: [DISCUSS] can we use weex.io as the short domain name fortheapache project
Hi I don't know why it is slow, I just tried, very quickly. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "申远"; Date: Mon, Feb 18, 2019 04:33 PM To: "general"; Subject: Re: Fwd: [DISCUSS] can we use weex.io as the short domain name fortheapache project > > 3. I don't think ASF websites are facing GFW issue. ASF website is quite slow when accessing from China, I am not sure whether this is a GFW issue or simply the server is on another continent without a CDN. We received complains about weex.apache.org from China mainland years ago, so we deploy website to weex-project.io for fast access in China, as many of our users are from China and there is CDN for weex-project.io . If there is a solution for this issue, please let me know. Best Regards, YorkShen 申远 吴晟 Sheng Wu 于2019年2月18日周一 下午3:52写道： > Hi YorkShen > > > From my understanding, weex project, including branding and logo, should > be donated to ASF(at least before Graduation). > The basic policy is, weex.apache.org should be the only official website > for the project. > And project's website should be hosted in Apache Infra. > > > If you have others, let's say weex.io and weex-project.io, and run by > your committers team, I suggest > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user > convenience. > 2. For the Chinese documents, if your committers/contributors maintain > this, put it in `http://weex.apache.org/cn/`makes > <http://weex.apache.org/cn/makes> sense. > 3. I don't think ASF websites are facing GFW issue. > > > If you want to publish another domain/website for ecosystem, you should > avoid using `weex-`, `weex.`, to avoid branding issues. > And I suggest you don't do that, because the community will be split. > > > The following are just suggestions from my experiences. > Blog(cn/en) post are popular in many Apache project, which could be easily > supported by our CI hook in GitHub, also have post control and review. > If you want helps from this, ping me or `d...@skywalking.apache.org`, we > have done something. > > > For Q robots, if you are running that on GitHub issue, a Robot account > with project subscription should be good enough. > If you want to do that at Website, I think it will be more complex. > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > > > > > > -- Original -- > From: "申远"; > Date: Mon, Feb 18, 2019 03:07 PM > To: "general"; > > Subject: Fwd: [DISCUSS] can we use weex.io as the short domain name for > theapache project > > > > Hi, there > > I am a PPMC member of incubator-weex, there is some confusion about > third-party domain and it seems like difficult to resolve in dev@ mailing > list, maybe someone here could give a hand to solve the problem of domains. > > 1.I 'd like to know if there is a formal rule that projects should use > xxx.apache.org instead of xxx.io, which is shorter and easier to remember. > 2. we have another domain weex-project.io for fast access of Çhinese > Developers as GFW have some confluence on https://weex.apache.org/cn/. Is > this against rules for apache project. > > Best Regards, > YorkShen > > 申远 > > > -- Forwarded message - > From: Dan > Date: 2019年2月15日周五 下午2:39 > Subject: [DISCUSS] can we use weex.io as the short domain name for the > apache project > To: > > > Hi, Myrle/Willem, > > Currently, we have a domain name of weex.io and want to use it to replace > the previous weex-project.io domain name for the following reasons: > > 1. The domain name is shorter and easier to remember. > 2. Apache's website has slower access to the developer in China, so there > is a mirror website weex-project.io for Chinese developer. > 3. We expect to support https on this website and support some of our own > server functions, such as Q robots, article blog posts, etc. > > I would like to ask if apache has any restrictions on this third-party > domain name, and look forward to hearing from you. > > Thanks, > Dan
Re: Fwd: [DISCUSS] can we use weex.io as the short domain name for theapache project
Hi YorkShen From my understanding, weex project, including branding and logo, should be donated to ASF(at least before Graduation). The basic policy is, weex.apache.org should be the only official website for the project. And project's website should be hosted in Apache Infra. If you have others, let's say weex.io and weex-project.io, and run by your committers team, I suggest 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user convenience. 2. For the Chinese documents, if your committers/contributors maintain this, put it in `http://weex.apache.org/cn/`makes sense. 3. I don't think ASF websites are facing GFW issue. If you want to publish another domain/website for ecosystem, you should avoid using `weex-`, `weex.`, to avoid branding issues. And I suggest you don't do that, because the community will be split. The following are just suggestions from my experiences. Blog(cn/en) post are popular in many Apache project, which could be easily supported by our CI hook in GitHub, also have post control and review. If you want helps from this, ping me or `d...@skywalking.apache.org`, we have done something. For Q robots, if you are running that on GitHub issue, a Robot account with project subscription should be good enough. If you want to do that at Website, I think it will be more complex. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "申远"; Date: Mon, Feb 18, 2019 03:07 PM To: "general"; Subject: Fwd: [DISCUSS] can we use weex.io as the short domain name for theapache project Hi, there I am a PPMC member of incubator-weex, there is some confusion about third-party domain and it seems like difficult to resolve in dev@ mailing list, maybe someone here could give a hand to solve the problem of domains. 1.I 'd like to know if there is a formal rule that projects should use xxx.apache.org instead of xxx.io, which is shorter and easier to remember. 2. we have another domain weex-project.io for fast access of Çhinese Developers as GFW have some confluence on https://weex.apache.org/cn/. Is this against rules for apache project. Best Regards, YorkShen 申远 -- Forwarded message - From: Dan Date: 2019年2月15日周五 下午2:39 Subject: [DISCUSS] can we use weex.io as the short domain name for the apache project To: Hi, Myrle/Willem, Currently, we have a domain name of weex.io and want to use it to replace the previous weex-project.io domain name for the following reasons: 1. The domain name is shorter and easier to remember. 2. Apache's website has slower access to the developer in China, so there is a mirror website weex-project.io for Chinese developer. 3. We expect to support https on this website and support some of our own server functions, such as Q robots, article blog posts, etc. I would like to ask if apache has any restrictions on this third-party domain name, and look forward to hearing from you. Thanks, Dan
Re: Podlings not following ASF release policy
If we don't want the unapproved release happens in this case, I think we should asked them to give an exact date of joining the incubator. The new incubator project community should know, after the proposal accepted and with the date deadline, we don't allow to do unapproved release. And we keep this in our proposal guide document and template, also ask the new proposal make clear in their proposal. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Justin Mclean Date: Sat,Feb 9,2019 9:16 AM To: general Subject: Re: Podlings not following ASF release policy Hi, One of the issues I??ve seen is that project continues to make releases in GitHub after being accepted into the incubator, in some case is this because the repo hasn??t been moved over yet, in other cases it??s because they believe that the code base is not Apache ready. What should we do in this situations? From what I seen it usually just delays transfer of the repo and encourages unapproved releases. I would would push for mentors speeding up that transfer rather than allowing unapproved releases. What do others think? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Unapproved Sharding Sphere releases
I support move than copy too. Move is better, not just for keeping star, fork and watch. These are also important too. The more important is, GitHub provides repo address auto redirect. If the user or article links to the old repo, it will forward to the new one(Apache one) automatically. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Chris Lambertus Date: Sat,Feb 9,2019 4:34 AM To: general Cc: dev Subject: Re: Unapproved Sharding Sphere releases > On Feb 7, 2019, at 1:52 PM, Dave Fisher wrote: > > > >> On Feb 7, 2019, at 1:44 PM, Craig Russell wrote: [snip] >> >> Larger discussion: Is there a reason for projects coming into incubation to >> have the old repository moved (i.e. renamed) instead of being copied? I >> cannot think of a good use case for moving versus copying. Seems like any >> project that had releases and a community outside Apache would want to copy, >> not move. > > If the project is moved then all of the thousands of forks and stars are > still associated with the original project. If copied then all of these will > be associated with the now abandoned repository and most of those will never > come along with the moving project. > > For the Chinese projects this can mean losing thousands of users and sometime > contributors to the project. > > So, I am a MOVE and not COPY. > > ShardingSphere has 6,633 stars and 2,363 forks plus 842 watches. > >> >> Smaller discussion: Should the JIRA have been written to request >> copying/forking the project? Or is this something that is supposed to be >> self-serve. I could not find a definitive answer to this. > > Ask Infra. ASICT they move by default. We endeavor to perform move operations wherever technically possible for the exact reason of retaining the stars and other metadata associated with the github project. It adds a few extra steps for us, but the projects always appreciate having that data retained. If we did a ??copy?? then there would be two extant repos which would cause no end of confusion, especially for people with forks and watches on the original repo. -Chris ASF Infra
Re: Unapproved Sharding Sphere releases
Hi By following the Apache policy, besides the suggestions I gave and done. Just a moment ago, I deleted the recent two unapproved releases, 3.1.0.m1 and 3.1.0 at GitHub release page[1]. In further, I will help the shardingsphere community to follow the policy. [1] https://github.com/apache/incubator-shardingsphere/releases Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Sheng Wu Date: Wed,Jan 30,2019 5:54 PM To: dev , dev Cc: Justin Mclean , jmclean Subject: Re: Unapproved Sharding Sphere releases Hi I think I agree the Justin's points. No matter the release happens in Apache org repo or not, it still happened after you asked and accepted by Incubator. So, it is not encouraged and not following the Apache way. I propose these adjustments 1. Add statement in GitHub release versions. Saying these are not Apache release. 2. Add statement in you website home, document and download pages, saying all available releases are not Apache releases 3. After the first approved release, you only says before this version(4.0.0 maybe) are not Apachre releases. 4. Add statement in GitHub project readme.md for the same thing. Especially for document pages, this needs to be tagged in clear way. I know, those releases in maven central repo are hard to release, and not good for the existing community. So, I hope my proposals are good enough. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: zhangli...@apache.org Date: Wed,Jan 30,2019 0:03 PM To: dev Cc: Justin Mclean , jmclean Subject: Re: Unapproved Sharding Sphere releases Hello Justin, Thanks for your advice. This is a legacy release, which we have discussed on the dev mail list[1] before. This release is done before the transfer to ASF repo and package rename. We are now preparing apache release which begins with new version(4.0.0). We will not release non-Apache version any more in the future. Any suggestion to identify versions like these kind of releases? [1] https://lists.apache.org/thread.html/a3bba7e53bfed6d18924b592ecf0533aebc8d307f8c7e399a7fec2cf@%3Cdev.shardingsphere.apache.org%3E -- Liang Zhang (John) Apache ShardingSphere & Dubbo Justin Mclean ??2019??1??30?? 6:23?? > Hi, > > Looking at [1] there seems to have been releases made after you have > entered incubation. All releases must be approved by the PPMC and the IPMC > (usually by voting). Can you please remove these releases and include in > your upcoming incubator report what you will do to stop this happening > going forward. > > Thanks, > Justin > > P.S please CC me on any replies as I'm not subscribed to this list > > 1.https://github.com/apache/incubator-shardingsphere/releases > >
Re: [RESULT][VOTE] Release Apache SkyWalking (incubating) version6.0.0-GA
> IMO it needs to be made clearer as the binaries are not clearly labeled as > such and in the same directory as the release, perhaps create a directory > called binary or bin and put them in that? How about we change like this? apache-skywalking-apm-incubating-6.0.0-GA.zip to apache-skywalking-apm-incubating-bin-6.0.0-GA.zip apache-skywalking-apm-incubating-6.0.0-GA.tar.gz to apache-skywalking-apm-incubating-bin-6.0.0-GA.tar.gz I will ask for the community, and do some adjustments. ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "justin"; Date: Tue, Jan 29, 2019 04:31 PM To: "general"; Subject: Re: [RESULT][VOTE] Release Apache SkyWalking (incubating) version6.0.0-GA Hi, > For Justin mentioned about name not clear, I have given the explanation about > the name of source tar with `-src.tar.tgz` suffix. > And I have added the statement in skywalking download page[1] to make what is > the Apache release more clear. IMO it needs to be made clearer as the binaries are not clearly labeled as such and in the same directory as the release, perhaps create a directory called binary or bin and put them in that? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Dubbo (Incubating) 2.7.0 [RC2]
+1 binding from me I checked. 1. asc and sha512 existed and checked. 2. compile from source successfully 3. rat passed 4. license, notice and disclaimer exist in source and dist tar Good luck, Dubbo team. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "hux...@apache.org"; Date: Tue, Jan 29, 2019 10:03 AM To: "Incubator General"; Subject: Re: [VOTE] Release Apache Dubbo (Incubating) 2.7.0 [RC2] Hi community, Dubbo 2.7.0 RC2 is still waiting for 1 more binding vote to get it passed. Would you please help to review and vote for the candidate? Any help is greatly appreciated! On Thu, Jan 24, 2019 at 10:28 PM Huxing Zhang wrote: > > Hello Incubator Community, > > The Apache Dubbo community has voted on and approved a proposal to release > Apache Dubbo (Incubating) version 2.7.0. > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Apache Dubbo™ (incubating) is a high-performance, java based, open source > RPC framework. Dubbo offers three key functionalities, which include > interface based remote call, fault tolerance & load balancing, and > automatic service registration & discovery. > > Dubbo community vote and result thread: > https://lists.apache.org/thread.html/60b3ef868d8acd127c18584968d98dd6191c41dd3a426f98703f68f6@%3Cdev.dubbo.apache.org%3E > > The release candidates (RC2): > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.7.0 > > The staging repo: > https://repository.apache.org/content/repositories/orgapachedubbo-1005 > > Git tag for the release (RC2): > https://github.com/apache/incubator-dubbo/tree/dubbo-2.7.0 > > Hash for the release tag: > 614bcebc01336ee5047a98f96b28915680c0399c > > Release Notes: > https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md > > The artifacts have been signed with Key : > AF1B3C2AC648B9E8C9AC6F26CD69F886A620E8EC, which can be > found in the keys file: > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache Dubbo (Incubating) Team -- Best Regards！ Huxing - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Release Apache SkyWalking (incubating) version 6.0.0-GA
Hi all, Apache SkyWalking (incubating) Team is glad to announce the first release of Apache SkyWalking Incubating 6.0.0-GA. SkyWalking: APM (application performance monitor) tool for distributed systems, especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures. Vote Thread: https://lists.apache.org/thread.html/5914e0a68fb3e8f3fd9efe6df676b4d5b1817a9943b3901c79145f39@%3Cgeneral.incubator.apache.org%3E Download Links : http://skywalking.apache.org/downloads/ Release Notes : https://github.com/apache/incubator-skywalking/blob/v6.0.0-GA/CHANGES.md Website: http://skywalking.apache.org/ SkyWalking Resources: - Issue: https://github.com/apache/incubator-skywalking/issues - Mailing list: d...@skywalkiing.incubator.apache.org - Documents: https://github.com/apache/incubator-skywalking/blob/v6.0.0-GA/docs/README.md - Apache SkyWalking (incubating) Team = *Disclaimer* Apache SkyWalking (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108
[RESULT][VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA
Hi The release vote finished, we got 4 (+1 binding) from Igansi, Sheng Wu, ShaoFeng Shi, Willem Jiang 1 (-1 binding) from Justin. 1 (+1 unbinding) from William Guo The vote passed. I am working on the further release process. For Justin mentioned about name not clear, I have given the explanation about the name of source tar with `-src.tar.tgz` suffix. And I have added the statement in skywalking download page[1] to make what is the Apache release more clear. Thank you all to take part in the vote and release processes. Appreciate! [1] http://skywalking.apache.org/downloads/ -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: " Sheng Wu"; Date: Sat, Jan 26, 2019 04:49 PM To: "general"; Subject: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA Hi All, This is a call for vote to release Apache SkyWalking (Incubating) version 6.0.0-GA. The Apache SkyWalking community has tested, voted and approved the proposed release of Apache SkyWalking (Incubating) 6.0.0-GA We now kindly request the Incubator PMC members review and vote on this incubator release. SkyWalking: APM (application performance monitor) tool for distributed systems, especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures. Underlying technology is a distributed tracing system. Vote Thread: * https://lists.apache.org/thread.html/5ee4634d3cc72449082f527952ab5b135cb0d171f2eb3bfa2caf664f@%3Cdev.skywalking.apache.org%3E Release notes: * https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md#600-ga Release Candidate: * https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-GA/ * sha512 checksums - 6e07c174a0473af245c05869e485a4ddc1f4b7b1ba1d55c65b81d5ed37041f632985f6c5d3e13773fc5940917b71940131580b4f9fbd1853521e906c7b60f11d apache-skywalking-apm-incubating-6.0.0-GA-src.tgz - a19a24b790f41b1d7f93547104fbfc70a1dc208d855026b0c4696d1991518a952d031b62a76bfa923394042757dc92aa87e6cac6502d015f30258e9959e393bf apache-skywalking-apm-incubating-6.0.0-GA.tar.gz - 4f0bff2bf2edb207f9b209abdc8c5433d3f7a0f1f24d515344204dac6a3a4aa2e2ebb9354f3725e75b47e7d3bee52e0a9a454136b410df29034db0d478b60164 apache-skywalking-apm-incubating-6.0.0-GA.zip Maven 2 staging repository: * https://repository.apache.org/content/repositories/orgapacheskywalking-1028/org/apache/skywalking Release Tag : * (Git Tag) v6.0.0-GA Release CommitID : * https://github.com/apache/incubator-skywalking/tree/8b638258bb9ae9d512f946b5622fb65948a937e8 * Git submodule * skywalking-ui: https://github.com/apache/incubator-skywalking-ui/tree/c44642f73b9f73a54b0d716cade5094304e1a67b * apm-protocol/apm-network/src/main/proto: https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/b66fa070fd647662f06497e4ed3657eb258cb6e9 * oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol https://github.com/apache/incubator-skywalking-query-protocol/tree/c65a23bd6b9bba8d1df30d4de261624952df2b7b Keys to verify the Release Candidate : * https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS corresponding to wush...@apache.org Guide to build the release from source : * https://github.com/apache/incubator-skywalking/blob/v6.0.0-GA/docs/en/guides/How-to-build.md * docs/en/guides/How-to-build.md in source tar. Voting will start now (Jan. 26th 2019) and will remain open for at least 72 hours, Request IPMC to give their vote. [ ] +1 Release this package. [ ] +0 No opinion. [ ] -1 Do not release this package because ------ Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108
Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA
Hi Justin A statement is added at the top of download page[1]. > Only source code releases are official Apache releases, the Windows and Linux > binary releases are just for end users connivance. [1] . http://skywalking.apache.org/downloads/ -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "justin"; Date: Mon, Jan 28, 2019 07:52 AM To: "general"; Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA Hi, Looking at your download page [1], it IMO also needs to made clearer that the binaries linked to there are not offical releases. Thanks, Justin 1. https://skywalking.apache.org/downloads/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA
Hi, Justin In the same folder this is a *-src.tar.gz, which is source code tar. Why do you think the other two are not connivance binary tar and zip? And how do you want to make it more clear? Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Justin Mclean Date: Mon,Jan 28,2019 7:40 AM To: general Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA Hi, -1 binding Looking at [1] and [2] in [3] they contain multiple jars containing compiled source code. Apache only makes releases that contain source code, it??s not clear these are binaries just for the connivance of users. Thanks, Justin 1. apache-skywalking-apm-incubating-6.0.0-GA.tar.gz 2. apache-skywalking-apm-incubating-6.0.0-GA.zip 3. https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-GA/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA
Hi Justin Making the download page more clear, such as add a statement on that page, make sense to me. Anf I will do that. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Justin Mclean Date: Mon,Jan 28,2019 7:52 AM To: general Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA Hi, Looking at your download page [1], it IMO also needs to made clearer that the binaries linked to there are not offical releases. Thanks, Justin 1. https://skywalking.apache.org/downloads/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA
Move my +1 from skywalking dev vote. -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "ShaoFeng Shi"; Date: Sun, Jan 27, 2019 08:40 PM To: "general"; Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA I checked the signature, the sha512 hash, and the license file, they are good; "mvn clean package" and "mvn test" are all passed after I set global proxy for NPM. Here is my vote: +1 (binding) Best regards, Shaofeng Shi ?? Apache Kylin PMC Work email: shaofeng@kyligence.io Kyligence Inc: https://kyligence.io/ Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html Join Kylin user mail group: user-subscr...@kylin.apache.org Join Kylin dev mail group: dev-subscr...@kylin.apache.org Sheng Wu ??2019??1??26?? 4:49?? > Hi All, > This is a call for vote to release Apache SkyWalking (Incubating) version > 6.0.0-GA. > > > The Apache SkyWalking community has tested, voted and approved the proposed > release of Apache SkyWalking (Incubating) 6.0.0-GA > > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > > SkyWalking: APM (application performance monitor) tool for distributed > systems, > especially designed for microservices, cloud native and container-based > (Docker, Kubernetes, Mesos) architectures. > Underlying technology is a distributed tracing system. > > > Vote Thread: >* > https://lists.apache.org/thread.html/5ee4634d3cc72449082f527952ab5b135cb0d171f2eb3bfa2caf664f@%3Cdev.skywalking.apache.org%3E > > > Release notes: > > > > >* > https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md#600-ga > > > > > Release Candidate: > > > > >* https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-GA/ >* sha512 checksums > - > 6e07c174a0473af245c05869e485a4ddc1f4b7b1ba1d55c65b81d5ed37041f632985f6c5d3e13773fc5940917b71940131580b4f9fbd1853521e906c7b60f11d > apache-skywalking-apm-incubating-6.0.0-GA-src.tgz > - > a19a24b790f41b1d7f93547104fbfc70a1dc208d855026b0c4696d1991518a952d031b62a76bfa923394042757dc92aa87e6cac6502d015f30258e9959e393bf > apache-skywalking-apm-incubating-6.0.0-GA.tar.gz > - > 4f0bff2bf2edb207f9b209abdc8c5433d3f7a0f1f24d515344204dac6a3a4aa2e2ebb9354f3725e75b47e7d3bee52e0a9a454136b410df29034db0d478b60164 > apache-skywalking-apm-incubating-6.0.0-GA.zip > > > > > Maven 2 staging repository: > > > > >* > https://repository.apache.org/content/repositories/orgapacheskywalking-1028/org/apache/skywalking > > > > > Release Tag : > > > > >* (Git Tag) v6.0.0-GA > > > > > Release CommitID : > > > > >* > https://github.com/apache/incubator-skywalking/tree/8b638258bb9ae9d512f946b5622fb65948a937e8 >* Git submodule > * skywalking-ui: > https://github.com/apache/incubator-skywalking-ui/tree/c44642f73b9f73a54b0d716cade5094304e1a67b > * apm-protocol/apm-network/src/main/proto: > https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/b66fa070fd647662f06497e4ed3657eb258cb6e9 > * > oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol > > https://github.com/apache/incubator-skywalking-query-protocol/tree/c65a23bd6b9bba8d1df30d4de261624952df2b7b > > > > > Keys to verify the Release Candidate : > > > > >* https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS > corresponding to wush...@apache.org > > > > > Guide to build the release from source : > > > > >* > https://github.com/apache/incubator-skywalking/blob/v6.0.0-GA/docs/en/guides/How-to-build.md >* docs/en/guides/How-to-build.md in source tar. > > > Voting will start now (Jan. 26th 2019) and will remain open for at least > 72 hours, Request IPMC to give their vote. >[ ] +1 Release this package. >[ ] +0 No opinion. >[ ] -1 Do not release this package because > > > > -- > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108
[VOTE] Release Apache SkyWalking (incubating) version 6.0.0-GA
Hi All, This is a call for vote to release Apache SkyWalking (Incubating) version 6.0.0-GA. The Apache SkyWalking community has tested, voted and approved the proposed release of Apache SkyWalking (Incubating) 6.0.0-GA We now kindly request the Incubator PMC members review and vote on this incubator release. SkyWalking: APM (application performance monitor) tool for distributed systems, especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures. Underlying technology is a distributed tracing system. Vote Thread: * https://lists.apache.org/thread.html/5ee4634d3cc72449082f527952ab5b135cb0d171f2eb3bfa2caf664f@%3Cdev.skywalking.apache.org%3E Release notes: * https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md#600-ga Release Candidate: * https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-GA/ * sha512 checksums - 6e07c174a0473af245c05869e485a4ddc1f4b7b1ba1d55c65b81d5ed37041f632985f6c5d3e13773fc5940917b71940131580b4f9fbd1853521e906c7b60f11d apache-skywalking-apm-incubating-6.0.0-GA-src.tgz - a19a24b790f41b1d7f93547104fbfc70a1dc208d855026b0c4696d1991518a952d031b62a76bfa923394042757dc92aa87e6cac6502d015f30258e9959e393bf apache-skywalking-apm-incubating-6.0.0-GA.tar.gz - 4f0bff2bf2edb207f9b209abdc8c5433d3f7a0f1f24d515344204dac6a3a4aa2e2ebb9354f3725e75b47e7d3bee52e0a9a454136b410df29034db0d478b60164 apache-skywalking-apm-incubating-6.0.0-GA.zip Maven 2 staging repository: * https://repository.apache.org/content/repositories/orgapacheskywalking-1028/org/apache/skywalking Release Tag : * (Git Tag) v6.0.0-GA Release CommitID : * https://github.com/apache/incubator-skywalking/tree/8b638258bb9ae9d512f946b5622fb65948a937e8 * Git submodule * skywalking-ui: https://github.com/apache/incubator-skywalking-ui/tree/c44642f73b9f73a54b0d716cade5094304e1a67b * apm-protocol/apm-network/src/main/proto: https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/b66fa070fd647662f06497e4ed3657eb258cb6e9 * oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol https://github.com/apache/incubator-skywalking-query-protocol/tree/c65a23bd6b9bba8d1df30d4de261624952df2b7b Keys to verify the Release Candidate : * https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS corresponding to wush...@apache.org Guide to build the release from source : * https://github.com/apache/incubator-skywalking/blob/v6.0.0-GA/docs/en/guides/How-to-build.md * docs/en/guides/How-to-build.md in source tar. Voting will start now (Jan. 26th 2019) and will remain open for at least 72 hours, Request IPMC to give their vote. [ ] +1 Release this package. [ ] +0 No opinion. [ ] -1 Do not release this package because -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108
Re: [VOTE]: Release Apache Dubbo Spring Boot Project (Incubating) 0.2.1 and 0.1.2
Hi, I think you should separate the release vote. Because if -1 to one release, it is hard to be clear in ml. Thanks. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Mercy Ma Date: Thu,Jan 24,2019 5:57 PM To: Incubator General Subject: Re: [VOTE]: Release Apache Dubbo Spring Boot Project (Incubating) 0.2.1 and 0.1.2 Hello all, This is a call for a vote to release Apache Dubbo Spring Boot Project (Incubating) 0.2.1 and 0.1.2. The Apache Dubbo community has voted on and approved a proposal to release Apache Dubbo Spring Boot Project (Incubating) 0.2.1 and 0.1.2. We now kindly request the Incubator PMC members review and vote on this incubator release. Apache Dubbo?6?4 (incubating) is a high-performance, java based, open source RPC framework. Dubbo offers three key functionalities, which include interface based remote call, fault tolerance & load balancing, and automatic service registration & discovery. Dubbo community vote and result thread: https://lists.apache.org/thread.html/e86b324bf3c8c606cb609560a1c4693669a734197e8e4ea95efbd194@%3Cdev.dubbo.apache.org%3E The release candidates (RC1): 0.2.1: https://dist.apache.org/repos/dist/dev/incubator/dubbo/spring-boot-project/0.2.1/ 0.1.2: https://dist.apache.org/repos/dist/dev/incubator/dubbo/spring-boot-project/0.1.2/ Git tag for the release (RC1): 0.2.1: https://github.com/apache/incubator-dubbo-spring-boot-project/tree/0.2.1-release 0.1.2: https://github.com/apache/incubator-dubbo-spring-boot-project/tree/0.1.2-release Hash for the release tag: 0.2.1: 79e9fa899b74324a8e83d00aac10e3d899b8c3f8 0.1.2: cb66ba32400986609f9e00b0d160173e7b2f55d2 Release Notes: 0.2.1: https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/0.2.1 0.1.2: https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/0.1.2 The artifacts have been signed with Key: 28681CB1, which can be found in the keys file: https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS The vote will be open for at least 72 hours or until the necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Thanks, The Apache Dubbo (Incubating) Team
Re: [VOTE] Shut down unused/inactive incubator lists
+1 Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: sebb Date: Mon,Jan 21,2019 8:12 AM To: general Subject: Re: [VOTE] Shut down unused/inactive incubator lists The following lists are all but inactive: announce@ Last post Jan 2008 android-interest@ Last post Mar 2011 dev@ - only general circulars jaxws-tck@ (private) Last post 2012 projects@ Last post Jul 2011 user@ - only general circulars I think they should be shut down. Please vote so an Infra Jira can be raised to shut them down. They can have a bounce message added to direct posters to general@/private@ as appropriate [ ] +1 [ ] -1 - give a reason please Please vote by end January 2019 Sebb. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-beta
I see. The tag is only true source release if you do "git clone & submodule init & submodule update", then UI and other submodule codes come out. If you use download button at GitHub page, github doesn't include the submodule, which is a github issue. We have noticed this and also this is why we put a section in our compiling document, to guide user build from GitHub. Thanks for helping on recheck these details. Justin. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Justin Mclean Date: Mon,Dec 24,2018 8:09 AM To: general Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-beta Hi, > Could you provide more detail about the differences? > SkyWalking has a release shell script[1], which excludes some files(such as > git and submodule files) from github tag to build the source tar. Is this > what you found? Could be, also some more difference between the UI. Just download the branch from gthub and do a diff -r and you see the differences. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-beta
> You may what to check what is tagged in SVN and what going into the release > as there a few minor differences (non source released). Hi, Justin Could you provide more detail about the differences? SkyWalking has a release shell script[1], which excludes some files(such as git and submodule files) from github tag to build the source tar. Is this what you found? [1] https://github.com/apache/incubator-skywalking/blob/master/tools/releasing/create_source_release.sh#L63 Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Justin Mclean Date: Mon,Dec 24,2018 6:13 AM To: general Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-beta Hi, +1 binding. I checked: - incubating in name - DISCLAIMER exits - LICENSE and NOTICE are fine - Al source file have ASF headers - No unexpected binary files - Can compile from source You may what to check what is tagged in SVN and what going into the release as there a few minor differences (non source released). Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-beta
Move my +1 binding from dev list Checked 1. Features test. Tested H2, ElasticSearch, MySQL as storage in my local laptop, running in standalone mode, collect data in Javaagent. Passed 2. All artifacts in staging repository are published with .asc, .md5, *sha1 files 3. Source code and distribution package with .asc, .sha512 4. LICENSE and NOTICE are in Source code and distribution package. 5. shasum512 is right. 6. Build passed 7. Apache RAT check. 8. DISCLAIMER exists -- Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 -- Original -- From: "ShaoFeng Shi"; Date: Sat, Dec 22, 2018 08:04 PM To: "general"; Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-beta Verified the LICENSE and NOTICE file are good; The src package is signed by Hongtao Gao who is PPMC, the SHA hash is also good. Maven package and test are successful with Java 1.8, Maven 3.5.3 on CentOS 6.5. Here is my vote: +1 (binding) Best regards, Shaofeng Shi ?? Apache Kylin PMC Work email: shaofeng@kyligence.io Kyligence Inc: https://kyligence.io/ Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html Join Kylin user mail group: user-subscr...@kylin.apache.org Join Kylin dev mail group: dev-subscr...@kylin.apache.org Hongtao Gao ??2018??12??21?? 10:55?? > Hi all, > This is a call for vote to release Apache SkyWalking (Incubating) version > 6.0.0-beta. > > The Apache SkyWalking community has tested, voted and approved the proposed > release of Apache SkyWalking (Incubating) 6.0.0-beta > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > SkyWalking: APM (application performance monitor) tool for distributed > systems, > especially designed for microservices, cloud native and container-based > (Docker, Kubernetes, Mesos) architectures. > Underlying technology is a distributed tracing system. > > Vote Thread: > > * > > https://lists.apache.org/thread.html/317455cefb04263e94387b573f50358e2ae40d46120f8980218a3739@%3Cdev.skywalking.apache.org%3E > > Result Thread: > > * From the vote thread. > > Release notes: > > * https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md > > Release Candidate: > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-beta > * sha512 checksums > - > > 13442491bbcf306d4a62993cb81625b5d69044086c67e5dd023c32e4dbf5dc8d38ce47b50de0e7ee1714bcaca0d059b83ff9e0e301b2df8b54dbf8965b839090 > apache-skywalking-apm-incubating-6.0.0-beta-src.tgz > - > > c050dd52993ec61de487cd37de6d024862a8e0f32751ccc3fb8faefd87ca0a9bc73cdf9126d0af4178fecac9750e9348e624b658bd49c1af53084961cf056e53 > apache-skywalking-apm-incubating-6.0.0-beta.tar.gz > - > > dc5f1397ce9c54b07008c24dacbb56821fe3d3a37071071fde1d5ee622d8b015bf305d7d99c14f6a74094cfff7f26c0572b4ba424e3035a86612a272cff3cf96 > apache-skywalking-apm-incubating-6.0.0-beta.zip > > Maven 2 staging repository: > > * > > https://repository.apache.org/content/repositories/orgapacheskywalking-1026/org/apache/skywalking/ > > Release Tag : > > * (Git Tag) https://github.com/apache/incubator-skywalking/tree/v6.0.0- > <https://github.com/apache/incubator-skywalking/tree/v6.0.0-alpha>beta > > Release CommitID : > > * > > https://github.com/apache/incubator-skywalking/tree/1a3b4f314d52d7b8cc55fc4bfbcf28494c57d6ee > * Git submodule >* skywalking-ui: > > https://github.com/apache/incubator-skywalking-ui/tree/756bc74e0b1351eefb860cbc2b05d86b138d4f0f >* apm-protocol/apm-network/src/main/proto: > > https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/b66fa070fd647662f06497e4ed3657eb258cb6e9 >* > > oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol: > > https://github.com/apache/incubator-skywalking-query-protocol/tree/c65a23bd6b9bba8d1df30d4de261624952df2b7b > > Keys to verify the Release Candidate : > > * https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS > corresponding hanahm...@apache.org > > Guide to build the release from source : > > * > > https://github.com/apache/incubator-skywalking/blob/v6.0.0-beta/docs/en/guides/How-to-build.md > > Voting will start now (Dec 21th, 2018, 03:00 AM, UTC) and will remain open > for at least 72 hours, Request all PPMC members to give their vote. > [ ] +1 Release this package. > [ ] +0 No opinion. > [ ] -1 Do not release this package because > > -- > Gao Hongtao > Apache SkyWalking & ShardingSphere >
Re: Release checklist application
I wany to try this tool. Should be an interesting tool. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Justin Mclean Date: Mon,Dec 17,2018 1:47 AM To: general Subject: Re: Release checklist application Hi, Hopefully everyone is familiar with the incubator checklist that was created a few months back [1] I run into a company called Safety Culture [2] that does an online/mobile compliance application and repurposed it to use the incubator release check list. It works quite nicely and may be a useful tool when checking releases. Coincidentally an IPMC member Brett Porter currently works there and is willing to help out. Hopefully we can get access to a wider audience, but currently if you want to take a look just ask and I??ll grant you access. Thanks, Justin 1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist 2. https://safetyculture.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Airflow to TLP
+1 binding Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Hitesh Shah Date: Thu,Dec 6,2018 0:14 PM To: general Subject: Re: [VOTE] Graduate Apache Airflow to TLP +1 (binding) -- Hitesh On Wed, Dec 5, 2018 at 7:28 PM Dave Fisher wrote: > +1 (binding) > > Regards, > Dave > > Sent from my iPhone > > > On Dec 5, 2018, at 7:07 PM, Bolke de Bruin wrote: > > > > Hi Dave, > > > > Yes it is optional. Please See installation instructions. > > > > Bolke > > > > > > Op do 6 dec. 2018 00:59 schreef Dave Fisher > > >> Hi - > >> > >> Please explain the status of the GPL??d code mentioned here - > >> https://issues.apache.org/jira/browse/AIRFLOW-3400 > >> > >> Is it an optional dependency? > >> > >> Regards, > >> Dave > >> > >>> On Dec 5, 2018, at 3:31 PM, Jakob Homan wrote: > >>> > >>> Hello- > >>> > >>> The Airflow podling community has VOTEd[0] to graduate, following a > >>> very successful DISCUSS[1]. Accordingly I'm bringing the resolution > >>> up for an IPMC VOTE. > >>> > >>> The podling result was: > >>> Overall: 21 x +1 votes, 0 x -1 votes > >>> > >>> Binding +1 x 11: Kaxil, Tao, Bolke, Fokko, Maxime, Arthur, Hitesh, > >>> Chris, Sid, Ash, Jakob. > >>> Non-binding +1 x 10: Daniel, Shah, Stefan, Kevin, Marc, Sunil, > >>> Adityan, Deng, Neelesh, Sai > >>> > >>> Since entering the Incubator in 2016, the Airflow community has: > >>> * successfully produced 7 releases > >>> * added 9 new committers/PPMC members > >>> * built a diverse group of committers from multiple different > employers > >>> * had more than 3,300 JIRA tickets opened > >>> * completed the project maturity model with positive responses[2] > >>> > >>> Here's my binding +1. The VOTE will run for at least 72 hours. > >>> > >>> Thanks, > >>> Jakob > >>> > >>> [0] > >> > https://mail-archives.apache.org/mod_mbox/airflow-dev/201812.mbox/%3c115b1380-619d-41d7-a30e-9c041cd4d...@gmail.com%3E > >>> [1] > >> > https://lists.apache.org/thread.html/%3c0a763b0b-7d0d-4353-979a-ac6769eb0...@gmail.com%3E > >>> [2] > >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation > >>> > >>> > >>> > >>> Establish the Apache Airflow Project > >>> > >>> WHEREAS, the Board of Directors deems it to be in the best > >>> interests of the Foundation and consistent with the > >>> Foundation's purpose to establish a Project Management > >>> Committee charged with the creation and maintenance of > >>> open-source software, for distribution at no charge to > >>> the public, related to workflow automation and scheduling > >>> that can be used to author and manage data pipelines. > >>> > >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management > >>> Committee (PMC), to be known as the "Apache Airflow Project", > >>> be and hereby is established pursuant to Bylaws of the > >>> Foundation; and be it further > >>> > >>> RESOLVED, that the Apache Airflow Project be and hereby is > >>> responsible for the creation and maintenance of software > >>> related to workflow automation and scheduling that can be > >>> used to author and manage data pipelines; and be it further > >>> > >>> RESOLVED, that the office of "Vice President, Apache Airflow" be > >>> and hereby is created, the person holding such office to > >>> serve at the direction of the Board of Directors as the chair > >>> of the Apache Airflow Project, and to have primary responsibility > >>> for management of the projects within the scope of > >>> responsibility of the Apache Airflow Project; and be it further > >>> > >>> RESOLVED, that the persons listed immediately below be and > >>> hereby are appointed to serve as the initial members of the > >>> Apache Airflow Project: > >>> > >>> * Alex Guziel > >>> * Alex Van Boxel > >>> * Arthur Wiedmer > >>> * Ash Berlin-Taylor > >>> * Bolke de Bruin > >>> * Chris Riccomini >
Re: [VOTE] Retire Quickstep podling from Apache Incubator
+1 binding. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Willem Jiang Date: Wed,Nov 28,2018 4:52 PM To: general Subject: Re: [VOTE] Retire Quickstep podling from Apache Incubator +1 binding. Willem Jiang Twitter: willemjiang Weibo: willem On Wed, Nov 28, 2018 at 8:03 AM Roman Shaposhnik wrote: > > Hi! > > after a discussion with the Quickstep community: > > https://lists.apache.org/thread.html/6c4998e6feaec2651511a0d461d45924847135b60aa00e084301bc59@%3Cdev.quickstep.apache.org%3E > and a formal passing vote: > > https://lists.apache.org/thread.html/e0e759c1ae95a46b00aad9a44ddaaf6a007039029bc0a3167381e328@%3Cprivate.quickstep.apache.org%3E > > I would like to call an IPMC VOTE on the following proposal: > > Given the lack of community participation in moving > Apache Quickstep (incubating) towards graduation we > are proposing to retire the project from the Apache Incubator. > > The project can continue existing on GitHub as an ALv2 licensed > open source project but will stop being affiliated with an Apache > Software Foundation. > > [ ] +1 Retire Quickstep from the Incubator. > [ ] +0 Don't care. > [ ] -1 Don't retire Quickstep from the Incubator because... > > The vote will be open for at least 72 hours. > > Thanks, > Roman. > > - > 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: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-alpha
Hi Justin Thanks for pointing out. And yes, it is BSD-2. I will fix this in next release. -- Sheng Wu Apache SkyWalking & Sharding-Sphere -- Original -- From: "justin"; Date: Wed, Nov 14, 2018 01:32 PM To: "general"; Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-alpha Hi, +1 (binding) I checked: - incubating in name - signatures and hashes good - DISCLAIMER exists - LICENSE and NOTICE correct - no unexpected binary files in releases - all source files have ASF headers - can compile from source One very tiny issue is that Gogo protobuf isn??t a BSD 3 clause license as mention in LICENSE but actually BSD 2 clause license looking at it??s source header. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Release Apache SkyWalking (incubating) version 6.0.0-alpha
Hi all, Apache SkyWalking (incubating) Team is glad to announce the first release of Apache SkyWalking Incubating 6.0.0-alpha. SkyWalking: APM (application performance monitor) tool for distributed systems, especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures. Vote Thread: https://lists.apache.org/thread.html/6abd7ae96210cb7eb6d70a356db1b8d3e5038a58d3ac8db531a42151@%3Cgeneral.incubator.apache.org%3E Download Links : http://skywalking.apache.org/downloads/ Release Notes : https://github.com/apache/incubator-skywalking/blob/v6.0.0-alpha/CHANGES.md Website: http://skywalking.apache.org/ SkyWalking Resources: - Issue: https://github.com/apache/incubator-skywalking/issues - Mailing list: d...@skywalkiing.incubator.apache.org - Documents: https://github.com/apache/incubator-skywalking/blob/v6.0.0-alpha/docs/README.md - Apache SkyWalking (incubating) Team = *Disclaimer* Apache SkyWalking (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. -- Sheng Wu Apache SkyWalking & Sharding-Sphere
Re: [RESULT][VOTE] Release Apache SkyWalking (incubating) version 6.0.0-alpha
The vote for releasing Apache SkyWalking 6.0.0-alpha (incubating) is closed, now. Vote result: 5 (+1 binding) Willem Jiang, Luke Han, Justin Mclean, Mick Semb Wever, Jean-Baptiste Onofr?? 1 (+1 no binding) William Guo. Thank you everyone for taking the time to review the release and help us. I will process to publish the release and send ANNOUNCE. -- Sheng Wu Apache SkyWalking & Sharding-Sphere -- Original -- From: "Jean-Baptiste Onofr??"; Date: Wed, Nov 14, 2018 05:40 PM To: "general"; Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 6.0.0-alpha +1 (binding) Checked the build, signature and headers. Regards JB On 10/11/2018 12:49, Sheng Wu wrote: > Hi All, > This is a call for vote to release Apache SkyWalking (Incubating) version > 6.0.0-alpha. > > > The Apache SkyWalking community has tested, voted and approved the proposed > release of Apache SkyWalking (Incubating) 6.0.0-alpha > > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > > SkyWalking: APM (application performance monitor) tool for distributed > systems, > especially designed for microservices, cloud native and container-based > (Docker, Kubernetes, Mesos) architectures. > Underlying technology is a distributed tracing system. > > > > Vote Thread: > * > https://lists.apache.org/thread.html/649d6ca16404ed752fd80ea1b6fc2c9aeaae1c525032ae90e3529cd5@%3Cdev.skywalking.apache.org%3E > > > Release notes: > > > > > * https://github.com/apache/incubator-skywalking/blob/v6.0.0-alpha/CHANGES.md > > > > > Release Candidate: > > > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-alpha/ > * sha512 checksums > - > 6ef68b622c6c26db5143238f545ef569919757b70ec3c950305063da8ded8789c2bf2cc31e8edeaa90e18a3697786dff1ef287c03cd8ff5701e11a75b3b65899 > apache-skywalking-apm-incubating-6.0.0-alpha-src.tgz > - > acfae5d3ef91ba7ffbb2ad7aaf58f92ea494c5c55593a2e2ad393140194cd9db7f5a5a0e57066160d10c3e556749186b4549768484a9d341d49a1af083e240ed > apache-skywalking-apm-incubating-6.0.0-alpha.tar.gz > - > 7553603875fc7a77d8cb7ea0108edaea25fc8790a8b13388b2ea1d3730b5f81a3771cf39703bcb89ce75a0387ed6ad7b8ed1d1a54d943e4e48de6e6f124072c9 > apache-skywalking-apm-incubating-6.0.0-alpha.zip > > > > > Maven 2 staging repository: > > > > > * > https://repository.apache.org/content/repositories/orgapacheskywalking-1025/org/apache/skywalking/ > > > > > Release Tag : > > > > > * https://github.com/apache/incubator-skywalking/tree/v6.0.0-alpha > > > > > Release CommitID : > > > > > * > https://github.com/apache/incubator-skywalking/tree/14009ce1172e8d70c5410029a096d3ae1a41c76d > * Git submodule > * skywalking-ui: > https://github.com/apache/incubator-skywalking-ui/tree/26f2c3b7bd93aa71897e842d90d272ee4cb618dc > * apm-protocol/apm-network/src/main/proto: > https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/e7fc69462955c86d70f3f7f33712dfe33ecefbc6 > * > oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol > > https://github.com/apache/incubator-skywalking-query-protocol/tree/c65a23bd6b9bba8d1df30d4de261624952df2b7b > > > > > Keys to verify the Release Candidate : > > > > > * https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS > corresponding to wush...@apache.org > > > > > Guide to build the release from source : > > > > > * > https://github.com/apache/incubator-skywalking/blob/v6.0.0-alpha/docs/en/guides/How-to-build.md > * `docs/en/guides/How-to-build.md` in source tar > > > > Voting will start now (10th Nov. date) and will remain open for at least 72 > hours, Request IPMC to give their vote. > [ ] +1 Release this package. > [ ] +0 No opinion. > [ ] -1 Do not release this package because > > > > > > -- > Sheng Wu > Apache SkyWalking & Sharding-Sphere > -- Jean-Baptiste Onofr?? jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
