Podling Baremaps Report Reminder - January 2023

[kirs]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 January 2023.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, January 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/January2023

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Podling Baremaps Report Reminder - January 2023

[kirs]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 January 2023.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, January 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/January2023

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Podling Baremaps Report Reminder - January 2023

[kirs]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 January 2023.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, January 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/January2023

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Podling Baremaps Report Reminder - June 2023

[kirs]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 21 June 2023.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, June 07).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/June2023

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Podling Baremaps Report Reminder - June 2023

[kirs]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 21 June 2023.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, June 07).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/June2023

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Podling Baremaps Report Reminder - December 2023

[kirs]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 20 December 2023.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, December 06).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/December2023

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: Welcome to Apache Baremaps!

[Calvin Kirs]

Hi Bertrand,

Thanks for your help, we don't seem to have created any other mail
groups yet. Do you have an application?
If not I can go ahead and do it, regarding the project code repository
transfer, this will be done after the ICLA submission is done, we
already have a ticket.

On Tue, Oct 11, 2022 at 3:03 PM Bertrand Delacretaz
 wrote:
>
> Hi,
>
> Baremaps was accepted in the Incubator yesterday, we're reading to
> start discussing the next steps!
>
> The following pages have information on how to setup the rest of the
> podling's infrastructure:
> - https://incubator.apache.org/cookbook/#podling_infrastructure_setup
> - https://infra.apache.org/infra-incubator.html
>
> -Bertrand
>
> -
> 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

Re: Welcome to Apache Baremaps!

[Calvin Kirs]

On Tue, Oct 11, 2022 at 4:18 PM Bertrand Delacretaz
 wrote:
>
> Hi Calvin,
>
> Le mar. 11 oct. 2022 à 09:26, Calvin Kirs  a écrit :
> > we don't seem to have created any other mail
> > groups yet. Do you have an application?...
>
> I haven't requested them yet, if you want to do that you're welcome!
>
> However I'm not sure if a users mailing list is useful right now,
> maybe we can start with just dev (+commits etc.) and see if there's a
> real need?
Hi, I have requested the creation of commits and privates, now we just
need to wait for the creation to succeed.
 As for the user, let the team decide.
>
> I'll inform people in the general@incubator.a.o thread about this list
> so things can get started.
>
> -Bertrand
>
> -
> 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

Re: Welcome to Apache Baremaps!

[Calvin Kirs]

Hi Bertil,

Could you contact other mentors and initial committers to subscribe to
the mailing list(dev and private)?
Then we can start the ICLA submission.



On Tue, Oct 11, 2022 at 4:48 PM Calvin Kirs  wrote:
>
> On Tue, Oct 11, 2022 at 4:18 PM Bertrand Delacretaz
>  wrote:
> >
> > Hi Calvin,
> >
> > Le mar. 11 oct. 2022 à 09:26, Calvin Kirs  a écrit :
> > > we don't seem to have created any other mail
> > > groups yet. Do you have an application?...
> >
> > I haven't requested them yet, if you want to do that you're welcome!
> >
> > However I'm not sure if a users mailing list is useful right now,
> > maybe we can start with just dev (+commits etc.) and see if there's a
> > real need?
> Hi, I have requested the creation of commits and privates, now we just
> need to wait for the creation to succeed.
>  As for the user, let the team decide.
> >
> > I'll inform people in the general@incubator.a.o thread about this list
> > so things can get started.
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
> > For additional commands, e-mail: dev-h...@baremaps.apache.org
> >
>
>
> --
> Best wishes！
> CalvinKirs



--
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: Welcome to Apache Baremaps!

[Calvin Kirs]

Hi,

We don't need an SGA or CCLA, you mentioned in your proposal that this
is a personal project and therefore the project is owned by you.

Everyone else (init committers) needs to submit an ICLA except you and
Josh (your ICLAs exist).
Please note that ICLA should send it to secret...@apache.org. and CC
priv...@baremaps.apache.org.(needs to sent by the Committer itself)

On Wed, Oct 12, 2022 at 2:50 PM Bertil Chapuis  wrote:
>
> Hello Calvin,
>
> Yes, I will do that today. Is the following form the one I should send to all 
> the committers?
> https://www.apache.org/licenses/icla.pdf
>
> INFRA-23762 also mention an SGA. From what I read, sending all the ICLA 
> should be sufficent. Is that right?
> https://incubator.apache.org/guides/ip_clearance.html
>
> Thank you for your help,
>
> Bertil
>
> > On 12 Oct 2022, at 06:46, Calvin Kirs  wrote:
> >
> > Hi Bertil,
> >
> > Could you contact other mentors and initial committers to subscribe to
> > the mailing list(dev and private)?
> > Then we can start the ICLA submission.
> >
> >
> >
> > On Tue, Oct 11, 2022 at 4:48 PM Calvin Kirs  wrote:
> >>
> >> On Tue, Oct 11, 2022 at 4:18 PM Bertrand Delacretaz
> >>  wrote:
> >>>
> >>> Hi Calvin,
> >>>
> >>> Le mar. 11 oct. 2022 à 09:26, Calvin Kirs  a écrit :
> >>>> we don't seem to have created any other mail
> >>>> groups yet. Do you have an application?...
> >>>
> >>> I haven't requested them yet, if you want to do that you're welcome!
> >>>
> >>> However I'm not sure if a users mailing list is useful right now,
> >>> maybe we can start with just dev (+commits etc.) and see if there's a
> >>> real need?
> >> Hi, I have requested the creation of commits and privates, now we just
> >> need to wait for the creation to succeed.
> >> As for the user, let the team decide.
> >>>
> >>> I'll inform people in the general@incubator.a.o thread about this list
> >>> so things can get started.
> >>>
> >>> -Bertrand
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
> >>> For additional commands, e-mail: dev-h...@baremaps.apache.org
> >>>
> >>
> >>
> >> --
> >> Best wishes！
> >> CalvinKirs
> >
> >
> >
> > --
> > Best wishes！
> > CalvinKirs
>


-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: Baremaps joins the Apache Incubator

[Calvin Kirs]

On Sat, Oct 15, 2022 at 8:27 AM Josh Fischer  wrote:
>
> I think it would be good to start deciding what the initial tasks are for
> us to start integrating into Apache infra.  E.g. website, issues tracking,
> github org transfer etc.  Might we handle this in the call that Julian was
> talking about?
Hi,

Development around the code can still be done in the original
repository, we are waiting for the ICLA ready before transferring it,
Bertil has already created a ticket[1].

If the team has time, I would recommend going ahead and doing the
project name determination first [2], this is very important, if is
ok, submit the ticket early for the brand team to handle.

If there is time, we may need a meeting to present how things work at Apache.

[1]https://issues.apache.org/jira/browse/INFRA-23762
[2] https://incubator.apache.org/guides/names.html#name-search
>
> - Josh
>
>
>
> On Fri, Oct 14, 2022 at 9:35 AM George Percivall 
> wrote:
>
> > Bertil,
> >
> > Congratulations on getting Baremaps accepted in the Apache Incubator.
> >
> > I encourage others on this list to take a look and give comments to the
> > Baremaps team.
> >
> >
> > George Percivall
> > GeoRoundtable 
> >
> > > On Oct 14, 2022, at 9:37 AM, Bertil Chapuis  wrote:
> > >
> > > Hello Geospatial,
> > >
> > > I’m really excited to announce that Baremaps has been accepted in the
> > Incubator.
> > >
> > > As stated in the proposal [1], Baremaps is a toolkit and a set of
> > infrastructure components for creating, publishing, and operating online
> > maps. In addition to learning the Apache Way our goals are:
> > > - to grow a community and attract new contributors;
> > > - to release a customizable attribution-free map schema and style;
> > > - to publish a tiled world map in different formats (mvt, png, 3D Tiles
> > Next, etc.);
> > > - to release additional services and components (IP to location,
> > location search, etc.).
> > >
> > > Do not hesitate to check the status of our ongoing effort to create
> > vector tiles based on OpenStreetMap data [2].
> > >
> > > Our main challenge will be to form and grow a community around the
> > project. Do not hesitate to share your thoughts here or in our dev mailing
> > list [3]. We are eager to learn more about your use cases and to join the
> > Geospatial community at Apache.
> > >
> > > Best regards,
> > >
> > > Bertil Chapuis
> > >
> > > [1]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal
> > > [2] https://demo.baremaps.com/
> > > [3] https://lists.apache.org/list.html?dev@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

Re: Baremaps joins the Apache Incubator

[Calvin Kirs]

On Sat, Oct 15, 2022 at 7:13 PM Bertrand Delacretaz
 wrote:
>
> Hi,
>
> Le sam. 15 oct. 2022 à 02:27, Josh Fischer  a écrit :
> > ...I think it would be good to start deciding what the initial tasks are for
> > us to start integrating into Apache infra.  E.g. website, issues tracking,
> > github org transfer etc.  Might we handle this in the call that Julian was
> > talking about?..
>
> ...or asynchronously on this list, just start new threads for the
> relevant topics.
+1
>
> -Bertrand
>
> -
> 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

Re: Baremaps joins the Apache Incubator

[Calvin Kirs]

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  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

Re: Kick-off meeting

[Calvin Kirs]

Hi Julian,

Thank you. I'm not sure for now, but if I happen to have the time then
I will attend.

On Sun, Oct 16, 2022 at 8:18 AM Julian Hyde  wrote:
>
> I'd like to schedule a video meeting to kick off the incubation
> process. Previous projects that I have mentored have found it useful:
> a chance for initial committers and mentors to meet each other, a
> chance for everyone to ask all of the questions that may be on your
> mind, and a chance for us folks at the ASF to talk about the Apache
> Way and why it is important. (If you think the Apache Way is about
> writing well-documented, high performance code you might be
> surprised.)
>
> Attendance is not mandatory, but it would be great if most of you
> (mentors, initial committers) could attend. Also, if there is a
> stakeholder sponsoring your work (a manager, a research supervisor, or
> a spouse who will be looking after the kids while you write code) they
> are welcome to attend as well. They might be interested to find out
> what Apache is all about.
>
> So, let's find a time that is convenient for everyone who wishes to
> attend. I'm in California on Pacific time, but I suspect that the
> majority of initial committers are on Central European time. Is anyone
> in an east asian time zone (China, India, Australia)? Is 1800 UTC (8pm
> in France, 10am in California, 1am in China) a good time for everyone?
> I could do as early as 1500 UTC (7am California, 5pm France) or as
> late as 0500 UTC (10pm California, 7am France).
>
> How about this Thursday (20th October) or the following Tuesday (25th
> October) at 1800 UTC?
>
> If those times/dates don't work, please reply with your preferred
> dates and times of day.
>
> Julian
>
> -
> 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

Re: Code style and root package

[Calvin Kirs]

On Wed, Oct 19, 2022 at 2:44 PM Julian Hyde  wrote:
>
> 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.
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.
>
> 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
>
> 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
>  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  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

Re: Code style and root package

[Calvin Kirs]

On Fri, Oct 21, 2022 at 3:19 AM Bertil Chapuis  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
This is not allowed. even though you use an automatically generated
file, essentially its license does not change.
>
>
> >> 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
> >>  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  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
>


-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: rethink of the Readme.md at the root of the project

[Calvin Kirs]

+1 to keeping baremaps as the name,

btw, as I mentioned before, If the final discussion is unanimous, then
it's best to submit a ticket to the brand team to approve the name as
soon as possible.

On Thu, Oct 27, 2022 at 11:43 PM Josh Fischer  wrote:
>
> +1 to keeping baremaps as the name.
>
> On Thu, Oct 27, 2022 at 10:04 AM Bertil Chapuis  wrote:
>
> >
> >
> > > On 27 Oct 2022, at 15:32, Josh Fischer  wrote:
> > >
> > > Either is fine with me, Would you give context on why you chose
> > > Baremaps or why'd you like to change it to Warbler?  What is the
> > > meaning behind them?
> >
> > Originally, I thought that we would have to release the domain names (
> > baremaps.com, baremaps.org, baremaps.net) while entering the incubator
> > and I was worried that someone else may register them. Therefore, we
> > initiated a discussion about the name. Eventually, as there is no trademark
> > on baremaps, we submitted the proposal with this name without finishing the
> > discussion.
> >
> > If there is no other reaction to this thread I suggest that we simply keep
> > the baremaps name.
> >
> >
> > --
> Sent from A Mobile Device



-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: rethink of the Readme.md at the root of the project

[Calvin Kirs]

