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
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
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
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 In
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 In
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 th
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, 2
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
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:
> >
e.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,
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 abou
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 or
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
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 chan
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 throu
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)
+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 T
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
aps/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 ou
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
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/addition
etails 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 emai
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, D
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 websi
c 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
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://comm
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
> 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
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 Eve
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
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,
e 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 s
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
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 $FIL
s 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
> > re
t; 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:
> >>
>
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.
> >>
+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 ha
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 do
ersion 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
+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 th
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, publ
-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 dep
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 iden
+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
+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
> >
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-so
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
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 releas
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 gr
50 matches
Mail list logo
