Regarding the GPL/LGPL dependencies. It is true that an ASF top-level project cannot make releases with those dependencies. But these issues can be solved during incubation. Incubating projects have some leeway while making their first releases. I suggest that you do not try to solve the GPL/LGPL problems now.
Regarding copyright. If you changed a copyright notice from ‘Copyright 2020’ to ‘Copyright 2022’ that is a misrepresentation, because you are claiming that all of the code in that file was written in 2022 and therefore (assuming a hypothetical 50 years of copyright protection) would be protected by copyright until 2072. When in fact some of the code would expire in 2070. Long story short, you should add years to the copyright notice, not modify/remove them. But dealing with copyright notices is another thing that is best done during incubation. Apache policy is to move copyright notices into NOTICE files. Again, best done during incubation. > On Oct 21, 2022, at 1:19 AM, Bertil Chapuis <bchap...@gmail.com> wrote: > > >>> Changing package names is probably harmless. But file headers and >>> copyright notices should not be changed until after IP transfer >>> (repository migration). > > The license header was changed before this discussion (19 days ago). The > LICENSE.header file contained an outdated copyright notice (2020) that I > simply removed. I can rollback these changes if needed, but as the LICENSE > file was present from the beginning of the projet, can we assume that > everyone agreed with these terms? > > Along this line, the steps needed to address licensing issues and IP > clearance during incubation remain a bit vague to me and I created an issue > to track them. > https://github.com/baremaps/baremaps/issues/502 > > In terms of license, all the LGPL dependencies have been replaced last > summer. My main concern is related to the osmpbf data format. The protobuf > descriptor used by this format is released under the terms of the GNU Lesser > General Public License. In my understanding this file should not be included > in our release, however, we can include the source files we generate with it. > Is this interpretation correct? > https://github.com/baremaps/baremaps/blob/main/baremaps-osm/src/main/proto/osmformat.proto > > >>> I'm not 100% sure, but I don't think that GitHub PRs and issues will >>> come through the IP transfer process. If so, people may need to open >>> new PRs once the repo is in Apache. >> don't worry, the Issue PR will all move over, just the upstream and >> downstream relationship changes a little bit, but that doesn't matter >> at all. > > Good to know, thank you. > >>> >>> Are there any reasons why we can't start the repository migration? >> I see the secretary has confirmed everyone's ICLA. I think we can >> start moving now. >> https://issues.apache.org/jira/browse/INFRA-23762 > > I think we can start the migration and I notified Drew Foulks two days ago. I > tried to invite him in the github organization, but I havn’t found his > username on github. > > Best, > > Bertil > > > >>> >>> The status page, https://incubator.apache.org/projects/baremaps.html, >>> is probably a good guide to these tasks. >>> >>> On Wed, Oct 19, 2022 at 8:58 AM Antoine Drabble >>> <antoine.drab...@gmail.com> wrote: >>>> >>>> Hi Bertil, >>>> >>>> This is great news for the ICLAs! >>>> >>>> I have made a review of your PR regarding the package name and the code >>>> style. I hope we can merge it as soon as possible to avoid conflicts. >>>> >>>> Otherwise I'm looking forward to our meeting on the 25th. >>>> >>>> Have a good day, >>>> Antoine Drabble >>>> >>>> On Tue, 18 Oct 2022 at 22:45, Bertil Chapuis <bchap...@gmail.com> wrote: >>>> >>>>> Hello Everyone, >>>>> >>>>> I think we received all the ICLAs and we will soon be able to leave the >>>>> baremaps github organisation for a new home. >>>>> >>>>> In preparation for the changes ahead, I renamed the root package into >>>>> org.apache.baremaps and updated the code style. These changes affect most >>>>> source code and configuration files in the repository. I tried the >>>>> snapshot >>>>> release locally and everything works well. >>>>> >>>>> https://github.com/baremaps/baremaps/pull/496 >>>>> >>>>> If you dream of a large cosmetic change in the codebase, now is the time >>>>> to discuss it ;) We have a short window of time with few branches and pull >>>>> requests open. >>>>> >>>>> Best regards, >>>>> >>>>> Bertil >>>>> >>>>> >>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org >>> For additional commands, e-mail: dev-h...@baremaps.apache.org >>> >> >> >> -- >> Best wishes！ >> CalvinKirs >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org >> For additional commands, e-mail: dev-h...@baremaps.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org For additional commands, e-mail: dev-h...@baremaps.apache.org