On Thu, Oct 27, 2022 at 9:32 PM Josh Fischer  wrote:
>
> On Wed, Oct 26, 2022 at 8:00 AM Bertil Chapuis  wrote:
> >
> >
> >
> > > On 26 Oct 2022, at 13:22, Antoine Drabble  
> > > wrote:
> > >
> > > 1. I like the logo at the start, it looks more welcoming. That is probably
> > > another topic, but should we try to find a good logo, or is the logo on 
> > > the
> > > Baremaps website our official logo? I really liked the DALL-E
> > > warbler images, maybe we could make a bird logo out of this?
> >
> > The name is probably something the community should discuss and vote for. 
> > Once the final name is set we can launch a contest on 99designs or on 
> > another platform to create a logo.
> I don't think this is necessary.  Unless you feel strongly about it.
> >
> > Josh, one difficulty most of us have as non-native english speakers is to 
> > know if a name sounds good. What do you think of Apache Baremaps or Apache 
> > Warbler?
>
> Either is fine with me, Would you give context on why you chose
> Baremaps or why'd you like to change it to Warbler?  What is the
> meaning behind them?
> >
> > > 2. Starting with "What is Baremaps" or "What can be accomplished with
> > > Baremaps" is very important I think. I imagine that as a new project in
> > > incubation, many people will just come to see what Baremaps is and leave 
> > > as
> > > soon as they know what it does.
> >
> > Yes, but we don’t want them to leave without doing something.
>
> Being able to get people to engage in the project easily is important.
> >
> > > 3. Link to the live demo for people who quickly want to take a look. If we
> > > add too much information before this, we might lose the reader's 
> > > attention.
> >
> > Yes.
> >
> > > 4. "Getting Started" or "Quick Start". Here I think we should redirect to
> > > other pages. As Bertil pointed out, some people will just want to use the
> > > CLI from a release and use a Postgis database that runs on Docker or
> > > Kubernetes. In some use cases, you don't need a postgis database. There
> > > will be other people that want to compile the code in an IDE.
> >
> > It looks like many projects have a landing page and publish documentation 
> > for releases. Another nice reference is Apache Ignite[1].
>
> I like when projects have a "quickstart" section for users and
> "developer" section for people who want to go deeper.
> >
> > > 5. The other sections could be useful as well such as "How to contribute",
> > > "Roadmap", "Community" (link to the mailing list maybe), "License"...
> >
> > Yes. Also, Apache has some guidelines and a checklist for web sites [2]
> >
> > Josh, do you have experience with the infrastructure for web sites at 
> > Apache?
> I do. There are some things that need to be done to the website for
> compliance Apache (for sure), it looks like [2] outlines most of it.
If you need any help, feel free to contact me.
> >
> >
> > [1] https://ignite.apache.org/
> > [2] https://github.com/baremaps/baremaps/issues/489
> >
> >
> >
> > > [1] https://github.com/apache/incubator-devlake
> > >
> > > On Wed, 26 Oct 2022 at 11:43, Andrea Borghi <
> > > andreafrancesco.bor...@gmail.com> wrote:
> > >
> > >> - Were there parts of the documentation/examples that you had difficulty
> > >> understanding?
> > >>
> > >> it's more a problem to find them easily then understanding IMHO.
> > >>
> > >>
> > >> - Cartographer wants to create maps and developers want to code. Should 
> > >> we
> > >> make have two different quick start guides?
> > >>
> > >> that's a good point!
> > >>
> > >>
> > >> On 10/26/22 11:40, Bertil Chapuis wrote:
> >  What do you think?
> > >>> It's a good idea, the documentation should help people get started
> > >> quickly. The migration to Apache is also an opportunity to revise the web
> > >> site [1].
> > >>>
> > >>> Some additional thoughts/questions:
> > >>> - The live reloading feature (dev mode) is quite unique but often goes
> > >> under the radar. Should we make a gif or a video?
> > >>> - Cartographer wants to create maps and developers want to code. Should
> > >> we make have two different quick start guides?
> > >>> - Were there parts of the documentation/examples that you had difficulty
> > >> understanding?
> > >>>
> > >>> [1] https://github.com/baremaps/baremaps/issues/491
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >> -
> > >> 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
>


-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: Baremaps joins the Apache Incubator

[Calvin Kirs]

On Sat, Nov 5, 2022 at 9:04 PM Bertil Chapuis  wrote:
>
> Thank your Calvin, I went through the references and created a checklist for 
> the first release [1].
>
> Some of the time consuming points have been addressed before submitting the 
> proposal (e.g. replacing LGPL dependencies by Apache compatible 
> alternatives). However, we still have a lot of work and verifications to make 
> before the first release. I hope this ticket can help us track progress.

Well done! after everything is done, I can check it out.
>
> [1] https://github.com/baremaps/baremaps/issues/492
>
> > On 17 Oct 2022, at 04:54, Calvin Kirs  wrote:
> >
> > 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  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
> >
>


-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: Draft of the release process

[Calvin Kirs]

Hi,

We are missing disclaimers[1].

We should not include binary code in the source code, I think you
forgot to exclude it(*.jar) when you packaged the source code.
(btw,maven-wrapper is donated to ASF with a version upgraded, we
better upgrade to the new version 3.1.x which was released under the
ASF umbrella)

We usually include a RELEASE-NOTE or CHANGE-LOG in the source package.

Here is a complete release process[2][3][4]. maybe it will be useful.

[1]https://incubator.apache.org/policy/incubation.html#disclaimers
[2]https://incubator.apache.org/guides/releasemanagement.html#best-practice
[3]https://www.apache.org/legal/release-policy.html#what
[4]https://infra.apache.org/release-distribution

On Mon, Nov 21, 2022 at 6:24 AM Julian Hyde  wrote:
>
> Thanks for creating a process. Now we have a process, we can iterate.
> A few thoughts.
>
> 1. On terminology. The release itself consists of the source code,
> literally the src.tar.gz file. People incorrectly use the term 'binary
> release' but the binaries are just artifacts generated from the
> release.
>
> Part of the reason that binaries are not part of the release is that
> it's only practical to vote on source code. What you have done here,
> generating and signing binaries from the source code, is about the
> best we can do.
>
> An Apache project MAY distribute binary artifacts with a release.
> Since Baremaps is a Java project, I would recommend deploying the jars
> to Maven Central. There are Maven plugins to stage the jars in
> Apache's repository so that people can inspect them during the vote.
>
> 2. On process. The release manager will send an email to vote on the
> artifacts. The email contains the hashes of the objects (to prevent,
> among other things, a man-in-the-middle attack where a server spoofs
> github.com), and instructions to verify the artifacts.
>
> As a mentor, I generally recommend that the first release is source
> only, and therefore you would not mention the binary artifacts in the
> release vote.
>
> 3. On the contents of the release. I noticed a few errors in the files:
>  * the LICENSE file still contains its appendix; you should remove it;
>  * in NOTICE, '2022 and onwards' should be '2022';
>  * there will need to be a DISCLAIMER file noting the incubating status;
>  * maven-wrapper.jar should not be in the source distro (see
> https://issues.apache.org/jira/browse/LEGAL-570);
>  * I strongly recommend that there is a README or README.txt file,
> written for the person who has just downloaded and unzipped the tar
> ball, describing what they have downloaded (including the version) and
> how to build it (yes, it's unfortunate that this file clashes with the
> README.md required by GitHub);
>  * I would add headers to every text file that supports it, e.g.
> pom.xml, READM.md, baremaps.bat; there is an argument to skip for
> files where size is important, e.g. .js files that won't be minified;
>  * Are there any generated files in the source code?
> maplibre-gl-inspect.js and schema.db.
>
> Errors are expected at this point. I'm sure I will find many more when
> there is a release candidate. :)
>
> 4. On licensing. The NOTICE file looks in fairly good shape. But I
> think we will need to audit the various test data sets.
>
> 5. On the location. Generally RMs stage the files into Apache
> subversion before a release vote. This ensures that the artifacts
> cannot be accidentally updated or deleted. (It also makes it easier
> for me, because I can just do 'svn update' on my directory that maps
> to https://dist.apache.org/repos/dist/dev/incubator/baremaps.)
>
> Lastly, I recommend that java classes have javadoc, without exception.
> (This advice pertains to the software development process, not
> releases, so feel free to ignore it.) Javadoc is a great place to
> document the purpose of a class; not just what it does, but why it is
> necessary, how it works, how you should use it, and why we put it in
> this place. If contributors see classes without javadoc they will
> contribute classes without javadoc, so if you start badly, things will
> only get worse over time.
>
> Julian
>
> On Fri, Nov 18, 2022 at 9:33 AM Bertil Chapuis  wrote:
> >
> > Hello Everyone,
> >
> > The following draft release has been generated with github actions:
> > https://github.com/apache/incubator-baremaps/releases/tag/untagged-4d07860016b500637021
> >
> > We have two distributions (source and binary) created with the maven 
> > assembly plugin. The checksums and signatures are generated by the CI. For 
> > now, the PGP signatures are computed with the PGP key used to sign the 
> > maven artifacts. The release action is located here:
> > https://github.com/apache/incubator-baremaps/blob/cd0a1fdb7c7c29a6f41d1f299239cb61580b3036/.github/workflows/release.yml#L23
> >
> > In order to publish a new release, the release manager would have to 
> > perform the following steps:
> > 1) create a branch for the release
> > 2) execute the mvn release:prepare co

Re: Podling Baremaps Report Reminder - December 2022

[Calvin Kirs]

Hi Josh,

Thanks for your hard work, just a correction, we have not submitted
the project name for the check. I mentioned how to do that in my
earliest email.

On Tue, Nov 22, 2022 at 11:00 PM Josh Fischer  wrote:
>
> Here is the starting point for the board report [1].  Make any
> changes/additions you feel should be there.  I meant to get to this sooner,
> but you know, I was off getting married :-).  I think we should aim to
> submit the report by Tuesday, December 6.
>
> [1]:
> https://docs.google.com/document/d/1Yj1xeeU-N-Tx02fmYz2EUTcNpKOUcKxYbqM1uYg-cnE/edit?usp=sharing
>
> On Thu, Nov 17, 2022 at 10:50 PM  wrote:
>
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 21 December 2022.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, December 07).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Candidate names should not be made public before people are actually
> > elected, so please do not include the names of potential committers or
> > PPMC members in your report.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/December2022
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Note: The format of the report has changed to use markdown.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
> > -
> > 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

Re: Podling Baremaps Report Reminder - December 2022

[Calvin Kirs]

Hi Josh,

Could you paste it here[1]?  thanks.

[1]https://cwiki.apache.org/confluence/display/INCUBATOR/December2022#baremaps

On Fri, Dec 2, 2022 at 12:22 AM Josh Fischer  wrote:
>
> Thanks for checking, Calvin. I thought it was completed already..  I’ll
> look through email list for details on how to get it done.
>
> On Thu, Dec 1, 2022 at 9:48 AM Calvin Kirs  wrote:
>
> > Hi Josh,
> >
> > Thanks for your hard work, just a correction, we have not submitted
> > the project name for the check. I mentioned how to do that in my
> > earliest email.
> >
> > On Tue, Nov 22, 2022 at 11:00 PM Josh Fischer  wrote:
> > >
> > > Here is the starting point for the board report [1].  Make any
> > > changes/additions you feel should be there.  I meant to get to this
> > sooner,
> > > but you know, I was off getting married :-).  I think we should aim to
> > > submit the report by Tuesday, December 6.
> > >
> > > [1]:
> > >
> > https://docs.google.com/document/d/1Yj1xeeU-N-Tx02fmYz2EUTcNpKOUcKxYbqM1uYg-cnE/edit?usp=sharing
> > >
> > > On Thu, Nov 17, 2022 at 10:50 PM  wrote:
> > >
> > > > Dear podling,
> > > >
> > > > This email was sent by an automated system on behalf of the Apache
> > > > Incubator PMC. It is an initial reminder to give you plenty of time to
> > > > prepare your quarterly board report.
> > > >
> > > > The board meeting is scheduled for Wed, 21 December 2022.
> > > > The report for your podling will form a part of the Incubator PMC
> > > > report. The Incubator PMC requires your report to be submitted 2 weeks
> > > > before the board meeting, to allow sufficient time for review and
> > > > submission (Wed, December 07).
> > > >
> > > > Please submit your report with sufficient time to allow the Incubator
> > > > PMC, and subsequently board members to review and digest. Again, the
> > > > very latest you should submit your report is 2 weeks prior to the board
> > > > meeting.
> > > >
> > > > Candidate names should not be made public before people are actually
> > > > elected, so please do not include the names of potential committers or
> > > > PPMC members in your report.
> > > >
> > > > Thanks,
> > > >
> > > > The Apache Incubator PMC
> > > >
> > > > Submitting your Report
> > > >
> > > > --
> > > >
> > > > Your report should contain the following:
> > > >
> > > > *   Your project name
> > > > *   A brief description of your project, which assumes no knowledge of
> > > > the project or necessarily of its field
> > > > *   A list of the three most important issues to address in the move
> > > > towards graduation.
> > > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> > be
> > > > aware of
> > > > *   How has the community developed since the last report
> > > > *   How has the project developed since the last report.
> > > > *   How does the podling rate their own maturity.
> > > >
> > > > This should be appended to the Incubator Wiki page at:
> > > >
> > > > https://cwiki.apache.org/confluence/display/INCUBATOR/December2022
> > > >
> > > > Note: This is manually populated. You may need to wait a little before
> > > > this page is created from a template.
> > > >
> > > > Note: The format of the report has changed to use markdown.
> > > >
> > > > Mentors
> > > > ---
> > > >
> > > > Mentors should review reports for their project(s) and sign them off on
> > > > the Incubator wiki page. Signing off reports shows that you are
> > > > following the project - projects that are not signed may raise alarms
> > > > for the Incubator PMC.
> > > >
> > > > Incubator PMC
> > > >
> > > > -
> > > > 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
> >
> > --
> Sent from A Mobile Device



-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: Name approval ticket

[Calvin Kirs]

Hi Josh,
Thank you, but we should provide a ticket here[1],
also need to show our preliminary investigation[2].

[1] 
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-206?filter=allopenissues
[2] https://incubator.apache.org/guides/names.html#name-search

On Tue, Dec 6, 2022 at 1:18 AM Bertil Chapuis  wrote:
>
> Thanks a lot for logging the issue.
>
> > On 5 Dec 2022, at 16:27, Josh Fischer  wrote:
> >
> > You can track it here: https://issues.apache.org/jira/browse/TM-144
>


-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: Reworking the documentation

[Calvin Kirs]

Hi Antoine,

Well done, btw, regarding some deadlinks, we could add checks in CI,
here is a useful tool [1]. (Some links may cause 403 due to frequent
visits.) but overall it is good, we have used it in SkyWalking for a
long time[2].

In addition, we can need to make a plan to do the official website of
the project, or hand it over to other volunteers. here is the list to
check [3].


[1] https://github.com/tcort/markdown-link-check
[2] 
https://github.com/apache/skywalking/blob/master/.github/workflows/dead-link-checker.yaml
[3] https://incubator.apache.org/guides/sites.html

On Wed, Dec 7, 2022 at 9:56 PM Antoine Drabble
 wrote:
