Re: Apache ECharts-邀请函.pdf

[Wenli Zhang]

Hi Jiang Ye,

Thanks for the invitation. We had great cooperation last year.
We will discuss this year's invitation and get back to you later.

Thanks

*Ovilia*


On Thu, Mar 24, 2022 at 11:45 AM 江叶  wrote:

>
>  Dear Ovilia and Apache ECharts PMC,
>
>
> Hope this email finds you well. We would like to express our sincere 
> gratitude to you and Apache ECharts for supporting the China Data Content 
> Competition last year.
>
>
>  " China Data Content Competition" changed its name to "China Data Content of 
> Year 2022 ",and it will be launched on April 13, 2022.
>
>
> We’re writing to invite Apache ECharts to provide technical support for 
> entries who take part in the China Data Content of Year 2022. Please kindly 
> find attached the invitation, event description, and benefits display.
>
> Thank you and we look forward to hearing from you!
>
> 羡辙老师：您好
>
> 感谢您及Apache
> ECharts，在2021年对中国数据内容大赛会的支持。“中国数据内容大赛”今年更名为“2022年中国数据内容年度案例征集”。今天诚邀Apache
> ECharts作为2022年中国数据内容年度案例征集的技术支持单位，为选手提供作品技术支持。邀请函、赛事介绍以及权益展示在附件中，请查收。
>
> 盼复，祝好！
>
>

Re: China Data Content Competition 2021 Technical Support Invitation

[Wenli Zhang]

Hi Cheying,

Apache ECharts would be glad to offer technical support to the event.
Hope we could see more inspiring data visualization works this year.

Thanks

*Ovilia*


On Fri, Apr 9, 2021 at 5:43 PM 车颖  wrote:

>
> Dear Ms. Xianzhe,
>
> Hope this email finds you well. We would like to express our sincere
> gratitude to you and Apache ECharts for supporting the China Data Content
> Competition last year.
>
> We’re also writing to invite Apache ECharts to provide technical support
> for entries who take part in the China Data Content Competition 2021.
> Please kindly find attached the invitation, event description, and benefits
> display.
>
> Thank you and we look forward to hearing from you!
>
> https://dataviz-cms.oss-cn-beijing.aliyuncs.com/assets/file/CDCC_2021_Technical_Support_Invitation.pdf
>
>
> 羡辙老师：您好
>
> 感谢您及Apache ECharts，在2020年对中国数据内容大赛及大会的支持，今天诚邀Apache
> ECharts作为2021年中国数据内容大赛的技术支持单位，为参赛选手提供作品技术支持。邀请函、赛事介绍以及权益展示在附件中，请查收。
>
> 盼复，祝好！
>
>

Re: Bar label contain 3 strings

[Wenli Zhang]

Hi,

Do you mind creating a demo for us to understand better?
You can create one using https://gallery.echartsjs.com/editor.html (Chinese)
or https://codepen.io/Ovilia/pen/dyYWXWM .

Thanks

*Ovilia*


On Mon, Jul 6, 2020 at 3:41 AM Amal BinHelal  wrote:

> Hello
> Dear Wenli,
> I hope you find my email well
>
> I want to have 3 string in the label but only i can have one with the
> value {b} and {c}
>  Let assume I have these data
> {value:50, name: "user", description:"text", country: "France"}
>
> How I can manage that ? to show it in bar label
> Tried to have function with loop in formatter but it didn’t work
>
> Thank you so much for your hard work I really precipitate your effort
>
>
> --
> Regards, Amal BinHelal
>

Re: ECharts @types

[Wenli Zhang]

Thank you!

*Wenli Zhang*



On Tue, Jun 2, 2020 at 2:53 PM Tomek Rajnisz  wrote:

> Hi,
>
> You are right. Maintaining @types seems to be waste of time now. I think
> moving into TypeScript is a very good idea.
> Good luck! You are doing great job!
>
> Greetings,
> trajnisz
>
> wt., 2 cze 2020 o 04:27 Wenli Zhang  napisał(a):
>
>> Hi,
>>
>> Thanks for your helping!
>>
>> But I'd suggest not spending too much effort maintaining it because we
>> are already developing with TypeScript under "next" branch which should
>> probably be merged into master in another one or two months. By that time,
>> DefinitelyTyped is not necessary any more.
>>
>> Currently, the types under DefinitelyTyped was generated using
>> https://github.com/iRON5/echarts-ts-describer . But as you see, this
>> repo is not maintained for a long time, and many of the types are changed
>> manually.
>>
>> *Wenli Zhang*
>>
>>
>>
>> On Mon, Jun 1, 2020 at 10:29 PM Tomek Rajnisz 
>> wrote:
>>
>>> Hi Ovilia,
>>>
>>> I`m currently working with echarts in TS. Using @types (
>>> https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/echarts)
>>> i can see that a lot of code is unnecessarily unrepeated. I can help
>>> correct it.
>>> I would like to ask if you have any method of generating these .d.ts
>>> files or it was all written by hand? It would save me a lot of time.
>>>
>>> Greetings,
>>> trajnisz
>>>
>>

Re: ECharts @types

[Wenli Zhang]

Hi,

Thanks for your helping!

But I'd suggest not spending too much effort maintaining it because we are
already developing with TypeScript under "next" branch which should
probably be merged into master in another one or two months. By that time,
DefinitelyTyped is not necessary any more.

Currently, the types under DefinitelyTyped was generated using
https://github.com/iRON5/echarts-ts-describer . But as you see, this repo
is not maintained for a long time, and many of the types are changed
manually.

*Wenli Zhang*



On Mon, Jun 1, 2020 at 10:29 PM Tomek Rajnisz  wrote:

> Hi Ovilia,
>
> I`m currently working with echarts in TS. Using @types (
> https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/echarts)
> i can see that a lot of code is unnecessarily unrepeated. I can help
> correct it.
> I would like to ask if you have any method of generating these .d.ts files
> or it was all written by hand? It would save me a lot of time.
>
> Greetings,
> trajnisz
>

Re: Echart customize tooltip

[Wenli Zhang]

Hi, This is a pure-CSS problem and not related to ECharts.
Please try with something like this.
https://stackoverflow.com/questions/19719048/center-triangle-at-bottom-of-div

*Wenli Zhang*



On Sun, May 31, 2020 at 5:20 PM Amal BinHelal 
wrote:

> Hello,
> Sorry for the late reply
>  I tried many ways to do that even using extra css but it didn’t work
> So my question is can I draw a little arrow at the bottom of the tooltip
>
> On Thu, 21 May 2020 at 7:48 AM Wenli Zhang  wrote:
>
>> tooltip.position could be a callback function
>> https://echarts.apache.org/en/option.html#tooltip.position You can use
>> that to return a position on the ring.
>>
>>
>> *Wenli Zhang*
>>
>>
>>
>> On Wed, May 20, 2020 at 11:26 PM Amal BinHelal 
>> wrote:
>>
>>> Hello dear,
>>> I hope you fine
>>> I saw some of your project using chart I was wondering if there is
>>> anyway to make tooltip with arrow like this picture?
>>> I tried many ways even I tried label and make it outside but I couldn't
>>> put the arrow
>>>
>>>
>>> Thank you
>>>
>>> --
>>> Regards, Amal BinHelal
>>>
>> --
> Regards, Amal BinHelal
>

Re: Criteria for new ECharts committers

[Wenli Zhang]

Thank you Kevin! That's really good  advice.

What do other guys think? Please let me know. :)

Zhang Wenli
http://zhangwenli.com


On Wed, Nov 7, 2018 at 3:53 AM Kevin A. McGrail  wrote:

> I would recommend you look towards what you can do to:
>
> A) encourage people who are not coders to contribute.  Right now, you only
> cover coders.  Bug management, graphics, documentation, testing, etc. are
> all necessary.
>
> B) Consider a lower bar towards entry.  For example, the SVN project allows
> anyone who is a committer on another project to commit.  I'm not saying
> that broad but right now, I think you want to encourage people who have
> high quality but low volume commits still.
>
> Regards,
> KAM
>
>
> --
> Kevin A. McGrail
> VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
> On Sun, Nov 4, 2018 at 7:15 AM Wenli Zhang  wrote:
>
> > Hi all,
> >
> > As you can see, we have several new contributors making PRs for our
> > project.
> > And here we'd like to discuss what criteria is requested for one to
> become
> > a committer.
> >
> > Here are some of my suggestions to start with:
> >
> > 1. We can set a minimum number for required PRs merged or issues
> > contributed. And we need to discuss the amount for them. How about 3
> merged
> > PRs and 10 issues?
> > As for the definition of *issues contributed*, I think they should report
> > to us those issues that they think they've helped or made a progress, and
> > let us judge.
> >
> > 2. I'd suggest candidates send an email for application (maybe to the
> > private mailing list) and mention the links of their PRs or solved issues
> > or other contributions (like document fixing, suggestions and etc.). If
> you
> > guys agree on this, we shall put a notice about the details on our
> website
> > or GitHub about how to apply.
> >
> > 3. The quality is even more important, so this should probably also be
> > assessed by us.
> >
> > 4. Another requirement I think necessary is the commitment to contribute,
> > which may be in the form of making more PRs or fixing document errors, or
> > answering issue problems.
> >
> > 5. After an offline discussion with Dave, Shen Yi and Su Shuang, we think
> > it is necessary to require those new committers to make PR before their
> > commits are merged. It's a safer way to make sure our code is at its best
> > state.
> >
> > Please feel free to share your opinions on this topic!
> > And looking forward to having new committers. :)
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
>

