Re: [QUESTION] do pom files need to have a license header
Hi, In general, it is best to have ASF headers on all possible files. That way if they become separated from the source bundle, people will know what license it’s under and where it comes from. (Also see [3]) People reviewing releases are less likely to ask if these are 3rd party files. The policy [1] does list some files that don’t require a header but pom files are not in that list. [2] However given the files are autogenerated they would probably not be covered by copyright and not need a header. Kind Regards, Justin 1. https://www.apache.org/legal/src-headers.html 2. https://www.apache.org/legal/src-headers.html#faq-exceptions 3. https://www.apache.org/legal/src-headers.html#faq-whyheader - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [QUESTION] do pom files need to have a license header
The source archive/tarball includes a LICENSE and NOTICE which specifies the license for that artifact. The individual files' header simply reinforces that. In some release artifacts, individual files have a slightly different license (eg. a third-party MIT-licensed piece of source), which definitely needs to be recorded within those files. IMO, it is just fine for the pom file to not contain a license header, since the entire distribution is licensed as ALv2. Cheers, -g On Sun, Jan 29, 2023 at 11:31 AM PJ Fanning wrote: > Hi everyone, > > The Apache Pekko builds use the sbt tool for building and this generates > pom files for us. They do not include any headers (example [1]). > It seems the norm to add an XML comment with Apache License info (example > from log4j [2]). > Does the Pekko team need to fix this or is it just a nicety to have the > license header in the pom files? If the answer is that we do need to fix > this, does this also apply to other published files? sbt generates and > publishes a 'buildinfo' file as part of the maven publish (example [2]). > > Regards, > PJ > > > [1] > https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.pom > [2] > https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/2.19.0/log4j-api-2.19.0.pom > [3] > https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.buildinfo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache EventMesh (incubating) 1.8.0-rc2
+1, I have checked: [√] 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 EventMesh repo. [√] All files have license headers if necessary. [√] No compiled archives bundled in source archive. At 2023-01-30 11:05:25, "杨军" wrote: >+1, I have checked: > > >[√] 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 EventMesh repo. >[√] All files have license headers if necessary. >[√] No compiled archives bundled in source archive. > >发自我的 iPhone > >> 在 2023年1月29日，16:08，walterzywei 写道： >> >> Thank you all for your check and vote , and I also want to carry over >> the vote by Justin Mclean and Francois Fpapon from dev, so I would >> like to send the result later. >> >> Thanks, >> Your EventMesh Release Manager >> >> Alex Luo 于2023年1月28日周六 23:02写道： >>> >>> +1, I have checked: >>> >>> >>> [√] 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 EventMesh repo. >>> [√] All files have license headers if necessary. >>> [√] No compiled archives bundled in source archive. >>> >>> Alex >>> On 2023/01/28 14:32:53 Mengyang Tang wrote: +1, I have checked: [√] 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 EventMesh repo. [√] All files have license headers if necessary. [√] No compiled archives bundled in source archive. At 2023-01-18 20:23:00, "walterzywei" wrote: > Hello Incubator Community, > > This is a call for a vote to release Apache EventMesh(Incubating) > version 1.8.0-rc2 > > The Apache EventMesh community has voted on and approved a > proposal to release > Apache EventMesh(Incubating) version 1.8.0-rc2 > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > EventMesh community vote thread: > • https://lists.apache.org/thread/z6p2kxw2l1zv641fsx4bhjgtmdh4xwyg > > Vote result thread: > • https://lists.apache.org/thread/16js8nnlbypy203snxk2fqzt3vjz1yg5 > > The release candidate: > • https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.8.0-rc2 > > Git tag for the release: > • https://github.com/apache/incubator-eventmesh/tree/v1.8.0-rc2 > Release notes: > • https://eventmesh.apache.org/events/release-notes/v1.8.0 > > The artifacts signed with PGP key > 16D5190EA34AC32AE3CE05A753FF44C181774D3F, corresponding to > walterzy...@apache.org, that can be found in keys file: > • https://downloads.apache.org/incubator/eventmesh/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, > On behalf of Apache EventMesh(Incubating) community > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org >>> For additional commands, e-mail: dev-h...@eventmesh.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
Re: [VOTE] Release Apache EventMesh (incubating) 1.8.0-rc2
+1, I have checked: [√] 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 EventMesh repo. [√] All files have license headers if necessary. [√] No compiled archives bundled in source archive. 发自我的 iPhone > 在 2023年1月29日，16:08，walterzywei 写道： > > Thank you all for your check and vote , and I also want to carry over > the vote by Justin Mclean and Francois Fpapon from dev, so I would > like to send the result later. > > Thanks, > Your EventMesh Release Manager > > Alex Luo 于2023年1月28日周六 23:02写道： >> >> +1, I have checked: >> >> >> [√] 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 EventMesh repo. >> [√] All files have license headers if necessary. >> [√] No compiled archives bundled in source archive. >> >> Alex >> >>> On 2023/01/28 14:32:53 Mengyang Tang wrote: >>> +1, I have checked: >>> >>> >>> [√] 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 EventMesh repo. [√] All files have license headers if necessary. [√] >>> No compiled archives bundled in source archive. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> At 2023-01-18 20:23:00, "walterzywei" wrote: Hello Incubator Community, This is a call for a vote to release Apache EventMesh(Incubating) version 1.8.0-rc2 The Apache EventMesh community has voted on and approved a proposal to release Apache EventMesh(Incubating) version 1.8.0-rc2 We now kindly request the Incubator PMC members review and vote on this incubator release. EventMesh community vote thread: • https://lists.apache.org/thread/z6p2kxw2l1zv641fsx4bhjgtmdh4xwyg Vote result thread: • https://lists.apache.org/thread/16js8nnlbypy203snxk2fqzt3vjz1yg5 The release candidate: • https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.8.0-rc2 Git tag for the release: • https://github.com/apache/incubator-eventmesh/tree/v1.8.0-rc2 Release notes: • https://eventmesh.apache.org/events/release-notes/v1.8.0 The artifacts signed with PGP key 16D5190EA34AC32AE3CE05A753FF44C181774D3F, corresponding to walterzy...@apache.org, that can be found in keys file: • https://downloads.apache.org/incubator/eventmesh/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, On behalf of Apache EventMesh(Incubating) community - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org >> For additional commands, e-mail: dev-h...@eventmesh.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
[ANNOUNCE] Apache EventMesh (incubating) 1.8.0 available
Hi all, Apache EventMesh (incubating) Team is glad to announce the new release of Apache EventMesh (incubating) 1.8.0. Apache EventMesh (incubating) is a dynamic cloud-native eventing infrastructure used to decouple the application and backend middleware layer, which supports a wide range of use cases that encompass complex multi-cloud, widely distributed topologies using diverse technology stacks. Download Links: https://eventmesh.apache.org/download/ Release Notes: https://eventmesh.apache.org/events/release-notes/v1.8.0/ Website: https://eventmesh.apache.org/ EventMesh Resources: - Issue: https://github.com/apache/incubator-eventmesh/issues - Mailing list: d...@eventmesh.apache.org Apache EventMesh (incubating) Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[QUESTION] do pom files need to have a license header
Hi everyone, The Apache Pekko builds use the sbt tool for building and this generates pom files for us. They do not include any headers (example [1]). It seems the norm to add an XML comment with Apache License info (example from log4j [2]). Does the Pekko team need to fix this or is it just a nicety to have the license header in the pom files? If the answer is that we do need to fix this, does this also apply to other published files? sbt generates and publishes a 'buildinfo' file as part of the maven publish (example [2]). Regards, PJ [1] https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.pom [2] https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/2.19.0/log4j-api-2.19.0.pom [3] https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.buildinfo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Release Apache EventMesh (incubating) 1.8.0-rc2
Hi all, Thanks for reviewing and voting for Apache EventMesh(Incubating) version 1.8.0-rc2 release, I am happy to announce the release voting has passed with 3 binding votes, no +0 or -1 votes. Binding votes are from IPMC +1 Justin Mclean +1 Francois Fapon +1 li gang Non-binding votes: +1 Mengyang Tang +1 Alex Luo No further +0 votes and -1 votes The voting thread is: • https://lists.apache.org/thread/094cqglk2jsjg1osb5d92n73l9qnknvn Many thanks for all our mentors helping us with the release procedure, and all IPMC helped us to review and vote for Apache EventMesh(Incubating) release.I will be working on publishing the artifacts soon. Thanks, On behalf of Apache EventMesh(Incubating) community - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Re:[VOTE] Release Apache EventMesh (incubating) 1.8.0-rc2
Thank you all for your check and vote , and I also want to carry over the vote by Justin Mclean and Francois Fpapon from dev, so I would like to send the result later. Thanks, Your EventMesh Release Manager Alex Luo 于2023年1月28日周六 23:02写道： > > +1, I have checked: > > > [√] 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 EventMesh repo. > [√] All files have license headers if necessary. > [√] No compiled archives bundled in source archive. > > Alex > > On 2023/01/28 14:32:53 Mengyang Tang wrote: > > +1, I have checked: > > > > > > [√] 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 EventMesh repo. [√] All files have license headers if necessary. [√] > > No compiled archives bundled in source archive. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > At 2023-01-18 20:23:00, "walterzywei" wrote: > > >Hello Incubator Community, > > > > > >This is a call for a vote to release Apache EventMesh(Incubating) > > >version 1.8.0-rc2 > > > > > >The Apache EventMesh community has voted on and approved a > > >proposal to release > > >Apache EventMesh(Incubating) version 1.8.0-rc2 > > > > > >We now kindly request the Incubator PMC members review and vote on this > > >incubator release. > > > > > >EventMesh community vote thread: > > >• https://lists.apache.org/thread/z6p2kxw2l1zv641fsx4bhjgtmdh4xwyg > > > > > >Vote result thread: > > >• https://lists.apache.org/thread/16js8nnlbypy203snxk2fqzt3vjz1yg5 > > > > > >The release candidate: > > >• https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.8.0-rc2 > > > > > >Git tag for the release: > > >• https://github.com/apache/incubator-eventmesh/tree/v1.8.0-rc2 > > >Release notes: > > >• https://eventmesh.apache.org/events/release-notes/v1.8.0 > > > > > >The artifacts signed with PGP key > > >16D5190EA34AC32AE3CE05A753FF44C181774D3F, corresponding to > > >walterzy...@apache.org, that can be found in keys file: > > >• https://downloads.apache.org/incubator/eventmesh/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, > > >On behalf of Apache EventMesh(Incubating) community > > > > > >- > > >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > >For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@eventmesh.apache.org > For additional commands, e-mail: dev-h...@eventmesh.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
