Thank you!
For last release please change to N/A - I think that is referring to ASF
release.
Also if you could answer the last three questions in the report too.
On Mon, Aug 31, 2020 at 5:43 PM Jia Yu wrote:
> Dear Sedona Mentors and other committers,
>
>
>
> I just added some new content to
Great. Do you mean issue should go to JIRA? issues@ should just be a feed
of JIRA
On Mon, Sep 7, 2020 at 3:14 AM Jia Yu wrote:
> Hello all,
>
> 1. Sedona website has been moved to http://sedona.apache.org/ It is still
> using the old content for now. The new website will come soon.
>
> 2.
Fantastic. Thank you for all the details. Hopefully the source import will
be completed soon.
On Tue, Sep 1, 2020 at 1:14 AM Jia Yu wrote:
> Thanks for the comments. I have fixed that.
>
>
>
> On Mon, Aug 31, 2020 at 10:06 PM Felix Cheung
>
> wrote:
>
>
>
>
Actually I just saw the update from this morning
It’s here
https://github.com/apache/incubator-sedona
On Tue, Sep 1, 2020 at 12:33 PM Felix Cheung wrote:
> Fantastic. Thank you for all the details. Hopefully the source import will
> be completed soon.
>
>
> On Tue, Sep 1, 2020
> On Sat, Oct 3, 2020 at 5:31 PM Jia Yu wrote:
>
> > Hi Felix,
> >
> > I will write the report tomorrow. I will let you guys know once I am
> done.
> >
> > Thanks,
> > Jia
> >
> > On Sat, Oct 3, 2020 at 5:18 PM Felix Cheung
> > wrote:
&
Thx
On Mon, Oct 5, 2020 at 10:42 PM Jia Yu wrote:
> Yes, indeed. I am not sure why. I copied the content back and now it has
> all sections and text.
>
> On Mon, Oct 5, 2020 at 8:39 PM Felix Cheung
> wrote:
>
> > Thanks- it looks like the report is truncated? It se
Maybe it is moderation? Although I don’t think I’ve seen any mail that is
pending moderation.
But generally we can have discussion in dev@
issues@ in a lot of projects are dedicated only for JIRA updates (which
could be a lot)
On Thu, Oct 1, 2020 at 7:38 PM Jia Yu wrote:
> Hello Felix,
>
>
Any volunteer for this report?
On Sat, Sep 19, 2020 at 6:07 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
The report is already on the wiki page? I’m still trying to see something
is missing.
On Thu, Aug 6, 2020 at 12:37 AM Justin Mclean wrote:
> Hi,
>
> This report is now late, please submit it.
>
> Thanks,
>
> Justin
>
>
Ok I will take out the date/placeholder.
Jia - it will be great if you go add your thought in the bootstrapping.
On Thu, Aug 6, 2020 at 4:23 PM Justin Mclean
wrote:
> HI,
>
>
>
> > The report is already on the wiki page? I’m still trying to see
> something is missing.
>
>
>
> It because I use
submit the CLA and then the code will be
>
> imported to ASF Git repo."
>
>
>
> I have contacted the committer Masha via an individual email several days
>
> ago but am still waiting for her response.
>
>
>
> Thanks,
>
> Jia
>
>
>
>
And as a reminder the report is up
https://cwiki.apache.org/confluence/display/INCUBATOR/August2020
Please review.
From: jmcl...@apache.org
Sent: Saturday, August 1, 2020 5:54:53 PM
To: d...@sedona.incubator.apache.org
Subject: Podling Sedona Report Reminder -
Hi,
We are due for the first report, I have taken a shot at the updates, under
Sedona in
https://cwiki.apache.org/confluence/display/INCUBATOR/August2020
Please review and edit.
Felix
Sounds good. You can request on
https://selfserve.apache.org/
To create a repo for incubator-sedona-website.git
From: Jia Yu
Sent: Friday, July 31, 2020 4:37:15 PM
To: dev@sedona.apache.org
Subject: Sedona project website template
Hi folks,
We are creating a
I’d think you just open a ticket on INFRA, similar to this
https://issues.apache.org/jira/browse/INFRA-20830
On Tue, Dec 8, 2020 at 2:21 AM Jia Yu wrote:
> Hi Felix,
>
> I notice that JIRA does not send notifications to us or the dev list so I
> sometimes miss users' JIRA ticket.
>
> When I
ovided" in
> Sedona's POM.xml. If a user wants to use CRS transformation in Sedona, they
> will have to add some GeoTools library by themselves.
>
>
> On Mon, Nov 23, 2020 at 6:24 PM Felix Cheung
> wrote:
>
> > On Mon, Nov 23, 2020 at 6:03 PM Felix Cheung
> > wr
F has any recommended work
> arounds for shipping code with licenses that it does not approve of.
>
> Cheers,
>
> Jim
>
> On 11/23/20 1:41 PM, Felix Cheung wrote:
> > I can help review around Dev 13 to give a first pass. It should give you
> an
> > easier path t
On Mon, Nov 23, 2020 at 6:03 PM Felix Cheung wrote:
> I’d strongly recommend the community to move towards the first release
> with the WIP disclaimer
>
> https://incubator.apache.org/policy/incubation.html#work_in_progress_disclaimer
>
> https://incubator.apache.org/poli
Hello,
There has been, in the past, incidents where the shared Travis resource is
exhausted.
It might help if you restrict to build one branch (like main) only.
Some projects have acquired corporate sponsorship for a separate Travis
instance.
Some has moved to another system, like GitHub
each Spark version:
>> >
>> > https://github.com/apache/zeppelin/blob/master/spark/pom.xml#L185
>> >
>> >
>> > Do you think this method is better?
>> >
>> >
>> >
>> > Netanel Malka,
>> > Big Data Consultant
>&g
I am not sure it should be a branch? It is common to deal with this as a
compile target, not as a separate branch. A separate branch might have
difficulty to release?
There are a few example in projects where they handle multiple Spark target
version like this.
On Wed, Nov 11, 2020 at 12:56 PM
I believe this is the jts discussion in the other thread.
On Mon, Nov 16, 2020 at 12:54 PM Netanel Malka wrote:
> Hi Jia,
> I tried to use the branch sedona-1.0-doc but the artifact for 1.16.2 is
> not in the Maven Central so I cannot compile the project.
>
> I got:
> The POM for
t;
> > >>> I totally agree with Jim on that. Jim, would you like to take the
> lead
> > >> on that - I trust that you can bring this task to completion. Jia,
> would
> > >> you please let us know how we can incorporate the changes into the
Great progress!
To add,
A) I’d strongly recommend the WIP disclaimer - it would be much easier to
pass with in the first release
https://incubator.apache.org/policy/incubation.html#disclaimers
B) more info in signing, checksum
https://infra.apache.org/release-signing.html
C) signing key should
Reminder.
From: jmcl...@apache.org
Sent: Friday, October 23, 2020 10:54:49 PM
To: d...@sedona.incubator.apache.org
Subject: Podling Sedona Report Reminder - November 2020
Dear podling,
This email was sent by an automated system on behalf of the Apache
eline: https://incubator.apache.org/guides/distribution.html
>
> If you scroll down to the bottom, you will see the section.
>
> @Felix Cheung Felix, does Pawel need to be
> aware of anything else, besides the incubator PyPi guideline?
>
> Thank you very much!
> Jia
>
> On
ription:
> cid:image001.jpg@01C85203.36A2AF30]
> --
> *From:* Paweł Kociński
> *Sent:* Wednesday, December 30, 2020 22:09
> *To:* Jia Yu
> *Cc:* dev@sedona.apache.org; Jinxuan Wu; Mohamed Sarwat; Netanel Malka;
> Zongsi Zhang; Felix Cheung; Netanel Malka
>
/api/javadoc auto generated? if that is the case,
we probably shouldn't have the HTML committed in the repo
5.
/trunk/import/*
what is this for?
6. should add a small section on how to build (or link to) the project in
README.md
On Wed, Dec 30, 2020 at 6:24 PM Felix Cheung wrote:
> Yes
>
https://sedona.staged.apache.org/download/publish/.
> The "compile code" is still available:
> https://sedona.staged.apache.org/download/compile/
>
> Regards,
> Jia
>
> On Sat, Jan 23, 2021 at 5:46 PM Felix Cheung
> wrote:
>
>> 1/ the tarball should unpack to incub
We should definitely have the source release on
https://dist.apache.org/repos/dist/dev/incubator/
We are voting for source release (and the git tag) - binaries are for
convenience.
Von, can you clarify the final package name inline? I think you are looking
at the artifact ID not a package name?
1/ the tarball should unpack to incubator-sedona-sedona-1.0.0-incubating
and not incubator-sedona-sedona-1.0.0-incubating-rc1 - this is because once
the vote is passed, you will not be rebuilding the tarball - as the one we
voted on, signed etc, that one will be the actual release.
2. also
> be
> > able to publish it before rc3.
> >
> > If you have any questions, refer to the voting results of other items in
> > the incubation list. Of course, you are welcome to discuss it in your
> email.
> >
> > [1] https://dist.apache.org/repos/dist/dev/in
Reminder
From: jmcl...@apache.org
Sent: Wednesday, January 20, 2021 10:20:08 PM
To: d...@sedona.incubator.apache.org
Subject: Podling Sedona Report Reminder - February 2021
Dear podling,
This email was sent by an automated system on behalf of the Apache
This could be highly interesting!
From: Youngwoo Kim (김영우)
Sent: Monday, February 1, 2021 7:03:36 PM
To: Jia Yu
Cc: dev@sedona.apache.org
Subject: Re: Stream-stream join in structured streaming
Got it, thank you Jia for noticing that!
Youngwoo
On Tue, Feb 2,
Let’s close this vote and move to IPMC
On Wed, Jan 27, 2021 at 8:30 AM Mo Sarwat wrote:
> I vote +1
>
> On Wed, Jan 20, 2021 at 1:26 AM Jia Yu wrote:
>
> > Hi all,
> >
> > This is a call for vote on Apache Sedona (incubating) 1.0.0 rc1. Please
> > refer to the changes listed at the bottom of
Reminder
From: jmcl...@apache.org
Sent: Thursday, April 22, 2021 6:04:11 PM
To: d...@sedona.incubator.apache.org
Subject: Podling Sedona Report Reminder - May 2021
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC.
https://databricks.com/session_na21/large-scale-geospatial-indexing-and-analysis-on-apache-spark
I will be talking about Sedona (which we use!)
1. You probably shouldn't put .md doc on release share - if I understand
the suggestion is to include it into the src.tar.gz (and into the source
repo) so that they are git tagged and packaged together
2. Do you have java artifacts that should be staged?
3. checklist
incubating in name
signature
docs/archive is for the old GeoSpark docs. We keep it in the doc website
> for users who are still using GeoSpark, instead of Sedona. The generated
> docs are put here: http://sedona.apache.org/archive/download/overview/
>
> Thanks,
> Jia
>
>
> On Thu, May 20, 2021 at 10:50
You can’t skip the release vote process but you can make the vote a lot
easier / cleaner if the only diff / commit is the one line change.
We can a quick role in dev@ and once there is 3 votes (like today) we bring
it to IPMC for 72hr. Hopefully it’s not too bad.
Unfortunately you will need to
https://whimsy.apache.org/pods/project/sedona
entral to bring those Sedona required GeoTools jars to
> Maven Central. Since it is LGPL, it might be OK to do so.
>
> On Thu, Feb 11, 2021 at 5:18 PM Felix Cheung
> wrote:
>
> > Who owns or manages GeoTools if it is LGPL?
> >
> > On Thu, Feb 11, 2021 at 12:01 PM Jia Yu
Who owns or manages GeoTools if it is LGPL?
On Thu, Feb 11, 2021 at 12:01 PM Jia Yu wrote:
> Pawel,
>
> Python-adapter module is always being used by users. But it does not come
> with GeoTools. To use it, users have to (1) compile the source code of
> Python-adapter, or (2) add GeoTools
Could folks please look into the download link?
-- Forwarded message -
From: Justin Mclean
Date: Wed, Sep 15, 2021 at 6:18 PM
Subject: [MENTORS] Download pages and links to podling releases
To:
Hi,
Can mentors please make themselves familiar with the requirements for
-- Forwarded message -
From: Justin Mclean
Date: Sat, Nov 6, 2021 at 4:48 PM
Subject: Re: [MENTORS] Podling reports this month
To:
Hi,
The report can be found in the usual place:
https://cwiki.apache.org/confluence/display/INCUBATOR/November2021
Kind Regards,
Justin
Hi!
Highly recommend the community look at and complete the Maturity mode
https://community.apache.org/apache-way/apache-project-maturity-model.html
Also it is a good idea to compute some community stats: number of contributions
(commits), number of contributors (and growth since incubation),
Btw some projects have scripts that automate most of the steps there. It
will be worthwhile look into those.
On Tue, Jul 27, 2021 at 3:53 PM Jia Yu wrote:
> Hi Sedona PMC members,
>
> We are planning to release Apache Sedona 1.1.0 as soon as possible. For
> this release, I think we should find
project decisions being made in public by the committers?
>- Are the decision-making guidelines published and agreed to by all of
>the committers?
>
> Licensing awareness
>
>- Are all licensing, trademark, credit issues being taken care of and
>acknowledged by all co
Reminder
From: johndam...@apache.org
Sent: Wednesday, April 27, 2022 5:50:12 PM
To: d...@sedona.incubator.apache.org
Subject: Podling Sedona Report Reminder - May 2022
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator
-- Forwarded message -
From:
Date: Sat, Oct 22, 2022 at 9:08 PM
Subject: Podling Sedona Report Reminder - November 2022
To:
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
>From what I can see, it’s only directly used in two places
- tests
- sql variant
https://github.com/apache/incubator-sedona/blob/65080422b6256a0f12cc74347ac2ed531d26a4f6/R/R/dependencies.R#L135
Don’t know enough about dbplyr to tell if that functionality can be turned
off (say if sql is not
Please take a look at the bottom of this report
https://incubator.apache.org/clutch/sedona.html
And esp at
https://whimsy.apache.org/pods/project/sedona
What’s the thought on R dbplyr dependency?
From: Jia Yu
Sent: Saturday, November 12, 2022 12:40:27 PM
To: dev@sedona.apache.org
Subject: Re: [VOTE] Release Apache Sedona 1.3.0-incubating-rc1
Dear all,
This release is supposed to be the last release before
53 matches
Mail list logo