>
> Hello everyone,
>
> I have worked a bit on the documentation recently.
>
> In my opinion the first step to grow the community is to have a welcoming
> and easy to read documentation. Whether it is to understand the code
> structure, test out Baremaps or just understand what Baremaps is.
>
> In my opinion this is not clear at the moment. The scope of the project has
> evolved from the initial goal which was to create vector tiles from OSM
> data.
>
> Most of the links to Github are broken on the website. The example files
> are no longer available on the main repository which break both
> the IntelliJ configurations and the documentation. Finally, the main README
> is also outdated.
>
> I have created 3 PRs, [1] to update the README, [2] to put back the
> examples in the main repository and [3] to improve and add new sections to
> the website.
>
> My work is probably not perfect as I had to edit a lot of files in a short
> amount of time. I still have to test out all the guides as well. If anyone
> is interested in reviewing my pull requests or testing the guides, please
> do.
>
> Anyway we should probably merge this quickly, as many things in the current
> documentation are outdated or broken. Then we can improve it iteratively.
>
> [1]https://github.com/apache/incubator-baremaps/pull/550
> [2]https://github.com/apache/incubator-baremaps/pull/551
> [3]https://github.com/apache/incubator-baremaps-site/pull/1
>
> Best regards,
> Antoine Drabble



-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: Name approval ticket

[Calvin Kirs]

Hi,
  The expected search results are not complete, can anyone of us fill it in?

 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-207

On Wed, Dec 7, 2022 at 2:33 AM Josh Fischer  wrote:
>
> Re-created: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-207
>
> On Mon, Dec 5, 2022 at 9:55 PM Josh Fischer  wrote:
>
> > Guess my multitasking got the best of me :-/.  I’ll fix this in the
> > morning.
> >
> >
> >
> > On Mon, Dec 5, 2022 at 8:32 PM Calvin Kirs  wrote:
> >
> >> Hi Josh,
> >> Thank you, but we should provide a ticket here[1],
> >> also need to show our preliminary investigation[2].
> >>
> >> [1]
> >> https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-206?filter=allopenissues
> >> [2] https://incubator.apache.org/guides/names.html#name-search
> >>
> >> On Tue, Dec 6, 2022 at 1:18 AM Bertil Chapuis  wrote:
> >> >
> >> > Thanks a lot for logging the issue.
> >> >
> >> > > On 5 Dec 2022, at 16:27, Josh Fischer  wrote:
> >> > >
> >> > > You can track it here: https://issues.apache.org/jira/browse/TM-144
> >> >
> >>
> >>
> >> --
> >> Best wishes！
> >> CalvinKirs
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
> >> For additional commands, e-mail: dev-h...@baremaps.apache.org
> >>
> >> --
> > Sent from A Mobile Device
> >



-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

GSoC 2023 has started

[Calvin Kirs]

Hi guys,

GSoC 2023[1] has started, GSoC is a good opportunity to involve more
contributors, increase diversity and build solid communities around
ASF Projects.

Please let me know if you need any help with the GSoC process.
Here are some related materials that we could learn about.
[1]https://community.apache.org/gsoc.html
[2]https://developers.google.com/open-source/gsoc/timeline
-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: [VOTE] Release Apache Baremaps 0.7.1-rc2 (incubating)

[Calvin Kirs]

Hi,
+1 (binding) we used DISCLAIMER-WIP

I checked:
- incubating in the name
- signature and hashes are fine
- DISCLAIMER-WIP exists
- LICENSE and NOTICE exist
-Can compile from source

In addition to what Julian said, I have a little addition.
The license file and NOTICE of the binary package are missing. It
seems that we have not done this work. Maybe it can be done in the
next version.
Another point, did we forget to publish maven components? Sorry I
didn't find it, I don't know what I missed.

On Sun, Mar 19, 2023 at 1:39 AM Julian Hyde  wrote:
>
> I agree with your conclusion, not entirely with your reasoning. We will need 
> three IPMC votes during the vote on general@i.a.o  but 
> we don’t technically need them now, and they don’t strictly need to be 
> mentors. We need information, so that you as RM can make an informed decision 
> about whether this RC is good. And it is reasonable to ask mentors to 
> scrutinize and vote on releases at the dev@ stage.
>
> I saw that George voted (thanks!). Can we have a vote from one or two more 
> mentors - Bertrand, Calvin, Martin - so that if there are problems we can 
> save everyone the trouble of an IPMC vote.
>
> Julian
>
>
> > On Mar 18, 2023, at 4:46 AM, Bertil Chapuis  wrote:
> >
> > Thank you all for your valuable input on the release and for the nice 
> > GitHub activity following our mailing list discussion.
> >
> > According to the incubation process [1], we require three IPMC votes for 
> > approval. We currently have two (thanks, George and Julian) and await a 
> > third.
> >
> > I propose extending the 72-hour deadline to secure the final IPMC vote, 
> > after which we'll determine if we release 0.7.1-rc2 or introduce a third 
> > release candidate.
> >
> > Enjoy your weekend,
> >
> > Bertil
> >
> > [1] - https://incubator.apache.org/guides/releasemanagement.html
> >
> >
> >> On 17 Mar 2023, at 13:00, George Percivall  
> >> wrote:
> >>
> >> +1
> >>
> >> perciv...@apache.org
> >>
> >> On Fri, Mar 17, 2023, 7:17 AM James Smith  wrote:
> >>
> >>> Hi,
> >>>
> >>> I change my 0 by a +1.
> >>>
> >>> I resolve the problem of the test failing on my machine.
> >>> It was due to the fact that my system was in French and not in English.
> >>>
> >>> I track this issue here:
> >>> https://github.com/apache/incubator-baremaps/issues/609
> >>>
> >>> Have a good day.
> >>>
> >>> James Smith
> >>>
> >>> On 2023/03/17 09:03:17 James Smith wrote:
>  Hi!
> 
>  0
> 
>  - Test the bin on macOS 13.2.
>  - Check the hash of the bin and src release.
>  - I have a failed test `IpLocTest.findAll:94 expected: <7> but was: <6>`
> >>> with maven 3.8.1, java 17.0.2-oracle will running a `mvn clean install`. I
> >>> have not looked why this test failed for the moment.
> 
>  Regards,
>  James Smith
> 
> 
>  On 2023/03/14 20:20:19 Bertil Chapuis wrote:
> > Hello Everyone,
> >
> > Let’s give this a second attempt ;)
> >
> > Please, Do not hesitate to participate and vote even if you're not
> >>> actively involved in the project or if you just subscribed to the mailing
> >>> list. This release process is a great opportunity to engage the community
> >>> and gather valuable feedback.
> >
> > I have created a build for Apache Baremaps 0.7.1 (incubating), release
> >>> candidate 2.
> >
> > Thanks to everyone who has contributed to this release and helped
> >>> improving the release process.
> >
> > You can read the release notes here:
> > https://github.com/apache/incubator-baremaps/releases/tag/v0.7.1-rc2 <
> >>> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.1-rc2>
> >
> > The commit to be voted upon:
> >
> >>> https://github.com/apache/incubator-baremaps/commit/6619632bb56dd20d58280329c5105208c342bfc1
> >>> <
> >>> https://github.com/apache/incubator-baremaps/commit/6619632bb56dd20d58280329c5105208c342bfc1
> 
> >
> >>> https://gitbox.apache.org/repos/asf?p=incubator-baremaps.git;a=commit;h=6619632bb56dd20d58280329c5105208c342bfc1
> >>> <
> >>> https://gitbox.apache.org/repos/asf?p=incubator-baremaps.git;a=commit;h=6619632bb56dd20d58280329c5105208c342bfc1
> 
> >
> > Its hash is 6619632bb56dd20d58280329c5105208c342bfc1 and its tag is
> >>> v0.7.1-rc2.
> >
> > The artifacts to be voted on are located here:
> > https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.1-rc2/ <
> >>> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.1-rc2/>
> >
> > The hashes of the artifacts are as follows:
> >
> >>> d91dd0f1ebc30a24c7660f6099032eb3b0bc0b36db867dee85e2f8fb6da18113f4b2381fc34a757eb1c0e91522372c66ea75faadc37680cf4c3177ca4eef97a1
> >>> ./baremaps-0.7.1-incubating-src.tar.gz
> >
> >>> 5023a16b337e75edd58d06b024fb840ad03030885011ab592919aeddc9b1e32fec9969b41037cbb36bb65749e8b05e9da423acac674eba9174ba5001e8fd5074
> >>> ./baremaps-0.7.1-incubating-bin.tar.gz
> >
> > Release

Re: [VOTE] Release Apache Baremaps 0.7.1-rc2 (incubating)

[Calvin Kirs]

On Sun, Mar 19, 2023 at 6:20 PM Bertil Chapuis  wrote:
>
> Hello Calvin,
> Hello Julian,
>
> Thanks a lot for checking the release and helping us adjusting our process.
>
> Calvin, I see a license and notice file at the root of the binary package. 
> Are we supposed to add these files elsewhere?
 we can refer to this: https://infra.apache.org/licensing-howto.html#binary

>Regarding the maven artifacts, the goal is to include them in a future 
>release. Previously, we were publishing them on maven central, but we are not 
>sure yet how to publish them on apache’s server. Is there a documentation for 
>this? The closest I found from a documentation is Zookeepers release procedure 
>[1].

please refer to here: https://infra.apache.org/publishing-maven-artifacts.html
>
> Thank you, Julian, for the clarification. If I understand things correctly, I 
> should have sent the email for the vote directly to the incubator general 
> list and cc'd the Baremaps' dev list. Without further notice, I will simply 
> extend this vote by forwarding it to the general mailing list on Monday.
>
> Best,
>
> Bertil
>
> [1] 
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease+using+maven+release+plugin
>
>
>
> > On 19 Mar 2023, at 04:25, Calvin Kirs  wrote:
> >
> > Hi,
> > +1 (binding) we used DISCLAIMER-WIP
> >
> > I checked:
> > - incubating in the name
> > - signature and hashes are fine
> > - DISCLAIMER-WIP exists
> > - LICENSE and NOTICE exist
> > -Can compile from source
> >
> > In addition to what Julian said, I have a little addition.
> > The license file and NOTICE of the binary package are missing. It
> > seems that we have not done this work. Maybe it can be done in the
> > next version.
> > Another point, did we forget to publish maven components? Sorry I
> > didn't find it, I don't know what I missed.
> >
> > On Sun, Mar 19, 2023 at 1:39 AM Julian Hyde  wrote:
> >>
> >> I agree with your conclusion, not entirely with your reasoning. We will 
> >> need three IPMC votes during the vote on general@i.a.o 
> >> <mailto:general@i.a.o> but we don’t technically need them now, and they 
> >> don’t strictly need to be mentors. We need information, so that you as RM 
> >> can make an informed decision about whether this RC is good. And it is 
> >> reasonable to ask mentors to scrutinize and vote on releases at the dev@ 
> >> stage.
> >>
> >> I saw that George voted (thanks!). Can we have a vote from one or two more 
> >> mentors - Bertrand, Calvin, Martin - so that if there are problems we can 
> >> save everyone the trouble of an IPMC vote.
> >>
> >> Julian
> >>
> >>
> >>> On Mar 18, 2023, at 4:46 AM, Bertil Chapuis  wrote:
> >>>
> >>> Thank you all for your valuable input on the release and for the nice 
> >>> GitHub activity following our mailing list discussion.
> >>>
> >>> According to the incubation process [1], we require three IPMC votes for 
> >>> approval. We currently have two (thanks, George and Julian) and await a 
> >>> third.
> >>>
> >>> I propose extending the 72-hour deadline to secure the final IPMC vote, 
> >>> after which we'll determine if we release 0.7.1-rc2 or introduce a third 
> >>> release candidate.
> >>>
> >>> Enjoy your weekend,
> >>>
> >>> Bertil
> >>>
> >>> [1] - https://incubator.apache.org/guides/releasemanagement.html
> >>>
> >>>
> >>>> On 17 Mar 2023, at 13:00, George Percivall  
> >>>> wrote:
> >>>>
> >>>> +1
> >>>>
> >>>> perciv...@apache.org
> >>>>
> >>>> On Fri, Mar 17, 2023, 7:17 AM James Smith  wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I change my 0 by a +1.
> >>>>>
> >>>>> I resolve the problem of the test failing on my machine.
> >>>>> It was due to the fact that my system was in French and not in English.
> >>>>>
> >>>>> I track this issue here:
> >>>>> https://github.com/apache/incubator-baremaps/issues/609
> >>>>>
> >>>>> Have a good day.
> >>>>>
> >>>>> James Smith
> >>>>>
> >>>>> On 2023/03/17 09:03:17 James Smith wrote:
> >>>>>> Hi!
>

Re: [ANNOUNCE] Apache Baremaps 0.7.1 (incubating) released

[Calvin Kirs]

Hi,

Glad we took the first step, but looking back at our download page, it has some 
issues. We need to rework the download page in accordance with ASF 
requirements[1].

[1]https://infra.apache.org/release-download-pages.html#download-page

On 2023/04/05 14:02:08 Bertil Chapuis wrote:
> Hello Everyone,
> 
> The Apache Baremaps (incubating) community is pleased to announce the release 
> of Apache Baremaps 0.7.1 (incubating). Apache Baremaps (incubating) is a 
> toolkit and a set of infrastructure components for creating, publishing, and 
> operating online maps.
> 
> This is our first release since joining the Apache Software Foundation and an 
> important milestone in the project's history. Thank you to everyone who 
> contributed to this release and thank you to the mentors for their guidance 
> and support.
> 
> We are looking to grow the community and welcome new contributors. If you are 
> interested in contributing to the project, please contact us on the mailing 
> list or on GitHub. We will be happy to help you get started.
> 
> The release notes are available here:
> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.1
> 
> The artifacts are available here:
> https://dist.apache.org/repos/dist/release/incubator/baremaps/0.7.1
> 
> The hashes of the artifacts are as follows:
> d91dd0f1ebc30a24c7660f6099032eb3b0bc0b36db867dee85e2f8fb6da18113f4b2381fc34a757eb1c0e91522372c66ea75faadc37680cf4c3177ca4eef97a1
>  ./baremaps-0.7.1-incubating-src.tar.gz
> 5023a16b337e75edd58d06b024fb840ad03030885011ab592919aeddc9b1e32fec9969b41037cbb36bb65749e8b05e9da423acac674eba9174ba5001e8fd5074
>  ./baremaps-0.7.1-incubating-bin.tar.gz
> 
> The repository is available here:
> https://github.com/apache/incubator-baremaps
> 
> The documentation is available here:
> https://baremaps.apache.org
> 
> The mailing list is available here:
> https://lists.apache.org/list.html?dev@baremaps.apache.org
> 
> The issue tracker is available here:
> https://github.com/apache/incubator-baremaps/issues
> 
> Best regards,
> 
> Bertil
> 

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: [ANNOUNCE] New Baremaps committer: Leonard Cseres

