Changing package names is probably harmless. But file headers and copyright notices should not be changed until after IP transfer (repository migration).
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. Are there any reasons why we can't start the repository migration? 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
