For Docker and Nexus, we need to ask the INFRA team to help us create them.
For the release process and distribution, you can refer to[1][2] We need to sort out the dependencies in the project, we can refer to the licensing policy regarding third parties.[3] There are some good aids that can be used[4]. How to assemble LICENSE and NOTICE files, we can refer to [5]: There are other details that we can discuss later on in a new thread specific to the project. [1]https://incubator.apache.org/guides/releasemanagement.html [2]https://incubator.apache.org/guides/distribution.html [3]https://apache.org/legal/resolved.html [4]https://github.com/apache/skywalking-eyes [5]https://infra.apache.org/licensing-howto.html#bundle-asf-product On Mon, Oct 17, 2022 at 2:07 AM Bertil Chapuis <bchap...@gmail.com> wrote: > > > > If you want an idea for tasks, there is an incubation status template > > [1] and I'm just about to copy it so that it appears on the incubator > > site [2]. > > Thanks, I took a little time this afternoon to cleanup the issue tracker and > improve labelling. > > > I would divide the tasks into administration, code, and marketing. On > > the marketing side, it's important to get a basic website up and > > running [3]. > > The current website is published with Jekyll [1]. Github Pages is not > supported by the infrastructure team at apache, but Jekyll is mentioned among > the recommended tools. I logged a couple of issues to discuss and track this > [2,3,4]. > > > In my opinion, a twitter account for the project is > > critical. > > Baremaps is now on twitter ;-) > https://twitter.com/ApacheBaremaps/status/1581698370938474497 > > > The biggest task is the first release. (It's a larger task than you > > can imagine, because we need to deal with things like licensing, key > > signing, tar balls, and votes. But it's a good opportunity for the > > community to work together.) > > The releases are currently published on maven central with the maven release > plugin. Is there a place where we can find information regarding the > non-technical issues associated with a release (e.g., licensing, etc.)? We > can discuss this in the following issue [5]. > > I guess we should refactor the package structure from com.baremaps to > org.apache.baremaps before creating new branches . Is now a good time? > > [1] https://github.com/baremaps/baremaps/tree/main/docs > [2] https://github.com/baremaps/baremaps/issues/489 > [3] https://github.com/baremaps/baremaps/issues/490 > [4] https://github.com/baremaps/baremaps/issues/491 > [5] https://github.com/baremaps/baremaps/issues/492 -- Best wishes！ CalvinKirs --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org For additional commands, e-mail: dev-h...@baremaps.apache.org