[Calvin Kirs]

Hi Leonard,

Welcome, and thank you for your contributions!

I have submitted a request to create an id(leonardcs) for you, this
may take some time, usually no more than a week.

On Thu, Jun 8, 2023 at 11:08 PM Leo  wrote:
>
> Hello Everyone,
>
> Thank you for the warm welcome. I am just missing an Apache ID as my ID 
> suggestion was already taken.
>
> > "Please provide the Apache Baremaps podling (copied) with a valid Apache 
> > id. They can then request your account using Whimsy.
> > You can provide more than one id in case your next choice is also 
> > unavailable."
>
> Here are the possible IDs:
> - leonardcs
> - leonardcser
>
> Thank you in advance.
>
> Best Regards,
> Leonard
>
>
> On 2023/06/08 11:45:14 Bertil Chapuis wrote:
> > Hello Everyone,
> >
> > On behalf of the Baremaps PMC, I'm happy to announce that Leonard Cseres 
> > has accepted an invitation to become a committer on Apache Baremaps.
> >
> > Welcome, and thank you for your contributions!
> >
> > Bertil Chapuis
> >
> -
> 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

Re: Let's drop a new release of Apache Baremaps

[Calvin Kirs]

Good job!


The new website looks great, but there are still some aspects that
don't comply with the ASF rule.

https://incubator.apache.org/guides/sites.html

On Fri, Aug 18, 2023 at 9:43 PM Josh Fischer  wrote:
>
> You can count me in, Bertil.
>
> -  Josh
>
> Sent from my iPhone
>
> > On Aug 18, 2023, at 3:02 AM, Bertil Chapuis  wrote:
> >
> > Hello Everyone,
> >
> > I hope you are all having a wonderful summer.
> >
> > The activity on Apache Baremaps has been great since our last release 
> > (v0.7.1, April), and it's probably a good time to drop a new version 
> > (v0.7.2?). Below is a draft of the release notes. Please note that we have 
> > welcomed 6 new contributors, 2 new committers, and have launched a 
> > beautiful new website.
> >
> > Would any of you be interested in participating in this effort? As our 
> > community grows, the goal is to share ownership and decision-making. A 
> > release is a perfect opportunity to get involved. Here's a non-exhaustive 
> > list of areas where assistance would be appreciated:
> > - Test the various examples
> > - Ensure that the documentation is accurate
> > - Review and refine the release process
> > - Verify and vote for the release artifacts
> > - Publish jars on the Apache Maven repository
> >
> > Next week, I plan to dedicate an afternoon (either Monday, Wednesday, 
> > Thursday, or Friday) to this task and would be happy to exchange on the 
> > topic.
> >
> > Happy mapping,
> >
> > Bertil
> >
> > —
> >
> > Apache Baremaps v0.7.2
> >
> > ## What's Changed
> > * Release Baremaps 0.7.1 by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/597
> > * maplibre-gl: bump to 2.4.0 by @zvikara in 
> > https://github.com/apache/incubator-baremaps/pull/602
> > * Fix links in README files by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/615
> > * Improve reporting for workflow execution by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/612
> > * Add the `apache-` prefix to tar release by @swerky in 
> > https://github.com/apache/incubator-baremaps/pull/611
> > * Add missing files in release and exclude unwanted folders by @swerky in 
> > https://github.com/apache/incubator-baremaps/pull/610
> > * Implement the vector tile specification by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/617
> > * Add support for FlatGeoBuf by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/591
> > * Improve the transformation workflow by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/620
> > * Add CodeQL workflow by @jorgectf in 
> > https://github.com/apache/incubator-baremaps/pull/534
> > * Improve the osm simplifications by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/625
> > * Support js files in export command by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/626
> > * Correctly reproject geometries by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/628
> > * Update the OGC API specification files by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/630
> > * ogcapi, maintenance dependencies by @Perdjesk in 
> > https://github.com/apache/incubator-baremaps/pull/631
> > * Add raster split view for dev by @leonardcser in 
> > https://github.com/apache/incubator-baremaps/pull/636
> > * Feature/osm-split-view by @leonardcser in 
> > https://github.com/apache/incubator-baremaps/pull/637
> > * Fix invalid query execution by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/627
> > * Catch null pointer exception server resources by @leonardcser in 
> > https://github.com/apache/incubator-baremaps/pull/638
> > * Add third-party licenses to the binary distribution by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/642
> > * Add version of the application into the README by @swerky in 
> > https://github.com/apache/incubator-baremaps/pull/613
> > * Fix encoding issue in geocoder by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/643
> > * Update and simplify OGCAPI implementation by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/633
> > * Merge the mvt and vectortile packages by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/644
> > * Rename Tile into TileCoord by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/645
> > * Move tile store in a dedicated package by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/646
> > * Merge the database and openstreetmap packages by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/647
> > * Infer user IP from HTTP headers or connection by @bchapuis in 
> > https://github.com/apache/incubator-baremaps/pull/648
> > * Fix aeroway layering order and color by @leonardcser in 
> > https://github.com/apache/incubator-baremaps/pull/650
> > * Simplify IpLoc package by @bchapuis in 
> > https://github

Re: Let's drop a new release of Apache Baremaps

[Calvin Kirs]

Hi,
Regarding the fourth, you mean Nexus access with baremaps enabled?
It's easy, just need a ticket like this[1]

[1] https://issues.apache.org/jira/browse/INFRA-16105

On Tue, Aug 22, 2023 at 2:08 PM Bertil Chapuis  wrote:
>
> Great, let’s book a time slot at 13h30 (UTC+2) on Thursday to discuss the 
> release process. Here is a link for those who are interested to join/meet [1].
>
> Something I’d love to discuss is the cadence and the automation of the 
> release process. We disabled it to comply with the apache guidelines when 
> entering the incubator. These guidelines recently got updated and it is now 
> possible to sign the artifacts with the CI [2] and with a key dedicated to 
> signing [3].
>
> Another point is the publication of artifacts on the maven repository. The 
> current release process does not include this step [4], and it would be great 
> to do it.
>
> Best,
>
> Bertil
>
> [1] https://meet.google.com/mra-htfq-ghr
> [2] https://www.apache.org/legal/release-policy.html#release-signing
> [3] https://infra.apache.org/release-signing.html#automated-release-signing
> [4] https://github.com/apache/incubator-baremaps/blob/main/RELEASE.md
>
>
> > On 21 Aug 2023, at 13:58, perdj...@protonmail.com.invalid 
> >  wrote:
> >
> >
> > Available this week Wednesday/Thursday UTC+2 during office hours (9h-17h), 
> > I would be interested in participating in the release process.
> >
> > cheers
> >
> > --- Original Message ---
> > On Friday, August 18th, 2023 at 17:53, Calvin Kirs  wrote:
> >
> >
> >> Good job!
> >>
> >>
> >> The new website looks great, but there are still some aspects that
> >> don't comply with the ASF rule.
> >>
> >> https://incubator.apache.org/guides/sites.html
> >>
> >> On Fri, Aug 18, 2023 at 9:43 PM Josh Fischer j...@joshfischer.io wrote:
> >>
> >>> You can count me in, Bertil.
> >>>
> >>> - Josh
> >>>
> >>> Sent from my iPhone
> >>>
> >>>> On Aug 18, 2023, at 3:02 AM, Bertil Chapuis bchap...@gmail.com wrote:
> >>>>
> >>>> Hello Everyone,
> >>>>
> >>>> I hope you are all having a wonderful summer.
> >>>>
> >>>> The activity on Apache Baremaps has been great since our last release 
> >>>> (v0.7.1, April), and it's probably a good time to drop a new version 
> >>>> (v0.7.2?). Below is a draft of the release notes. Please note that we 
> >>>> have welcomed 6 new contributors, 2 new committers, and have launched a 
> >>>> beautiful new website.
> >>>>
> >>>> Would any of you be interested in participating in this effort? As our 
> >>>> community grows, the goal is to share ownership and decision-making. A 
> >>>> release is a perfect opportunity to get involved. Here's a 
> >>>> non-exhaustive list of areas where assistance would be appreciated:
> >>>> - Test the various examples
> >>>> - Ensure that the documentation is accurate
> >>>> - Review and refine the release process
> >>>> - Verify and vote for the release artifacts
> >>>> - Publish jars on the Apache Maven repository
> >>>>
> >>>> Next week, I plan to dedicate an afternoon (either Monday, Wednesday, 
> >>>> Thursday, or Friday) to this task and would be happy to exchange on the 
> >>>> topic.
> >>>>
> >>>> Happy mapping,
> >>>>
> >>>> Bertil
> >>>>
> >>>> —
> >>>>
> >>>> Apache Baremaps v0.7.2
> >>>>
> >>>> ## What's Changed
> >>>> * Release Baremaps 0.7.1 by @bchapuis in 
> >>>> https://github.com/apache/incubator-baremaps/pull/597
> >>>> * maplibre-gl: bump to 2.4.0 by @zvikara in 
> >>>> https://github.com/apache/incubator-baremaps/pull/602
> >>>> * Fix links in README files by @bchapuis in 
> >>>> https://github.com/apache/incubator-baremaps/pull/615
> >>>> * Improve reporting for workflow execution by @bchapuis in 
> >>>> https://github.com/apache/incubator-baremaps/pull/612
> >>>> * Add the `apache-` prefix to tar release by @swerky in 
> >>>> https://github.com/apache/incubator-baremaps/pull/611
> >>>> * Add missing files in release and exclude unwanted folders by @swerky 
> >>>>

Re: [VOTE] Release Apache Baremaps 0.7.2-rc1 (incubating)

[Calvin Kirs]

Good to see we are trying to release the first binary version, but
there are some issues with the license. pls follow [1]

[1] https://www.apache.org/legal/release-policy.html#compiled-packages

On Tue, Aug 29, 2023 at 11:04 PM Bertil Chapuis  wrote:
>
> Thanks for reporting this. I obviously don’t see this warning ;)
>
> Could this be related to the fact that the KEYS file need to be imported or 
> trusted?
> wget https://downloads.apache.org/incubator/baremaps/KEYS
> gpg --import KEYS
>
> My public key is also published here:
> https://keys.openpgp.org/search?q=bchapuis%40gmail.com
>
>
> > On 29 Aug 2023, at 16:39, Josh Fischer  wrote:
> >
> > Right now I’m 0.
> >
> > I’ve not run across this before, I’m not sure if it’s an issue for the 
> > release.  See gpg output below about the key not being certified.  This is 
> > the reason my vote is 0 at the moment.
> > gpg --verify $FILE.asc $FILE
> > gpg: Signature made Thu Aug 24 07:11:17 2023 CDT
> > gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
> > gpg: Good signature from "Bertil Chapuis " [unknown]
> > gpg: WARNING: This key is not certified with a trusted signature!
> >
> > I checked:
> > - Downloaded; checked hashes/signatures; checked LICENSE, NOTICE, 
> > DISCLAIMER-WIP; compiled and ran tests on OSX, OpenJDK 17, Maven 3.8.4.
> > - Rat check showed 1441 unapproved licenses.  However, since we are a WIP 
> > and I think this issue is known, so we are good.
> > - I tried to run the example from the tar.gz binary, but the website seems 
> > to refer to the repo - not a release. As an example, the openStreet Map 
> > example wouldn’t work with one of our binary releases. This isn’t a blocker 
> > by any means, just a developer experience idea that I thought about while 
> > checking the release.
> >
> > $ cd examples/openstreetmap
> > $ baremaps workflow execute --file workflow.json
> >
> > Because the “examples” folder wasn’t in the binary release I wasn’t sure 
> > how to run the example.
> >
> > - Josh
> >
> >> On Aug 28, 2023, at 3:20 PM, Bertil Chapuis  wrote:
> >>
> >> Thank you Josh and Julian. There is no hurry, especially if we can 
> >> increase the duration of the vote.
> >>
> >> As we all have busy schedule, I will probably extend future release votes 
> >> to one week in the future.
> >>
> >> Best,
> >>
> >> Bertil
> >>
> >>> On 28 Aug 2023, at 19:07, Julian Hyde  wrote:
> >>>
> >>> What Josh said. I’ll review & vote today. Apologies.
> >>>
>  On Aug 28, 2023, at 7:42 AM, Josh Fischer  wrote:
> 
>  I apologize for my absence.  I will spend some time looking at it in the 
>  next 24 hours.
> 
>  This is one of the fun and challenging parts of working through the 
>  incubator. I’ve had votes go over two weeks before.  Our best bet is to 
>  get as many binding (preferably 3) votes on the dev@baremaps list.  It’s 
>  often harder to get votes on general@a.o .
> 
> 
>  Let’s wait a few more days to get binding votes. Open-source moves at 
>  the speed of open-source, fun!
> 
> > On Aug 28, 2023, at 9:10 AM, Bertil Chapuis  wrote:
> >
> > Hello Everyone,
> >
> > We don’t have enough vote for publishing our release. Can we extend the 
> > deadline or should we start a new vote?
> >
> > I see that some projects, such as Apache Pekko, ask the incubator 
> > mailing-list to vote for their releases. Should we try to do the same?
> >
> > Best regards,
> >
> > Bertil
> >
> >
> >> On 24 Aug 2023, at 14:52, Bertil Chapuis  wrote:
> >>
> >> Hello Everyone,
> >>
> >> Following our online release party (thank you Leonard and Perdjesk), 
> >> we have created a build for Apache Baremaps (incubating) 0.7.2, 
> >> release candidate 1.
> >>
> >> Thanks to everyone who has contributed to this release.
> >>
> >> You can read the release notes here:
> >> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc1
> >>
> >> The commit to be voted upon:
> >> https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc1
> >>
> >> Its hash is e917d5b02fdb64c3f715afd449bb1fe9ca5c2f58.
> >>
> >> Its tag is v0.7.2-rc1.
> >>
> >> The artifacts to be voted on are located here:
> >> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc1/
> >>
> >> The hashes of the artifacts are as follows:
> >> d910b50ebed4200d0ef6f0c1ee3e4db0cd95ea005fe54fca66dfc4ec4dca73e96edc8913654c85c73539d6a9d27481157fea9f456a9f3aa451c178a811a89ea0
> >>  ./apache-baremaps-0.7.2-incubating-src.tar.gz
> >> fda00056b97857f966e92cf7e118071f5b6d44f9652176a4626cec38c5b0738933b24e23efef423eafba2111bc6a22e6f00a67fda2f10b0011f9c22f3208
> >>  ./apache-baremaps-0.7.2-incubating-bin.tar.gz
> >>
> >> Release artifacts are signed with the following key:
> >> http://people.apache.org/keys/committer/bchapuis.

