Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, > "Attribution — You must give appropriate credit, provide a link to the > license, and indicate if changes were made. You may do so in any reasonable > manner, but not in any way that suggests the licensor endorses you or your > use.” License stuff goes in LICENSE. If the license ask for anything beyond that and it not covered by license then they go in NOTICE. [1] Other other things that go in NOTICE are relocated copyrights and content from other NOTICE files. > Do you consider the GeoJSON not to be binary? (In ./countries) Yes for instance take a look at these files [2] and you see they are in plain text son format and are not binary. Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#mod-notice 2. apache-superset-0.32.0rc2/superset/assets/src/visualizations/CountryMap/countries/*.geojson - 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, +1 (binding) I checked: - Incubating in name - signatures and hash file fine - DISCLAIMER exists - LICENSE and NOTICE good - code in release candidate matches code in version control - No unexpected binary files - Source files have correct header except one which has been fixed. 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 OpenWhisk Composer 0.11.0 (incubating)
Hi, One issue I see with the instructions script is that you are asking people to download it from head, this may make it hard to verify old releases or may give different results during the voting process if changes are made. It may be better to package the verifying script inside the release candidate. Another is from the output of the script it’s unclear where it downloaded the files or what rc it is testing, adding that may be useful. It also clones incubator-openwhisk-utilities which might be seen as misleading as should it be cloning incubator-openwhisk-composer so it can compare what’s in version control to what in the release candidate. Again this seem to be checking out head which would change over time so it might be possible for it to give inconstant results. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[GitHub] [incubator] ebarboni commented on issue #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ebarboni commented on issue #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#issuecomment-487161758 you're welcome. Sorry I was on another bad typo management typo 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
[GitHub] [incubator] ottlinger merged pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ottlinger merged pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10 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
[GitHub] [incubator] ottlinger commented on issue #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ottlinger commented on issue #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#issuecomment-487161564 Thanks for your contribution :+1: 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
[GitHub] [incubator] ottlinger commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ottlinger commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r279058001 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: + +- a Chair for the new project aka PMC Chair. The Chair will also be appointed an + link:http://www.apache.org/foundation/[Officer] + of the Apache Software Foundation. This allows them +access to official resources of the foundation as well +as granting power to act on behalf of Apache. + +WARNING: Usually once this happens, the secretary will inform the new chair. Occasionally, this will be missed: if more than 72 hours has passed since the Board meeting, it may be worth pinging the board to request confirmation. -The link:#tlp-resolution[resolution] will appoint a Chair for the new -project. The Chair will also be appointed an -link:http://www.apache.org/foundation/[Officer] -of the Apache Software Foundation. This allows them -access to official resources of the foundation as well -as granting power to act on behalf of Apache. +- the initial member of Project Managnement Committees aka PMC member. Review comment: @ebarboni I'd say just commit the changes, should not be a problem. 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: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi - From time to time podlings do not put incubating or incubator in the name. The clutch analysis does catch this in the daily scan of the release distribution areas. On https://incubator.apache.org/clutch/ look down towards the bottom for “Other Issues”. On a podling clutch analysis page these show as: https://incubator.apache.org/clutch/toree.html#errata Regards, Dave > On Apr 25, 2019, at 7:39 PM, Justin Mclean wrote: > > - incubating is missing from name - 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 Dave, Thanks! I’m glad Bertrand has been a help. OpenWhisk is similar to Sling in that there are a number of repositories and release artifacts. Regards, Dave > On Apr 22, 2019, at 3:14 PM, David P Grove wrote: > > > > > On 2019/04/22 19:09:36, Dave Fisher wrote: >> Hi - >> >> I am concerned about an overly automated release process. Please explain > what the role of the Release Manager is in your process? How does the > release manager sign these automatically generated artifacts? How are > release artifacts moved from > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/ to > https://dist.apache.org/repos/dist/release/incubator/openwhisk/ once the > vote is passed? Are there staged artifacts anywhere else like > repository.apache.org? Or to NPM. > > Hi Dave, > > Not sure how much detail is appropriate here. Will quickly summarize > and maybe it makes sense to move any detailed feedback you have to the > OpenWhisk dev list which is cc'ed? Our mentor Bertrand has been actively > involved in helping us refine this process. > > A Release Manager manually initiates each of the major steps in the > process. The gory details can be found at our release repo [1] and the > instructions for the release manager [2]. The basic workflow is that after > the completion of a DISCUSS thread, a Release Manager defines a config.json > that specifies the components being released (names, gitrepos, git commit > hash, version, release candidate number). This config file is then fed > into scripts that generate/sign the artifacts using the Release Manager's > key, push them to the right place in > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/, and generates > an email body for a VOTE thread (this last script is brand new). After a > successful completion of the IPMC vote, the Release Manager initiates the > move from dist/dev to dist/release by running a script on their local > machine that does the svn operations. > > There are no staged artifacts during the voting process outside of > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/. > >> >> BTW - The link to the commit currently leads to a 404. >> > > Noted. Bug in the still-being-worked-on script to generate the email. It > should have been outputting a URL in > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/ not in github. > > --dave > > [1] https://github.com/apache/incubator-openwhisk-release > [2] > https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md - 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)
We do still need one more binding +1 vote from an IMPC member to be able to close this vote and finally make this release. If someone would be willing to either use the rcverify.sh script we use in the OpenWhisk project as described below or otherwise check the artifacts at https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.11.0-incubating-rc2/ using whatever method you prefer and cast a binding vote it would be greatly appreciated. In his previous non-vote in this thread Justin pointed out a file with a short-form license header; it has been fixed in master (for next release). thanks, --dave On 2019/04/26 13:59:27, "David P Grove" wrote: > > > > Justin Mclean wrote on 04/25/2019 10:41:28 PM:> > >> > > 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?> > > Per the original dev list vote email [1]> > > > You can use this UNIX script to download the release and verify the> > checklist below:> > >> > https://gitbox.apache.org/repos/asf?p=incubator-openwhisk-release.git;a=blob_plain;f=tools/rcverify.sh;hb=HEAD> > > >> > > rcverify.sh openwhisk-composer 'OpenWhisk Composer' 0.11.0-incubating rc2> > > Running the referenced script on your local machine with those arguments> > downloads the specified artifacts and produces a log of what was verified> > that is included in our individual votes as in [2].> > > --dave> > > [1]> > https://lists.apache.org/thread.html/71290ca376a3a1ef591c655dfb92ad9f355b5489ae31dc093c0c54bf@%3Cdev.openwhisk.apache.org%3E> > [2]> > https://lists.apache.org/thread.html/940bc4d86675ae4a26d514cf5f6070be86eca9d6077da47c03a1a5b4@%3Cdev.openwhisk.apache.org%3E> >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi Justin The CC-BY 4.0 is included in both NOTICE and LICENSE due to " Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use." Is that is misinterpretation then? Do you consider the GeoJSON not to be binary? (In ./countries) Cheers Bolke Sent from my iPhone > On 26 Apr 2019, at 16:05, Justin Mclean wrote: > > Hi, > >> The GIS data is under CC BY 4.0 see here: >> >> Hence the reference to this license. > > Which should be in LICENSE not NOTICE but not a major issue. > >> According to https://apache.org/legal/resolved.html it is fine to include >> this in binary form (whether it can be as part of a source release I leave >> that up to you, it’s a bit of a grey area to me in this case). > > Which is fine, except it’s not in binary form in the source release. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
[GitHub] [incubator] ebarboni commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ebarboni commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278945492 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: + +- a Chair for the new project aka PMC Chair. The Chair will also be appointed an + link:http://www.apache.org/foundation/[Officer] + of the Apache Software Foundation. This allows them +access to official resources of the foundation as well +as granting power to act on behalf of Apache. + +WARNING: Usually once this happens, the secretary will inform the new chair. Occasionally, this will be missed: if more than 72 hours has passed since the Board meeting, it may be worth pinging the board to request confirmation. -The link:#tlp-resolution[resolution] will appoint a Chair for the new -project. The Chair will also be appointed an -link:http://www.apache.org/foundation/[Officer] -of the Apache Software Foundation. This allows them -access to official resources of the foundation as well -as granting power to act on behalf of Apache. +- the initial member of Project Managnement Committees aka PMC member. Review comment: @ottlinger sorry it's on the next commit. But I miss the workflow maybe I should do a rebase forced push ? 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: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, > The GIS data is under CC BY 4.0 see here: > > Hence the reference to this license. Which should be in LICENSE not NOTICE but not a major issue. > According to https://apache.org/legal/resolved.html it is fine to include > this in binary form (whether it can be as part of a source release I leave > that up to you, it’s a bit of a grey area to me in this case). Which is fine, except it’s not in binary form in the source release. 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 OpenWhisk Composer 0.11.0 (incubating)
Justin Mclean wrote on 04/25/2019 10:41:28 PM: > > 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? Per the original dev list vote email [1] > You can use this UNIX script to download the release and verify the checklist below: > https://gitbox.apache.org/repos/asf?p=incubator-openwhisk-release.git;a=blob_plain;f=tools/rcverify.sh;hb=HEAD > > rcverify.sh openwhisk-composer 'OpenWhisk Composer' 0.11.0-incubating rc2 Running the referenced script on your local machine with those arguments downloads the specified artifacts and produces a log of what was verified that is included in our individual votes as in [2]. --dave [1] https://lists.apache.org/thread.html/71290ca376a3a1ef591c655dfb92ad9f355b5489ae31dc093c0c54bf@%3Cdev.openwhisk.apache.org%3E [2] https://lists.apache.org/thread.html/940bc4d86675ae4a26d514cf5f6070be86eca9d6077da47c03a1a5b4@%3Cdev.openwhisk.apache.org%3E
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Also on [5] and [6] the license location is here https://github.com/syntagmatic/parallel-coordinates which includes divgrid.js in examples/lib as part of the package and from the same author. Cheers Bolke Verstuurd vanaf mijn iPad > Op 26 apr. 2019 om 15:14 heeft Bolke de Bruin het > volgende geschreven: > > Additionally > > [3] Is CC-BY 4.0 as mentioned > [4] is in licenses/ and states the correct license. > [5] [6] ([6] is equal to [9]) are from the same author and the correct > license (BSD-3) is included in licenses/ (see also: > http://bl.ocks.org/syntagmatic/3150059 - scroll down please). > > All above licenses are mentioned in LICENSE.txt > > Other items I leave up to the release manager to answer. > > Bolke. > > Verstuurd vanaf mijn iPad > >> Op 26 apr. 2019 om 10:03 heeft Bolke de Bruin het >> volgende geschreven: >> >> Hi Justin, >> >> The GIS data is under CC BY 4.0 see here: >> >> https://journals.plos.org/plosone/article/file?type=supplementary=info:doi/10.1371/journal.pone.0151586.s002 >> >> Hence the reference to this license. According to >> https://apache.org/legal/resolved.html it is fine to include this in binary >> form (whether it can be as part of a source release I leave that up to you, >> it’s a bit of a grey area to me in this case). >> >> Cheers >> Bolke >> >> >> Verstuurd vanaf mijn iPad >> >>> Op 26 apr. 2019 om 06:20 heeft Sheng Wu het >>> volgende geschreven: >>> >>> 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
[GitHub] [incubator] ebarboni commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ebarboni commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278945492 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: + +- a Chair for the new project aka PMC Chair. The Chair will also be appointed an + link:http://www.apache.org/foundation/[Officer] + of the Apache Software Foundation. This allows them +access to official resources of the foundation as well +as granting power to act on behalf of Apache. + +WARNING: Usually once this happens, the secretary will inform the new chair. Occasionally, this will be missed: if more than 72 hours has passed since the Board meeting, it may be worth pinging the board to request confirmation. -The link:#tlp-resolution[resolution] will appoint a Chair for the new -project. The Chair will also be appointed an -link:http://www.apache.org/foundation/[Officer] -of the Apache Software Foundation. This allows them -access to official resources of the foundation as well -as granting power to act on behalf of Apache. +- the initial member of Project Managnement Committees aka PMC member. Review comment: sorry it's on the next commit. 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
[GitHub] [incubator] ottlinger commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ottlinger commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278941445 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: + +- a Chair for the new project aka PMC Chair. The Chair will also be appointed an + link:http://www.apache.org/foundation/[Officer] + of the Apache Software Foundation. This allows them +access to official resources of the foundation as well +as granting power to act on behalf of Apache. + +WARNING: Usually once this happens, the secretary will inform the new chair. Occasionally, this will be missed: if more than 72 hours has passed since the Board meeting, it may be worth pinging the board to request confirmation. -The link:#tlp-resolution[resolution] will appoint a Chair for the new -project. The Chair will also be appointed an -link:http://www.apache.org/foundation/[Officer] -of the Apache Software Foundation. This allows them -access to official resources of the foundation as well -as granting power to act on behalf of Apache. +- the initial member of Project Managnement Committees aka PMC member. Review comment: @ebarboni the typo is still there. Not sure if @ShaneCurcuru 's additions should be added as well. 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: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Additionally [3] Is CC-BY 4.0 as mentioned [4] is in licenses/ and states the correct license. [5] [6] ([6] is equal to [9]) are from the same author and the correct license (BSD-3) is included in licenses/ (see also: http://bl.ocks.org/syntagmatic/3150059 - scroll down please). All above licenses are mentioned in LICENSE.txt Other items I leave up to the release manager to answer. Bolke. Verstuurd vanaf mijn iPad > Op 26 apr. 2019 om 10:03 heeft Bolke de Bruin het > volgende geschreven: > > Hi Justin, > > The GIS data is under CC BY 4.0 see here: > > https://journals.plos.org/plosone/article/file?type=supplementary=info:doi/10.1371/journal.pone.0151586.s002 > > Hence the reference to this license. According to > https://apache.org/legal/resolved.html it is fine to include this in binary > form (whether it can be as part of a source release I leave that up to you, > it’s a bit of a grey area to me in this case). > > Cheers > Bolke > > > Verstuurd vanaf mijn iPad > >> Op 26 apr. 2019 om 06:20 heeft Sheng Wu het >> volgende geschreven: >> >> 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 >>> >>>
[GitHub] [incubator] ebarboni commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ebarboni commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278936939 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: + +- a Chair for the new project aka PMC Chair. The Chair will also be appointed an + link:http://www.apache.org/foundation/[Officer] + of the Apache Software Foundation. This allows them +access to official resources of the foundation as well +as granting power to act on behalf of Apache. + +WARNING: Usually once this happens, the secretary will inform the new chair. Occasionally, this will be missed: if more than 72 hours has passed since the Board meeting, it may be worth pinging the board to request confirmation. -The link:#tlp-resolution[resolution] will appoint a Chair for the new -project. The Chair will also be appointed an -link:http://www.apache.org/foundation/[Officer] -of the Apache Software Foundation. This allows them -access to official resources of the foundation as well -as granting power to act on behalf of Apache. +- the initial member of Project Managnement Committees aka PMC member. Review comment: addition changes done in commit 2d1c717. 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
[GitHub] [incubator] ShaneCurcuru commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ShaneCurcuru commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278910195 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: + +- a Chair for the new project aka PMC Chair. The Chair will also be appointed an + link:http://www.apache.org/foundation/[Officer] + of the Apache Software Foundation. This allows them +access to official resources of the foundation as well +as granting power to act on behalf of Apache. + +WARNING: Usually once this happens, the secretary will inform the new chair. Occasionally, this will be missed: if more than 72 hours has passed since the Board meeting, it may be worth pinging the board to request confirmation. -The link:#tlp-resolution[resolution] will appoint a Chair for the new -project. The Chair will also be appointed an -link:http://www.apache.org/foundation/[Officer] -of the Apache Software Foundation. This allows them -access to official resources of the foundation as well -as granting power to act on behalf of Apache. +- the initial member of Project Managnement Committees aka PMC member. Review comment: Addition (should have been here originally): > s/act on behalf of Apache./act on behalf of Apache within the scope of their project's activities./ PMC Chairs are only empowered to speak on behalf of their project and to accomplish the duties for their specific project. 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
[GitHub] [incubator] ShaneCurcuru commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ShaneCurcuru commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278909814 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: Review comment: To be more precise: ```suggestion The Board votes on graduation resolutions at their monthly meeting. If the Board votes to pass the resolution, that then appoints the listed Project Management Committee including: ``` Resolutions are formal acts of the ASF, which the board votes to pass (or occasionally defer to a later meeting). Once the board votes, the actions written in the resolution are formally done (like appointing PMC members and the VP officer). 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
[GitHub] [incubator] ebarboni commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ebarboni commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278899569 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: Review comment: can this be said: The board (if the resolution is passed) will appoint Project Managnement Committees composed of 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
[GitHub] [incubator] ottlinger commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ottlinger commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278895353 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: Review comment: typo: Managnement -> Management I personally do not understand the sentence: "The passed will appoint PMC" - is it supposed to be "If passed the newly formed PMC will:"? 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
[GitHub] [incubator] ottlinger commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description
ottlinger commented on a change in pull request #10: INCUBATOR-202 Proposal for enhancing graduation steps description URL: https://github.com/apache/incubator/pull/10#discussion_r278895674 ## File path: pages/guides/transferring.ad ## @@ -38,69 +39,80 @@ themselves. Graduating as New Top Level Project += Board resolution and roster appointment + When graduating to a new project, the process is more complex. Creating a new project requires a -link:http://www.apache.org/foundation/board/calendar.html[resolution] +link:graduation.html#preparing_a_charter[resolution] to be passed by the link:http://www.apache.org/foundation/board/[Board]. -Usually once this happens, the secretary will +You may look at older minutes from the link:http://www.apache.org/foundation/board/calendar.html[calendar] and check for "Establish ProjectName" + +The passed will appoint Project Managnement Committees: + +- a Chair for the new project aka PMC Chair. The Chair will also be appointed an + link:http://www.apache.org/foundation/[Officer] + of the Apache Software Foundation. This allows them +access to official resources of the foundation as well +as granting power to act on behalf of Apache. + +WARNING: Usually once this happens, the secretary will inform the new chair. Occasionally, this will be missed: if more than 72 hours has passed since the Board meeting, it may be worth pinging the board to request confirmation. -The link:#tlp-resolution[resolution] will appoint a Chair for the new -project. The Chair will also be appointed an -link:http://www.apache.org/foundation/[Officer] -of the Apache Software Foundation. This allows them -access to official resources of the foundation as well -as granting power to act on behalf of Apache. +- the initial member of Project Managnement Committees aka PMC member. Review comment: typo: Managnement -> Management 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: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi Justin, The GIS data is under CC BY 4.0 see here: https://journals.plos.org/plosone/article/file?type=supplementary=info:doi/10.1371/journal.pone.0151586.s002 Hence the reference to this license. According to https://apache.org/legal/resolved.html it is fine to include this in binary form (whether it can be as part of a source release I leave that up to you, it’s a bit of a grey area to me in this case). Cheers Bolke Verstuurd vanaf mijn iPad > Op 26 apr. 2019 om 06:20 heeft Sheng Wu het > volgende geschreven: > > 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 >> >>
