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, 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/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.ttf > 18. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.woff > 19. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.woff2 > 20 >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
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/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.ttf 18. apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.woff 19. apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.woff2 20 apache-superset-0.32.0rc2/superset/translations/de/LC_MESSAGES/messages.mo 21. https://www.pngfly.com/png-79pbyi/ 22. https://www.glyphicons.com/license/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache OpenWhisk Composer 0.11.0 (incubating)
Hi, > If that URL was missing what where people actually voting on? Looking at the > vote thread on the dev list it seem it was a GitHub hash?? Can anyone answer this? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[GitHub] [incubator] ebarboni opened a new pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ebarboni opened a new pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10 An attempt to enhance the graduation steps as we (Apache NetBeans) encounter 404 error on the Service Desk Link. Also trying to split the PMC chair and PMC "todolist". Fixed some links Hope it helps This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Joining Superset as a Mentor
Hi Jakob- I’ve added you to the Superset mentor list. Please subscribe to priv...@incubator.apache.org along with all of the appropriate superset mailing lists. Regards, Dave > On Apr 25, 2019, at 1:42 PM, Jakob Homan wrote: > > Superset could use an extra mentor to help with the incubation > process. I've checked with the PPMC and they're on board with me > joining as such. Accordingly, I volunteer to mentor that project. > > -Jakob > > - > 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
Joining Superset as a Mentor
Superset could use an extra mentor to help with the incubation process. I've checked with the PPMC and they're on board with me joining as such. Accordingly, I volunteer to mentor that project. -Jakob - 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
+1 (binding) * Checked DISCLAIMER/ LICENSE/ NOTICE, * Checked headers * Verified sig (Only Max's key is in there, we should probably have others roll a release too in the future) * Spotchecked licenses * Verified md512 hash. -Jakob On Wed, Apr 24, 2019 at 4:14 PM Alan Gates wrote: > > Forwarding my +1 from the dev list. Checked the NOTICE, LICENSE, and > DISCLAIMER files. Did a quick check that everything had appropriate Apache > License headers, and I didn't find any binaries in the RC. > > Alan. > > On Wed, Apr 24, 2019 at 1:37 PM Maxime Beauchemin < > maximebeauche...@gmail.com> wrote: > > > Dear all, > > > > The source release 0.32.0 RC2 for Apache Superset is baked and available > > at: > > https://dist.apache.org/repos/dist/dev/incubator/superset/, public > > keys are available > > at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS > > > > This is the second ASF release candidate of Superset (!)* We're still > > ironing out our release process, so please bear with us and help if you > > can* > > . > > > > Here's link to original successful VOTE thread on dev@: > > > > http://mail-archives.apache.org/mod_mbox/superset-dev/201904.mbox/%3ccah7q75ip1lzq61+6yvfoqvb2nser8vhsa5rca87uzrrbpj9...@mail.gmail.com%3E > > > > As I went along, I documented the process in RELEASING.md in the repo, > > latest edits here https://github.com/apache/incubator-superset/pull/7329 > > > > For context (and similarly to 0.31) the `0.32` release branch was cut at > > SHA 1fece0d2f, that was merged on master on Jan 22nd. From that common > > ancestor, the following list of commit was added as cherry-picks. The SHAs > > in the list bellow reference the cherries on the release branch, PR number > > are available to get more details. > > > > New commits since 0.32.0rc1 *in bold:* > > > > *8fb4ba0d (HEAD -> release--0.32, tag: 0.32.0rc2) 0.32.0rc2* > > *3e6f6848 Add disclaimer and remove counter (#6738)* > > c7b32ac8 (tag: 0.32.0rc1, apache/release--0.32) 0.32.0rc1 > > b89cdbdc RELEASING.md from master > > 0e23f2e6 Add sign.sh > > 21804346 [load_examples] download data at runtime (#7314) > > b32d5900 Remove LICENSE entry around dataset (#7318) > > b3aa5633 (release--0.31) 0.31rc23 > > 24a595f4 bugfix: improve 'Time Table' (#6959) > > c70abbed 0.31rc22 > > dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244) > > 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198) > > (#7242) > > a9d54894 0.31.0rc21 > > b959fcd2 fix PRODUCT-67916 Click OK button cannot close error message modal > > (#7179) > > 2da9613f Update __init__.py (#7166) > > 538da2e3 0.31.0.rc20 > > 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade (#7145) > > 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade (#7144) > > daf2b8e5 Bump python lib croniter to an existing version (#7132) > > eb4c1355 Use metric name instead of metric in filter box (#7106) > > 2ff721ae handle null column_name in sqla and druid models > > e83a07d3 [forms] Fix handling of NULLs > > 76d26f37 0.31.0.rc19 > > fe78b4ec Fix filter_box migration PR #6523 (#7066) > > c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined query > > (#7029) > > b64a452a [sql lab] improve table name detection in free form SQL (#6793) > > 2357c4aa Adding custom control overrides (#6956) > > 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963) > > 5d8dd142 [csv-upload] Fixing message encoding (#6971) > > f454dedd [main] Disable resetting main DB attributes (#6845) > > e967b268 [sqla] Fixing order-by for non-inner-joins (#6862) > > a5d9a4e0 Adding template_params to datasource editor for sqla tables > > (#6869) > > 6b895413 [datasource] Ensuring consistent behavior of datasource > > editing/saving. (#7037) > > 8ef2789f Adding warning message for sqllab save query (#7028) > > 0ebdb564 fix inaccurate data calculation with adata rolling and > > contribution (#7035) > > b3af6a26 [fix] explore chart from dashboard missed slice title (#7046) > > c54b067c [db-engine-spec] Aligning Hive/Presto partition logic (#7007) > > bd65942e Changing time table viz to pass formatTime a date (#7020) > > 50accda9 [fix] Cursor jumping when editing chart and dashboard titles > > (#7038) > > 5ace5769 0.31.0rc17 > > 927a5846 [WIP] fix user specified JSON metadata not updating dashboard on > > refresh (#7027) > > fafb824d 0.31.0rc16 > > 7b72985e [fix] /superset/slice/id url is too long (#6989) > > b497d9e7 fix dashboard links in welcome page (#6756) > > c42afa11 0.31.0rc15 > > 35c55278 Enhancement of query context and object. (#6962) > > 1c41020c Split tags migration (#7002) > > ec7a0b22 0.31.0rc14 > > 4655cb4c Remove Cypress from package.json (#6912) > > fb8e3208 0.31.0rc13 > > b4cbe13d VIZ-190 fix (#6958) > > 5b7b22fd 0.31.0rc12 > > 51804229 Fix deck.gl form data (#6953) > > 9939a52d 0.31.0rc11 > > c3db74d9 (apache/cherry_c3db74d9021f9e60ef21beeb0847ff9f4b0277fd) Fix > > rendering regression from the introduction of bignumber (#6937) > > 9940d30a 0.31.0rc10 > >
Re: [RESUTL] [VOTE]: Release Apache DLab (incubating) 2.1 (RC2)
Congrats to the community of Apache DLab incubating for its first release under Apache Software Foundation. - Henry On Mon, Apr 15, 2019 at 2:38 AM Bohdan Hliva wrote: > Hi, > > The release vote finished, We’ve received: > 3 (+1 binding) from Justin Mclean, Henry Saputra and P. Taylor Goetz > 0 (-1 binding) > > The vote thread: > > https://lists.apache.org/thread.html/9b4f94cb771812112f5068e20816e68d96583dfbc4dafbfd8dcb9b0a@%3Cgeneral.incubator.apache.org%3E > > The vote passed. I am working on the further release process. > Many thanks to all who participated. > > Best regards, > The Apache DLab (Incubating) Team > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: incubator website guide transferring
Hi Eric, We know the guide needs an update and have an open JIRA issue: https://issues.apache.org/jira/projects/INCUBATOR/issues/INCUBATOR-202 The pages are here: https://github.com/apache/incubator/blob/master/pages/guides/graduation.ad https://github.com/apache/incubator/blob/master/pages/guides/transferring.ad Pull Requests are welcome! Regards, Dave > On Apr 25, 2019, at 5:13 AM, Eric Barboni wrote: > > 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: incubator website guide transferring
Hi Sheng, We will,but this I was only trying to give feedback for updating the website (if it should). It seems that Apache PLC4X hit the same issue a week ago. It seems the good path to follow is the following http://www.apache.org/dev/infra-contact#requesting-graduation Regards Eric -Message d'origine- De : Sheng Wu Envoyé : jeudi 25 avril 2019 14:26 À : general@incubator.apache.org Objet : 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 > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IP CLEARANCE] SkyWalking RocketBot UI project contribution
+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: 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 > >
incubator website guide transferring
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
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
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 to discuss this with the project owners and Dubbo community to work out a ETA. > 2. After that, all members in this group will be join Apache if they are > willing to (after they go through the vote certainly) As long as the project is under ASF, anyone can become committer by earning enough merit. > 3. After the transition is done, this particular group will be deleted +1. > > I will init the vote for the long term plan in dubbo's community today, and > we will get back with the concrete transition plan with ETA to the board > meeting as soon as possible. I hope we can satisfy the IPMC by doing this. > Pls. let me know if this is sufficient. We can adjust the plan if any > further suggestion comes up. I think the Dubbo community can deliver an improved version of [1] to IPMC, by filling all the blanks and with a new column ETA. [1] https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > Regards, > -Ian. > > > On Thu, Apr 25, 2019 at 12:29 AM Dave Fisher wrote: > > > 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
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
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 2. Stop using Dubbo logo as group's avatar - done 3. Rename all project names in compliance with the policies - ongoing 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 2. After that, all members in this group will be join Apache if they are willing to (after they go through the vote certainly) 3. After the transition is done, this particular group will be deleted I will init the vote for the long term plan in dubbo's community today, and we will get back with the concrete transition plan with ETA to the board meeting as soon as possible. I hope we can satisfy the IPMC by doing this. Pls. let me know if this is sufficient. We can adjust the plan if any further suggestion comes up. Regards, -Ian. On Thu, Apr 25, 2019 at 12:29 AM Dave Fisher wrote: > 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