Re: [VOTE] Release Apache Baremaps 0.7.2-rc1 (incubating)

[Calvin Kirs]

On Tue, Aug 29, 2023 at 10:39 PM Josh Fischer  wrote:
>
> Right now I’m 0.
>
> I’ve not run across this before, I’m not sure if it’s an issue for the 
> release.  See gpg output below about the key not being certified.  This is 
> the reason my vote is 0 at the moment.
> gpg --verify $FILE.asc $FILE
> gpg: Signature made Thu Aug 24 07:11:17 2023 CDT
> gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
> gpg: Good signature from "Bertil Chapuis " [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!

don't worry, it's ok.
>
> I checked:
> - Downloaded; checked hashes/signatures; checked LICENSE, NOTICE, 
> DISCLAIMER-WIP; compiled and ran tests on OSX, OpenJDK 17, Maven 3.8.4.
> - Rat check showed 1441 unapproved licenses.  However, since we are a WIP and 
> I think this issue is known, so we are good.
> - I tried to run the example from the tar.gz binary, but the website seems to 
> refer to the repo - not a release. As an example, the openStreet Map example 
> wouldn’t work with one of our binary releases. This isn’t a blocker by any 
> means, just a developer experience idea that I thought about while checking 
> the release.
>
> $ cd examples/openstreetmap
> $ baremaps workflow execute --file workflow.json
>
> Because the “examples” folder wasn’t in the binary release I wasn’t sure how 
> to run the example.
>
> - Josh
>
> > On Aug 28, 2023, at 3:20 PM, Bertil Chapuis  wrote:
> >
> > Thank you Josh and Julian. There is no hurry, especially if we can increase 
> > the duration of the vote.
> >
> > As we all have busy schedule, I will probably extend future release votes 
> > to one week in the future.
> >
> > Best,
> >
> > Bertil
> >
> >> On 28 Aug 2023, at 19:07, Julian Hyde  wrote:
> >>
> >> What Josh said. I’ll review & vote today. Apologies.
> >>
> >>> On Aug 28, 2023, at 7:42 AM, Josh Fischer  wrote:
> >>>
> >>> I apologize for my absence.  I will spend some time looking at it in the 
> >>> next 24 hours.
> >>>
> >>> This is one of the fun and challenging parts of working through the 
> >>> incubator. I’ve had votes go over two weeks before.  Our best bet is to 
> >>> get as many binding (preferably 3) votes on the dev@baremaps list.  It’s 
> >>> often harder to get votes on general@a.o .
> >>>
> >>>
> >>> Let’s wait a few more days to get binding votes. Open-source moves at the 
> >>> speed of open-source, fun!
> >>>
>  On Aug 28, 2023, at 9:10 AM, Bertil Chapuis  wrote:
> 
>  Hello Everyone,
> 
>  We don’t have enough vote for publishing our release. Can we extend the 
>  deadline or should we start a new vote?
> 
>  I see that some projects, such as Apache Pekko, ask the incubator 
>  mailing-list to vote for their releases. Should we try to do the same?
> 
>  Best regards,
> 
>  Bertil
> 
> 
> > On 24 Aug 2023, at 14:52, Bertil Chapuis  wrote:
> >
> > Hello Everyone,
> >
> > Following our online release party (thank you Leonard and Perdjesk), we 
> > have created a build for Apache Baremaps (incubating) 0.7.2, release 
> > candidate 1.
> >
> > Thanks to everyone who has contributed to this release.
> >
> > You can read the release notes here:
> > https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc1
> >
> > The commit to be voted upon:
> > https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc1
> >
> > Its hash is e917d5b02fdb64c3f715afd449bb1fe9ca5c2f58.
> >
> > Its tag is v0.7.2-rc1.
> >
> > The artifacts to be voted on are located here:
> > https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc1/
> >
> > The hashes of the artifacts are as follows:
> > d910b50ebed4200d0ef6f0c1ee3e4db0cd95ea005fe54fca66dfc4ec4dca73e96edc8913654c85c73539d6a9d27481157fea9f456a9f3aa451c178a811a89ea0
> >  ./apache-baremaps-0.7.2-incubating-src.tar.gz
> > fda00056b97857f966e92cf7e118071f5b6d44f9652176a4626cec38c5b0738933b24e23efef423eafba2111bc6a22e6f00a67fda2f10b0011f9c22f3208
> >  ./apache-baremaps-0.7.2-incubating-bin.tar.gz
> >
> > Release artifacts are signed with the following key:
> > http://people.apache.org/keys/committer/bchapuis.asc
> > https://downloads.apache.org/incubator/baremaps/KEYS
> >
> > The README file for the src distribution contains instructions for 
> > building and testing the release.
> >
> > Please vote on releasing this package as Apache Baremaps 0.7.2.
> >
> > The vote is open for the next 72 hours and passes if a majority of at 
> > least three +1 PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Baremaps 
> > [ ] 0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Here is my vote:
> >
> > +1 (binding): I checked the signatures and the checksums; I bui

Re: [VOTE] Release Apache Baremaps 0.7.2-rc1 (incubating)

[Calvin Kirs]

I'll find time tomorrow to list specific checks.
BTW, we cannot fully rely on rat to indicate whether the license is compliant.
In addition, regarding the modification of source code dependencies,
we'd better list the specific files in the LICENSE file, otherwise it
is difficult for us to judge whether this part is compliant.

On Tue, Aug 29, 2023 at 11:31 PM Calvin Kirs  wrote:
>
> On Tue, Aug 29, 2023 at 10:39 PM Josh Fischer  wrote:
> >
> > Right now I’m 0.
> >
> > I’ve not run across this before, I’m not sure if it’s an issue for the 
> > release.  See gpg output below about the key not being certified.  This is 
> > the reason my vote is 0 at the moment.
> > gpg --verify $FILE.asc $FILE
> > gpg: Signature made Thu Aug 24 07:11:17 2023 CDT
> > gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
> > gpg: Good signature from "Bertil Chapuis " [unknown]
> > gpg: WARNING: This key is not certified with a trusted signature!
>
> don't worry, it's ok.
> >
> > I checked:
> > - Downloaded; checked hashes/signatures; checked LICENSE, NOTICE, 
> > DISCLAIMER-WIP; compiled and ran tests on OSX, OpenJDK 17, Maven 3.8.4.
> > - Rat check showed 1441 unapproved licenses.  However, since we are a WIP 
> > and I think this issue is known, so we are good.
> > - I tried to run the example from the tar.gz binary, but the website seems 
> > to refer to the repo - not a release. As an example, the openStreet Map 
> > example wouldn’t work with one of our binary releases. This isn’t a blocker 
> > by any means, just a developer experience idea that I thought about while 
> > checking the release.
> >
> > $ cd examples/openstreetmap
> > $ baremaps workflow execute --file workflow.json
> >
> > Because the “examples” folder wasn’t in the binary release I wasn’t sure 
> > how to run the example.
> >
> > - Josh
> >
> > > On Aug 28, 2023, at 3:20 PM, Bertil Chapuis  wrote:
> > >
> > > Thank you Josh and Julian. There is no hurry, especially if we can 
> > > increase the duration of the vote.
> > >
> > > As we all have busy schedule, I will probably extend future release votes 
> > > to one week in the future.
> > >
> > > Best,
> > >
> > > Bertil
> > >
> > >> On 28 Aug 2023, at 19:07, Julian Hyde  wrote:
> > >>
> > >> What Josh said. I’ll review & vote today. Apologies.
> > >>
> > >>> On Aug 28, 2023, at 7:42 AM, Josh Fischer  wrote:
> > >>>
> > >>> I apologize for my absence.  I will spend some time looking at it in 
> > >>> the next 24 hours.
> > >>>
> > >>> This is one of the fun and challenging parts of working through the 
> > >>> incubator. I’ve had votes go over two weeks before.  Our best bet is to 
> > >>> get as many binding (preferably 3) votes on the dev@baremaps list.  
> > >>> It’s often harder to get votes on general@a.o <mailto:general@a.o>.
> > >>>
> > >>>
> > >>> Let’s wait a few more days to get binding votes. Open-source moves at 
> > >>> the speed of open-source, fun!
> > >>>
> > >>>> On Aug 28, 2023, at 9:10 AM, Bertil Chapuis  wrote:
> > >>>>
> > >>>> Hello Everyone,
> > >>>>
> > >>>> We don’t have enough vote for publishing our release. Can we extend 
> > >>>> the deadline or should we start a new vote?
> > >>>>
> > >>>> I see that some projects, such as Apache Pekko, ask the incubator 
> > >>>> mailing-list to vote for their releases. Should we try to do the same?
> > >>>>
> > >>>> Best regards,
> > >>>>
> > >>>> Bertil
> > >>>>
> > >>>>
> > >>>>> On 24 Aug 2023, at 14:52, Bertil Chapuis  wrote:
> > >>>>>
> > >>>>> Hello Everyone,
> > >>>>>
> > >>>>> Following our online release party (thank you Leonard and Perdjesk), 
> > >>>>> we have created a build for Apache Baremaps (incubating) 0.7.2, 
> > >>>>> release candidate 1.
> > >>>>>
> > >>>>> Thanks to everyone who has contributed to this release.
> > >>>>>
> > >>>>> You can read the release notes here:
> > >>>>> https://github.c

Re: [VOTE] Release Apache Baremaps 0.7.2-rc1 (incubating)

[Calvin Kirs]

 2023, at 12:02 PM, Bertil Chapuis  wrote:
> >
> > Hello Calvin,
> >
> > It would be great if you can list a few actionable items regarding 
> > licensing.
> >
> > https://github.com/apache/incubator-baremaps/issues/492
> >
> > I did a pass on almost everything before joining the incubator, and had to 
> > rewrite or find alternatives to all the problematic GPL dependencies. A 
> > second pass made after joining the incubator revealed a few additional 
> > issues, but I think we are close from being compliant. In my opinion, the 
> > main issue is related to datasets (e.g. openstreetmap files) used in the 
> > tests. We added the DISCLAIMER-WIP to acknowledge these issues in the src 
> > and binary distributions without blocking the release process.
> >
> > Best regards,
> >
> > Bertil
> >
> >> On 29 Aug 2023, at 18:12, Josh Fischer  wrote:
> >>
> >> Calvin,
> >>
> >> You made me think of a license question.  With Heron, we kept a separate 
> >> copy of all the licenses that were not ALV2 [1].  Is this something that 
> >> needs to be done for Baremaps?
> >>
> >> 1. https://github.com/apache/incubator-heron/tree/master/licenses
> >>
> >> - Josh
> >>
> >>> On Aug 29, 2023, at 11:04 AM, Calvin Kirs  wrote:
> >>>
> >>> I'll find time tomorrow to list specific checks.
> >>> BTW, we cannot fully rely on rat to indicate whether the license is 
> >>> compliant.
> >>> In addition, regarding the modification of source code dependencies,
> >>> we'd better list the specific files in the LICENSE file, otherwise it
> >>> is difficult for us to judge whether this part is compliant.
> >>>
> >>> On Tue, Aug 29, 2023 at 11:31 PM Calvin Kirs  >>> <mailto:k...@apache.org>> wrote:
> >>>>
> >>>> On Tue, Aug 29, 2023 at 10:39 PM Josh Fischer  
> >>>> wrote:
> >>>>>
> >>>>> Right now I’m 0.
> >>>>>
> >>>>> I’ve not run across this before, I’m not sure if it’s an issue for the 
> >>>>> release.  See gpg output below about the key not being certified.  This 
> >>>>> is the reason my vote is 0 at the moment.
> >>>>> gpg --verify $FILE.asc $FILE
> >>>>> gpg: Signature made Thu Aug 24 07:11:17 2023 CDT
> >>>>> gpg:using RSA key 
> >>>>> 16D7A0B27D5ADD52BD57932971751399FB39CB84
> >>>>> gpg: Good signature from "Bertil Chapuis " [unknown]
> >>>>> gpg: WARNING: This key is not certified with a trusted signature!
> >>>>
> >>>> don't worry, it's ok.
> >>>>>
> >>>>> I checked:
> >>>>> - Downloaded; checked hashes/signatures; checked LICENSE, NOTICE, 
> >>>>> DISCLAIMER-WIP; compiled and ran tests on OSX, OpenJDK 17, Maven 3.8.4.
> >>>>> - Rat check showed 1441 unapproved licenses.  However, since we are a 
> >>>>> WIP and I think this issue is known, so we are good.
> >>>>> - I tried to run the example from the tar.gz binary, but the website 
> >>>>> seems to refer to the repo - not a release. As an example, the 
> >>>>> openStreet Map example wouldn’t work with one of our binary releases. 
> >>>>> This isn’t a blocker by any means, just a developer experience idea 
> >>>>> that I thought about while checking the release.
> >>>>>
> >>>>> $ cd examples/openstreetmap
> >>>>> $ baremaps workflow execute --file workflow.json
> >>>>>
> >>>>> Because the “examples” folder wasn’t in the binary release I wasn’t 
> >>>>> sure how to run the example.
> >>>>>
> >>>>> - Josh
> >>>>>
> >>>>>> On Aug 28, 2023, at 3:20 PM, Bertil Chapuis  wrote:
> >>>>>>
> >>>>>> Thank you Josh and Julian. There is no hurry, especially if we can 
> >>>>>> increase the duration of the vote.
> >>>>>>
> >>>>>> As we all have busy schedule, I will probably extend future release 
> >>>>>> votes to one week in the future.
> >>>>>>
> >>>>>> Best,
> >>>>>>
> >>>>>> Bertil
> >>>>>>
> >&

Re: [VOTE] Release Apache Baremaps 0.7.2-rc1 (incubating)

[Calvin Kirs]

Only in ./baremaps-renderer: .prettierignore
> >> Only in ./baremaps-renderer: .prettierrc.json
> >> Only in ./baremaps-renderer: README.md
> >> Only in ./baremaps-renderer: tsconfig.json
> >> Only in 
> >> /tmp/apache-baremaps-0.7.2-incubating-src/baremaps-server/src/main/resources:
> >>  maputnik
> >> Only in .: basemap
> >> Only in .: examples
> >> Only in .: .git
> >> Only in .: .github
> >> Only in .: .gitignore
> >> Only in .: .min
> >> Only in .: mvnw
> >> Only in .: mvnw.cmd
> >> diff -r ./README /tmp/apache-baremaps-0.7.2-incubating-src/README
> >> 1c1
> >> < # Apache Baremaps (incubating) ${project.version}
> >> ---
> >>> # Apache Baremaps (incubating) 0.7.2
> >> diff -r ./scripts/generate-artifacts.sh 
> >> /tmp/apache-baremaps-0.7.2-incubating-src/scripts/generate-artifacts.sh
> >> 22c22
> >> < version=$(./mvnw -q -Dexec.executable=echo 
> >> -Dexec.args='${project.version}' --non-recursive exec:exec)
> >> ---
> >>> version=$(./mvnw -q -Dexec.executable=echo -Dexec.args='0.7.2' 
> >>> --non-recursive exec:exec)
> >> 35c35
> >> < for artifact in ./baremaps-$version-incubating-*; do
> >> ---
> >>> for artifact in ./apache-baremaps-$version-incubating-*; do
> >>
> >> Any reason not to include .github/, .gitignore, examples, basemap, and the 
> >> various files in baremaps-renderer ?
>
> We use the baremaps-renderer solely to perform integration tests on the 
> basemap before making significant changes to the style. I’m not sure if it 
> makes sense to include it in the release.
>
> >> [2] In LICENSE, you should remove the "APPENDIX: How to apply the Apache 
> >> License to your work” section.
>
> Sorry for that, I believe you already mentioned this point in a previous 
> review.
>
> >> [3] I received the same error as Calvin did:
> >>
> >>  gpg: Good signature from "Bertil Chapuis " [unknown].
> >>  gpg: WARNING: This key is not certified with a trusted signature!
> >>  gpg:  There is no indication that the signature belongs to the 
> >> owner.
> >>
> >> This error can be fixed by Bertil getting his key signed by someone in our 
> >> web of trust. This can be done after release, but let’s get it done.
>
> It would be great if someone could guide me in this process. I believe 
> Bertrand could help as we meet in person from time to time.
>
> Best regards,
>
> Bertil
>
> >>> On Aug 29, 2023, at 12:02 PM, Bertil Chapuis  wrote:
> >>>
> >>> Hello Calvin,
> >>>
> >>> It would be great if you can list a few actionable items regarding 
> >>> licensing.
> >>>
> >>> https://github.com/apache/incubator-baremaps/issues/492
> >>>
> >>> I did a pass on almost everything before joining the incubator, and had 
> >>> to rewrite or find alternatives to all the problematic GPL dependencies. 
> >>> A second pass made after joining the incubator revealed a few additional 
> >>> issues, but I think we are close from being compliant. In my opinion, the 
> >>> main issue is related to datasets (e.g. openstreetmap files) used in the 
> >>> tests. We added the DISCLAIMER-WIP to acknowledge these issues in the src 
> >>> and binary distributions without blocking the release process.
> >>>
> >>> Best regards,
> >>>
> >>> Bertil
> >>>
> >>>> On 29 Aug 2023, at 18:12, Josh Fischer  wrote:
> >>>>
> >>>> Calvin,
> >>>>
> >>>> You made me think of a license question.  With Heron, we kept a separate 
> >>>> copy of all the licenses that were not ALV2 [1].  Is this something that 
> >>>> needs to be done for Baremaps?
> >>>>
> >>>> 1. https://github.com/apache/incubator-heron/tree/master/licenses
> >>>>
> >>>> - Josh
> >>>>
> >>>>> On Aug 29, 2023, at 11:04 AM, Calvin Kirs  wrote:
> >>>>>
> >>>>> I'll find time tomorrow to list specific checks.
> >>>>> BTW, we cannot fully rely on rat to indicate whether the license is 
> >>>>> compliant.
> >>>>> In addition, regarding the modification of source code dependencies,
> >>>>> we'd better list the specific files in 

Re: [VOTE] Release Apache Baremaps 0.7.2-rc3 (incubating)

[Calvin Kirs]

+1 （binding）

I checked:
- incubating in name
- signatures and hashes are fine
- disclaimer-wip exists
- license and notice files look good
- file have correct ASF headers if necessary

On Thu, Oct 5, 2023 at 7:19 PM Jean-Baptiste Onofré  wrote:
>
> +1 (binding)
>
> I checked:
> - signatures and hashes ok
> - asf headers
> - license, notice and disclaimer are there
> - no binary found in source distribution
>
> Thanks
> Regards
> JB
>
> Le mar. 3 oct. 2023 à 00:10, Bertil Chapuis  a écrit :
>
> > Hello Everyone,
> >
> > This is a call for a vote to release Apache Baremaps 0.7.2 (incubating),
> > release candidate 3. Apache Baremaps is a toolkit and a set of
> > infrastructure components for creating, publishing, and operating online
> > maps.
> >
> > We would like to thanks everyone who has vetted the previous release
> > candidates and who has contributed to the project. This release candidate
> > fixes the issues identified in the previous vote thread:
> > https://lists.apache.org/thread/vzvl8rl5h5k9vj3j2xhbkn92zvn4db2f
> >
> > We now would like to request the Incubator PMC members to review and vote
> > on this new release candidate.
> >
> > You can read the release notes here:
> > https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc3
> >
> > The commit to be voted upon:
> > https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc3
> >
> > Its hash is 823b55507eec425776d996b64b489c8235f6bb37.
> >
> > Its tag is v0.7.2-rc3.
> >
> > The artifacts to be voted on are located here:
> > https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc3/
> >
> > The hashes of the artifacts are as follows:
> > 658ed9f9d7836c774095bd6079a39c92b366da38d733a04f2334ca39e55d41001ea997c826f9024bae51034ee6861d153ef1948defff8ebf02ce18b79d52319b
> > ./apache-baremaps-0.7.2-incubating-src.tar.gz
> > 778a4c2e657b5f632f9abe547d68978da40f162bdddc6dc342586b40952b0c72a0c4f6976cc47f720134c7e547af58f1efa39ddb2441e7f57c7a35fee68a1915
> > ./apache-baremaps-0.7.2-incubating-bin.tar.gz
> >
> > Release artifacts are signed with the following key:
> > http://people.apache.org/keys/committer/bchapuis.asc
> > https://downloads.apache.org/incubator/baremaps/KEYS
> >
> > The README file for the src distribution contains instructions for
> > building and testing the release.
> >
> > Please vote on releasing this package as Apache Baremaps 0.7.2.
> >
> > The vote is open for the next 72 hours and passes if a majority of at
> > least three +1 PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Baremaps 0.7.2
> > [ ] 0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Best,
> >
> > Bertil
> >



-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: March report for Apache Baremaps

[Calvin Kirs]

Hi Bertil,

I'm thrilled to see the community is dedicated to the work on Licenses.

I noticed we're still using the domain [1]. If needed, we can reach
out to the Infra team for assistance. They often provide options like
demo.baremaps.apache.org, and can also offer us corresponding machines
or domain forwarding.

[1]https://demo.baremaps.com/

On Thu, Mar 7, 2024 at 6:45 AM Bertil Chapuis  wrote:
>
> Hello Everyone,
>
> I hope you are doing well. I submitted the March report for Baremaps directly 
> on Confluence [1].
>
> Here are a few highlights:
> - I believe that all non-compliant dependencies and datasets have now been 
> removed (what a relief ;-). I hope that we will be able to remove the 
> "disclaimer-wip” soon and that I will have more time to focus on other 
> aspects (community building, releases, documentation, etc.)
> - Noticeable improvements were made to the tileset and style of the basemap, 
> including icons, layer ordering, legends, etc.
> - A new workflow for the daylight map distribution has been introduced. This 
> means we now have ML-detected buildings and roads coming from Microsoft, 
> Google, and Facebook for low-populated areas.
> - Support for the PMTiles format was added.
>
> Best regards,
>
> Bertil
>
>
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/March2024#baremaps
>
>
>
> -
> 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

Re: March report for Apache Baremaps

[Calvin Kirs]

On Thu, Mar 7, 2024 at 4:15 PM Bertil Chapuis  wrote:
>
> Thank you Calvin,
>
> Yes, the baremaps.com domain is still used for the project and, as mentioned 
> in the proposal, I’m ready to transfer it to the Apache Foundation upon 
> request. Domain forwarding could be a great solution.
>
> The demonstration is still hosed on a dedicate Hetzner server. The main 
> problem is that our needs in terms of compute and storage exceed the default 
> infra [2] by a wide margin and the vector tiles we serve contain data derived 
> from licensed datasets (OpenStreetMap, natural earth, etc.). These reasons 
> made me think that it will be hard to move the demonstration server to 
> Apache’s infrastructure. For context, the demonstration server has 32 CPUs, 
> 128G RAM, and 16TB of NVMe SSDs. Do you think Apache could provide this kind 
> of infrastructure?
It's a significant expense, so it might be difficult to pull off. are
you personally providing this machine now?

Additionally, I have some thoughts on your changes[1] that I'd like to
discuss and improve, but it will take some time. If the community has
any plans to release a new version soon, please let me know.

[1]https://github.com/apache/incubator-baremaps/pull/841/
>
> Best,
>
> Bertil
>
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal
> [2] https://infra.apache.org/vm-for-project.html
>
>
>
> > On 7 Mar 2024, at 03:30, Calvin Kirs  wrote:
> >
> > Hi Bertil,
> >
> > I'm thrilled to see the community is dedicated to the work on Licenses.
> >
> > I noticed we're still using the domain [1]. If needed, we can reach
> > out to the Infra team for assistance. They often provide options like
> > demo.baremaps.apache.org, and can also offer us corresponding machines
> > or domain forwarding.
> >
> > [1]https://demo.baremaps.com/
> >
> > On Thu, Mar 7, 2024 at 6:45 AM Bertil Chapuis  wrote:
> >>
> >> Hello Everyone,
> >>
> >> I hope you are doing well. I submitted the March report for Baremaps 
> >> directly on Confluence [1].
> >>
> >> Here are a few highlights:
> >> - I believe that all non-compliant dependencies and datasets have now been 
> >> removed (what a relief ;-). I hope that we will be able to remove the 
> >> "disclaimer-wip” soon and that I will have more time to focus on other 
> >> aspects (community building, releases, documentation, etc.)
> >> - Noticeable improvements were made to the tileset and style of the 
> >> basemap, including icons, layer ordering, legends, etc.
> >> - A new workflow for the daylight map distribution has been introduced. 
> >> This means we now have ML-detected buildings and roads coming from 
> >> Microsoft, Google, and Facebook for low-populated areas.
> >> - Support for the PMTiles format was added.
> >>
> >> Best regards,
> >>
> >> Bertil
> >>
> >>
> >> [1] 
> >> https://cwiki.apache.org/confluence/display/INCUBATOR/March2024#baremaps
> >>
> >>
> >>
> >> -
> >> 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
>


-- 
Best wishes！
CalvinKirs

-
To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
For additional commands, e-mail: dev-h...@baremaps.apache.org

Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Calvin Kirs]