Criteria for new ECharts committers

[Wenli Zhang]

Hi all,

As you can see, we have several new contributors making PRs for our project.
And here we'd like to discuss what criteria is requested for one to become
a committer.

Here are some of my suggestions to start with:

1. We can set a minimum number for required PRs merged or issues
contributed. And we need to discuss the amount for them. How about 3 merged
PRs and 10 issues?
As for the definition of *issues contributed*, I think they should report
to us those issues that they think they've helped or made a progress, and
let us judge.

2. I'd suggest candidates send an email for application (maybe to the
private mailing list) and mention the links of their PRs or solved issues
or other contributions (like document fixing, suggestions and etc.). If you
guys agree on this, we shall put a notice about the details on our website
or GitHub about how to apply.

3. The quality is even more important, so this should probably also be
assessed by us.

4. Another requirement I think necessary is the commitment to contribute,
which may be in the form of making more PRs or fixing document errors, or
answering issue problems.

5. After an offline discussion with Dave, Shen Yi and Su Shuang, we think
it is necessary to require those new committers to make PR before their
commits are merged. It's a safer way to make sure our code is at its best
state.

Please feel free to share your opinions on this topic!
And looking forward to having new committers. :)

Zhang Wenli
http://zhangwenli.com

Re: [VOTE] Release Apache ECharts 4.2.0 (release candidate 2)

[Wenli Zhang]

+1

Zhang Wenli
http://zhangwenli.com


On Sat, Oct 27, 2018 at 4:23 PM SHUANG SU  wrote:

> I am pleased to be calling this vote for the release of Apache ECharts
> 4.2.0 (release candidate 2).
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.0-rc.2/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
>
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=1a566de
>
> The Release Note is available in:
>
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.0-rc.2/RELEASE_NOTE.txt
>
> Some shell commands for validating the release:
>
> ```shell
> # Download the release:
> curl
>
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.0-rc.2/apache-echarts-4.2.0-rc.2-incubating-src.zip
> -o apache-echarts-4.2.0-rc.2-incubating-src.zip
> unzip apache-echarts-4.2.0-rc.2-incubating-src.zip -d
> apache-echarts-4.2.0-rc.2-incubating-src > /dev/null
>
> # Build the project (Node.js environment is required):
> cd "apache-echarts-4.2.0-rc.2-incubating-src" && npm install && cd ..
> node "apache-echarts-4.2.0-rc.2-incubating-src/build/build.js" --release
> # (See help: `node
> "apache-echarts-4.2.0-rc.2-incubating-src/build/build.js" --help`)
> ```
>
>
> Please vote on releasing this package as:
> Apache ECharts 4.2.0 (release candidate 2)
> by "2018-10-30T09:12:13.512Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
>
> --
>  Su Shuang (100pah)
> --
>

Re: Podling Report Reminder - November 2018

[Wenli Zhang]

Hi Justin,

Sorry I missed that question. Updated now.

Yes. They helped a lot and solved many of our problems.

Thank you for your reminding.

Zhang Wenli
http://zhangwenli.com


On Sun, Oct 28, 2018 at 9:18 AM Justin Mclean  wrote:

> Hi,
>
> Thanks for filling out your podling report. However I noticed you didn't
> answer the question:
> "Have your mentors been helpful and responsive or are things falling
> through the cracks? In the latter case, please list any open issues
> that need to be addressed."
>
> If you could do so that would be a great help.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org
>
>

Re: [Improvement] Click event triggering

[Wenli Zhang]

Hi Shuang,

I think it a good idea to expose mouse events on *grid*. By mouse events, I
mean something like mouseenter, mousemove, mouseleave and etc.
Recently we got this issues asking exactly the same thing:
https://github.com/apache/incubator-echarts/issues/9281 .

We should probably provide events on grid first, and later on, we can also
provide events on other components.


Zhang Wenli
http://zhangwenli.com


On Thu, Oct 25, 2018 at 3:00 PM SHUANG SU  wrote:

