"Issues" mailing is not available?

2020-10-01 Thread Jia Yu
Hello Felix,

Several users reported that the issues@sedona.apache.org is not a valid
email address or their email didn't appear in the mailing list. But it
looks like I can still post emails to this mailing list.
https://lists.apache.org/list.html?issues@sedona.apache.org

Do you know whether there is anything wrong with the mailing list?

Thanks,
Jia


Sedona new website is online

2020-09-15 Thread Jia Yu
Hi folks,

I just refactored the sedona website: http://sedona.apache.org/

I eventually choose to still use mkdocs to manage our documentation
website. Since we already use mkdocs before, re-build everything using
Jekyll requires too much work.

The documentation source code is still in "docs" and "docs-override". You
can still build it using "mkdocs serve" and make sure you have "material"
theme installed:
https://squidfunk.github.io/mkdocs-material/getting-started/

Thanks,
Jia


Re: Progresso of the initial setup

2020-09-07 Thread Jia Yu
Yes, you are right. Issues should be on JIRA :)

On Mon, Sep 7, 2020 at 13:04 Felix Cheung  wrote:

> 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. GitHub issue has been disabled. All new issues should go to
>> issues@sedona.apache.org. Please find the exported issues on GitHub in
>> the attached file.
>>
>> 3. GitHub PRs have been integrated with JIRA. To link a PR to an existing
>> JIRA ticket, use [SEDONA-XXX] in the PR title. XXX is the JIRA ticket ID.
>> For example, "[SEDONA-1] Move to JTS".
>>
>> 4. Old code is put in "trunk/import" in case of future IP clearance issues
>>
>> Thanks,
>> Jia
>>
>>
>>
>
>