+1 binding
I'm truly sorry for the tardiness of my vote.

I checked:
- incubating in name
- signatures and hashes are fine
- disclaimer-wip exists
- license and notice files look good
- file have correct ASF headers if necessary

Todo:
- License information should reside in the LICENSE file, not the NOTICE
file.
- The binary distribution should include third-party LICENSE files and
NOTICE files (if applicable, such as for projects using the Apache 2.0
license with accompanying NOTICE files).


These tasks will take some time and we can work on them together later. I
apologize for being a bit busy lately.

Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Calvin Kirs]

Carry my +1 binding from dev@ vote.

On Thu, Apr 18, 2024 at 7:06 PM Bertil Chapuis  wrote:

> Hello Everyone,
>
> This is a call for a vote to release Apache Baremaps 0.7.3 (incubating),
> release candidate 1. Apache Baremaps is a toolkit and a set of
> infrastructure components for creating, publishing, and operating online
> maps.
>
> We already voted for this release candidate in our dev mailing list:
> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
>
> We now would like to request the Incubator PMC members to review and vote
> on this release.
>
> You can read the release notes here:
> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
>
> The commit to be voted upon:
> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
>
> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
>
> Its tag is v0.7.3-rc1.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
>
> The hashes of the artifacts are as follows:
> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
> ./apache-baremaps-0.7.3-incubating-src.tar.gz
> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
> ./apache-baremaps-0.7.3-incubating-bin.tar.gz
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/bchapuis.asc
> https://downloads.apache.org/incubator/baremaps/KEYS
>
> The README file for the src distribution contains instructions for
> building and testing the release.
>
> Please vote on releasing this package as Apache Baremaps 0.7.3.
>
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Baremaps 0.7.3
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because…
>
> Best regards,
>
> Bertil Chapuis
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Best wishes！
CalvinKirs

Re: [VOTE] Release Apache Baremaps 0.8.1-rc1 (incubating)

[Calvin Kirs]

-1 binding

I checked:

Source Package

- The DISCLAIMER file is missing (we need to include this file during
incubation).
- The NOTICE and LICENSE files look good.

Binary Package

- The DISCLAIMER file is missing.
- The LICENSE file looks fine, but you haven’t included LICENSE files for
other dependencies [1], such as Hadoop [2].
- The NOTICE file should follow Section 4 of the Apache License 2.0 (AL2)
[3]. (If dependencies use AL2 and have a NOTICE file, AL2 generally
requires including them. To be honest, I’ve only seen this requirement with
AL2 .) For example [4].