> (1)
> In this case, should we resolve it by just exposing mouse events of "grid"?
>
>
> (2)
> The click event have been exposed on "axis label" and "title".
> But not by defualt, for old version compatibility reasons.
> see:
>
> https://ecomfe.github.io/echarts-doc/public/en/option.html#yAxis.triggerEvent
>
> https://ecomfe.github.io/echarts-doc/public/en/option.html#title.triggerEvent
>
> But "Other components trigger events" is necessary.
> We have been gradually exposing some events for components,
> like "axis", "title", But not enough.
>
>
>
>
> ------
>  Su Shuang (100pah)
> --
>
>
>
> On Thu, 25 Oct 2018 at 13:54, Wenli Zhang  wrote:
>
> > When user listens click event using:
> >
> > chart.on('click', function() {...})
> >
> > It only receives message when the click is on the series item.
> > In the case of line charts, it only triggers when clicks on the small
> > symbol on the line.
> >
> > But for line charts that with axisPointer or tooltip of 'axis' type
> (e.g.:
> > http://gallery.echartsjs.com/editor.html?c=xSJfK8-MCo=2 ), this may
> not
> > make sense.
> > It is expected that click event is triggered whenever clicking inside
> grid
> > area, or maybe whenever tooltip or axisPointer is shown.
> > This is extremely useful on mobile since currently click can almost never
> > triggered except that touch exactly on the symbol item.
> >
> > Another thing is, it is also often requested that clicks on other
> > components, like axis label, title, and etc. should also be triggered and
> > can be listened by users.
> >
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
>

[Improvement] Click event triggering

[Wenli Zhang]

When user listens click event using:

chart.on('click', function() {...})

It only receives message when the click is on the series item.
In the case of line charts, it only triggers when clicks on the small
symbol on the line.

But for line charts that with axisPointer or tooltip of 'axis' type (e.g.:
http://gallery.echartsjs.com/editor.html?c=xSJfK8-MCo=2 ), this may not
make sense.
It is expected that click event is triggered whenever clicking inside grid
area, or maybe whenever tooltip or axisPointer is shown.
This is extremely useful on mobile since currently click can almost never
triggered except that touch exactly on the symbol item.

Another thing is, it is also often requested that clicks on other
components, like axis label, title, and etc. should also be triggered and
can be listened by users.


Zhang Wenli
http://zhangwenli.com

[Feature Request] axisPointer position snap to data

[Wenli Zhang]

Hi dear developers,

Here we'd like to discuss about
https://github.com/apache/incubator-echarts/issues/7651 . Since the issues
is in Chinese, here I'm going to describe it in English.

[image: axisPointer position.png]

Basically, it is required in the issue that the cross point of the
axisPoint always snap to data point. In this case, the x position of the
cross point is decided by mouse position, and the y position by the data of
the corresponding x position.

But currently, ECharts doesn't provide a method for the y position to be at
data position. I'm not sure if *snap* is the correct word since currently
the snap option in axisPoint seems to mean to be near to the data but not
compulsively.

Expected: https://gupiao.baidu.com/stock/sh01.html?from=aladingpc
Current ECharts: http://gallery.echartsjs.com/editor.html?c=x8K2BwAFx5=2

We'd like to discuss in this email:
1. Should we implement the feature as the *Expected* example shows?
2. Should this be called *snap* or something else?
3. Should we provide an option or make this default?
4. Is there anything we should be aware of when implementing this? @100pah

Zhang Wenli
http://zhangwenli.com

Re: ICLA of new committer

[Wenli Zhang]

Hi Dave,

I've never received any email from priv...@echarts.apache.org.
I subscribed private channel much the same like dev@, but can only receive
dev but not private. I also asked some other
Could any one check if I'm on the list some how?

Besides, we have two new contributors sent ICLA files a few days ago but
have no reply from secretary. Is this normal?

Thanks!

Zhang Wenli
http://zhangwenli.com


On Thu, Oct 11, 2018 at 11:58 PM Dave Fisher  wrote:

> Have a look at priv...@echarts.apache.org
>
> All of the ECharts initial committers / PPMC should be subscribed.
>
> It is on private@ where we discuss making a contributor into a committer
> and/or PPMC. An archived discussion via email is required.
>
> We should discuss on dev@ how to be clear about when an ICLA is required.
> At a minimum it needs to be clear that all PRs are Apache License v2.
>
> (secretary has been bcc’d)
>
> Regards,
> Dave
>
>
>
> Sent from my iPhone
>
> On Oct 11, 2018, at 7:08 AM, Kevin A. McGrail 
> wrote:
>
> I do not know.  Craig, can you give some insight?  Zhang, what's the name
> and email of the person who filed the ICLA?  Did they reference echarts?
>
> On 10/10/2018 11:02 PM, Wenli Zhang wrote:
>
> Hi Kevin,
>
> Thanks for your reply.
>
> What happens if secretary doesn't reply?
>
> Zhang Wenlihttp://zhangwenli.com
>
>
> On Mon, Oct 8, 2018 at 7:55 PM Kevin A. McGrail  
> 
> wrote:
>
>
> Hi Zhang,
>
> With the ICLA, you are free to use the PR as the project deems best.  I
> have forwarded your email to secretary@ so they can record the document.
>
> Congrats on building your community!
>
> Regards,
> KAM
> On 10/8/2018 2:38 AM, Wenli Zhang wrote:
>
> PDF in last email is too large. Here's a compressed version.
>
> Zhang Wenlihttp://zhangwenli.com
>
>
> On Mon, Oct 8, 2018 at 2:35 PM Wenli Zhang  
>  wrote:
>
>
> Dear mentors,
>
> We have merged a pull request 
> (https://github.com/apache/incubator-echarts/pull/8759) from the
> community, and his ICLA file is attached in this email.
>
> This is the first time we merge a PR after we joined Apache. So please
> tell us if there's anything else we need to do.
>
> Thanks!
>
> Zhang Wenlihttp://zhangwenli.com
>
> --
> *Kevin A. McGrail*
> 703-798-0171 (wireless)https://www.linkedin.com/in/kmcgrail
>
>
> --
> *Kevin A. McGrail*
> 703-798-0171 (wireless)
> https://www.linkedin.com/in/kmcgrail
>
>

Re: At Least 10 Podling Rosters are Messed Up in Whimsy

[Wenli Zhang]

Sorry, I forgot to update PMC this month.

As you can see, we have several contributors making pull requests and
sending ICLA recently. And our community is definitely growing recently.

I will report it next month. Sorry for that.


Zhang Wenli
http://zhangwenli.com


On Tue, Oct 16, 2018 at 2:31 AM Kevin A. McGrail 
wrote:

> Hi All,
>
> We should be looking at people to add to the PMC.  You guys do a ton of
> work on the product and need to focus on the community growth too!
>
> It's amazing to login to my computer and see all the work you do overnight!
>
> Regards,
> KAM
> --
> Kevin A. McGrail
> VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
> -- Forwarded message -
> From: Dave Fisher 
> Date: Mon, Oct 15, 2018 at 2:26 PM
> Subject: At Least 10 Podling Rosters are Messed Up in Whimsy
> To: Apache Incubator PMC 
>
>
> Hi IPMC,
>
> I’ve reviewed whimsy rosters and have found that 10 of 51 podlings rosters
> are definitely messed up and show either no or very few PPMC members.
>
> These are:
> Gearpump
> Gobblin
> Hivemall
> Marvin-AI
> Nemo
> Omid
> Quickstep
> Unomi
> Spot
> Annotator
> I’m not sure that Livy is updated properly.
>
> These probably missed an update to the roster:
> Pagespeed
> BatchEE
> Joshua
> Sensoft
> Superset
>
> The following show no growth:
> Crail
> Daffodil
> Doris
> ECharts
> Milagro
> Tephra
> Weex
> Regards,
> Dave
>

Re: ICLA of new committer

[Wenli Zhang]

Hi Kevin,

Thanks for your reply.

What happens if secretary doesn't reply?

Zhang Wenli
http://zhangwenli.com


On Mon, Oct 8, 2018 at 7:55 PM Kevin A. McGrail 
wrote:

> Hi Zhang,
>
> With the ICLA, you are free to use the PR as the project deems best.  I
> have forwarded your email to secretary@ so they can record the document.
>
> Congrats on building your community!
>
> Regards,
> KAM
> On 10/8/2018 2:38 AM, Wenli Zhang wrote:
>
> PDF in last email is too large. Here's a compressed version.
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> On Mon, Oct 8, 2018 at 2:35 PM Wenli Zhang  wrote:
>
>> Dear mentors,
>>
>> We have merged a pull request (
>> https://github.com/apache/incubator-echarts/pull/8759) from the
>> community, and his ICLA file is attached in this email.
>>
>> This is the first time we merge a PR after we joined Apache. So please
>> tell us if there's anything else we need to do.
>>
>> Thanks!
>>
>> Zhang Wenli
>> http://zhangwenli.com
>>
>
> --
> *Kevin A. McGrail*
> 703-798-0171 (wireless)
> https://www.linkedin.com/in/kmcgrail
>

Re: ICLA of new committer

[Wenli Zhang]

PDF in last email is too large. Here's a compressed version.

Zhang Wenli
http://zhangwenli.com


On Mon, Oct 8, 2018 at 2:35 PM Wenli Zhang  wrote:

> Dear mentors,
>
> We have merged a pull request (
> https://github.com/apache/incubator-echarts/pull/8759) from the
> community, and his ICLA file is attached in this email.
>
> This is the first time we merge a PR after we joined Apache. So please
> tell us if there's anything else we need to do.
>
> Thanks!
>
> Zhang Wenli
> http://zhangwenli.com
>

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

How to add new committers

[Wenli Zhang]

Dear mentors,

We are considering merging new PR at
https://github.com/apache/incubator-echarts/pull/8966 . Since this is the
first time we accept commit from community, I have a few questions to ask:

1. Does he need to become a committer (so that he need to follow
https://www.apache.org/dev/new-committers-guide.html ) before or after we
merge the pull request?

2. Is there anything else we need to do before and after we merge the PR?

Thanks!

Zhang Wenli
http://zhangwenli.com

Feature request: more responsive label for pie charts #4082

[Wenli Zhang]

Hi all,

Here's a frequently requested feature on GitHub, a more responsive label
design for pie charts. See
https://github.com/apache/incubator-echarts/issues/4082 for more detail.

In this email, we'd like to discuss about the potential methods to improve
it.

Here are some of my ideas for a start.

1. Restrict labels not to be outside the container
2. For long labels, we can add '\n' at certain position (fixed length? only
labels cannot be put inside the container?)
3. A bold attempt to put labels more far away (may cause labelLine length
altered)

Any more idea?

Zhang Wenli
http://zhangwenli.com

Re: Request for Apache Website server

[Wenli Zhang]

Hi,

Just a remind on last topic. Any comments?

Zhang Wenli
http://zhangwenli.com

On Fri, Jun 29, 2018 at 3:04 PM, Wenli Zhang  wrote:

> Hi all,
>
> Thanks for your help and I've published ECharts website at
> https://echarts.apache.org/index.html
>
> I wonder if we can make `asf-site` branch as default branch on GitHub
> https://github.com/apache/incubator-echarts-website ?
> By default, it should be set under Settings - Branches - Default Branch.
> But I don't have the right to do it. Could anyone help to do so?
>
> Zhang Wenli
> http://zhangwenli.com
>
> On Wed, Jun 13, 2018 at 4:07 PM, Kevin A. McGrail 
> wrote:
>
>> Excellent.  I'm sorry it took me so long to realize it was stuck in the
>> wrong Jira!
>>
>> --
>> Kevin A. McGrail
>> VP Fundraising, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>> On Tue, Jun 12, 2018 at 10:21 PM, Wenli Zhang 
>> wrote:
>>
>> > Thanks Kevin and John,
>> >
>> > I've created a ticket at https://issues.apache.org/jira
>> /browse/INFRA-16645
>> > .
>> >
>> > Zhang Wenli
>> > http://zhangwenli.com
>> >
>> > On Tue, Jun 12, 2018 at 5:14 PM, John D. Ament 
>> > wrote:
>> >
>> > > Yes, an infra ticket is required to enable the echarts site to use the
>> > git
>> > > repo.  http://issues.apache.org/jira/browse/INFRA will bring you
>> right
>> > to
>> > > them.
>> > >
>> > > John
>> > >
>> > > On Tue, Jun 12, 2018 at 5:08 AM Kevin A. McGrail > >
>> > > wrote:
>> > >
>> > > > Wenli, I talked to Justin about this and I agree.  We believe you
>> need
>> > to
>> > > > raise an INFRA JIRA rather than a echarts Jira ticket.
>> > > >
>> > > > https://issues.apache.org/jira/secure/Dashboard.jspa
>> > > >
>> > > >
>> > > > --
>> > > > Kevin A. McGrail
>> > > > VP Fundraising, Apache Software Foundation
>> > > > Chair Emeritus Apache SpamAssassin Project
>> > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> <(703)%20798-0171>
>> > > >
>> > > > On Thu, Jun 7, 2018 at 2:24 AM, Wenli Zhang 
>> > > wrote:
>> > > >
>> > > > > Hi John,
>> > > > >
>> > > > > I created an index.html file under asf-site branch (
>> > > > > https://github.com/apache/incubator-echarts-website/
>> > > > > blob/asf-site/index.html
>> > > > > ), but apparently it is not hosted at https://echarts.apache.org/
>> > > > > index.html
>> > > > > .
>> > > > >
>> > > > > The doc ( http://www.apache.org/dev/project-site.html ) says that
>> > > > > "Typically
>> > > > > these will be built as a jenkins job or a buildbot job". I wonder
>> if
>> > > this
>> > > > > is compulsive, since currently we use gulp.js and Node.js to
>> generate
>> > > our
>> > > > > website, and we'd prefer to have our generated static files
>> hosted.
>> > > > > In this case, should we use jenkins or buildbot job? Besides, I
>> > didn't
>> > > > see
>> > > > > detail information about how to use the tools along with GitHub
>> > > asf-site
>> > > > > branch. Could you please explain it to us?
>> > > > >
>> > > > > Thanks for your time!
>> > > > >
>> > > > > Zhang Wenli
>> > > > > http://zhangwenli.com
>> > > > >
>> > > > > On Fri, Jun 1, 2018 at 10:45 AM, Wenli Zhang <
>> oviliazh...@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > Hi John,
>> > > > > >
>> > > > > > I managed to push to the repo. Thanks!
>> > > > > >
>> > > > > > Zhang Wenli
>> > > > > > http://zhangwenli.com
>> > > > > >
>> > > > > > On Fri, Jun 1, 2018 at 9:14 AM, John D. Ament <
>> > johndam...@apache.org
>> > > >
>> > > > > > wrote:
>> > > > > >
>> &

Re: Request for Apache Website server

[Wenli Zhang]

Hi John,

I created an index.html file under asf-site branch (
https://github.com/apache/incubator-echarts-website/blob/asf-site/index.html
), but apparently it is not hosted at https://echarts.apache.org/index.html
.

The doc ( http://www.apache.org/dev/project-site.html ) says that "Typically
these will be built as a jenkins job or a buildbot job". I wonder if this
is compulsive, since currently we use gulp.js and Node.js to generate our
website, and we'd prefer to have our generated static files hosted.
In this case, should we use jenkins or buildbot job? Besides, I didn't see
detail information about how to use the tools along with GitHub asf-site
branch. Could you please explain it to us?

Thanks for your time!

Zhang Wenli
http://zhangwenli.com

On Fri, Jun 1, 2018 at 10:45 AM, Wenli Zhang  wrote:

> Hi John,
>
> I managed to push to the repo. Thanks!
>
> Zhang Wenli
> http://zhangwenli.com
>
> On Fri, Jun 1, 2018 at 9:14 AM, John D. Ament 
> wrote:
>
>> Could you double check? The repo is empty, so needs something pushed to
>> it.
>>
>> John
>>
>> On Wed, May 30, 2018 at 11:07 PM Wenli Zhang 
>> wrote:
>>
>> > Hi John,
>> >
>> > Thanks for reply.
>> >
>> > You mentioned that just created a git repo. I guess that should be
>> > https://github.com/apache/incubator-echarts-website .
>> > But we don't have the access to it, probably admin right is needed.
>> >
>> > Thanks!
>> >
>> > Zhang Wenli
>> > http://zhangwenli.com
>> >
>> > On Thu, May 31, 2018 at 10:54 AM, John D. Ament 
>> > wrote:
>> >
>> > > Sending an email is probably the easiest way to get started.  I
>> believe
>> > > what you did was create a JIRA ticket in our JIRA board, INFRA has
>> their
>> > > own.
>> > >
>> > > Getting a website is a handful of steps.
>> > >
>> > > - Create a git repo created (just did that)
>> > > - Create two branches on the repo.  One that includes the source files
>> > for
>> > > editing, another that includes the final production build.  We
>> typically
>> > > use "master" for the code, and "asf-site" for the build output
>> > > - Create an automated build process so that when someone pushes to
>> > master,
>> > > it builds and places output into asf-site branch.  If you review
>> > > https://github.com/apache/incubator/blob/master/build_site.sh it
>> should
>> > > give you a general understanding of how that works.  This script is
>> run
>> > > from Jenkins.
>> > > - Once we have that build in place, we can ask INFRA to serve our
>> > asf-site
>> > > branch as the website for echarts.incubator.apache.org
>> > >
>> > > Let me know if that works.
>> > >
>> > > John
>> > >
>> > >
>> > > On Wed, May 30, 2018 at 10:48 PM Wenli Zhang 
>> > > wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > We'd like to request for Apache Website server for
>> > > > http://echarts.incubator.apache.org/ .
>> > > >
>> > > > We want to use gitpubsub, so how can we create this git repo?
>> > > >
>> > > > I created this issue
>> > > >
>> > > > https://issues.apache.org/jira/projects/ECHARTS/issues/
>> > > ECHARTS-1?filter=allopenissues
>> > > > but no one replied. So I guess I need to send this email to discuss
>> > about
>> > > > it.
>> > > >
>> > > > Thanks!
>> > > >
>> > > > Zhang Wenli
>> > > > http://zhangwenli.com
>> > > >
>> > >
>> >
>>
>
>

Re: Request for Apache Website server

[Wenli Zhang]

Hi John,

I managed to push to the repo. Thanks!

Zhang Wenli
http://zhangwenli.com

On Fri, Jun 1, 2018 at 9:14 AM, John D. Ament  wrote:

> Could you double check? The repo is empty, so needs something pushed to it.
>
> John
>
> On Wed, May 30, 2018 at 11:07 PM Wenli Zhang 
> wrote:
>
> > Hi John,
> >
> > Thanks for reply.
> >
> > You mentioned that just created a git repo. I guess that should be
> > https://github.com/apache/incubator-echarts-website .
> > But we don't have the access to it, probably admin right is needed.
> >
> > Thanks!
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
> > On Thu, May 31, 2018 at 10:54 AM, John D. Ament 
> > wrote:
> >
> > > Sending an email is probably the easiest way to get started.  I believe
> > > what you did was create a JIRA ticket in our JIRA board, INFRA has
> their
> > > own.
> > >
> > > Getting a website is a handful of steps.
> > >
> > > - Create a git repo created (just did that)
> > > - Create two branches on the repo.  One that includes the source files
> > for
> > > editing, another that includes the final production build.  We
> typically
> > > use "master" for the code, and "asf-site" for the build output
> > > - Create an automated build process so that when someone pushes to
> > master,
> > > it builds and places output into asf-site branch.  If you review
> > > https://github.com/apache/incubator/blob/master/build_site.sh it
> should
> > > give you a general understanding of how that works.  This script is run
> > > from Jenkins.
> > > - Once we have that build in place, we can ask INFRA to serve our
> > asf-site
> > > branch as the website for echarts.incubator.apache.org
> > >
> > > Let me know if that works.
> > >
> > > John
> > >
> > >
> > > On Wed, May 30, 2018 at 10:48 PM Wenli Zhang 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > We'd like to request for Apache Website server for
> > > > http://echarts.incubator.apache.org/ .
> > > >
> > > > We want to use gitpubsub, so how can we create this git repo?
> > > >
> > > > I created this issue
> > > >
> > > > https://issues.apache.org/jira/projects/ECHARTS/issues/
> > > ECHARTS-1?filter=allopenissues
> > > > but no one replied. So I guess I need to send this email to discuss
> > about
> > > > it.
> > > >
> > > > Thanks!
> > > >
> > > > Zhang Wenli
> > > > http://zhangwenli.com
> > > >
> > >
> >
>

Re: Request for Apache Website server

[Wenli Zhang]

Hi John,

Thanks for reply.

You mentioned that just created a git repo. I guess that should be
https://github.com/apache/incubator-echarts-website .
But we don't have the access to it, probably admin right is needed.

Thanks!

Zhang Wenli
http://zhangwenli.com

On Thu, May 31, 2018 at 10:54 AM, John D. Ament 
wrote:

> Sending an email is probably the easiest way to get started.  I believe
> what you did was create a JIRA ticket in our JIRA board, INFRA has their
> own.
>
> Getting a website is a handful of steps.
>
> - Create a git repo created (just did that)
> - Create two branches on the repo.  One that includes the source files for
> editing, another that includes the final production build.  We typically
> use "master" for the code, and "asf-site" for the build output
> - Create an automated build process so that when someone pushes to master,
> it builds and places output into asf-site branch.  If you review
> https://github.com/apache/incubator/blob/master/build_site.sh it should
> give you a general understanding of how that works.  This script is run
> from Jenkins.
> - Once we have that build in place, we can ask INFRA to serve our asf-site
> branch as the website for echarts.incubator.apache.org
>
> Let me know if that works.
>
> John
>
>
> On Wed, May 30, 2018 at 10:48 PM Wenli Zhang 
> wrote:
>
> > Hi,
> >
> > We'd like to request for Apache Website server for
> > http://echarts.incubator.apache.org/ .
> >
> > We want to use gitpubsub, so how can we create this git repo?
> >
> > I created this issue
> >
> > https://issues.apache.org/jira/projects/ECHARTS/issues/
> ECHARTS-1?filter=allopenissues
> > but no one replied. So I guess I need to send this email to discuss about
> > it.
> >
> > Thanks!
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
>

Re: [VOTE] Release Apache ECharts 4.1.0.rc3

[Wenli Zhang]

Looks good to me. +1

Zhang Wenli
http://zhangwenli.com

On Thu, May 10, 2018 at 10:45 AM, 李木子  wrote:

> It's look good to me and I am a +1.
>
> 2018-05-10 5:46 GMT+08:00 Kevin A. McGrail :
>
> > It's a marked improvement and I am a +1.
> >
> > On Wed, May 9, 2018, 09:22 沈毅  wrote:
> >
> > > +1
> > >
> > > checked:
> > > - distribution files are correct.
> > > - No files missing license.
> > > - Files using d3 and zrender are included in LICENSE.
> > > - MD5 is correct.
> > > - DISCLAIMER is included.
> > > - NOTICE is correct.
> > >
> > > SHUANG SU  于2018年5月8日周二 上午2:10写道：
> > >
> > > > I am pleased to be calling this vote for the release of Apache
> ECharts
> > > > 4.1.0.rc3.
> > > >
> > > > The release candidate to be voted over is available at:
> > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc3/
> > > >
> > > > The release candidate is signed with a GPG key available at:
> > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> > > >
> > > > A tagged git repository is available for review at:
> > > > https://github.com/apache/incubator-echarts/releases/tag/4.1.0.rc3
> > > >
> > > > The Git commit for this release is:
> > > >
> > > >
> > > https://gitbox.apache.org/repos/asf?p=incubator-echarts.
> > git;a=commit;h=f98eb21
> > > >
> > > > The Release Note is available in:
> > > >
> > > >
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > 1.0.rc3/RELEASE_NOTE.txt
> > > >
> > > > Some shell commmands for validating the release:
> > > >
> > > > ```shell
> > > > # Download the release:
> > > > curl
> > > >
> > > >
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > 1.0.rc3/apache-echarts-4.1.0.rc3-incubating.zip
> > > > -o apache-echarts-4.1.0.rc3-incubating.zip
> > > > unzip apache-echarts-4.1.0.rc3-incubating.zip -d
> > > > apache-echarts-4.1.0.rc3-incubating > /dev/null
> > > >
> > > > # Rebuild the project:
> > > > cd "apache-echarts-4.1.0.rc3-incubating" && npm install && cd ..
> > > > node "apache-echarts-4.1.0.rc3-incubating/build/build.js" --release
> > > > # (See help: `node "apache-echarts-4.1.0.rc3-
> > incubating/build/build.js"
> > > > --help`)
> > > >
> > > > # Run Apache Rat:
> > > > java -jar "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar"
> |
> > > less
> > > > # (See help: `java -jar
> > > > "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" --help`)
> > > > ```
> > > >
> > > >
> > > > Please vote on releasing this package as:
> > > > Apache ECharts 4.1.0.rc3
> > > >
> > > > This vote will be open until "2018-05-10T19:03:22.908Z" and passes
> if a
> > > > majority
> > > > of at least three +1 Apache ECharts IPMC votes are cast.
> > > >
> > > > [ ] +1 Release this package
> > > > [ ] 0 I don't feel strongly about it, but don't object
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Anyone can participate in testing and voting, not just committers,
> > please
> > > > feel free to try out the release candidate and provide your votes.
> > > >
> > > >
> > > > --
> > > >  Su Shuang (100pah)
> > > > --
> > > >
> > >
> > >
> > > --
> > > Yi Shen
> > > Senior Developer
> > > Baidu, Inc.
> > >
> >
>

Re: [VOTE] ECharts v4.1.0 release vote for podling dev list

[Wenli Zhang]

John,

I saw you committed with svn for release. What is the repo url of this svn
project? And is there a web page to access it?

Sorry for my confusion...

Zhang Wenli
http://zhangwenli.com

On Thu, Apr 19, 2018 at 8:42 PM, John D. Ament <johndam...@apache.org>
wrote:

> Wenli,
>
> Apologies for late reply.
>
> You can find a template for what a release vote looks like at
> https://lists.apache.org/thread.html/a38f7b44e75d2515a23f4626ddeebc
> d08ef4d81c399fd47105c8abc7@%3Cdev.juneau.apache.org%3E
>
> There's a few important items:
>
> - Creating /dist/dev and /dist/release.  I can do this tonight, unless
> someone else gets to it first.
> - A checked in KEYS file.
> - A packaged source release.  This should effectively be your git
> repository, minus the .git folder.  Typically in tar.gz or zip formats.
> - Signatures for the source release bundle, based on the KEYS checked in.
>
> This is all covered on the release documentation I linked you to
> previously.
>
> John
>
> On 2018/04/19 11:09:43, Wenli Zhang <oviliazh...@gmail.com> wrote:
> > Hi John,
> >
> > So I should make a tag on current commit and resend a new email. Did I
> > understand it right?
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
> > On Tue, Apr 17, 2018 at 5:52 PM, Wenli Zhang <oviliazh...@gmail.com>
> wrote:
> >
> > > Hi John,
> > >
> > > I've read the document but I'm a little confused about what release
> > > artifacts are.
> > > Should I make a git tag on GitHub and copy the link in release vote
> email?
> > > I'm not sure how to get a link like http://www.apache.org/
> > > dist/incubator/echarts as the document says.
> > >
> > > Zhang Wenli
> > > http://zhangwenli.com
> > >
> > > On Tue, Apr 17, 2018 at 5:37 PM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > >> In order to create a release, you need to have release artifacts.  I
> don't
> > >> see any artifacts in this email, so I have to vote -1
> > >>
> > >> Please review https://incubator.apache.org/
> guides/releasemanagement.html
> > >>  and https://incubator.apache.org/policy/incubation.html#releases as
> well
> > >> as the associated links from those pages.
> > >>
> > >> John
> > >>
> > >> On Tue, Apr 17, 2018 at 3:00 AM Wenli Zhang <oviliazh...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > We'd like to release v4.1.0 and please +1 if approve.
> > >> >
> > >> >
> > >> >
> > >> > Diff of changes is available at:
> > >> >
> > >> > https://github.com/apache/incubator-echarts/compare/871af5ec
> > >> 38649984ca326ce689603ce8f51ec85c...master
> > >> >
> > >> >
> > >> >
> > >> > Here are the bugs fixed, new features, and enhanced features:
> > >> >
> > >> > Feature: add zoom and drag interactions for tree diagram.
> > >> > Feature: support keeping-aspect for legend path. #7831
> > >> >
> > >> > Enhance: optimize candlestick rendering and zooming in hundreds of
> > >> thousand
> > >> > of data.
> > >> > Enhance: enhance the category axis ticks and labels when there was
> no
> > >> > enough space to display all labels.
> > >> > Enhance: order of nodes for sankey diagram. #3390 #3543 #6365 #4880
> > >> #4986
> > >> > Enhance: performance of bar chart in hundreds of thousand of data.
> > >> > Enhance: sampling performance in progressive mode.
> > >> > Enhance: parallel performance in progressive mode.
> > >> > Enhance: currently do not filter empty data item in data zoom, which
> > >> makes
> > >> > line chart keeping broken. #7955
> > >> > Enhance: support toolbox.feature merge.
> > >> > Enhance: add tree directions from right to left, from bottom to top
> for
> > >> > tree series. #7351 #7154
> > >> >
> > >> > Fix: resolve browser become unresponsive when the data of sankey
> series
> > >> has
> > >> > cycle. #7495 #8117 #7583 #7325 #6555
> > >> > Fix: currently we fetch name from dateItem.name firstly in list.
> #7966
> > >> > Fix: typed array incorrect usage in WeChat app.
> > >> > Fix: option in axi

[VOTE] ECharts v4.1.0 release vote for podling dev list

[Wenli Zhang]

Hi all,

We'd like to release v4.1.0 and please +1 if approve.



Diff of changes is available at:
https://github.com/apache/incubator-echarts/compare/871af5ec38649984ca326ce689603ce8f51ec85c...master



Here are the bugs fixed, new features, and enhanced features:

Feature: add zoom and drag interactions for tree diagram.
Feature: support keeping-aspect for legend path. #7831

Enhance: optimize candlestick rendering and zooming in hundreds of thousand
of data.
Enhance: enhance the category axis ticks and labels when there was no
enough space to display all labels.
Enhance: order of nodes for sankey diagram. #3390 #3543 #6365 #4880 #4986
Enhance: performance of bar chart in hundreds of thousand of data.
Enhance: sampling performance in progressive mode.
Enhance: parallel performance in progressive mode.
Enhance: currently do not filter empty data item in data zoom, which makes
line chart keeping broken. #7955
Enhance: support toolbox.feature merge.
Enhance: add tree directions from right to left, from bottom to top for
tree series. #7351 #7154

Fix: resolve browser become unresponsive when the data of sankey series has
cycle. #7495 #8117 #7583 #7325 #6555
Fix: currently we fetch name from dateItem.name firstly in list. #7966
Fix: typed array incorrect usage in WeChat app.
Fix: option in axis data item did not work. #7954
Fix: markArea only displayed the last one. #7902
Fix: rounding error in clip symbol for line chart. #7913
Fix: bar chart start point was incorrect when multiple axes exist. #7412
Fix: markArea did not display when using ordinal string. #7849
Fix: dataZoom threw error when series was empty. #7666
Fix: add compatibility of data exceptions for sankey series. #2867
Fix: error when remove node or render again for the tree series. #8038
#8040 #7720 #7363 #7315
Fix: sunburst chart roll-up element is not removed when chart.setOption
called. #8132
Fix: SVG axisPointer text position bug #7947
Fix: large lines chart render bug in large mode.
Fix: The last day of a month was not displayed in calendar #8045.
Fix: dataSample caused incorrect extent when data is NaN.
Fix: data sample worked abnormally when using `series.encode`. #8017
Fix: `legendHoverLink: false` did not work appropriately when multiple
series have the same name. #8010
Fix: Some of the graph hover style did not work.


Please vote to approve the release.
Thanks!


Zhang Wenli
http://zhangwenli.com

Re: Move GitBox notifications to commits list?

[Wenli Zhang]

Agree. Could one of our mentor help to configure? Or tell us how to do so?
Thanks!

Zhang Wenli
http://zhangwenli.com

On Tue, Apr 17, 2018 at 4:27 AM, SHUANG SU  wrote:

> Agree. How to set it to move gitbox notifications to notifications@?
>
> 2018-04-16 18:03 GMT+08:00 John D. Ament :
>
> > Hi all
> >
> > Just a friendly ping from a mentor.  I like to stay up on the dev
> > discussions, but tons of gitbox mails flowing in.
> >
> > Another podling of mine went with a notifications@ list.
> >
> > John
> >
> > On Sun, Apr 8, 2018 at 10:17 AM John D. Ament 
> > wrote:
> >
> > > On Sun, Apr 8, 2018 at 9:55 AM Daniel Gruno 
> > wrote:
> > >
> > >> On 04/08/2018 03:53 PM, John D. Ament wrote:
> > >> > Hi,
> > >> >
> > >> > I find it a bit difficult to sift through the developer activities.
> > >> Right
> > >> > now, all gitbox notifications are going to dev@.  I think they make
> > >> more
> > >> > sense to go to commits@, potentially an issues@ list.
> > >> >
> > >> > What do others think?
> > >> >
> > >> > John
> > >> >
> > >>
> > >> or make an issues@ list? Would be nice if we had it split three ways:
> > >>
> > >> dev@: development discussions
> > >> issues@: PRs etc
> > >> commits: git commits
> > >>
> > >>
> > > How would you classify the comments added to a PR?  issues@? or
> commits@
> > ?
> > >
> > >
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> > >> For additional commands, e-mail: dev-h...@echarts.apache.org
> > >>
> > >>
> >
>

Re: ECharts Website

[Wenli Zhang]

Hi John,

Thanks for the detailed explanation.

The echarts-www project is currently not included in SGA, so we should
change the license and then file infra request.
But we worry that if "admin" role is not given to us, like what happens to
echarts repo now, it may be hard for us to find out what's going on when
error occurs during building website. Since we may try a few times to build
correctly, I believe it's quite inefficient to email admin each time we
failed to build.

The website is currently generated using gulp, by running `bash
release.sh`. And the generated HTML files and other assets are under root
directory. Do the files hosted on `asf-site` branch hosted on Apache's
server or GitHub Pages? If on Apache server, how should we get the error
log of server?

Another question is, do we have to make this website ready before we
release a new version? That may take a few more days or even weeks to be
ready, considering the delay of email communication.

Thanks!

Zhang Wenli
http://zhangwenli.com

On Mon, Apr 16, 2018 at 6:01 PM, John D. Ament <johndam...@apache.org>
wrote:

> Hi Wenli,
>
> We can host that at Apache.  We do need to make a few changes to work
> within the branding policies.  Please review
> https://incubator.apache.org/guides/branding.html and
> https://incubator.apache.org/guides/sites.html
>
> Was the website included in the SGA?  If not, would you be able to get
> another SGA put together that includes the website?  If it was included,
> please just file another infra request to move the git repo over.
>
> It looks like you're using jade to build the website.  I think that's
> already a supported tool, if not I'm sure we can install it.
>
> Typically we maintain two branches, but jade may work differently.  On the
> "master" or "develop" branch is where the source code for the website
> lives.  Typically there is a build script that would be created that wraps
> the actual build from master into a "asf-site" branch.  That branch
> contains the final build output for the website.  If everything is on a
> single branch, that should still work, just gets a little confusing since
> somehow it needs to be built.  Do you build it manually?  We can do Jenkins
> jobs or Buildbot jobs to do it (I personally prefer Jenkins, much more self
> serve).
>
> You can take a look at what I put together for the incubator website, which
> uses jbake and velocity to run:
> https://github.com/apache/incubator/blob/master/build_site.sh
>
> John
>
> On Sun, Apr 15, 2018 at 11:16 PM Wenli Zhang <oviliazh...@gmail.com>
> wrote:
>
> > We are currently using https://github.com/ecomfe/echarts-www to generate
> > website https://ecomfe.github.io/echarts-doc/public/en/index.html .
> Could
> > we have another project like
> > https://github.com/apache/incubator-echarts-www
> > for the podling website?
> >
> > Where is the server then, and how should we build and release the
> website?
> >
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
> > On Mon, Apr 16, 2018 at 10:39 AM, Wenli Zhang <oviliazh...@gmail.com>
> > wrote:
> >
> > > Hi John,
> > >
> > > We are currently using https://ecomfe.github.io/echarts-doc/public/en/
> > > index.html for website.
> > > Is this podling website required before we release a new version?
> > >
> > >
> > > Zhang Wenli
> > > http://zhangwenli.com
> > >
> > > On Mon, Apr 16, 2018 at 12:31 AM, John D. Ament <johndam...@apache.org
> >
> > > wrote:
> > >
> > >> Both URLs will end up working for them (echarts.apache.org and
> > >> echarts.incubator.apache.org).  I personally don't care which is used
> > >> regularly, and it helps projects to not use the incubator suffixed one
> > >> when
> > >> graduating.  As long as the website complies with branding policies
> and
> > >> release download policies.
> > >>
> > >> John
> > >>
> > >> On Sun, Apr 15, 2018 at 9:53 AM Kevin A. McGrail <kmcgr...@apache.org
> >
> > >> wrote:
> > >>
> > >> > John, do they use echarts.incubator.apache.org to start?
> > >> >
> > >> > On Sun, Apr 15, 2018, 09:24 John D. Ament <johndam...@apache.org>
> > >> wrote:
> > >> >
> > >> > > All,
> > >> > >
> > >> > > We've received a media request about our website.  Currently there
> > is
> > >> no
> > >> > > website for ECharts.  What are the plans for building a website?
> > >> > >
> > >> > > John
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>

Re: ECharts Website

[Wenli Zhang]

We are currently using https://github.com/ecomfe/echarts-www to generate
website https://ecomfe.github.io/echarts-doc/public/en/index.html . Could
we have another project like https://github.com/apache/incubator-echarts-www
for the podling website?

Where is the server then, and how should we build and release the website?


Zhang Wenli
http://zhangwenli.com

On Mon, Apr 16, 2018 at 10:39 AM, Wenli Zhang <oviliazh...@gmail.com> wrote:

> Hi John,
>
> We are currently using https://ecomfe.github.io/echarts-doc/public/en/
> index.html for website.
> Is this podling website required before we release a new version?
>
>
> Zhang Wenli
> http://zhangwenli.com
>
> On Mon, Apr 16, 2018 at 12:31 AM, John D. Ament <johndam...@apache.org>
> wrote:
>
>> Both URLs will end up working for them (echarts.apache.org and
>> echarts.incubator.apache.org).  I personally don't care which is used
>> regularly, and it helps projects to not use the incubator suffixed one
>> when
>> graduating.  As long as the website complies with branding policies and
>> release download policies.
>>
>> John
>>
>> On Sun, Apr 15, 2018 at 9:53 AM Kevin A. McGrail <kmcgr...@apache.org>
>> wrote:
>>
>> > John, do they use echarts.incubator.apache.org to start?
>> >
>> > On Sun, Apr 15, 2018, 09:24 John D. Ament <johndam...@apache.org>
>> wrote:
>> >
>> > > All,
>> > >
>> > > We've received a media request about our website.  Currently there is
>> no
>> > > website for ECharts.  What are the plans for building a website?
>> > >
>> > > John
>> > >
>> >
>>
>
>

Re: ECharts todo list of next release

[Wenli Zhang]

Hi Kevin,

Please help create a project for echarts since I don't have the right to do
so.

As about my name, sorry for the confusion.
My lastname is Zhang and firstname is Wenli.
Yes, we Chinese sometimes do switch the order since we are confused which
one is the correct order. I've heard of two versions of ordering for
foreign names to be translated into English. One says that firstname goes
first in English name (and I guess that's why it's called firstname haha)
so it should be Wenli Zhang. Another saying is that, foreign names should
follow the custom order of foreign languages, which makes it Zhang Wenli.
Anyway, I would prefer to be called Wenli. And do please tell me if there
is a correct order. :)


Zhang Wenli
http://zhangwenli.com

On Fri, Apr 13, 2018 at 9:42 PM, Kevin A. McGrail <kmcgr...@apache.org>
wrote:

>  Great point.  I didn't know the self serve had gone live.  I thought it
> was still in testing.  Wenli, you'll see the ability to create a Jira
> project there.  John, not sure what you meant about git repo.  Was that a
> different issue or a Fruedian slip?
>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
> On Fri, Apr 13, 2018 at 8:31 AM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > On Fri, Apr 13, 2018 at 7:51 AM Kevin A. McGrail <kmcgr...@apache.org>
> > wrote:
> >
> > > Zhang,
> > >
> > > First, I have a dumb question.  Your email address is Wenli Zhang and
> > your
> > > signature is Zhang Wenli.  I see this often with names in China.  Can
> you
> > > tell me more about this?  Is Zhang your given name and Wenli your
> > surname?
> > > Why do you switch them?  In English, I would expect a command like
> > McGrail,
> > > Kevin if it was my lastname/firstname.
> > >
> > > Second, to add a project for echarts to Jira, what I would do is open a
> > > Jira ticket with infrastructure.  Then you can search echarts issues in
> > > jira and retag them.  They might also use different jira instances for
> > > projects, I don't know but I'll leave that to infrastructure.  The key
> > > point is ask them for what you need.
> > >
> > >
> > If you're not aware, Infra now supports a large number of features as
> self
> > serve options.  Last I checked, they're open for ASF Members and Chairs,
> so
> > you or I can submit a request on the podling's behalf to get the various
> > resources https://selfserve.apache.org/
> >
> > Note that any PPMC member can request a git repo.
> >
> > Wenli, I shall close your JIRA ticket as it is not how we manage this.
> >
> > John
> >
> >
> > > Regards,
> > > KAM
> > >
> > > --
> > > Kevin A. McGrail
> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > > Chair Emeritus Apache SpamAssassin Project
> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
> > >
> > > On Fri, Apr 13, 2018 at 3:07 AM, Wenli Zhang <oviliazh...@gmail.com>
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > I've created a todo list of our next release, ECharts 4.1.0 at
> > > > https://issues.apache.org/jira/browse/INCUBATOR-211 .
> > > > I'm not quite sure if I did it right?
> > > >
> > > > I wonder if we could have a project called echarts on JIRA so that we
> > can
> > > > better filter this kind of issues later? I didn't find the way/access
> > to
> > > do
> > > > so, could anyone give a hand?
> > > >
> > > > Thanks!
> > > >
> > > > Zhang Wenli
> > > > http://zhangwenli.com
> > > >
> > >
> >
>

ECharts todo list of next release

[Wenli Zhang]

Hi all,

I've created a todo list of our next release, ECharts 4.1.0 at
https://issues.apache.org/jira/browse/INCUBATOR-211 .
I'm not quite sure if I did it right?

I wonder if we could have a project called echarts on JIRA so that we can
better filter this kind of issues later? I didn't find the way/access to do
so, could anyone give a hand?

Thanks!

Zhang Wenli
http://zhangwenli.com

Re: About how to track features of next release

[Wenli Zhang]

Great. Then we shall use JIRA to discuss ideas.

Zhang Wenli
http://zhangwenli.com

On Mon, Apr 9, 2018 at 9:45 PM, Kevin A. McGrail <kmcgr...@apache.org>
wrote:

> I recommend Jira tickets STRONGLY because that way the ideas can be done
> any time by anyone.
>
> With a volunteer community, you might have someone new from the internet be
> interested and jump on one of the ideas.
>
> Regards,
> KAM
>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
> On Sun, Apr 8, 2018 at 11:04 PM, Wenli Zhang <oviliazh...@gmail.com>
> wrote:
>
> > Hi mentors,
> >
> > I was informed that we should discuss what features to include in next
> > release. And I would like to ask how this should be done.
> >
> > Should we send an email for each feature for others to discuss and vote,
> or
> > open a JIRA ticket for each feature?
> >
> > Thanks!
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
>

Re: Podling Report Reminder - April 2018

[Wenli Zhang]

Thanks John.

It says I should send my username to "general@incubator". Is this an email
or how should I send it? If it is email, I guess there's something missing
in the suffix part of "incubator"?

Zhang Wenli
http://zhangwenli.com

On Sun, Apr 8, 2018 at 9:41 PM, John D. Ament <johndam...@apache.org> wrote:

> Wenli,
>
> There's information at https://wiki.apache.org/incubator/ on steps
> required
> to gain write access.  Take a look at the info box at the top.
>
> John
>
> On Sat, Apr 7, 2018 at 11:53 PM Wenli Zhang <oviliazh...@gmail.com> wrote:
>
> > Hi John,
> >
> > I will be responsible for podling report of ECharts.
> > Could I have the authority of accessing pages like
> > https://wiki.apache.org/incubator/April2018 ?
> >
> > I asked Shen Yi to edit it for me this month.
> >
> > ​Thanks!​
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
> > On Sun, Apr 8, 2018 at 11:31 AM, Wenli Zhang <oviliazh...@gmail.com>
> > wrote:
> >
> >> Sorry for the delay. I will draft it now.
> >>
> >> Zhang Wenli
> >> http://zhangwenli.com
> >>
> >> On Thu, Apr 5, 2018 at 9:43 PM, John D. Ament <johndam...@apache.org>
> >> wrote:
> >>
> >>> Just following up on the below..  Any takers?
> >>>
> >>> On Wed, Apr 4, 2018 at 7:11 AM John D. Ament <johndam...@apache.org>
> >>> wrote:
> >>>
> >>> > Hi all,
> >>> >
> >>> > Just a reminder that our report is due today.  Anyone available to
> >>> draft
> >>> > it?
> >>> >
> >>> > John
> >>> >
> >>> >
> >>> > On Tue, Apr 3, 2018 at 8:56 PM <johndam...@apache.org> 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, 18 April 2018, 10:30 am PDT.
> >>> >> 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, April 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.
> >>> >>
> >>> >> 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://wiki.apache.org/incubator/April2018
> >>> >>
> >>> >> Note: This is manually populated. You may need to wait a little
> before
> >>> >> this page is created from a template.
> >>> >>
> >>> >> 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...@echarts.apache.org
> >>> >> For additional commands, e-mail: dev-h...@echarts.apache.org
> >>> >>
> >>> >>
> >>>
> >>
> >>
> >
>

Re: ECharts @ The ASF - Next Steps

[Wenli Zhang]

Hi John,

I created this ticket and I'm not sure if I did it right.
https://issues.apache.org/jira/browse/INFRA-16224

Please have a look?
Thanks!

Zhang Wenli
http://zhangwenli.com

On Thu, Mar 22, 2018 at 9:26 PM, John D. Ament <johndam...@apache.org>
wrote:

> Your project is under "Incubator" so just choose Incubator in the project
> list.
>
> https://issues.apache.org/jira/browse/INFRA to file a JIRA ticket with
> Infra.  Request to migrate the git repos over.
>
> John
>
> On Thu, Mar 22, 2018 at 2:49 AM Wenli Zhang <oviliazh...@gmail.com> wrote:
>
> > Thanks Dave,
> >
> > It seems that ECharts is not in JIRA projects. Is this what you mean by
> > *JIRA ticket*?
> >
> > Shen Yi has the admin rights of ecomfe/echarts project on GitHub. His
> JIRA
> > id is shenyi.
> >
> > Thanks!
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
> > On Thu, Mar 22, 2018 at 2:34 PM, Dave Fisher <dave2w...@comcast.net>
> > wrote:
> >
> > > Hi -
> > >
> > > Welcome to the ASF.
> > >
> > > To move the github repository a member of the Apache Infra team needs
> > > temporary admin rights in the original, contributing github repository
> in
> > > order to move it to the Apache Incubator. If you know the Admin please
> > > provide in the Infra JIRA ticket.
> > >
> > > If you need help then one of your mentors can create the ticket for you
> > > tomorrow.
> > >
> > > Regards,
> > > Dave
> > >
> > > Sent from my iPhone
> > >
> > > On Mar 21, 2018, at 11:03 PM, Wenli Zhang <oviliazh...@gmail.com>
> wrote:
> > >
> > > Thanks John and Kevin for your reply.
> > >
> > > So right now I shall just wait for Kevin to contact Infra. Right?
> > >
> > > Zhang Wenli
> > > http://zhangwenli.com
> > >
> > > On Wed, Mar 21, 2018 at 10:04 PM, John D. Ament <johndam...@apache.org
> >
> > > wrote:
> > >
> > >> On Wed, Mar 21, 2018 at 10:00 AM John D. Ament <johndam...@apache.org
> >
> > >> wrote:
> > >>
> > >> > On Wed, Mar 21, 2018 at 7:34 AM Kevin A. McGrail <
> kmcgr...@apache.org
> > >
> > >> > wrote:
> > >> >
> > >> >> Hi Zhang, you have SGAs filed and ICLA's from the committers so
> > >> >> definitely get that moving.  I would contact Infra.  See
> > >> >> http://www.apache.org/dev/infra-contact#requesting-menu and
> they'll
> > >> send
> > >> >> you to issues.apache.org/jira where you can put in a request.
> > >> >>
> > >> >> That request should likely state your goal and they can discuss git
> > and
> > >> >> mirrors on github and what's possible, etc.
> > >> >>
> > >> >
> > >> Typically what happens here is the podling asks to migrate the
> existing
> > >> repos to the apache github organization.  To do that, you'll need to
> > make
> > >> someone from infra an admin on the existing org (ecomfe) and they'll
> > >> migrate it over.  If that won't work (for your own security reasons)
> it
> > >> looks like they've been working on them on an as need basis so they
> > still
> > >> may be able to help.
> > >>
> > >>
> > >>
> > >> >
> > >> >> Re: Issue tracking and import from github, I would again open a
> > ticket
> > >> >> with Jira with your ideal goal:
> > >> >>
> > >> >> We would like jira setup & We would like help migrating existing
> > >> tickets
> > >> >> from https://github.com/ecomfe/echarts/issues to our jira instance
> > >> >>
> > >> >
> > >> > We allow projects to maintain github issues, so no need to migrate
> to
> > >> JIRA
> > >> > if the project wants to stay with github issues.
> > >> >
> > >> >
> > >> >>
> > >> >> Then based on what Infrastructure says, we can discuss a plan.
> > >> >>
> > >> >> Hope this helps!
> > >> >>
> > >> >> Regards,
> > >> >> KAM
> > >> >>
> > >> >>
> > >> >> --
> > >> >> Kevin A. McGrail
> > >> >> Asst. Treasurer &am

Re: ECharts @ The ASF - Next Steps

[Wenli Zhang]

Thanks Dave,

It seems that ECharts is not in JIRA projects. Is this what you mean by
*JIRA ticket*?

Shen Yi has the admin rights of ecomfe/echarts project on GitHub. His JIRA
id is shenyi.

Thanks!

Zhang Wenli
http://zhangwenli.com

On Thu, Mar 22, 2018 at 2:34 PM, Dave Fisher <dave2w...@comcast.net> wrote:

> Hi -
>
> Welcome to the ASF.
>
> To move the github repository a member of the Apache Infra team needs
> temporary admin rights in the original, contributing github repository in
> order to move it to the Apache Incubator. If you know the Admin please
> provide in the Infra JIRA ticket.
>
> If you need help then one of your mentors can create the ticket for you
> tomorrow.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> On Mar 21, 2018, at 11:03 PM, Wenli Zhang <oviliazh...@gmail.com> wrote:
>
> Thanks John and Kevin for your reply.
>
> So right now I shall just wait for Kevin to contact Infra. Right?
>
> Zhang Wenli
> http://zhangwenli.com
>
> On Wed, Mar 21, 2018 at 10:04 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
>> On Wed, Mar 21, 2018 at 10:00 AM John D. Ament <johndam...@apache.org>
>> wrote:
>>
>> > On Wed, Mar 21, 2018 at 7:34 AM Kevin A. McGrail <kmcgr...@apache.org>
>> > wrote:
>> >
>> >> Hi Zhang, you have SGAs filed and ICLA's from the committers so
>> >> definitely get that moving.  I would contact Infra.  See
>> >> http://www.apache.org/dev/infra-contact#requesting-menu and they'll
>> send
>> >> you to issues.apache.org/jira where you can put in a request.
>> >>
>> >> That request should likely state your goal and they can discuss git and
>> >> mirrors on github and what's possible, etc.
>> >>
>> >
>> Typically what happens here is the podling asks to migrate the existing
>> repos to the apache github organization.  To do that, you'll need to make
>> someone from infra an admin on the existing org (ecomfe) and they'll
>> migrate it over.  If that won't work (for your own security reasons) it
>> looks like they've been working on them on an as need basis so they still
>> may be able to help.
>>
>>
>>
>> >
>> >> Re: Issue tracking and import from github, I would again open a ticket
>> >> with Jira with your ideal goal:
>> >>
>> >> We would like jira setup & We would like help migrating existing
>> tickets
>> >> from https://github.com/ecomfe/echarts/issues to our jira instance
>> >>
>> >
>> > We allow projects to maintain github issues, so no need to migrate to
>> JIRA
>> > if the project wants to stay with github issues.
>> >
>> >
>> >>
>> >> Then based on what Infrastructure says, we can discuss a plan.
>> >>
>> >> Hope this helps!
>> >>
>> >> Regards,
>> >> KAM
>> >>
>> >>
>> >> --
>> >> Kevin A. McGrail
>> >> Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> >> Chair Emeritus Apache SpamAssassin Project
>> >> https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
>> >>
>> >> On Wed, Mar 21, 2018 at 6:27 AM, Wenli Zhang <oviliazh...@gmail.com>
>> >> wrote:
>> >>
>> >>> Hi Kevin,
>> >>>
>> >>> Is there anything we shall do before transferring ECharts repo to
>> Apache
>> >>> incubator? Or should we just wait for further notice?
>> >>>
>> >>> I noticed that you mentioned Jira in your last email. We haven't set
>> up
>> >>> Jira, so could you help us to do so, or tell us how to do it?
>> >>>
>> >>> Besides, after ECharts transferred to incubator, we would like to keep
>> >>> the
>> >>> old issues and new issues under ecomfe/echarts. Would that be
>> possible?
>> >>>
>> >>> Thanks!
>> >>>
>> >>> ​Best Regards,​
>> >>>
>> >>> Zhang Wenli
>> >>> http://zhangwenli.com
>> >>>
>> >>> On Tue, Mar 6, 2018 at 2:01 PM, Kevin A. McGrail <kmcgr...@apache.org
>> >
>> >>> wrote:
>> >>>
>> >>> > Hi Tan, I think so yes.  The sooner the repos are on ASF, the sooner
>> >>> > development can get kickstarted again.  I'm sure it's a pain living
>> in
>> >>> two

Re: ECharts @ The ASF - Next Steps

[Wenli Zhang]

Hi Kevin,

Is there anything we shall do before transferring ECharts repo to Apache
incubator? Or should we just wait for further notice?

I noticed that you mentioned Jira in your last email. We haven't set up
Jira, so could you help us to do so, or tell us how to do it?

Besides, after ECharts transferred to incubator, we would like to keep the
old issues and new issues under ecomfe/echarts. Would that be possible?

Thanks!

​Best Regards,​

Zhang Wenli
http://zhangwenli.com

On Tue, Mar 6, 2018 at 2:01 PM, Kevin A. McGrail 
wrote:

> Hi Tan, I think so yes.  The sooner the repos are on ASF, the sooner
> development can get kickstarted again.  I'm sure it's a pain living in two
> places right now.
>
> To me, the SGA is all that's needed for the Repos.  Have you sent a request
> to set them up via Jira?  Daniel might be able to help get that
> jumpstarted.
>
> Regards,
> KAM
>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
> On Mon, Mar 5, 2018 at 11:31 PM, Tan,Zhongyi  wrote:
>
> > Hi， kevin,
> >
> > I have send the Software Grant Agreement document already，so the #1 is
> > done。
> >
> > As the ICLAs,  I have pushed all 8 developer of chars to sign and send
> out
> > their ICLAs already.
> > Here is the list
> > developer   Signed and Send ICLASubscribe to maillist
> > Su Shuang   susu...@apache.org   yes
> > Shen Yi she...@apache.org yes
> > Zhang Wenli ovi...@apache.org yes
> > Li Deqing   deqin...@apache.org yes
> > Dong Ruierror...@apache.org yes
> > Lin Zhifeng ke...@apache.org   yes
> > Wang Juntingwan...@apache.org yes
> > Huang Houjind...@apache.org yes
> >
> > So we can move on to transfer repo now？
> > Thanks
> >
> >
> >
> > 在 2018/2/24 上午11:12， "Kevin A. McGrail"  > kevin.mcgr...@mcgrail.com>> 写入:
> >
> > On 2/23/2018 9:38 PM, Tan,Zhongyi wrote:
> > Thanks， now the status webpage has been updated.
> >
> > It looks great.
> >
> > What to do next?
> > Is it time to migrate the git repo?
> >
> > IMO, yes.  SGA, ICLAs and the code repos are #1 #2 & #3 from my
> > perspective.
> >
> >
> > Best,
> >
> > KAM
> >
> >
> >
> >
> >
> >
>