[1]https://www.apache.org/legal/release-policy.html#license-file
[2]https://github.com/apache/hadoop/tree/trunk/licenses-binary
[3]https://www.apache.org/licenses/LICENSE-2.0.html
[4]https://github.com/apache/hadoop/blob/trunk/NOTICE-binary



On Mon, Nov 11, 2024 at 3:33 PM Leo  wrote:

> +1
>
> Compiled on macOS, java 21 + checked sources
>
> > On 9 Nov 2024, at 15:48, Bertil Chapuis  wrote:
> >
> > Hello Everyone,
> >
> > I have created a build for Apache Baremaps (incubating) 0.8.1, release
> candidate 1. This release comes with exciting changes, including support
> for geoparquet, rasters, contours, and hillshade (more highlights in the
> release notes). Additionally, I removed the DISCLAIMER-WIP, as we addressed
> all the known issues related to licensing. Thanks to everyone who has
> contributed to this release!
> >
> > You can read the release notes here:
> > https://github.com/apache/incubator-baremaps/releases/tag/v0.8.1-rc1
> >
> > The commit to be voted upon:
> > https://github.com/apache/incubator-baremaps/tree/v0.8.1-rc1
> >
> > Its tag is v0.8.1-rc1 and its hash is
> a278ee95120965aa39eeaf848484abff3f3950f6.
> >
> > The artifacts to be voted on are located here:
> > https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.1-rc1/
> >
> > The hashes of the artifacts are as follows:
> >
> 72f9fce28d874a1965cefaad248a54b7984c833b110264b30210a25579e695933af20386d00da3c9e2c446709e87b33d4935658e9ed7ab7b5e79b5cf1ec1c8d7
> ./apache-baremaps-0.8.1-rc1-incubating-src.tar.gz
> >
> 4ae01426272b30e2df2fc5cad6a9efcad1d6c2dc26fc05befce1d9503e751737aecb0b4015cd5c6e990716530c3272c365e859438da4813acc5b9748e2c12c31
> ./apache-baremaps-0.8.1-rc1-incubating-bin.tar.gz
> >
> > Release candidate artifacts are signed automatically with the key
> (C81AC42AF2A7CACDF4C8A4F6936E280DF16599CB) created by the INFRA team:
> > https://downloads.apache.org/incubator/baremaps/KEYS
> >
> > The README file for the src distribution contains instructions for
> building and testing the release.
> >
> > Please vote on releasing this package as Apache Baremaps 0.8.1.
> >
> > The vote is open for 72 hours starting on Monday. It passes if a
> majority of at least three +1 PMC votes are cast.
> > [ ] +1 Release this package as Apache Baremaps 0.8.1
> > [ ] 0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Here is my vote:
> > +1 (non-binding): I built from source; executed the binary distribution;
> checked the checksums; checked the signatures.
> >
> > Best regards,
> >
> > Bertil
> > -
> > 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
>
>

-- 
Best wishes！
CalvinKirs

Re: [VOTE] Release Apache Baremaps 0.8.2-rc3 (incubating)

[Calvin Kirs]

Thanks Bertil,

+1 （binding）

I checked:
- incubating in name
- signatures and hashes are fine
- disclaimer exists
- license and notice files look good
- file have correct ASF headers if necessary

On Fri, Feb 7, 2025 at 9:36 PM Bertil Chapuis  wrote:

> Hello Everyone,
>
> Following the issue identified in the way NOTICE files were included in
> the project, here is a new release candidate. This version also integrates
> the latest contributions made to the project.
>
> You can read the release notes here:
> https://github.com/apache/incubator-baremaps/releases/tag/v0.8.2-rc3
>
> The commit to be voted upon:
> https://github.com/apache/incubator-baremaps/tree/v0.8.2-rc3
>
> Its tag is v0.8.2-rc3 and its hash is
> 03512049ff65bc15a24f39450810c2ac578a217f.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc3/
>
> The hashes of the artifacts are as follows:
> 69e57f9aa07d32d2759efcf0d7127b6cbcb46512d2e2c46d9f15171f5a03e99f529bb8e70d0f711af2f7ecf11eff39472cf4a25b5178937567ed7794bfbfb46e
> ./apache-baremaps-0.8.2-rc3-incubating-src.tar.gz
> f3e75ec2b5ddd2b729f1d8c683cf30f1c4cabc0e9eb7a32b0200d1e8b82710b123809f26dc6d3b00895f520339a240b3aab05230f6a14e9fb20f1b566f7b4060
> ./apache-baremaps-0.8.2-rc3-incubating-bin.tar.gz
>
> Release candidate artifacts are signed automatically with the key created
> by the INFRA team (C81AC42AF2A7CACDF4C8A4F6936E280DF16599CB):
> https://downloads.apache.org/incubator/baremaps/KEYS
>
> The maven staging repository for this release is:
> https://repository.apache.org/content/repositories/orgapachebaremaps-1012/
>
> The maven artifacts are signed with my PGP key
> (16D7A0B27D5ADD52BD57932971751399FB39CB84):
> https://downloads.apache.org/incubator/baremaps/KEYS
>
> The README file for the src distribution contains instructions for
> building and testing the release.
>
> Please vote on releasing this package as Apache Baremaps 0.8.2
> (incubating).
>
> The vote is open for 72 hours but can be open longer if the required
> number of votes is not obtained. It passes if a majority of at least three
> +1 PPMC votes are cast.
> [ ] +1 Release this package as Apache Baremaps 0.8.2 (incubating)
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Here is my vote.
> +1 (non-binding):
> - checked the presence of the LICENSE, NOTICE, and DISCLAIMER files in src
> and bin distribution;
> - checked the output of the rat report in the src distribution;
> - built and executed from the src distribution;
> - executed the bin distribution;
> - checked the checksums;
> - checked the signatures;
>
> I added some of the commands I used to verify this release below.
>
> Best regards,
>
> Bertil
>
> ———
>
> # Download the source release
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc3/apache-baremaps-0.8.2-rc3-incubating-src.tar.gz
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc3/apache-baremaps-0.8.2-rc3-incubating-src.tar.gz.asc
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc3/apache-baremaps-0.8.2-rc3-incubating-src.tar.gz.sha512
>
> # Verify the signature of the source release
> gpg --verify apache-baremaps-0.8.2-rc3-incubating-src.tar.gz.asc
>
> # Verify the checksum of the source release
> shasum -a 512 -c apache-baremaps-0.8.2-rc3-incubating-src.tar.gz.sha512
>
> # Unpack the source release and navigate to the source directory
> tar -xvf apache-baremaps-0.8.2-rc3-incubating-src.tar.gz
> cd apache-baremaps-0.8.2-incubating-src
>
> # Check the license headers
> mvn apache-rat:check
>
> # Generate the license headers report
> mvn apache-rat:rat
> less target/rat.txt
>
> # Build the project from source
> mvn clean package
>
> # Download the binary release
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc3/apache-baremaps-0.8.2-rc3-incubating-bin.tar.gz
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc3/apache-baremaps-0.8.2-rc3-incubating-bin.tar.gz.asc
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc3/apache-baremaps-0.8.2-rc3-incubating-bin.tar.gz.sha512
>
> # Verify the signature of the binary release
> gpg --verify apache-baremaps-0.8.2-rc3-incubating-bin.tar.gz.asc
>
> # Verify the checksum of the binary release
> shasum -a 512 -c apache-baremaps-0.8.2-rc3-incubating-bin.tar.gz.sha512
>
> # Unpack the binary release and navigate to the binary directory
> tar -xvf apache-baremaps-0.8.2-rc3-incubating-bin.tar.gz
> cd apache-baremaps-0.8.2-incubating-bin
>
> # Check if the binary release works
> ./bin/baremaps --version
>
> # Download a jar from the nexus repository
> wget
> https://repository.apache.org/content/repositories/orgapachebaremaps-1012/org/apache/baremaps/baremaps-data/0.8.2/baremaps-data-0.8.2.jar
> wget
> https://repository.apache.org/content/repositories/orgapachebaremaps-1012/org/apache/bar

Re: [VOTE] Release Apache Baremaps 0.8.1-rc4 (incubating)

[Calvin Kirs]

+1 binding (kirs IPMC)

I checked:
- incubating in name
- signatures and hashes are fine
- disclaimer-wip exists
- license and notice files look good
- file have correct ASF headers if necessary

The NOTICE for bundled items in the binary package should preferably be
appended to the NOTICE file in the root directory.

On Thu, Dec 12, 2024 at 9:51 AM Julian Hyde  wrote:

> +1 jhyde (binding, member IPMC)
>
> Downloaded; checked signatures and digests; checked NOTICE, LICENSE,
> README, DISCLAIMER; compiled and ran tests on Ubuntu 24.04.1, x86_64, JDK
> 21, Maven 3.8.1. Ran apache-rat.
>
> Julian
>
>
> > On Dec 11, 2024, at 12:26 AM, Leo  wrote:
> >
> > Hello,
> >
> > Ran checks on licenses, built from sources, checked binary.
> >
> > Here is my vote:
> >
> > +1 (non binding)
> >
> > Best,
> > Leonard
> >
> >> On 6 Dec 2024, at 22:43, Bertil Chapuis  wrote:
> >>
> >> Hello Everyone,
> >>
> >> Here are some of the commands I use to check the releases. I don’t use
> a script as the outputs often require to be checked individually. I hope
> this may help those of you who are not yet familiar with the process.
> >>
> >> Notice that mvn apache-rat:check should work for a freshly decompressed
> archive, but may fail after building from source or after generating the
> report due to the creation of additional files.
> >>
> >> Best,
> >>
> >> Bertil
> >>
> >>
> >>
> >> — Source release —
> >>
> >> # Download the source release
> >> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.1-rc4/apache-baremaps-0.8.1-rc4-incubating-src.tar.gz
> >> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.1-rc4/apache-baremaps-0.8.1-rc4-incubating-src.tar.gz.asc
> >> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.1-rc4/apache-baremaps-0.8.1-rc4-incubating-src.tar.gz.sha512
> >>
> >> # Verify the signature of the source release
> >> gpg --verify apache-baremaps-0.8.1-rc4-incubating-src.tar.gz.asc
> >>
> >> # Verify the checksum of the source release
> >> shasum -a 512 -c apache-baremaps-0.8.1-rc4-incubating-src.tar.gz.sha512
> >>
> >> # Unpack the source release and navigate to the source directory
> >> tar -xvf apache-baremaps-0.8.1-rc4-incubating-src.tar.gz
> >> cd apache-baremaps-0.8.1-incubating-src
> >>
> >> # Check the license headers
> >> mvn apache-rat:check
> >>
> >> # Generate the license headers report
> >> mvn apache-rat:rat
> >> less target/rat.txt
> >>
> >> # Build the project from source
> >> mvn clean package
> >>
> >>
> >>
> >> — Binary release —
> >>
> >> # Download the binary release
> >> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.1-rc4/apache-baremaps-0.8.1-rc4-incubating-bin.tar.gz
> >> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.1-rc4/apache-baremaps-0.8.1-rc4-incubating-bin.tar.gz.asc
> >> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.1-rc4/apache-baremaps-0.8.1-rc4-incubating-bin.tar.gz.sha512
> >>
> >> # Verify the signature of the binary release
> >> gpg --verify apache-baremaps-0.8.1-rc4-incubating-bin.tar.gz.asc
> >>
> >> # Verify the checksum of the binary release
> >> shasum -a 512 -c apache-baremaps-0.8.1-rc4-incubating-bin.tar.gz.sha512
> >>
> >> # Unpack the binary release and navigate to the binary directory
> >> tar -xvf apache-baremaps-0.8.1-rc4-incubating-bin.tar.gz
> >> cd apache-baremaps-0.8.1-incubating-bin
> >>
> >> # Check if the binary release works
> >> ./bin/baremaps --version
> >>
> >>
> >>
> >>
> >>> On 6 Dec 2024, at 15:58, Bertil Chapuis  wrote:
> >>>
> >>> Hello Everyone,
> >>>
> >>> This release candidate addresses several licensing issues identified
> on the incubator mailing list. I’ve done my best to harden everything, and
> I’d like to thank you in advance for your help in assessing this release
> candidate. Let’s think of this as the liveness property of Baremaps:
> something good eventually happens 😉
> >>>
> >>> You can read the release notes here:
> >>> https://github.com/apache/incubator-baremaps/releases/tag/v0.8.1-rc4
> >>>
> >>> The commit to be voted upon:
> >>> https://git

Re: [VOTE] Release maven artifacts for Apache Baremaps 0.8.1-rc4 (incubating)

[Calvin Kirs]

+1 kirs (IPMC member)

On Tue, Dec 17, 2024 at 12:46 PM Leo  wrote:

> Hi,
>
> +1 (non binding)
>
> Best,
> Leonard
>
>
> > On 16 Dec 2024, at 09:43, Andrea Borghi 
> wrote:
> >
> > Hello,
> > +1 (non binding)
> >
> > Bests
> > Andrea
> >
> >> On Mon, Dec 16, 2024 at 1:45 AM Julian Hyde 
> wrote:
> >>
> >> +1 jhyde (IPMC member)
> >>
> >>>> On Dec 15, 2024, at 6:12 AM, Bertil Chapuis 
> wrote:
> >>>
> >>> Hello Everyone,
> >>>
> >>> This is a call for a vote to release Maven artifacts for Apache
> Baremaps
> >> 0.8.1 (incubating), release candidate 4. This is the first time we are
> >> publishing Maven artifacts on the Nexus repository. For this reason, I
> >> decided to separate this vote from the main release process. In the
> future,
> >> all artifacts will be voted on in the same thread.
> >>>
> >>> The artifacts have been built and published with the tag v0.8.1-rc4 and
> >> the hash e6a24651ab7e347f336c7a8544984e998dfc0dd9.
> >>>
> >>> The maven staging repository for this release is:
> >>>
> >>
> https://repository.apache.org/content/repositories/orgapachebaremaps-1008/
> >>>
> >>> The artifacts are signed with the PGP key
> >> 16D7A0B27D5ADD52BD57932971751399FB39CB84, which is available in the KEYS
> >> file:
> >>> https://downloads.apache.org/incubator/baremaps/KEYS
> >>>
> >>> The vote will be open for at least 72 hours until the necessary number
> >>> of votes are reached.
> >>>
> >>> Please vote accordingly:
> >>> [ ] +1 approve
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove with the reason
> >>>
> >>> Here is my +1 (non-binding).
> >>> - I have downloaded and inspected several jars manually.
> >>> - I have ensured that the LICENSE and NOTICE files in the jars are the
> >> same as the ones in the source distribution.
> >>> - I have verified that several jars are signed correctly with the PGP
> >> key.
> >>> - I have verified that several checksums (md5 and sha256) match the
> jars.
> >>> - I have tested the SNAPSHOT version of the jar in a project and it
> >> worked as expected.
> >>>
> >>> Here are a few commands I used to verify the artifacts:
> >>> gpg --verify baremaps-dem-0.8.1.jar.asc baremaps-dem-0.8.1.jar
> >>> md5sum baremaps-dem-0.8.1.jar
> >>> shasum baremaps-dem-0.8.1.jar
> >>>
> >>> Here are the setting I added to my Maven settings.xml file:
> >>> 
> >>>   apache.snapshots.https
> >>>   MY_USERNAME
> >>>   MY_PASSWORD
> >>> 
> >>>
> >>> Here are the settings I added to my pom.xml files:
> >>> 
> >>>   
> >>>   apache.snapshots.https
> >>>   https://repository.apache.org/snapshots
> >>>   
> >>>   false
> >>>   
> >>>   
> >>>   true
> >>>   
> >>> 
> >>> 
> >>> 
> >>>   
> >>>   org.apache.baremaps
> >>>   baremaps-dem
> >>>   0.8.1-SNAPSHOT
> >>>   
> >>> 
> >>>
> >>> Best regards,
> >>>
> >>> Bertil
> >>>
> >>>
> >>>
> >>> -
> >>> 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
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
> For additional commands, e-mail: dev-h...@baremaps.apache.org
>
>

-- 
Best wishes！
CalvinKirs

Re: Suggestions to Enhance New Contributors' Onboarding Experience

[Calvin Kirs]

Hi Yongjun,

Thank you for sharing these suggestions from the perspective of a new
contributor.
Could you describe the specific changes you’d like to make?
We truly appreciate your contributions:)

On Sun, Jan 26, 2025 at 12:20 PM 홍용준  wrote:

> Dear Baremaps Team,
> When I first explore an open-source project, I follow a series of steps to
> familiarize myself with it. Based on this experience, I have outlined a few
> suggestions that could enhance the onboarding experience for new
> contributors to the Baremaps project.
>
>1.
>
>*Issue Labeling*
>
>While browsing the issues, I noticed that recent issues in the Baremaps
>project lack labels. Categorizing or prioritizing issues with labels can
>help new contributors quickly understand the context and navigate
> through
>them.
>2.
>
>*Standardized Templates*
>
>Introducing a detailed and standardized issue template could make the
>project more approachable for contributors. For reference, JUnit5
> provides
>well-structured issue templates that might serve as a good example:
>JUnit5 Issue Templates
>
>
>Similarly, a pull request (PR) template with a checklist could guide
>contributors before submitting their PRs. This would allow them to
> verify
>key requirements before maintainers review their submissions. For
> reference:
>JUnit5 Pull Request Template
><
> https://github.com/junit-team/junit5/blob/main/.github/PULL_REQUEST_TEMPLATE.md
> >
>3.
>
>*Ideal Issue Management Practices*
>
>Implementing an automated process to tag issues with labels like
>“waiting-for-triage” upon creation could make the issue-triage workflow
>smoother. Once maintainers review and categorize the issues,
> contributors
>can easily identify the type of issue and engage more effectively.
>4.
>
>*Improved Documentation*
>
>The existing Getting Started guide is well-written. However, adding
>step-by-step instructions, similar to Apache Kafka’s quickstart guide
>, could further enhance its
>usability.
>Alternatively, adopting a dual-track structure like TensorFlow's
>documentation, which caters separately to beginners and advanced users,
>might also be worth considering:
>TensorFlow Tutorials 
>5.
>
>*Comprehensive User Guide*
>
>While creating a comprehensive user guide may feel resource-intensive,
>it can significantly improve the experience for new users. For instance,
>JUnit provides an excellent User Guide
><
> https://github.com/junit-team/junit5/tree/main/documentation/src/docs/asciidoc/user-guide
> >
> that
>serves as a long-term resource for contributors and users alike.
>
> I understand that some of these suggestions may require considerable time
> and effort to implement. However, they could be considered as part of
> long-term goals to make Baremaps even more accessible to the community.
> Finally, I would like to express my admiration for the incredible work
> behind Baremaps. I am looking forward to contributing consistently to this
> fantastic project.
>
> Best regards,
>
> Yongjun Hong
>


-- 
Best wishes！
CalvinKirs

Re: [VOTE] Release Apache Baremaps 0.8.2-rc2 (incubating)

[Calvin Kirs]

Hi Bertil,

I'll be making some changes over the next couple of days, mainly related to
LICENSE issues.

If it's not urgent, I'd prefer to delay the release of this version. btw,
is there anyone else interested in taking on the next version release?

On Wed, Jan 15, 2025 at 8:04 PM Bertil Chapuis  wrote:

> Hello Everyone,
>
> Following the issue with the copyright identified in the NOTICE file, here
> is a second release candidate.
>
> You can read the release notes here:
> https://github.com/apache/incubator-baremaps/releases/tag/v0.8.2-rc2
>
> The commit to be voted upon:
> https://github.com/apache/incubator-baremaps/tree/v0.8.2-rc2
>
> Its tag is v0.8.2-rc2 and its hash is
> 905719c6ec705de2abbc15a0e57e206255c79373.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc2/
>
> The hashes of the artifacts are as follows:
> ce8ad63320b1d3d032229ad0e3c56181b38136872dbe81c437dac861421a0ee8207f5eb42eaec2e7478c258b1a1343d13c76c16b545d3e5755752a71b0e9aaf2
> ./apache-baremaps-0.8.2-rc2-incubating-src.tar.gz
> 5f691e5617ad45aee58e79f6695293bf84241018a379ad68c4f30eb654c43612c51107a831fb799e3cc990c02e8f324ce6a53f98d14d98feccf77b6ecca9975a
> ./apache-baremaps-0.8.2-rc2-incubating-bin.tar.gz
>
> Release candidate artifacts are signed automatically with the key created
> by the INFRA team (C81AC42AF2A7CACDF4C8A4F6936E280DF16599CB):
> https://downloads.apache.org/incubator/baremaps/KEYS
>
> The maven staging repository for this release is:
> https://repository.apache.org/content/repositories/orgapachebaremaps-1010
>
> The maven artifacts are signed with my PGP key
> (16D7A0B27D5ADD52BD57932971751399FB39CB84):
> https://downloads.apache.org/incubator/baremaps/KEYS
>
> The README file for the src distribution contains instructions for
> building and testing the release.
>
> Please vote on releasing this package as Apache Baremaps 0.8.2
> (incubating).
>
> The vote is open for 72 hours but can be open longer if the required
> number of votes is not obtained. It passes if a majority of at least three
> +1 PPMC votes are cast.
> [ ] +1 Release this package as Apache Baremaps 0.8.2 (incubating)
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Here is my vote.
> +1 (non-binding):
> - checked the presence of the LICENSE, NOTICE, and DISCLAIMER files in src
> and bin;
> - checked the copyright in the NOTICE files included in the artifacts of
> the release.
> - checked the presence of the licenses and notices directories in src and
> bin;
> - checked the output of the rat report in the source release;
> - built and executed from source;
> - executed the binary distribution;
> - checked the checksums;
> - checked the signatures;
>
> I added some of the commands I used to verify this release below.
>
> Best regards,
>
> Bertil
>
> ———
>
> # Download the source release
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc2/apache-baremaps-0.8.2-rc2-incubating-src.tar.gz
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc2/apache-baremaps-0.8.2-rc2-incubating-src.tar.gz.asc
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc2/apache-baremaps-0.8.2-rc2-incubating-src.tar.gz.sha512
>
> # Verify the signature of the source release
> gpg --verify apache-baremaps-0.8.2-rc2-incubating-src.tar.gz.asc
>
> # Verify the checksum of the source release
> shasum -a 512 -c apache-baremaps-0.8.2-rc2-incubating-src.tar.gz.sha512
>
> # Unpack the source release and navigate to the source directory
> tar -xvf apache-baremaps-0.8.2-rc2-incubating-src.tar.gz
> cd apache-baremaps-0.8.2-incubating-src
>
> # Check the license headers
> mvn apache-rat:check
>
> # Generate the license headers report
> mvn apache-rat:rat
> less target/rat.txt
>
> # Build the project from source
> mvn clean package
>
> # Download the binary release
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc2/apache-baremaps-0.8.2-rc2-incubating-bin.tar.gz
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc2/apache-baremaps-0.8.2-rc2-incubating-bin.tar.gz.asc
> wget
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.8.2-rc2/apache-baremaps-0.8.2-rc2-incubating-bin.tar.gz.sha512
>
> # Verify the signature of the binary release
> gpg --verify apache-baremaps-0.8.2-rc2-incubating-bin.tar.gz.asc
>
> # Verify the checksum of the binary release
> shasum -a 512 -c apache-baremaps-0.8.2-rc2-incubating-bin.tar.gz.sha512
>
> # Unpack the binary release and navigate to the binary directory
> tar -xvf apache-baremaps-0.8.2-rc2-incubating-bin.tar.gz
> cd apache-baremaps-0.8.2-incubating-bin
>
> # Check if the binary release works
> ./bin/baremaps --version
>
> # Download a jar from the nexus repository
> wget
> https://repository.apache.org/content/repositories/orgapachebaremaps-1010/org/apache/baremaps/baremaps-data/0.8.2/baremaps-d

Re: March report for Apache Baremaps

[Calvin Kirs]

Yes… we’re getting very close to graduation.

We can refer to this document [1] for an initial review.

We don’t yet have a guide for releasing new versions?

Also, it would be great if other PPMC members could step up as the next RM.

The community needs to demonstrate its ability to manage releases
effectively.

I’ll check on website and branding-related issues later (I reviewed and
resolved some of them last year).

A huge thanks to everyone in the community for their contributions!

[1]
https://community.apache.org/apache-way/apache-project-maturity-model.html

On Thu, Mar 6, 2025 at 8:03 AM Julian Hyde  wrote:

> PS I signed the report.
>
> > On Mar 5, 2025, at 3:59 PM, Julian Hyde  wrote:
> >
> > Thanks for adding the report promptly.
> >
> > The Board reviews a lot of reports, and so does not like hyperlinks.
> Rather than
> >
> >   > The February release summarizes well the latest developments:
> >   > https://github.com/apache/incubator-baremaps/releases/tag/v0.8.2
> >
> > I would say explicitly what the release achieved. The biggest thing to
> me is the number of contributors - 12 issues fixed by 6 contributors
> indicates a vibrant project.
> >
> > I agree that Baremaps is near graduation. (I recommend that community
> starts discussing graduation… including what’s left (if anything) to be
> done before graduation, the text of the graduation resolution, initial PMC
> members and chair… on this list. Scan the dev@ archives of
> recently-graduated projects to see how they did it.)
> >
> > Julian
> >
> >
> >> On Mar 5, 2025, at 8:08 AM, Bertil Chapuis  wrote:
> >>
> >> Hello Everyone,
> >>
> >> I published the March report directly on Confluence. Do not hesitate to
> add your comments or to sign it. It is mostly a copy of the February report
> for which I missed the notification.
> >>
> >>
> https://cwiki.apache.org/confluence/display/INCUBATOR/March2025#baremaps
> >>
> >> 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

Re: March report for Apache Baremaps

[Calvin Kirs]

I've only conducted a preliminary check... I think we can draft a document
on GitHub or another platform(wiki?), and then go through a step-by-step
review based on the maturity model together.

On Thu, Mar 6, 2025 at 11:10 AM Calvin Kirs  wrote:

> Yes… we’re getting very close to graduation.
>
> We can refer to this document [1] for an initial review.
>
> We don’t yet have a guide for releasing new versions?
>
> Also, it would be great if other PPMC members could step up as the next
> RM.
>
> The community needs to demonstrate its ability to manage releases
> effectively.
>
> I’ll check on website and branding-related issues later (I reviewed and
> resolved some of them last year).
>
> A huge thanks to everyone in the community for their contributions!
>
> [1]
> https://community.apache.org/apache-way/apache-project-maturity-model.html
>
> On Thu, Mar 6, 2025 at 8:03 AM Julian Hyde  wrote:
>
>> PS I signed the report.
>>
>> > On Mar 5, 2025, at 3:59 PM, Julian Hyde  wrote:
>> >
>> > Thanks for adding the report promptly.
>> >
>> > The Board reviews a lot of reports, and so does not like hyperlinks.
>> Rather than
>> >
>> >   > The February release summarizes well the latest developments:
>> >   > https://github.com/apache/incubator-baremaps/releases/tag/v0.8.2
>> >
>> > I would say explicitly what the release achieved. The biggest thing to
>> me is the number of contributors - 12 issues fixed by 6 contributors
>> indicates a vibrant project.
>> >
>> > I agree that Baremaps is near graduation. (I recommend that community
>> starts discussing graduation… including what’s left (if anything) to be
>> done before graduation, the text of the graduation resolution, initial PMC
>> members and chair… on this list. Scan the dev@ archives of
>> recently-graduated projects to see how they did it.)
>> >
>> > Julian
>> >
>> >
>> >> On Mar 5, 2025, at 8:08 AM, Bertil Chapuis  wrote:
>> >>
>> >> Hello Everyone,
>> >>
>> >> I published the March report directly on Confluence. Do not hesitate
>> to add your comments or to sign it. It is mostly a copy of the February
>> report for which I missed the notification.
>> >>
>> >>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/March2025#baremaps
>> >>
>> >> 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
>


-- 
Best wishes！
CalvinKirs