Re: Availability and Licensing Inquiry: Integration of Apache ECharts with Qlik Sense

[Dave Fisher]

Hi -

This ECharts extension is not a product of Apache ECharts. You would need to 
reach out to Qlik Sense. Maybe try https://garden.qlik.dev

Best,
Dave

> On Apr 19, 2024, at 6:05 AM, Parmeshwar More  
> wrote:
> 
> Hi Team,
> 
> I hope this email finds you well. We're currently exploring the possibility 
> of integrating Apache ECharts with Qlik Sense using the ECharts extension. 
> Could you kindly provide information regarding the availability of this 
> extension and its associated licensing terms?
> 
> Specifically, we would like to know if the ECharts extension for Qlik Sense 
> is freely available for use, or if it requires a paid license. Any details 
> you can provide on the process for obtaining and implementing the extension 
> would be greatly appreciated.
> 
> Thank you in advance for your assistance
> 
> [https://cyber.securityhq.com/hubfs/Blue%20line%20Email%20signature.png]
> [https://cyber.securityhq.com/hubfs/SecurityHQ-logo-no-space-email-signature.png]
> Parmeshwar More | Senior Analyst
> Mobile 00 91 8975 203 061
> pm...@securityhq.com
> www.securityhq.com
> [https://cyber.securityhq.com/hubfs/Email%20signature/Email-signature-banner-650x150-RPT-Global%20Threat%20Insight%20Q1%202024.jpg]
>  
> 
> 
> Latest updates, blogs and thought leadership check our Knowledge Base (Cyber 
> Security Resources  | Managed 
> Security Services | 
> SecurityHQ)
> 
> This email communication, including attachments is solely intended for the 
> use of the individual(s) to whom it is addressed. It may contain confidential 
> and/or legally privileged information. If you are not the intended recipient, 
> please notify the sender immediately and delete the message forthwith from 
> your mailing system; any disclosure, copying, distribution or taking action 
> based on the contents of this email is strictly prohibited and unlawful. 
> E-mail communications cannot be guaranteed to be timely, secure, error or 
> virus-free, for which sender does not take any liability. SecurityHQ Ltd 
> 2024. All rights reserved
> 
> Follow us 
> [https://cyber.securityhq.com/hubfs/Social%20Media%20Icons/facebook-grey-1.png]
>    
> [https://cyber.securityhq.com/hubfs/Social%20Media%20Icons/twitter-grey-1.png]
>    
> [https://cyber.securityhq.com/hubfs/Social%20Media%20Icons/linkedin-grey-1.png]
>    
> [https://cyber.securityhq.com/hubfs/Social%20Media%20Icons/youtube-grey-1.png]
>  


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

Re: Echarts plugin for Grafana.

[Dave Fisher]

Hi -

Great question.

> On Feb 21, 2024, at 1:26 AM, Artūrs Rubenis 
>  wrote:
> 
> Hello!
> 
> I'm interested in customizing the Echarts plugin in Grafana and had a 
> question. Is it possible to integrate additional imports, like jspdf, to 
> enable features such as saving a panel to PDF within Grafana? I'd appreciate 
> any insights you have on this.

I was not aware of the Echarts plugin for Grafana. I have experience 
configuring and rendering panels to png using the Grafana image renderer,  but 
creating a PDF without having to use Grafana Enterprise is very interesting to 
me.

Best,
Dave

> 
> Thanks,
> 
> Artūrs
> 


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

Re: [Discuss] About new mailing lists for GitBox messages

[Dave Fisher]

Hi,

Infra did a commit that has “fixed” the trouble.

https://github.com/apache/echarts/commit/8ea10f4d0be0d97f3a89410c7daf16112cf3769c

I think that putting all of the notifications into the commits@ list is 
sufficient.

Regards,
Dave

> On Apr 9, 2022, at 3:12 AM, Yi Shen  wrote:
> 
> +1 with Zhongxiang's proposal:
> - iss...@echarts.apache.org (for issues)
> - p...@echarts.apache.org(for pull requests)
> - notificati...@echarts.apache.org(for various notifications like GitHub
> actions)
> 
> PS it should be done ASAP.
> 
> On Sat, Apr 9, 2022 at 4:46 PM Ovilia  wrote:
> 
>> Hi all,
>> 
>> We have been receiving a lot of automatic emails since 4th April in this
>> mailing list.
>> We are considering creating new mailing lists for these kinds of messages
>> to prevent
>> overwhelming messages.
>> 
>> Zhongxiang has proposed the following names: [1]
>> - iss...@echarts.apache.org (for issues)
>> - p...@echarts.apache.org / pullreque...@echarts.apache.org (for pull
>> requests)
>> - notificati...@echarts.apache.org / j...@echarts.apache.org (for various
>> notifications like GitHub actions)
>> 
>> I would also like to hear about others' ideas. Whether we should create one
>> single mailing
>> list for issues, pull requests and actions all, or create three mailing
>> lists.
>> 
>> Thanks
>> 
>> [1] https://github.com/apache/echarts/pull/16855
>> 
>> *Ovilia*
>> 
> 
> 
> -- 
> Yi Shen
> Apache ECharts PMC


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

Re: ECharts for Evidence

[Dave Fisher]

Since ECharts is open source you can always try to implement a solution 
yourself and submit a PR!

All the best,
Dave

Sent from my iPhone

> On Nov 18, 2021, at 6:10 PM, Yi Shen  wrote:
> 
> Hi Sean.
> 
> Thanks a lot for your feedback! About these two issues your mentioned:
> 
> Stacking on x-axis with type = value or time
> 
> 
> It's a feature that has been mentioned a lot of times in our issue list.
> It's still not in our iteration plan but I think we will support it in the
> future.
> 
> containLabel not covering all
>> labels on chart
> 
> 
> Optimize label display has been an important topic since 5.0. We are going
> to adjust label position to avoid overflow the chart area in our
> near versions.
> 
> Regards!
> 
>> On Thu, Nov 18, 2021 at 11:31 PM Sean Hughes  wrote:
>> 
>> Hi,
>> 
>> I’m one of the founders of Evidence - a web framework for data analysts.
>> I’ve been building charts with ECharts for a few weeks now and have been
>> very impressed with your library and your prompt responses for issues on
>> Github!
>> 
>> I’m hoping to use ECharts as our main chart library for our product, but
>> there are a few issues holding us back from being able to do that. I was
>> hoping to hear if you have plans to address these in future versions of
>> the product and if so, how high up on your priority list they are.
>> 
>> Because we’re building a reusable framework for our users, we’re not
>> able to anticipate all potential situations, and as a result we can’t
>> make one-time adjustments (e.g., adding extra padding in one version of
>> a chart). Here are the issues we’re having:
>> Stacking on x-axis with type = value or time (bar and area chart
>> stacking do not work consistently)
>> I believe we may be able to handle this by writing some custom data
>> transformation logic to sync the values/times for our data series
>> Labels getting cut off by chart area (containLabel not covering all
>> labels on chart)
>> Though it wouldn’t be ideal, in the short-term if we could override the
>> overflow:hidden option on the DOM container, it would at least stop the
>> labels from looking cut off if there is whitespace beside the chart
>> I’ve created GitHub issues for other things we need in the library, but
>> those are minor things that I can work on. These two issues are major
>> blockers for us, so I have my fingers crossed that they’re on the
>> roadmap.
>> 
>> Let me know what you think.
>> 
>> Thanks!
>> Sean
>> 
>> s...@evidence.dev
>> (416) 910-9764
>> 
> 
> 
> -- 
> Yi Shen
> Apache ECharts PMC


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

Re: [ANNOUNCE] Release Apache ECharts 5.2.1

[Dave Fisher]

Please update this announcement to follow the download policy. Do not refer to 
dist.apache.org and check that every link works.

Thanks,
Dave

Sent from my iPhone

> On Sep 20, 2021, at 8:28 PM, Yi Shen  wrote:
> 
> Dear community,
> 
> The Apache ECharts team is proud to announce Apache ECharts 5.2.1.
> 
> Apache ECharts is a powerful, interactive charting and data visualization
> library for browser.
> 
> Download Links: https://dist.apache.org/repos/dist/release/echarts/5.2.1/
> 
> Release Notes: http://www.apache.org/dist/echarts/5.2.1/RELEASE_NOTE.txt
> 
> Website: http://echarts.apache.org/
> 
> 
> ECharts Resources:
> - Issue: https://github.com/apache/echarts/issues
> - Build Guide: https://github.com/apache/echarts/blob/5.2.1/README.md
> - Mailing-list: dev@echarts.apache.org
> 
> -- 
> Yi Shen
> Apache ECharts PMC


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

Re: ETA on Enhancement req

[Dave Fisher]

Hi -

If you have a need and can do the fix yourself then please submit a PR. This is 
an opens source project and contributions are welcome.

Regards,
Dave

> On Apr 26, 2021, at 11:52 AM, Zolper, John (Contractor)(CFPB) 
>  wrote:
> 
> Hello,
> 
> I understand there are a ton of enhancements on the list but for my client 
> this one really is important so I wanted to try to ask directly about it.
> 
> https://github.com/apache/echarts/issues/13843
> 
> If there’s any way to give either an ETA or update that would be immensely 
> appreciated.
> 
> Best,
> 
> JJ


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

Congratulations on Graduation

[Dave Fisher]

Hi ECharts,

Congratulations on graduation.

I have updated podlings.xml to reflect graduation.

You should now proceed with steps to move the project resources out of the 
Incubator.

See these guides.

https://infra.apache.org/infra-contact#requesting-graduation 

http://incubator.apache.org/guides/transferring.html 


Let me know if you have questions.

Regards,
Dave

Re: [VOTE] Release Apache ECharts (incubating) 5.0.0 (release candidate 3)

[Dave Fisher]

Hi -

Incubating in name, Signature, Checksum, DISCLAIMER, NOTICE, LICENSE, Rat Check 
All Good.

+1 (IPMC binding)

Regards,
Dave

> On Nov 20, 2020, at 9:12 AM, SHUANG SU  wrote:
> 
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 5.0.0 (release candidate 3).
> 
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/5.0.0-rc.3/
> 
> 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=de46c55
> 
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/5.0.0-rc.3/RELEASE_NOTE.txt
> 
> Build Guide:
> https://github.com/apache/incubator-echarts/blob/5.0.0-rc.3/README.md#build
> 
> Doc for 5.0.0-rc.3:
> https://echarts.apache.org/next/en/option.html
> 
> Examples for 5.0.0-rc.3:
> https://echarts.apache.org/next/examples/en/index.html
> 
> 
> Please vote on releasing this package as:
> Apache ECharts (incubating) 5.0.0 (release candidate 3)
> by "2020-11-23T18:10:56.066Z".
> 
> [ ] +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.
> 
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 
> --
> 
> 
> 
> Thanks,
> --
> Su Shuang (100pah)
> --


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

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

[Dave Fisher]

+1 (binding)

Checked signatures, hash, incubating in name, DISCLAIMER, LICENSE, NOTICE.

Builds on macOS with npm updated.

Regards,
Dave

> On Nov 11, 2020, at 4:51 AM, SHUANG SU  wrote:
> 
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 5.0.0 (release candidate 2).
> 
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/5.0.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=d7658ec
> 
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/5.0.0-rc.2/RELEASE_NOTE.txt
> 
> Build Guide:
> https://github.com/apache/incubator-echarts/blob/5.0.0-rc.2/README.md#build
> 
> Doc for 5.0.0-rc.2:
> https://echarts.apache.org/next/en/option.html
> 
> Examples for 5.0.0-rc.2:
> https://echarts.apache.org/next/examples/en/index.html
> 
> 
> Please vote on releasing this package as:
> Apache ECharts (incubating) 5.0.0 (release candidate 2)
> by "2020-11-14T13:45:01.761Z".
> 
> [ ] +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.
> 
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 
> --
> 
> 
> Thanks,
> --
> Su Shuang (100pah)
> --


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

Re: [VOTE] (Round 2) Graduate Apache ECharts (incubating) as a top level project

[Dave Fisher]

ck+List
>>>>>> 
>>>>>> -
>>>>>> 
>>>>>> X. Establish the Apache ECharts Project
>>>>>> 
>>>>>> WHEREAS, the Board of Directors deems it to be in the best
>>>>>> interests of the Foundation and consistent with the
>>>>>> Foundation's purpose to establish a Project Management
>>>>>> Committee charged with the creation and maintenance of
>>>>>> open-source software, for distribution at no charge to
>>>>>> the public, related to a charting and data visualization
>>>>>> library written in JavaScript.
>>>>>> 
>>>>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>>>> Committee (PMC), to be known as the "Apache ECharts Project",
>>>>>> be and hereby is established pursuant to Bylaws of the
>>>>>> Foundation; and be it further
>>>>>> 
>>>>>> RESOLVED, that the Apache ECharts Project be and hereby is
>>>>>> responsible for the creation and maintenance of software
>>>>>> related to a charting and data visualization
>>>>>> library written in JavaScript; and be it further
>>>>>> 
>>>>>> RESOLVED, that the office of "Vice President, Apache ECharts" be
>>>>>> and hereby is created, the person holding such office to
>>>>>> serve at the direction of the Board of Directors as the chair
>>>>>> of the Apache ECharts Project, and to have primary responsibility
>>>>>> for management of the projects within the scope of
>>>>>> responsibility of the Apache ECharts Project; and be it further
>>>>>> 
>>>>>> RESOLVED, that the persons listed immediately below be and
>>>>>> hereby are appointed to serve as the initial members of the
>>>>>> Apache ECharts Project:
>>>>>> 
>>>>>>   * Houjin Huang  
>>>>>>   * Deqing Li 
>>>>>>   * Dong Rui  
>>>>>>   * Kener Linfeng 
>>>>>>   * Kevin A. McGrail  
>>>>>>   * Wenli Zhang   
>>>>>>   * Shen Yi   
>>>>>>   * Shuang Su 
>>>>>>   * Siwen Su  
>>>>>>   * Junting Wang  
>>>>>>   * Zhongxiang Wang   
>>>>>>   * Dave Fisher   
>>>>>>   * Sheng Wu  
>>>>>>   * Zak Wu
>>>>>> 
>>>>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
>>>>>> be appointed to the office of Vice President, Apache ECharts, to
>>>>>> serve in accordance with and subject to the direction of the
>>>>>> Board of Directors and the Bylaws of the Foundation until
>>>>>> death, resignation, retirement, removal or disqualification,
>>>>>> or until a successor is appointed; and be it further
>>>>>> 
>>>>>> RESOLVED, that the initial Apache ECharts PMC be and hereby is
>>>>>> tasked with the creation of a set of bylaws intended to
>>>>>> encourage open development and increased participation in the
>>>>>> Apache ECharts Project; and be it further
>>>>>> 
>>>>>> RESOLVED, that the Apache ECharts Project be and hereby
>>>>>> is tasked with the migration and rationalization of the Apache
>>>>>> Incubator ECharts podling; and be it further
>>>>>> 
>>>>>> RESOLVED, that all responsibilities pertaining to the Apache
>>>>>> Incubator ECharts podling encumbered upon the Apache Incubator
>>>>>> Project are hereafter discharged.
>>>>>> 
>>>>>> Thanks
>>>>>> 
>>>>>> *Ovilia*
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>>>>> For additional commands, e-mail: dev-h...@echarts.apache.org
>>>>> 
>>>>> 
>>>> 
>>> 
>> 


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

Re: [DISCUSS] Graduate Apache ECharts (incubating) as a TLP

[Dave Fisher]

Hi Ovilla,

This makes sense.

I would add a LICENSE.md file at the top level of the four website generating 
repositories.

Also, make sure the README.md file explains the workflow of those repositories 
into the website repository.

These readme files are counting on redirection from ecomfe GitHub space to 
apache. Please correct them to be direct links.

Regards,
Dave

> On Oct 23, 2020, at 7:15 AM, Ovilia  wrote:
> 
> Hi Dave,
> 
> Thanks for the check.
> 
> These two projects are used to build ECharts's
> official Website, so they may be similar to
> https://github.com/apache/incubator-echarts-website
> in that:
> a) They don't have "releases" [1] by themselves
> b) They are not included in Apache ECharts's release distribution
> c) They are used only to generate the Website
> 
> The difference between them is that incubator-echarts-www
> and incubator-echarts-examples
> are used to generate the files in incubator-echarts-website.
> 
> According to [2],
>> With few exceptions
> <https://www.apache.org/legal/src-headers.html#faq-exceptions>, all
> human-readable Apache-developed files that are included within a
> distribution must include the header text
> <https://www.apache.org/legal/src-headers.html#header-text>. Documentation,
> including web site documentation distributed with the release, may include
> the header text within some form of metadata (such as HTML comments) or as
> a header or footer appearing in the visible documentation.
> Since these three projects are not included in the distribution of Apache
> ECharts (incubating),
> I don't think the header is required in this case.
> Please do correct me if I misunderstood the instructions. :)
> 
> [1] https://github.com/apache/incubator-echarts-www/releases
> [2] https://www.apache.org/legal/src-headers.html#faq-siteindocs
> 
> Thanks
> 
> *Ovilia*
> 
> 
> On Thu, Oct 22, 2020 at 2:38 AM Dave Fisher  wrote:
> 
>> Hi -
>> 
>> Thanks, I took a look.
>> 
>> Assuming that these will now all be Apache Licensed then there needs to be
>> LICENSE files in both repositories.
>> 
>> Also if these are ever released the source files will all need license
>> headers. [1]
>> 
>> The examples readme is still pointing to the ecomfe server.
>> 
>> Regards,
>> Dave
>> 
>> [1] https://www.apache.org/legal/src-headers.html
>> 
>>> On Sep 23, 2020, at 7:00 PM, Ovilia  wrote:
>>> 
>>> incubator-echarts-examples and incubator-echarts-www have been moved to
>>> Apache org on GitHub:
>>> https://github.com/apache/incubator-echarts-examples
>>> https://github.com/apache/incubator-echarts-www
>>> 
>>> 
>>> Thanks
>>> 
>>> *Ovilia*
>>> 
>>> 
>>> On Thu, Aug 27, 2020 at 5:07 PM Ville Brofeldt <
>> ville.v.brofe...@gmail.com>
>>> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> the releases are triggered by running `yarn ci:create-minor-version` and
>>>> `yarn ci:create-patch-version` for minor and patch releases
>> respectively.
>>>> After pushing to upstream master, deployment to npm happens
>> automatically.
>>>> I’m not familiar with the details on how this post push automation has
>> been
>>>> done in practice, but I can put you in touch with the person who has if
>>>> needed. My main point being that this makes it possible to decouple
>>>> triggering of deployment from the credentials used for deployment, as
>>>> anyone with the necessary rights to the repo can initiate the
>> deployment.
>>>> 
>>>> Ville
>>>> 
>>>>> On 26. Aug 2020, at 14.23, SHUANG SU  wrote:
>>>>> 
>>>>> Thanks for your review and suggestion Ville ~
>>>>> 
>>>>> I've tried to learn the publish script of
>>>>> https://github.com/apache-superset/superset-ui . But still not think
>> of
>>>>> some ideas from it. It seems to publish to some free CDN?
>>>>> At present we are using a third-party CDN with certain credentials
>>>> needed,
>>>>> and needs to make only PPMC know the pwd.
>>>>> 
>>>>>> We have updated the Website with a sponsored CDN to improve speed in
>>>> China
>>>>> and created an account for all PPMCs. But we are not sure how we
>>>>> should distribute the password of that account? Should we send the
>>>> password
>>>>> on the private
>>>>> mailing 

Re: [DISCUSS] Graduate Apache ECharts (incubating) as a TLP

[Dave Fisher]

Hi -

Thanks, I took a look.

Assuming that these will now all be Apache Licensed then there needs to be 
LICENSE files in both repositories.

Also if these are ever released the source files will all need license headers. 
[1]

The examples readme is still pointing to the ecomfe server.

Regards,
Dave

[1] https://www.apache.org/legal/src-headers.html

> On Sep 23, 2020, at 7:00 PM, Ovilia  wrote:
> 
> incubator-echarts-examples and incubator-echarts-www have been moved to
> Apache org on GitHub:
> https://github.com/apache/incubator-echarts-examples
> https://github.com/apache/incubator-echarts-www
> 
> 
> Thanks
> 
> *Ovilia*
> 
> 
> On Thu, Aug 27, 2020 at 5:07 PM Ville Brofeldt 
> wrote:
> 
>> Hi,
>> 
>> the releases are triggered by running `yarn ci:create-minor-version` and
>> `yarn ci:create-patch-version` for minor and patch releases respectively.
>> After pushing to upstream master, deployment to npm happens automatically.
>> I’m not familiar with the details on how this post push automation has been
>> done in practice, but I can put you in touch with the person who has if
>> needed. My main point being that this makes it possible to decouple
>> triggering of deployment from the credentials used for deployment, as
>> anyone with the necessary rights to the repo can initiate the deployment.
>> 
>> Ville
>> 
>>> On 26. Aug 2020, at 14.23, SHUANG SU  wrote:
>>> 
>>> Thanks for your review and suggestion Ville ~
>>> 
>>> I've tried to learn the publish script of
>>> https://github.com/apache-superset/superset-ui . But still not think of
>>> some ideas from it. It seems to publish to some free CDN?
>>> At present we are using a third-party CDN with certain credentials
>> needed,
>>> and needs to make only PPMC know the pwd.
>>> 
 We have updated the Website with a sponsored CDN to improve speed in
>> China
>>> and created an account for all PPMCs. But we are not sure how we
>>> should distribute the password of that account? Should we send the
>> password
>>> on the private
>>> mailing list? Is that safe enough?
>>> 
>>> For this original issue, I think another possible solution might be:
>>> Add the accounts of PPMCs as the admin of the third-party CDN. Then PPMCs
>>> are able to get the pwd from the admin console website of the third-party
>>> CDN.
>>> 
>>> 
>>> Thanks,
>>> --
>>> Su Shuang (100pah)
>>> --
>>> 
>>> 
>>> 
>>> On Tue, 25 Aug 2020 at 15:07, Ville Brofeldt 
>> wrote:
>>> 
 Hi ECharts community,
 
 I reviewed the graduation documents, and everything looks good at quick
 glance.
 
 With regards to CDN usernames/passwords, would it be possible to
>> automate
 the CDN deployment to avoid having to pass around credentials? On
 https://github.com/apache-superset/superset-ui there is a flow where
>> any
 admin is able to initiate deployment by issuing a single command and
 pushing to the main upstream repo, after which deployment to npm is
 performed automatically. Using this type of flow there wouldn't be a
>> need
 to manage separate user credentials to the CDN, and it would also make
>> the
 deployment process less error prone.
 
 Ville
 
 On 2020/07/27 05:07:23, Ovilia  wrote:
> Hi all,
> 
> Apache ECharts (incubating) has learned and grown a lot since our
> incubation in Jan
> 2018. Now, I'm glad to call on a discussion about whether we are ready
 for
> graduation and
> what remains to be done. Hopefully, after this discussion, we can set
>> the
> status to be
> "near graduation" in the monthly report.
> 
> Updates since incubation:
> - 2 new PPMCs (and another has completed the vote and undergoing the
> process) and 7
> new committers were elected and joined the community [1] and now
> we have committers working for more than 6 different companies.
> - Our mailing list [2] is very active and we have 79 people subscribed
>> to
> it.
> - Released 8 versions by 2 release managers [3]; release guide is at
>> [4]
> - 73 people have contributed to the project during incubation [9]
> - Assessment of the maturity model is available at [5]
> - Branding issues have been solved and name searching has been
>> completed
 [6]
> 
> Other things we need to discuss:
> 
> 1. Website
> We updated our Website [7] content, logo, document, and so on according
 to
> Apache rules
> and hopefully, it's following all requirements. You may help check the
> rules [8] and discuss
> the ones that you think need to change.
> 
> 2. Sponsored CDN
> We have updated the Website with a sponsored CDN to improve speed in
 China
> and
> created an account for all PPMCs. But we are not sure how we
> should distribute the
> password of that account? Should we send the password on the private
> mailing list? Is that safe enough?
> 

Re: Permission to use domain name

[Dave Fisher]

Hi -

I agree with Kevin.

> On Sep 19, 2020, at 11:32 AM, Kevin A. McGrail  wrote:
> 
> Hi Ovilia,
> 
> If the new domain doesn't reference apache or echarts name, that would
> be completely fine with a disclaimer as you suggest.  They could even
> use a Powered By Logo https://www.apache.org/foundation/press/kit/
> 
> I would ask branding for guidance on the domain name but something like
> gallery.baidu.com as a subdomain would be fine.  no need for a new
> domain name.

As long as it does not include “ECharts” in the domain name or url branding 
should be happy.

You can certainly link to it from the website. You should also have text that 
says that if anyone wants to offer a third party set of ECharts examples that 
they should contact the PMC. The PMC would review and add the links. 

Regards,
Dave

> 
> On 9/17/2020 11:07 PM, Ovilia wrote:
>> Yes, I agree with that it doesn't seem proper to let a company owned
>> product
>> use an Apache domain. 
>> 
>> As I said, we have technical difficulty donating the server. How can
>> we make
>> PPMC owns it if the server cannot be accessed outside of Baidu?
>> 
>> I really don't wish to make things complicated here. The gallery is a
>> platform
>> hosting user uploaded works of ECharts and it's not part of the
>> ECharts software
>> but a third-party tool.
>> 
>> So how about Baidu picking another domain name
>> (and ask IPMC for suggestion before purchasing) for the product and make
>> a clear notification that the gallery is not an official product of ASF?
>> ECharts official Website will not link to it if IPMC think it's not
>> proper.
>> 
>> IMO it shouldn't have any problem if it doesn't claim to be an
>> official ECharts 
>> product (correct me if I'm wrong) but just powered by ECharts. 
>> By using a domain name that does not contain ECharts in it, we hope
>> not to be
>> taken by mistake as an official product.
>> 
>> Hope this proposal could work with you.
>> 
>> Thanks
>> *
>> *
>> *Ovilia*
>> 
>> 
>> On Fri, Sep 18, 2020 at 10:49 AM Kevin A. McGrail > <mailto:kmcgr...@apache.org>> wrote:
>> 
>> 
>>On 9/14/2020 2:08 AM, Ovilia wrote:
>>> Another thing I'd like to confirm here is that, would it be OK
>>for the ASF
>>> that we use
>>> the domain name gallery.echarts.apache.org
>><http://gallery.echarts.apache.org> for the gallery while keeping
>>> the code
>>> license and the ownership of the user data to be of Baidu?
>> 
>>Ovilia, yes, I see that as a problem to use an apache.org
>><http://apache.org> sub-domain for
>>any third party.
>> 
>>> 
>>> Thanks
>>> 
>>> *Ovilia*
>>> 
>>> 
>>> On Sat, Sep 12, 2020 at 12:13 AM Zhongxiang Wang
>>mailto:wan...@apache.org>> wrote:
>>> 
>>>> I appreciate using a subdomain of echarts.apache.org
>><http://echarts.apache.org>.
>>>> 
>>>> It's simple enough to create a CNAME DNS record `
>>>> gallery.echarts.apache.org <http://gallery.echarts.apache.org>`
>>pointing to the current server of the domain `
>>>> gallery.echartsjs.com <http://gallery.echartsjs.com>` and we
>>have no need to do something extra.
>>>> 
>>>> Thanks,
>>>> Zhongxiang.
>>>> 
>>>> On 2020/09/11 08:06:38, Ovilia ><mailto:oviliazh...@gmail.com>> wrote:
>>>>> Thanks Dave!
>>>>> 
>>>>> In this case, I would personally prefer using
>>gallery.echarts.apache.org <http://gallery.echarts.apache.org>
>>>>> instead of
>>>>> gallery.echartsjs.com <http://gallery.echartsjs.com>.
>>>>> 
>>>>> Hope to hear from other PPMC members' opinions.
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> *Ovilia*
>>>>> 
>>>>> 
>>>>> On Fri, Sep 11, 2020 at 2:56 AM Dave Fisher ><mailto:w...@apache.org>> wrote:
>>>>> 
>>>>>> Hi -
>>>>>> 
>>>>>> (With my mentor hat.)
>>>>>> 
>>>>>> Apologies for the late reply. I am fine for this to happen.
>>It is not
>>>>>> unprecedented.
>>>>>> 
>>>>>> For example, the Apache OpenOffice PMC was able to continue using
>>>>>> openoffice.org <http://openoffice.o

Re: Permission to use domain name

[Dave Fisher]

Hi -

(With my mentor hat.)

Apologies for the late reply. I am fine for this to happen. It is not 
unprecedented.

For example, the Apache OpenOffice PMC was able to continue using 
openoffice.org since it already had a huge user base. While much of the domain 
is hosted on ASF infrastructure including PMC maintained VMs hosted on ASF 
Infra, a few subdomains like templates.openoffice.org is actually hosted via 
CNAME on sourceforge.net.

What Infra and Greg would like to see is the PPMC members discussing whether 
they have trouble with Baidu hosting a resource a particular subdomain.

Regards,
Dave

> On Sep 7, 2020, at 8:27 PM, Ovilia  wrote:
> 
> Do our mentors and Justin have anything to comment on this plan?
> Would it be all right if Baidu owns the user data and server while using
> Apache domain name?
> 
> Thanks
> 
> Ovilia
> 
> 
> On Tue, Sep 8, 2020 at 11:20 AM Yi Shen  > wrote:
> Hi Greg,
> 
> Thanks for the very detailed explanation.
> 
> What we concerned about is that we need to donate the server as we did on
> the website CDN in China.
> It will be good if we only need to create a CNAME for
> gallery.echarts.apache.org .
> 
> Regards.
> 
> On Fri, Sep 4, 2020 at 5:57 AM Greg Stein  > wrote:
> 
> > On Thu, Sep 3, 2020 at 4:16 AM Ovilia  > > wrote:
> > >...
> >
> > > I don't think we could use the domain name gallery.echarts.apache.org 
> > > 
> > but
> > > keep
> > > the server in Baidu company inside (correct me if I'm wrong),
> > >
> >
> > That should not be a problem! ... let's say the server is located at "
> > something-a38cf9.baidu.com " ... we can 
> > simply create a CNAME DNS record
> > for
> > gallery.echarts.apache.org  to point to 
> > that server. This is actually quite
> > normal for various apache.org  hostnames. We point to 
> > servers located "off
> > premises" all the time. Then, echarts can create links to direct people to
> > gallery.echarts.apache.org . Solved!
> >
> > Setting up such a CNAME is very simple for INFRA, so don't worry about the
> > work. We can have it set up as soon as the community reaches consensus on
> > that approach (eg. discussion/vote where Infra can see the community
> > agrees). Discuss, the file an INFRA Jira ticket.
> >
> > Cheers,
> > -g
> >
> 
> 
> -- 
> Yi Shen
> Apache ECharts(incubating) PPMC

Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Dave Fisher]

+1 (binding)

Great work ECharts team!

Regards,
Dave

> On Aug 16, 2020, at 8:36 PM, Ovilia  wrote:
> 
> Hi all,
> 
> Hello all,
> After our discussion about readiness for graduation to TLP on the dev
> mailing list [8], I would like to call a VOTE for Apache ECharts graduating
> as a top level project.
> 
> If this vote passes, the next step would be to submit the resolution below
> to the Incubator PMC, who would vote on sending it on to the Apache Board.
> 
> Vote:
> [ ] +1 - Recommend graduation of Apache ECharts as a TLP
> [ ]  0 - I don't feel strongly about it, but don't object
> [ ] -1 - Do not recommend graduation of Apache ECharts because...
> 
> The VOTE will open for at least 72 hours.
> 
> -
> 
> X. Establish the Apache ECharts Project
> 
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to
> the public, related to a charting and data visualization
> library written in JavaScript.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache ECharts Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache ECharts Project be and hereby is
> responsible for the creation and maintenance of software
> related to a charting and data visualization
> library written in JavaScript; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache ECharts" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache ECharts Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache ECharts Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache ECharts Project:
> 
>* Houjin Huang  
>* Deqing Li 
>* Dong Rui  
>* Kener Linfeng 
>    * Kevin A. McGrail  
>* Wenli Zhang   
>* Shen Yi   
>* Shuang Su 
>* Siwen Su  
>* Junting Wang  
>* Zhongxiang Wang   
>* Dave Fisher   
>* Sheng Wu  
>* Zak Wu
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
> be appointed to the office of Vice President, Apache ECharts, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
> 
> RESOLVED, that the initial Apache ECharts PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache ECharts Project; and be it further
> 
> RESOLVED, that the Apache ECharts Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator ECharts podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator ECharts podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> 
> -
> 
> More information:
> 
> - Assessment of the maturity model is available at [5].
> - A checklist of graduation is available at [6].
> - 3 new PPMCs and 6 new committers were elected and joined the community [1]
> since incubation and now we have committers working for more than 6
> different
> companies.
> - Our mailing list [2] is very active and we have 81 people subscribed to
> it.
> - Released 8 versions by 3 release managers [3] (and another version by
> another release manager is under voting stage); release guide is at [4].
> - 73 people have contributed to the project during incubation [10].
> - Branding issues have been solved and name searching has been completed
> [7].
> - Website [9] has been updated to meet up with Apache regulations.
> 
> -
> 
> 
> [1] https://echarts.apache.org/en/committers.html
> [2] https://lists.apache.org/list.html?dev@echarts.apache.org
> [3] https://dist.apache.org/repos/dist/release/incubator/echarts/
> [4]
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Guide
&

Some notes on graduation.

[Dave Fisher]

Hi -

(1) In reviewing the Maturity Model I noticed that the security page was copied 
from ServiceComb, but was not fully edited.

https://echarts.apache.org/en/security.html

Please make the necessary changes.

(2) Please always use PPMC Member or PMC Member and not PPMC or PMC when 
referring to people. The reason is that it is ambiguous when PPMCs is written 
as that really means several project management committees like Doris, Heron 
and ECharts.

https://echarts.apache.org/en/contributing.html

Please make the necessary changes.

(3) Once the board approves graduation to a top level project changes should be 
made to the download page.

Please make a wiki page where we can list the details of these changes.

(4) Be prepared to discuss the Online Builder confirming that it builds from a 
PMC approved Source release and only includes dependencies with approved 
licenses.

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

Re: [DISCUSS] Graduate Apache ECharts (incubating) as a TLP

[Dave Fisher]

Sent from my iPhone

> On Aug 3, 2020, at 4:21 AM, Yi Shen  wrote:
> 
> 
>> 
>> 
>> From my side, this is not the difference. The download source package is
>> never been voted is my concern.
>> I know the logically, it is just a subset, but whether there is a change or
>> unexpected files in the final download, we don't know. And no one would
>> check.
>> The whole vote/check process is for manual confirmation about that, the
>> source release is 100% following the ASF requirements.
>> 
> 
> I think I get your point. An important reason is the build script used on
> the custom builder page is not been checked and voted.
> I agree to remove this page. But there are still about 1.5k developers
> using this online tool everyday.
> We should take it carefully to guide these developers to build from source
> in local.

Let’s not be so quick to remove this service to ECharts users. Let’s think 
about how to make it compliant.

I’ve seen a message from a board member that they used this feature and thought 
it was cool.

Regards,
Dave

> 
> Thanks
> 
>> On Mon, Aug 3, 2020 at 4:28 PM Sheng Wu  wrote:
>> 
>> Yi Shen  于2020年8月3日周一 下午4:14写道：
>> 
>>> Hi, Sheng
>>> 
>>> The point is, you only vote for the source tar, which includes all
 contents, with an ASC and sha512 sign. So, only that is an official
>>> apache
 release.
 
>>> 
>>> I want to explain it a bit more. What we thought is bringing the local
>> CLI
>>> to the web.
>>> In which developers can
>>> 
>>> 1. Choose a version from the source tar list which have been voted.
>>> 2. Download the tar and check sha512 on the browser.
>>> 3. Unzip the tar and build the source into a single js file on the
>> browser.
>>> 4. Download the customized built js file.
>>> 
>>> I guess the main difference between this and the local CLI is all the
>>> processes are on the browser.
>>> Please remind us if we missed anything that may cause potential risks in
>>> it.
>>> 
>> 
>> From my side, this is not the difference. The download source package is
>> never been voted is my concern.
>> I know the logically, it is just a subset, but whether there is a change or
>> unexpected files in the final download, we don't know. And no one would
>> check.
>> The whole vote/check process is for manual confirmation about that, the
>> source release is 100% following the ASF requirements.
>> 
>> Sheng Wu 吴晟
>> Twitter, wusheng1108
>> 
>> 
>>> 
>>> Regards.
>>> 
>>> On Mon, Aug 3, 2020 at 3:03 PM Sheng Wu 
>> wrote:
>>> 
 Ovilia  于2020年8月3日周一 下午2:52写道：
 
> Thanks Sheng for the checking.
> 
> Here're my thoughts on these issues:
> 
> 1. I was referring to [1] when checking the navigator. I thought it
>>> meant
> if there's a
> "Sponsorship" link, it should link to xxx but I didn't realize it
>> means
 the
> link is
> mandatory. The following link should be added:
> Sponsorship, Thanks, Apache Software Foundation.
> 
> 
 Use this to check the potential issue.
 https://incubator.apache.org/clutch/echarts.html
 
 
> 2. Gallery is a place to host ECharts works from the community,
>>> something
> similar
> to jsfiddle or codepen. The server is currently hosted on a Baidu
>>> server
> and we don't
> have a current plan to donate it to ASF.
> How about removing the project from the navigator and list it
>> somewhere
 as
> a
> community resource?
> 
 
 Agree, should make it clear, that is a part of community/ecosystem. And
>>> not
 a part of ASF or Apache release. They just extend the Apache ECharts.
 
 
> 
> 3. Theme files are included in the source release [2] and the current
> download-theme page
> uses convenient binary files hosted on our server. Is this a problem?
> Extensions are mostly made by the community so they are links to
>>> related
> GitHub projects.
> I think we should put a more clear instruction on the
> download-extention page [3] that
> these projects are made by the community.
> 
 
 I just prefer to provide a clear statement and catalogs about links to
>>> 3rd
 party extensions, or Apache release.
 That includes, how and where to report the bug/security issue when
>> those
 extensions have issues.
 Also, where should hold their discussion, such as enhancement,
>> iteration.
 
 
> 
> 
> 4. The tools are currently under translation. We didn't put a "help
> translate" note because
> we have already found the people who wish to translate and it should
>> be
> done within a few
> weeks. Before then, the English Website will have a "(in Chinese)"
>> note
 in
> the navigator.
> 
 
 Good to know the progress. Could you check whether they could finish
>>> those
 before the graduation discussion in the incubator? I hope to ease other
 people's concern.
 
 
> 
> 5. The custom build is used to build 

Re: [DISCUSS] Watermark by default

[Dave Fisher]

+1, I agree with your conclusion.

Regards,
Dave

Sent from my iPhone

> On Jul 1, 2020, at 9:14 PM, Ovilia  wrote:
> 
> Thank you all for the discussion. I agree with most of them.
> Now I think we probably shouldn't provide watermarks.
> 
> Thanks
> 
> *Ovilia*
> 
> 
>> On Thu, Jul 2, 2020 at 11:54 AM SHUANG SU  wrote:
>> 
>> In my opinion, it is probably not a good idea to show a watermark by
>> default.
>> 
>> (1) Suppose a website has some content that is illegal in certain local
>> law, or has some controversial content, if we have the "Apache
>> ECharts" watermark on it by default, it probably brings trouble to that
>> brand and to our community. Even if the controversial content is outside
>> but just next to the chart, it also might make final users connect it to
>> the brand (depends on the style).
>> 
>> (2) It will bother the users. Users have to find a way to remove the
>> watermark, either for their own brand or for our brand.
>> And some users may be confused whether they "can" remove the watermark.
>> After all, brand is a sensitive issue, most of the developers and product
>> managers can not have enough knowledge about that. I am worried some users
>> may not intend to select an intrusive lib since there are many
>> other choices.
>> 
>> (3) A default watermark might affect the visual: it might overlap with some
>> text or graphic, even if it is opacity.
>> 
>> (4) Sometimes we can recognize some chart lib easily by some special
>> features and default colors. Compared to them, if echarts print "it is
>> echarts" literally, I am afraid it might bring an impression to users: it
>> is not "smart".
>> 
>> 
>> Thanks,
>> --
>> Su Shuang (100pah)
>> --
>> 
>> 
>> 
>>> On Thu, 2 Jul 2020 at 11:06, Sheng Wu  wrote:
>>> 
>>> Ovilia  于2020年7月2日周四 上午11:02写道：
>>> 
 The watermark itself is a way to make it easier for users to share that
 information.
 
 As for whether it is required to state using ECharts inside, could
>> Sheng
>>> Wu
 or other
 mentors help answer this question?
 
>>> 
>>> I think license says this,
>>> https://github.com/apache/skywalking/blob/master/LICENSE#L100
  (c) You must retain, in the Source form of any Derivative Works
>>>  that You distribute, all copyright, patent, trademark, and
>>>  attribution notices from the Source form of the Work,
>>>  excluding those notices that do not pertain to any part of
>>>  the Derivative Works; and
>>> 
>>> Apache 2.0 is business-friendly, it doesn't force the users to show this
>> on
>>> the product page.
>>> Is this triggered by the thing, Apache SkyWalking requesting BoCloud
>>> following Apache 2.0 License requirements?
>>> 
>>> Sheng Wu 吴晟
>>> Twitter, wusheng1108
>>> 
>>> 
 
 Thanks
 
 *Ovilia*
 
 
 On Thu, Jul 2, 2020 at 10:50 AM Clement Ho >> 
 wrote:
 
> I'm a little confused at the proposal. Is it to add a mandatory
> watermark/require users of ECharts to mention that they are using
>>> ECharts
> somewhere in their product or is it just making it easier for users
>> to
> share that they are using ECharts for their charting solution as an
> optional configuration?
> 
> On Wed, Jul 1, 2020 at 9:44 PM Ovilia  wrote:
> 
>> I'd like to propose adding a watermark stating something like
>> "Charts
>> provided using Apache
>> ECharts (incubating)" in ECharts 5.0 which is displayed as small
>> translucent text in the bottom
>> right corner and developers may have a way to opt out
>>> programmatically.
>> 
>> The reason behind this is letting more visitors to those charts
>> know
 that
>> they are made with
>> ECharts. We recognize that many developers may not make a
>> statement
 that
>> the product is
>> made with ECharts as the Apache license asks. Since we have so many
 users
>> (200,000 downloads
>> each week on npm), it's hard or almost impossible for us to find
>> and
> check
>> the violations.
>> 
>> So, we could use the watermark as a way to provide a simple method
>> to
> help
>> with the branding.
>> If some users prefer to opt out and maybe make a statement of using
> ECharts
>> elsewhere in their
>> product, they can do this easily with a simple option.
>> 
>> What do you think?
>> 
>> Thanks
>> 
>> *Ovilia*
>> 
> 
 
>>> 
>> 


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

Website with or without CDN

[Dave Fisher]

Hi -

In the last few months the Apache Infrastructure team has moved a huge amount 
of traffic away from www.apache.org to downloads.apache.org. In light of this I 
think it might be a good idea to get back to the long standing where the charts 
website is question.

Ideally it should be echarts.apache.org without needing a CDN. Is the issue 
more the very large video on the main page which then requires certain byte 
range support on the server plus dealing with the national firewalls, or is it 
the whole site. Can we find a compromise? Perhaps the video can be hosted in 
multiple places and have the page select which in JS depending on where the 
user is?

Just some thoughts.

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

Re: [STALE] [GitHub] [incubator-echarts] stale[bot] commented on issue #8056: series的pie类型

[Dave Fisher]

Hi Wenli,

OK, I understand. I have temporarily unsubscribed from commits@ yesterday as 
these emails were filling my mailbox.

There are quite a large number of stale issues. It's very boring work to go 
through all of these issues. Will this be a continual issue now or we these all 
triggered due to the repository migration when ECharts moved to the Apache 
Incubator?

Regards,
Dave

> On Apr 1, 2020, at 8:06 PM, Ovilia  wrote:
> 
> Hi Dave,
> 
> This is generated by the stale robot[1] which will add a comment to notice
> the user this issue will be closed soon for inactivity. It will be closed
> by the robot if no one comments within another week.
> 
> The config file can be found here [2].
> To be brief, it will set stale to issues that hasn't been active for more
> than 2 years and do not have "maybe-later" or "priority: high" labels on it.
> 
> Issues that haven't been active for two years are considered as stale
> because either the version they are using are too old to consider or
> authors are no longer concerning the problem. So by closing it
> automatically by a robot, we can keep focusing on the rest issues. But we
> do give a warning comment in case it should not be closed.
> 
> [1] https://github.com/marketplace/stale
> [2]
> https://github.com/apache/incubator-echarts/blob/master/.github/stale.yml
> 
> Thanks
> 
> Wenli
> 
> 
> On Thu, Apr 2, 2020 at 2:36 AM Dave Fisher  wrote:
> 
>> Hi -
>> 
>> Could someone please explain what process is happening with the stale[bot]?
>> 
>> Thanks,
>> Dave
>> 
>>> On Apr 1, 2020, at 11:23 AM, GitBox  wrote:
>>> 
>>> stale[bot] commented on issue #8056: series的pie类型
>>> URL:
>> https://github.com/apache/incubator-echarts/issues/8056#issuecomment-607415258
>>> 
>>> 
>>>  This issue has been automatically marked as stale because it has not
>> had recent activity. It will be closed if no further activity occurs. Thank
>> you for your contributions.
>>> 
>>> 
>>> 
>>> This is an automated message from the Apache Git Service.
>>> To respond to the message, please log on to GitHub and use the
>>> URL above to go to the specific comment.
>>> 
>>> For queries about this service, please contact Infrastructure at:
>>> us...@infra.apache.org
>>> 
>>> 
>>> With regards,
>>> Apache Git Services
>>> 
>>> -
>>> To unsubscribe, e-mail: commits-unsubscr...@echarts.apache.org
>>> For additional commands, e-mail: commits-h...@echarts.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
>> 


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

Re: [Blog] GitHub Star Breaking 40K, ECharts Is Now Working On The Next Big Release!

[Dave Fisher]

It would be good to discuss here on dev@ what will be in this next release and 
how the community can help get their favorite updates included!

Regards,
Dave

Sent from my iPhone

> On Apr 1, 2020, at 9:01 PM, Ovilia  wrote:
> 
> Hi all,
> 
> We've just posted a new blog on medium.
> 
> Check this out:
> *GitHub Star Breaking 40K, ECharts Is Now Working On The Next Big Release!*
> https://medium.com/@apache.echarts/github-star-breaking-40k-echarts-is-now-working-on-the-next-big-release-f36dd5e96eb4
> 
> You are welcomed to share it on your social networks.
> 
> Thanks
> 
> Wenli


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

[STALE] Re: [GitHub] [incubator-echarts] stale[bot] commented on issue #8056: series的pie类型

[Dave Fisher]

Hi -

Could someone please explain what process is happening with the stale[bot]?

Thanks,
Dave

> On Apr 1, 2020, at 11:23 AM, GitBox  wrote:
> 
> stale[bot] commented on issue #8056: series的pie类型
> URL: 
> https://github.com/apache/incubator-echarts/issues/8056#issuecomment-607415258
> 
> 
>   This issue has been automatically marked as stale because it has not had 
> recent activity. It will be closed if no further activity occurs. Thank you 
> for your contributions.
> 
> 
> 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
> 
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 
> 
> With regards,
> Apache Git Services
> 
> -
> To unsubscribe, e-mail: commits-unsubscr...@echarts.apache.org
> For additional commands, e-mail: commits-h...@echarts.apache.org
> 


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

Re: [Showcase] A tutorial to create COVID maps using ECharts

[Dave Fisher]

That’s very well done!

> On Mar 12, 2020, at 8:04 AM, siwen su  wrote:
> 
> Nice work +1
> 
> Yi Shen mailto:shenyi@gmail.com>> 于2020年3月12日周四 
> 下午10:57写道：
> Nice work!
> 
> On Thu, Mar 12, 2020 at 10:56 PM Ovilia  > wrote:
> Hi all,
> 
> I updated a video tutorial on creating COVID maps using ECharts and Leaflet. 
> Check it out at https://www.youtube.com/watch?v=YSE6NpXTJ1g 
>  .
> 
> <封面.png>
> 
> Wish you a good health. :)
> 
> Thanks
> 
> Wenli
> 
> 
> -- 
> Yi Shen  
> Apache ECharts(incubating) PPMC

Re: [DISCUSS] Update on the Website transferation

[Dave Fisher]

Sent from my iPhone

> On Mar 4, 2020, at 7:10 PM, Ovilia  wrote:
> 
> Thanks for the information, Dave.
> 
> How can we test the new CDN? Is there a notice Website for the information
> or could you share the IP with us please?

To be clear - please retest the two that have already been tried.

There were performance issues discovered recently with *.apache.org. These may 
have impacted your results.

If you have an offer for an Apache.org mirror in
China then please discuss on private@. That will take some efforts and there 
are no guarantees.

Regards,
Dave
> 
> Thanks
> 
> Wenli
> 
> 
>> On Thu, Mar 5, 2020 at 12:54 AM Dave Fisher  wrote:
>> 
>> Hi ECharts team,
>> 
>> Infrastructure has been making changes to the main Apache.com website to
>> separate out some of the downloading functionality due to stability issues.
>> These may have impacted your experience with the CDNs.
>> 
>> I think it would be good to perform another test of the two CDNs.
>> 
>> In addition we can discuss on private@ a mirror proposal which neither
>> Kevin nor I can approve. Such a proposal would need to be evaluated by the
>> Infrastructure and perhaps Fundraising teams.
>> 
>> Regards,
>> Dave
>> 
>>> On Mar 2, 2020, at 6:13 PM, Kevin A. McGrail 
>> wrote:
>>> 
>>> Hi Ovilia, What are the technical steps for the mirror you envision and
>> I can weigh in more?
>>> --
>>> Kevin A. McGrail
>>> Member, Apache Software Foundation
>>> Chair Emeritus Apache SpamAssassin Project
>>> https://www.linkedin.com/in/kmcgrail <
>> https://www.linkedin.com/in/kmcgrail> - 703.798.0171
>>> 
>>> 
>>> On Mon, Mar 2, 2020 at 2:35 AM Ovilia > oviliazh...@gmail.com>> wrote:
>>> Dear mentors,
>>> 
>>> What else can we do about this? What should we do if we wish to make the
>> mirror site happen?
>>> 
>>> Thanks
>>> 
>>> Wenli
>>> 
>>> 
>>> On Thu, Feb 20, 2020 at 7:29 PM SHUANG SU > <mailto:sushuang0...@gmail.com>> wrote:
>>> ---
>>> GroupA: (
>> https://echarts.apache.org/examples/data/thumb/sunburst-drink.jpg <
>> https://echarts.apache.org/examples/data/thumb/sunburst-drink.jpg>)
>>> 
>>> 
>>> ---
>>> GroupB: (
>> https://www.echartsjs.com/examples/data/thumb/sunburst-drink.jpg <
>> https://www.echartsjs.com/examples/data/thumb/sunburst-drink.jpg>)
>>> 
>>> 
>>> Each test case is repeat several times and the result are roughly
>> similar.
>>> It seams that in lots of place http://echarts.apache.org <
>> http://echarts.apache.org/> works, but sometimes it not stable to get the
>> result,
>>> and at some place and some time it can not be visited.
>>> 
>>> 
>>> Thanks,
>>> --
>>> Su Shuang (100pah)
>>> --
>>> 
>>> 
>>> 
>>> On Thu, 20 Feb 2020 at 19:22, SHUANG SU > sushuang0...@gmail.com>> wrote:
>>> Some of the rough test result is as follows:
>>> 
>>> GroupA: (
>> https://echarts.apache.org/en/documents/option-parts/option.json?1578303605813
>> <
>> https://echarts.apache.org/en/documents/option-parts/option.json?1578303605813
>>> )
>>> 
>>> 
>>> ---
>>> GroupB: (
>> https://www.echartsjs.com/en/documents/option-parts/option.json?1578303605813
>> <
>> https://www.echartsjs.com/en/documents/option-parts/option.json?1578303605813
>>> )
>>> 
>>> 
>>> 
>>> 
>>> Thanks,
>>> --
>>> Su Shuang (100pah)
>>> --
>>> 
>>> 
>>> 
>>> On Thu, 20 Feb 2020 at 19:20, SHUANG SU > sushuang0...@gmail.com>> wrote:
>>> Hi Dave,
>>> 
>>> Thanks to the CDN you provided. Since the CDN have been updated (see
>> https://issues.apache.org/jira/browse/INFRA-19436 <
>> https://issues.apache.org/jira/browse/INFRA-19436> ), the speed of the
>> website ( https://echarts.apache.org <https://echarts.apache.org/> )
>> improved a lot. With the help of browser cache, in my home (at Beijing), in
>> most cases the speed is not fast but acceptable, although some times it
>> occasionally slow and need retry several times or wait.
>>> 
>>> But recently I request some one others test the speed (from Shanghai,
>> Shenz

Re: [DISCUSS] Update on the Website transferation

[Dave Fisher]

Hi ECharts team,

Infrastructure has been making changes to the main Apache.com website to 
separate out some of the downloading functionality due to stability issues. 
These may have impacted your experience with the CDNs.

I think it would be good to perform another test of the two CDNs.

In addition we can discuss on private@ a mirror proposal which neither Kevin 
nor I can approve. Such a proposal would need to be evaluated by the 
Infrastructure and perhaps Fundraising teams.

Regards,
Dave

> On Mar 2, 2020, at 6:13 PM, Kevin A. McGrail  wrote:
> 
> Hi Ovilia, What are the technical steps for the mirror you envision and I can 
> weigh in more?  
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail <https://www.linkedin.com/in/kmcgrail> - 
> 703.798.0171
> 
> 
> On Mon, Mar 2, 2020 at 2:35 AM Ovilia  <mailto:oviliazh...@gmail.com>> wrote:
> Dear mentors,
> 
> What else can we do about this? What should we do if we wish to make the 
> mirror site happen?
> 
> Thanks
> 
> Wenli
> 
> 
> On Thu, Feb 20, 2020 at 7:29 PM SHUANG SU  <mailto:sushuang0...@gmail.com>> wrote:
> ---
> GroupA: (https://echarts.apache.org/examples/data/thumb/sunburst-drink.jpg 
> <https://echarts.apache.org/examples/data/thumb/sunburst-drink.jpg>)
> 
> 
> ---
> GroupB: (https://www.echartsjs.com/examples/data/thumb/sunburst-drink.jpg 
> <https://www.echartsjs.com/examples/data/thumb/sunburst-drink.jpg>)
> 
> 
> Each test case is repeat several times and the result are roughly similar.
> It seams that in lots of place http://echarts.apache.org 
> <http://echarts.apache.org/> works, but sometimes it not stable to get the 
> result,
> and at some place and some time it can not be visited.
> 
> 
> Thanks,
> --
>  Su Shuang (100pah)
> --
> 
> 
> 
> On Thu, 20 Feb 2020 at 19:22, SHUANG SU  <mailto:sushuang0...@gmail.com>> wrote:
> Some of the rough test result is as follows: 
> 
> GroupA: 
> (https://echarts.apache.org/en/documents/option-parts/option.json?1578303605813
>  
> <https://echarts.apache.org/en/documents/option-parts/option.json?1578303605813>)
> 
> 
> ---
> GroupB: 
> (https://www.echartsjs.com/en/documents/option-parts/option.json?1578303605813
>  
> <https://www.echartsjs.com/en/documents/option-parts/option.json?1578303605813>)
> 
> 
> 
> 
> Thanks,
> --
>  Su Shuang (100pah)
> --
> 
> 
> 
> On Thu, 20 Feb 2020 at 19:20, SHUANG SU  <mailto:sushuang0...@gmail.com>> wrote:
> Hi Dave, 
> 
> Thanks to the CDN you provided. Since the CDN have been updated (see 
> https://issues.apache.org/jira/browse/INFRA-19436 
> <https://issues.apache.org/jira/browse/INFRA-19436> ), the speed of the 
> website ( https://echarts.apache.org <https://echarts.apache.org/> ) improved 
> a lot. With the help of browser cache, in my home (at Beijing), in most cases 
> the speed is not fast but acceptable, although some times it occasionally 
> slow and need retry several times or wait.
> 
> But recently I request some one others test the speed (from Shanghai, 
> Shenzhen, Beijing). Some of them fed back that the speed is good, but some of 
> them say that it take 5~6s to load or even can not load anything (meanwhile 
> https://www.echartsjs.com <https://www.echartsjs.com/> works fine).
> 
> 
> Then I tried to use some website speed testing services to compare the speed.
> The services include: 
> https://www.boce.com/tool <https://www.boce.com/tool>
> http://tool.chinaz.com/speedtest <http://tool.chinaz.com/speedtest>
> https://www.17ce.com/ <https://www.17ce.com/>
> http://www.webkaka.com/webCheck.aspx 
> <http://www.webkaka.com/webCheck.aspx>
> The testing URL is:
> GroupA:
> 
> https://echarts.apache.org/en/documents/option-parts/option.json?1578303605813
>  
> <https://echarts.apache.org/en/documents/option-parts/option.json?1578303605813>
> https://echarts.apache.org/examples/data/thumb/sunburst-drink.jpg 
> <https://echarts.apache.org/examples/data/thumb/sunburst-drink.jpg>
> GroupB:
> 
> https://www.echartsjs.com/en/documents/option-parts/option.json?1578303605813 
> <https://www.echartsjs.com/en/documents/option-parts/option.json?1578303605813>
> https://www.echartsjs.com/examples/data/thumb/sunburst-drink.jpg 
> <https://www.echartsjs.com/examples/data/thumb/sunburst-drink.jpg>
> 
> Some of the test result a

Re: [DISCUSS] Update on the Website transferation

[Dave Fisher]

 
>> wrote:
>>>>>>> 
>>>>>>>> Hi York,
>>>>>>>> 
>>>>>>>> We are still testing the speed of the new CDN.
>>>>>>>> 
>>>>>>>> In the meantime, do you have any comparing numbers about the
>> speed
>>>>>> before
>>>>>>>> and after Weex using this CDN?
>>>>>>>> 
>>>>>>>> Thanks!
>>>>>>>> 
>>>>>>>> Wenli
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Thu, Oct 31, 2019 at 3:05 PM YorkShen 
>>> wrote:
>>>>>>>> 
>>>>>>>>> Just create a JIRA issue to INFRA, they will handle your
>>> request.
>>>>>>>>> 
>>>>>>>>> FYI: After you enable experimental CDN, you will need to wait
>>>>>> several
>>>>>>>> hours
>>>>>>>>> for China CDN cache refreshing each time you deploy the
>> website.
>>>>>> But if
>>>>>>>> you
>>>>>>>>> visit your website through a VPN hosted in USA/India, then
>>>>>> everything
>>>>>>>> takes
>>>>>>>>> effect immediately. I think this is a side effect of the
>>>>>> experimental
>>>>>>>> CDN.
>>>>>>>>> 
>>>>>>>>> Best Regards,
>>>>>>>>> YorkShen
>>>>>>>>> 
>>>>>>>>> 申远
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Ovilia  于2019年10月31日周四 下午2:33写道：
>>>>>>>>> 
>>>>>>>>>> Thanks, York. That's really helpful news to learn.
>>>>>>>>>> Can you give more information about this experimental CDN
>> and
>>>> how
>>>>>> we
>>>>>>>>> could
>>>>>>>>>> enable it?
>>>>>>>>>> 
>>>>>>>>>> Wenli
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> On Wed, Oct 30, 2019 at 8:49 PM York Shen >> 
>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> Hi, there
>>>>>>>>>>> 
>>>>>>>>>>> Just noticed you're bothering CDN problem from China. As a
>>>>>> committer
>>>>>>>> and
>>>>>>>>>>> PPMC member of Weex, I also suffered the problems months
>> ago,
>>>> but
>>>>>>>>> things go
>>>>>>>>>>> well after we enabl experimental CDN of Apache in China
>> [1].
>>> I
>>>>>> hope
>>>>>>>> this
>>>>>>>>>>> could also solve your problem.
>>>>>>>>>>> 
>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-18406
>>>>>>>>>>> 
>>>>>>>>>>> Best Regards,
>>>>>>>>>>> York Shen
>>>>>>>>>>> 
>>>>>>>>>>> 申远
>>>>>>>>>>> 
>>>>>>>>>>> On 2019/10/18 07:04:13, Ovilia 
>>> wrote:
>>>>>>>>>>>> In fact, it's possible to know the speed of different
>>>>>> countries.
>>>>>>>>>>>> 1. Open google analytics
>>>>>>>>>>>> 2. Behavior - Site speed - Page timings
>>>>>>>>>>>> 3. Set the secondary dimension to be Country
>>>>>>>>>>>> 
>>>>>>>>>>>> I'm not sure if it's appropriate to copy the data to the
>>> dev
>>>>>>> mailing
>>>>>>>>>>> list,
>>>>>>>>>>>> so I will skip the screenshot. :)
>>>>>>>>>>>> 
>>>>>>>>>>>> Wenli
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> O

Re: Podling Echarts Report Reminder - February 2020

[Dave Fisher]

Discuss then submit.

Sent from my iPhone

> On Jan 26, 2020, at 10:43 PM, Ovilia  wrote:
> 
> Thanks Dave.
> 
> Should we discuss on dev first and then submit or submit then discuss?
> 
> Thanks
> 
> Wenli
> 
> 
>> On Mon, Jan 27, 2020 at 2:25 PM Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> Please stay safe!
>> 
>> I’ll help once you are able to discuss the report on either dev or
>> private. I recommend having a few days on dev@.
>> 
>> Best Regards,
>> Dave
>> 
>>>> On Jan 26, 2020, at 10:13 PM, Ovilia  wrote:
>>> 
>>> Hi Justin,
>>> 
>>> Thanks for the reminder.
>>> Many of us are on Chinese New Year vocation. I shall submit the report
>>> before Feb 5th.
>>> 
>>> Thanks
>>> 
>>> Wenli
>>> 
>>> 
>>>> On Wed, Jan 22, 2020 at 12:38 PM  wrote:
>>> 
>>>> Dear podling,
>>>> 
>>>> This email was sent by an automated system on behalf of the Apache
>>>> Incubator PMC. It is an initial reminder to give you plenty of time to
>>>> prepare your quarterly board report.
>>>> 
>>>> The board meeting is scheduled for Wed, 19 February 2020, 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, February 05).
>>>> 
>>>> Please submit your report with sufficient time to allow the Incubator
>>>> PMC, and subsequently board members to review and digest. Again, the
>>>> very latest you should submit your report is 2 weeks prior to the board
>>>> meeting.
>>>> 
>>>> Candidate names should not be made public before people are actually
>>>> elected, so please do not include the names of potential committers or
>>>> PPMC members in your report.
>>>> 
>>>> Thanks,
>>>> 
>>>> The Apache Incubator PMC
>>>> 
>>>> Submitting your Report
>>>> 
>>>> --
>>>> 
>>>> Your report should contain the following:
>>>> 
>>>> *   Your project name
>>>> *   A brief description of your project, which assumes no knowledge of
>>>>   the project or necessarily of its field
>>>> *   A list of the three most important issues to address in the move
>>>>   towards graduation.
>>>> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>>>>   aware of
>>>> *   How has the community developed since the last report
>>>> *   How has the project developed since the last report.
>>>> *   How does the podling rate their own maturity.
>>>> 
>>>> This should be appended to the Incubator Wiki page at:
>>>> 
>>>> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020
>>>> 
>>>> Note: This is manually populated. You may need to wait a little before
>>>> this page is created from a template.
>>>> 
>>>> Note: The format of the report has changed to use markdown.
>>>> 
>>>> Mentors
>>>> ---
>>>> 
>>>> Mentors should review reports for their project(s) and sign them off on
>>>> the Incubator wiki page. Signing off reports shows that you are
>>>> following the project - projects that are not signed may raise alarms
>>>> for the Incubator PMC.
>>>> 
>>>> Incubator PMC
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>>>> For additional commands, e-mail: dev-h...@echarts.apache.org
>>>> 
>>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
>> 


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

Re: Podling Echarts Report Reminder - February 2020

[Dave Fisher]

Hi -

Please stay safe!

I’ll help once you are able to discuss the report on either dev or private. I 
recommend having a few days on dev@.

Best Regards,
Dave

> On Jan 26, 2020, at 10:13 PM, Ovilia  wrote:
> 
> Hi Justin,
> 
> Thanks for the reminder.
> Many of us are on Chinese New Year vocation. I shall submit the report
> before Feb 5th.
> 
> Thanks
> 
> Wenli
> 
> 
> On Wed, Jan 22, 2020 at 12:38 PM  wrote:
> 
>> Dear podling,
>> 
>> This email was sent by an automated system on behalf of the Apache
>> Incubator PMC. It is an initial reminder to give you plenty of time to
>> prepare your quarterly board report.
>> 
>> The board meeting is scheduled for Wed, 19 February 2020, 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, February 05).
>> 
>> Please submit your report with sufficient time to allow the Incubator
>> PMC, and subsequently board members to review and digest. Again, the
>> very latest you should submit your report is 2 weeks prior to the board
>> meeting.
>> 
>> Candidate names should not be made public before people are actually
>> elected, so please do not include the names of potential committers or
>> PPMC members in your report.
>> 
>> Thanks,
>> 
>> The Apache Incubator PMC
>> 
>> Submitting your Report
>> 
>> --
>> 
>> Your report should contain the following:
>> 
>> *   Your project name
>> *   A brief description of your project, which assumes no knowledge of
>>the project or necessarily of its field
>> *   A list of the three most important issues to address in the move
>>towards graduation.
>> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>>aware of
>> *   How has the community developed since the last report
>> *   How has the project developed since the last report.
>> *   How does the podling rate their own maturity.
>> 
>> This should be appended to the Incubator Wiki page at:
>> 
>> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020
>> 
>> Note: This is manually populated. You may need to wait a little before
>> this page is created from a template.
>> 
>> Note: The format of the report has changed to use markdown.
>> 
>> Mentors
>> ---
>> 
>> Mentors should review reports for their project(s) and sign them off on
>> the Incubator wiki page. Signing off reports shows that you are
>> following the project - projects that are not signed may raise alarms
>> for the Incubator PMC.
>> 
>> Incubator PMC
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
>> 


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

Re: [INFO] First meetup of Apache ECharts (incubating) in Shanghai

[Dave Fisher]

Excellent!

Are any other meetups planned?

Best Regards,
Dave

> On Dec 8, 2019, at 9:32 PM, Ovilia  wrote:
> 
> We held the first ECharts Meetup yesterday and it turned out great.
> 
> 
> 
> About 100 people from the community joined us in Shanghai. 
> 
> 
> 
> Four of our committers shared both technical topics and community-building 
> issues.
> Three speakers from the community also shared their own experiences with the 
> project.
> 
> 
> 
> We had a great time together and it's a nice opportunity to get to know our 
> users and introduce to them how to make our community better. 
> 
> Thanks
> 
> Wenli
> 
> 
> On Fri, Nov 29, 2019 at 11:17 AM Ovilia  > wrote:
> Hi! 
> We are going to hold our first offline event in Shanghai, China on Dec 7th, 
> 2019.
> 
> Agenda:
> Yi Shen: Technical history of ECharts
> Wenli Zhang: How to become a committer
> Shuang Su: Source code under the hood
> Feng Yu: From a user to a committer
> Lightning talks (TBD)
> Discussion
> 
> Apart from the speakers, Junting Wang spent great effort and made fabulous 
> posters for the event.
> 
> 
> It's really exciting to see the users face to face and know what they need 
> most.
> Hope we can hold more events in the future and looking forward to seeing you 
> guys.
> 
> To apply or see more details: (in Chinese)
> https://www.huodongxing.com/event/8520568966400 
> 
> 
> Thanks
> 
> Wenli

Re: [DISCUSS] Update on the Website transferation

[Dave Fisher]

> On Nov 13, 2019, at 12:33 PM, SHUANG SU  wrote:
> 
> Hi Dave,
> 
>> 13.107.246.10 echarts.apache.org <http://echarts.apache.org/>
> 
> I have been testing this CDN for a while in the network of my working place
> and home in Beijing.
> It seams faster then the current CDN. The speed is not unacceptable in the
> most place but
> somewhere and sometime there are little slow cases.
> 
> Shall we change our current CDN to this new CDN above? It probably provide
> better speed.
> And I can also test it in different place around China via some services.

Yes. Please open a JIRA issue in INFRA with a reference to this email thread.

Regards,
Dave

> 
> 
> Thanks,
> --
> Su Shuang (100pah)
> --
> 
> 
> 
> On Wed, 6 Nov 2019 at 14:14, Ovilia  wrote:
> 
>> Hi York,
>> 
>> We are still testing the speed of the new CDN.
>> 
>> In the meantime, do you have any comparing numbers about the speed before
>> and after Weex using this CDN?
>> 
>> Thanks!
>> 
>> Wenli
>> 
>> 
>> On Thu, Oct 31, 2019 at 3:05 PM YorkShen  wrote:
>> 
>>> Just create a JIRA issue to INFRA, they will handle your request.
>>> 
>>> FYI: After you enable experimental CDN, you will need to wait several
>> hours
>>> for China CDN cache refreshing each time you deploy the website. But if
>> you
>>> visit your website through a VPN hosted in USA/India, then everything
>> takes
>>> effect immediately. I think this is a side effect of the experimental
>> CDN.
>>> 
>>> Best Regards,
>>> YorkShen
>>> 
>>> 申远
>>> 
>>> 
>>> Ovilia  于2019年10月31日周四 下午2:33写道：
>>> 
>>>> Thanks, York. That's really helpful news to learn.
>>>> Can you give more information about this experimental CDN and how we
>>> could
>>>> enable it?
>>>> 
>>>> Wenli
>>>> 
>>>> 
>>>> On Wed, Oct 30, 2019 at 8:49 PM York Shen  wrote:
>>>> 
>>>>> Hi, there
>>>>> 
>>>>> Just noticed you're bothering CDN problem from China. As a committer
>> and
>>>>> PPMC member of Weex, I also suffered the problems months ago, but
>>> things go
>>>>> well after we enabl experimental CDN of Apache in China [1]. I hope
>> this
>>>>> could also solve your problem.
>>>>> 
>>>>> [1] https://issues.apache.org/jira/browse/INFRA-18406
>>>>> 
>>>>> Best Regards,
>>>>> York Shen
>>>>> 
>>>>> 申远
>>>>> 
>>>>> On 2019/10/18 07:04:13, Ovilia  wrote:
>>>>>> In fact, it's possible to know the speed of different countries.
>>>>>> 1. Open google analytics
>>>>>> 2. Behavior - Site speed - Page timings
>>>>>> 3. Set the secondary dimension to be Country
>>>>>> 
>>>>>> I'm not sure if it's appropriate to copy the data to the dev mailing
>>>>> list,
>>>>>> so I will skip the screenshot. :)
>>>>>> 
>>>>>> Wenli
>>>>>> 
>>>>>> 
>>>>>> On Fri, Oct 18, 2019 at 11:15 AM Yi Shen 
>>> wrote:
>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> In my perspective, analytics can tell us traffic on each document
>>>>> page.
>>>>>>> Which makes it easier for us to discuss the breaking changes.
>>>>>>> 
>>>>>>> Also, I think it's important to know the website speed in
>> different
>>>>> regions
>>>>>>> and different networks. But it seems currently our analytics can't
>>> do
>>>>> this
>>>>>>> kind of thing.
>>>>>>> 
>>>>>>> Thanks
>>>>>>> 
>>>>>>> On Thu, Oct 17, 2019 at 12:01 PM Ovilia 
>>>>> wrote:
>>>>>>> 
>>>>>>>> Thanks Dave.
>>>>>>>> 
>>>>>>>> I've shared the analytics accounts in private maillist on 13th
>>>>> June. [1]
>>>>>>>>> You should have received invitations emails from Google
>>> Analytics
>>>>> and
>>>>>>>> Baidu Tongji. Since Google A

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

[Dave Fisher]

+1 (binding)

Checked signatures and checksum
Incubating in name
DISCLAIMER checked
LICENSE checked
NOTICE checked
Builds with NPM
RAT check passes.

Regards,
Dave

> On Nov 8, 2019, at 4:22 AM, SHUANG SU  wrote:
> 
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.5.0 (release candidate 2).
> 
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.5.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=0ebdeaf4
> 
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.5.0-rc.2/RELEASE_NOTE.txt
> 
> Build Guide:
> https://github.com/apache/incubator-echarts/blob/4.5.0-rc.2/README.md#build
> 
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.5.0 (release candidate 2)
> by "2019-11-11T13:21:31.230Z".
> 
> [ ] +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.
> 
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 
> Thanks,
> --
> Su Shuang (100pah)
> --


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

Re: [VOTE] Release Apache ECharts (incubating) 4.5.0 (release candidate 1)

[Dave Fisher]

I found a README.md

It had this:

=
== File: ./README.md
=
# ECharts

http://echarts.baidu.com;>



That href needs to be changed.

Regards,
Dave

> On Nov 7, 2019, at 11:12 PM, SHUANG SU  wrote:
> 
> This vote is closed for the README.md issue.
> 
> A rc.2 will be created soon.
> 
> Thanks,
> --
> Su Shuang (100pah)
> --
> 
> 
> 
> On Fri, 8 Nov 2019 at 10:35, Yi Shen  wrote:
> 
>> Hi Shuang,
>> 
>> It seems README.md is still missing in this source release.
>> 
>> On Fri, Nov 8, 2019 at 1:43 AM SHUANG SU  wrote:
>> 
>>> I am pleased to be calling this vote for the release of Apache ECharts
>>> (incubating) 4.5.0 (release candidate 1).
>>> 
>>> The release candidate to be voted over is available at:
>>> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.5.0-rc.1/
>>> 
>>> 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=a2e3de13
>>> 
>>> The Release Note is available in:
>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.5.0-rc.1/RELEASE_NOTE.txt
>>> 
>>> Build Guide:
>>> 
>> https://github.com/apache/incubator-echarts/blob/4.5.0-rc.1/README.md#build
>>> 
>>> Please vote on releasing this package as:
>>> Apache ECharts (incubating) 4.5.0 (release candidate 1)
>>> by "2019-11-10T18:39:56.900Z".
>>> 
>>> [ ] +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.
>>> 
>>> A checklist for reference:
>>> 
>>> 
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>>> 
>>> Thanks,
>>> --
>>> Su Shuang (100pah)
>>> --
>>> 
>> 
>> 
>> --
>> Yi Shen
>> Apache ECharts(incubating) PPMC
>> 


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

Re: [DISCUSS] Update on the Website transferation

[Dave Fisher]

Hi Wenli,

This may be the same VPN IP address I gave you a few weeks ago. Did you test 
that?

Put this in your hosts file:
13.107.246.10 echarts.apache.org <http://echarts.apache.org/>

Regards,
Dave

> On Oct 31, 2019, at 2:33 PM, Ovilia  wrote:
> 
> Thanks, York. That's really helpful news to learn.
> Can you give more information about this experimental CDN and how we could
> enable it?
> 
> Wenli
> 
> 
> On Wed, Oct 30, 2019 at 8:49 PM York Shen  wrote:
> 
>> Hi, there
>> 
>> Just noticed you're bothering CDN problem from China. As a committer and
>> PPMC member of Weex, I also suffered the problems months ago, but things go
>> well after we enabl experimental CDN of Apache in China [1]. I hope this
>> could also solve your problem.
>> 
>> [1] https://issues.apache.org/jira/browse/INFRA-18406
>> 
>> Best Regards,
>> York Shen
>> 
>> 申远
>> 
>> On 2019/10/18 07:04:13, Ovilia  wrote:
>>> In fact, it's possible to know the speed of different countries.
>>> 1. Open google analytics
>>> 2. Behavior - Site speed - Page timings
>>> 3. Set the secondary dimension to be Country
>>> 
>>> I'm not sure if it's appropriate to copy the data to the dev mailing
>> list,
>>> so I will skip the screenshot. :)
>>> 
>>> Wenli
>>> 
>>> 
>>> On Fri, Oct 18, 2019 at 11:15 AM Yi Shen  wrote:
>>> 
>>>> Hi,
>>>> 
>>>> In my perspective, analytics can tell us traffic on each document page.
>>>> Which makes it easier for us to discuss the breaking changes.
>>>> 
>>>> Also, I think it's important to know the website speed in different
>> regions
>>>> and different networks. But it seems currently our analytics can't do
>> this
>>>> kind of thing.
>>>> 
>>>> Thanks
>>>> 
>>>> On Thu, Oct 17, 2019 at 12:01 PM Ovilia  wrote:
>>>> 
>>>>> Thanks Dave.
>>>>> 
>>>>> I've shared the analytics accounts in private maillist on 13th June.
>> [1]
>>>>>> You should have received invitations emails from Google Analytics
>> and
>>>>> Baidu Tongji. Since Google Analytics supports only gmail for email,
>> so
>>>>> those who don't
>>>>> have gmail in the following list [2], please tell me your gmail
>> account
>>>> so
>>>>> that I can invite you to our Google Analytics account.
>>>>> 
>>>>> If you need any help to access either of them, please let me know.
>>>>> 
>>>>> And yes, we should discuss more about how can we use this data to
>> help
>>>> make
>>>>> decisions in the following emails.
>>>>> 
>>>>> [1]
>>>>> 
>>>>> 
>>>> 
>> https://lists.apache.org/thread.html/a75cac8aa0a979146800a3688eccc95740c2fb53050689fcd198dfae@%3Cprivate.echarts.apache.org%3E
>>>>> 
>>>>> Wenli
>>>>> 
>>>>> 
>>>>> On Wed, Oct 16, 2019 at 10:34 PM Dave Fisher 
>> wrote:
>>>>> 
>>>>>> Hi Wenli,
>>>>>> 
>>>>>> I understand that these are analytics JS and Graphics files. I
>> would
>>>> like
>>>>>> to see the analytics data and how those analytics are used to make
>>>>>> decisions. I’d like to see that discussion occur on this mailing
>> list.
>>>>>> 
>>>>>> The community deserves to understand how the project's resources
>> are
>>>>>> monitored.
>>>>>> 
>>>>>> Regards,
>>>>>> Dave
>>>>>> 
>>>>>>> On Oct 15, 2019, at 10:49 PM, Ovilia 
>> wrote:
>>>>>>> 
>>>>>>> Hi Dave,
>>>>>>> 
>>>>>>> Thanks for the information about AzureCDN. I will have a try.
>>>>>>> 
>>>>>>> As about hm.js, this is the analytics file for Baidu Tongji,
>> similar
>>>> to
>>>>>>> Google Analytics.
>>>>>>> In previous discussions, we agreed to use both Baidu Tongji and
>>>> Google
>>>>>>> Analytics. In practice, we found that Baidu Tongji misses the
>>>> analytics
>>>>>> of
>>>>>>> 15% of page views outside of China, while Google Analyti

Re: [DISCUSS] Update on the Website transferation

[Dave Fisher]

Hi Wenli,

I understand that these are analytics JS and Graphics files. I would like to 
see the analytics data and how those analytics are used to make decisions. I’d 
like to see that discussion occur on this mailing list.

The community deserves to understand how the project's resources are monitored.

Regards,
Dave

> On Oct 15, 2019, at 10:49 PM, Ovilia  wrote:
> 
> Hi Dave,
> 
> Thanks for the information about AzureCDN. I will have a try.
> 
> As about hm.js, this is the analytics file for Baidu Tongji, similar to
> Google Analytics.
> In previous discussions, we agreed to use both Baidu Tongji and Google
> Analytics. In practice, we found that Baidu Tongji misses the analytics of
> 15% of page views outside of China, while Google Analytics misses 50% of
> page views from China.
> So I think it makes sense to use both Baidu Tongji and Google Analytics.
> 
> The hm.js is slow outside of China, just like analytics.js of Google
> Analytics is slow (or sometimes inaccessible) in China. But neither of
> these files should block the Web page rendering. So I think may not be a
> big issue.
> 
> Wenli
> 
> 
> On Wed, Oct 16, 2019 at 12:56 AM Dave Fisher  wrote:
> 
>> Hi -
>> 
>> No point in reopening the JIRA and no point in creating a new JIRA at this
>> time.
>> 
>> The slowness from the US side involves the hm.js and hm.gif which are
>> hosted by Baidu. These are the user statistics from Baidu. I would like to
>> see a discussion about how these are used on the dev@ mailing list,
>> 
>> There is an AzureCDN that can be tried:
>> 
>> Put the following in your /etc/hosts (or equivalent)
>> 
>> 13.107.246.10 echarts.apache.org <
>> https://slack-redir.net/link?url=http%3A%2F%2Fecharts.apache.org>
>> 
>> Let us know if it works better. If it does then we can ask INFRA to switch
>> CDNs.
>> 
>> Regards,
>> Dave
>> 
>> 
>>> On Oct 13, 2019, at 9:49 PM, Ovilia  wrote:
>>> 
>>> The JIRA ticket hasn't been replied by the infra for a month, probably
>>> because it's been closed.
>> https://issues.apache.org/jira/browse/INFRA-18919
>>> Should I open a new one, because I cannot re-open it?
>>> 
>>> Wenli
>>> 
>>> 
>>> On Fri, Sep 6, 2019 at 7:52 AM Kevin A. McGrail 
>> wrote:
>>> 
>>>> Done.
>>>> 
>>>> On 9/5/2019 6:31 AM, Ovilia wrote:
>>>>> Hi Kevin,
>>>>> 
>>>>> Could you please copy your last email to the JIRA [1] and continue our
>>>>> discussion there?
>>>>> It's quite inconvenient to have the conversation both on JIRA and with
>>>>> email.
>>>>> Thanks!
>>>>> 
>>>>> [1] https://issues.apache.org/jira/browse/INFRA-18919
>>>>> 
>>>>> Wenli
>>>>> 
>>>>> 
>>>>> On Thu, Sep 5, 2019 at 4:58 PM Kevin A. McGrail 
>>>> wrote:
>>>>> 
>>>>>> On 9/4/2019 11:31 PM, Ovilia wrote:
>>>>>>> Thanks, Kevin.
>>>>>>> 
>>>>>>> I've updated this information on JIRA [1].
>>>>>>> 
>>>>>>> As for the cost issue, we have a budget to cover it from Baidu but
>> need
>>>>>>> further discussion on the details if we decide to take this approach.
>>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-18919
>>>>>>> Wenli
>>>>>> So the goals I see are:
>>>>>> 
>>>>>> A) get the site up on echarts.apache.org running on ASF
>> Infrastructure
>>>>>> is goal #1
>>>>>> 
>>>>>> B) see if we can make it faster with ASF InfraStructure and a CDN to
>>>>>> avoid step C but realizing that step C is likely necessary...
>>>>>> 
>>>>>> C) provide a Chinese mirror of the echarts website that makes things
>>>>>> more usable for people from China.  For me, I thought about all our
>>>>>> policies and Apache Way.  I believe done with these steps laid out, it
>>>>>> is fine and within the jurisdiction of the project to decide:
>>>>>> 
>>>>>> - a 100% mirror of the ASF site, nothing different, that runs on a
>>>>>> subdomain such as zh.echarts.apache.org and automatically is synced
>>>> from
>

Re: [DISCUSS] Update on the Website transferation

[Dave Fisher]

Hi -

No point in reopening the JIRA and no point in creating a new JIRA at this time.

The slowness from the US side involves the hm.js and hm.gif which are hosted by 
Baidu. These are the user statistics from Baidu. I would like to see a 
discussion about how these are used on the dev@ mailing list,

There is an AzureCDN that can be tried:

Put the following in your /etc/hosts (or equivalent)

13.107.246.10 echarts.apache.org 


Let us know if it works better. If it does then we can ask INFRA to switch CDNs.

Regards,
Dave


> On Oct 13, 2019, at 9:49 PM, Ovilia  wrote:
> 
> The JIRA ticket hasn't been replied by the infra for a month, probably
> because it's been closed. https://issues.apache.org/jira/browse/INFRA-18919
> Should I open a new one, because I cannot re-open it?
> 
> Wenli
> 
> 
> On Fri, Sep 6, 2019 at 7:52 AM Kevin A. McGrail  wrote:
> 
>> Done.
>> 
>> On 9/5/2019 6:31 AM, Ovilia wrote:
>>> Hi Kevin,
>>> 
>>> Could you please copy your last email to the JIRA [1] and continue our
>>> discussion there?
>>> It's quite inconvenient to have the conversation both on JIRA and with
>>> email.
>>> Thanks!
>>> 
>>> [1] https://issues.apache.org/jira/browse/INFRA-18919
>>> 
>>> Wenli
>>> 
>>> 
>>> On Thu, Sep 5, 2019 at 4:58 PM Kevin A. McGrail 
>> wrote:
>>> 
 On 9/4/2019 11:31 PM, Ovilia wrote:
> Thanks, Kevin.
> 
> I've updated this information on JIRA [1].
> 
> As for the cost issue, we have a budget to cover it from Baidu but need
> further discussion on the details if we decide to take this approach.
> [1] https://issues.apache.org/jira/browse/INFRA-18919
> Wenli
 So the goals I see are:
 
 A) get the site up on echarts.apache.org running on ASF Infrastructure
 is goal #1
 
 B) see if we can make it faster with ASF InfraStructure and a CDN to
 avoid step C but realizing that step C is likely necessary...
 
 C) provide a Chinese mirror of the echarts website that makes things
 more usable for people from China.  For me, I thought about all our
 policies and Apache Way.  I believe done with these steps laid out, it
 is fine and within the jurisdiction of the project to decide:
 
 - a 100% mirror of the ASF site, nothing different, that runs on a
 subdomain such as zh.echarts.apache.org and automatically is synced
>> from
 the echarts.apache.org server.
 
 - A banner or something on echarts.apache.org/zh that recommends/links
 using zh.echarts.apache.org/zh for faster speed if they have issues.
 
 - Release downloads still link to ASF Infrastructure, e.g.,
 
 
>> https://www.apache.org/dist/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating-src.zip.asc
 .
 Question: are downloads problematically slow or they are just a few
 seconds slow and people don't complain about it because it's a download
 more than an interactive website?
 
 - Baidu donates the hostingso there are no financial impacts to the ASF
 
 - If any recognition of the donation is given, we make sure to follow
 fundraising targeted sponsorship policy (see
 https://www.apache.org/foundation/docs/Targeted-Sponsorship-Policy.pdf)
 which basically means it has to be approved.
 
 - And of course, the project PPMC votes to do this
 
 Hope this helps,
 
 KAM
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
 For additional commands, e-mail: dev-h...@echarts.apache.org
 
 
>> --
>> Kevin A. McGrail
>> kmcgr...@apache.org
>> 
>> Member, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
>> 

Re: [VOTE] Release Apache ECharts (incubating) 4.4.0 (release candidate 1)

[Dave Fisher]

Hi -

> On Oct 1, 2019, at 12:44 AM, Yi Shen  wrote:
> 
> Hi Dave,
> 
> 1) We have build instructions in the README
> https://github.com/apache/incubator-echarts/blob/master/README.md#build
> But I checked the source release again and surprisingly found the README is
> not in it.
> 
> Shuang, I think we should include the README in the next release, or we can
> have an individual doc about how to build.

Thanks. That really helps!

> 
> 2) Some information in the doc
> https://echarts.apache.org/en/tutorial.html#Get%20Started%20with%20ECharts%20in%205%20minutes
> is
> outdated.
> We will update it ASAP. Thanks for the reminding.

Do you have an issue for this that can be tracked?

> 
> 3) About https://echarts.baidu.com/dist/echarts.min.js  . We will remove
> this file since echarts.baidu.com will be not available.
> But I'm not sure how should we deal with the distribution files on the CDN
> like cloudflare or jsdelivr

Have you tried the apache distribution network to see how fast it is from some 
of the slow parts of the internet.

See how fast one of the releases downloads when you click on from either
http://incubator.apache.org/clutch/echarts.html#releases
Or
https://echarts.apache.org/en/download.html - choose the “Source"


> 
> 4) We will open a JIRA ticket to ask about the GitHub release tag.

Actually the question was asked, but not really answered in a way that allows 
easy guidance.

https://issues.apache.org/jira/browse/LEGAL-438

I’m going to work on that was I have another polling that also needs this 
guidance and what is happening now is “reasonable”.

Best Regards,
Dave

> Best regards.
> 
> On Tue, Oct 1, 2019 at 2:38 AM Dave Fisher  wrote:
> 
>> +1 (binding) - I have conditions listed below.
>> 
>> Checked:
>> Incubating in name
>> Detached signature and checksum
>> NOTICE
>> LICENSE including license-D3
>> DISCLAIMER
>> No unexpected binaries
>> RAT check
>> 
>> (1) The English instructions are not clear on how to build. There are
>> options on
>> 
>> https://echarts.apache.org/en/tutorial.html#Get%20Started%20with%20ECharts%20in%205%20minutes
>> But the links there are not proper -
>> (a) https://ecomfe.github.io/echarts-doc/public/en/download.html is a 404
>> - it should point to the download page.
>> (b) https://echarts.baidu.com/dist/echarts.min.js - this is not a proper
>> Apache Release artifact
>> (c) https://github.com/apache/incubator-echarts/releases - this is not a
>> proper location for Apache Releases until permission is requested and
>> received from Apache Legal - we’ll need to start a LEGAL JIRA asking if
>> these can be accepted. It may not happen since I don’t think the GitHub
>> release tags are immutable.
>> (d)
>> https://ecomfe.github.io/echarts-doc/public/en/tutorial.html#Use%20ECharts%20with%20webpack
>> is a 404. This should be on the Apache ECharts website.
>> 
>> (2) On this page:
>> https://echarts.apache.org/en/tutorial.html#Create%20Custom%20Build%20of%20ECharts
>> (a) the download page link is a 404.
>> (b) I don’t know enough to follow the further instructions. There are
>> options and I don’t which to pick.
>> 
>> (3) The download page has guides the user into (1) above.
>> 
>> I think that there are three action items:
>> (A) Fixing the links on en/tutorial.html along with improving the text.
>> (B) Create a LEGAL JIRA to make sure that the use of the Github.com
>> release tag meets requirements.
>> (C) Provide a prescriptive build instruction that allows new people and
>> your mentors better knowledge on how to build.
>> 
>> After this release is approved we can discuss how to use
>> archive.apache.org for the older releases on the Download page.
>> 
>> Regards,
>> Dave
>> 
>>> On Sep 30, 2019, at 5:19 AM, SHUANG SU  wrote:
>>> 
>>> I am pleased to be calling this vote for the release of Apache ECharts
>>> (incubating) 4.4.0 (release candidate 1).
>>> 
>>> The release candidate to be voted over is available at:
>>> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.4.0-rc.1/
>>> 
>>> 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=b2b38d67
>>> 
>>> The Release Note is available in:
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.4.0-rc.1/RELEASE_NOTE.txt
>>> 
>>> Some s

Re: [VOTE] Release Apache ECharts (incubating) 4.4.0 (release candidate 1)

[Dave Fisher]

+1 (binding) - I have conditions listed below.

Checked:
Incubating in name
Detached signature and checksum
NOTICE
LICENSE including license-D3
DISCLAIMER
No unexpected binaries
RAT check

(1) The English instructions are not clear on how to build. There are options on
https://echarts.apache.org/en/tutorial.html#Get%20Started%20with%20ECharts%20in%205%20minutes
But the links there are not proper -
(a) https://ecomfe.github.io/echarts-doc/public/en/download.html is a 404 - it 
should point to the download page.
(b) https://echarts.baidu.com/dist/echarts.min.js - this is not a proper Apache 
Release artifact
(c) https://github.com/apache/incubator-echarts/releases - this is not a proper 
location for Apache Releases until permission is requested and received from 
Apache Legal - we’ll need to start a LEGAL JIRA asking if these can be 
accepted. It may not happen since I don’t think the GitHub release tags are 
immutable.
(d) 
https://ecomfe.github.io/echarts-doc/public/en/tutorial.html#Use%20ECharts%20with%20webpack
 is a 404. This should be on the Apache ECharts website.

(2) On this page: 
https://echarts.apache.org/en/tutorial.html#Create%20Custom%20Build%20of%20ECharts
(a) the download page link is a 404.
(b) I don’t know enough to follow the further instructions. There are options 
and I don’t which to pick.

(3) The download page has guides the user into (1) above.

I think that there are three action items:
(A) Fixing the links on en/tutorial.html along with improving the text.
(B) Create a LEGAL JIRA to make sure that the use of the Github.com release tag 
meets requirements.
(C) Provide a prescriptive build instruction that allows new people and your 
mentors better knowledge on how to build.

After this release is approved we can discuss how to use archive.apache.org for 
the older releases on the Download page.

Regards,
Dave

> On Sep 30, 2019, at 5:19 AM, SHUANG SU  wrote:
> 
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.4.0 (release candidate 1).
> 
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.4.0-rc.1/
> 
> 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=b2b38d67
> 
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.4.0-rc.1/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.4.0-rc.1/apache-echarts-4.4.0-rc.1-incubating-src.zip
> -o apache-echarts-4.4.0-rc.1-incubating-src.zip
> unzip apache-echarts-4.4.0-rc.1-incubating-src.zip -d
> apache-echarts-4.4.0-rc.1-incubating-src > /dev/null
> 
> # Download and check the signatures (optional):
> curl
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.4.0-rc.1/apache-echarts-4.4.0-rc.1-incubating-src.zip.asc
> -o apache-echarts-4.4.0-rc.1-incubating-src.zip.asc
> curl
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.4.0-rc.1/apache-echarts-4.4.0-rc.1-incubating-src.zip.sha512
> -o apache-echarts-4.4.0-rc.1-incubating-src.zip.sha512
> # check asc
> gpg --verify apache-echarts-4.4.0-rc.1-incubating-src.zip.asc
> # check sha512
> shasum -a 512 -c apache-echarts-4.4.0-rc.1-incubating-src.zip.sha512
> 
> # Build the project (Node.js environment is required):
> cd "apache-echarts-4.4.0-rc.1-incubating-src" && npm install
> npm run release
> # (See help: `node "build/build.js" --help`)
> ```
> 
> 
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.4.0 (release candidate 1)
> by "2019-10-03T10:14:50.226Z".
> 
> [ ] +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.
> 
> A checklist for reference:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 
> 
> Thanks,
> --
> Su Shuang (100pah)
> --


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

Re: Speech video uploaded to YouTube

[Dave Fisher]

Hi Wenli,

This was an excellent talk! I especially enjoyed the after talk discussion with 
the gentlemen from Bloomberg. If you would share the contact information 
privately I would appreciate it.

Thanks,
Dave

> On Sep 22, 2019, at 8:39 AM, Ovilia  wrote:
> 
> Hi.
> I've updated my speech at the #ACNA19 with the topic of Web-based big data
> visualization topic to YouTube.
> Please check out https://youtu.be/oVo2qvBZsws and follow my channel if you
> are interested in it. :)
> 
> I hope to do more sharings on my YouTube channel to do the branding for
> ECharts.
> So if you're on YouTube, it would offer great help if you could give some
> comments or likes to help promote it.
> 
> Thanks!
> 
> Wenli


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

Re: 回复：Re: Happy Mid-Autumn Festival！

[Dave Fisher]

Hi - it was good to share Apache anniversary cake  last week! Enjoy the season!

All the best to the ECharts community ...

Regards,
Dave

Sent from my iPhone

> On Sep 16, 2019, at 4:44 AM, Liu Ted  wrote:
> 
> Ahah, How thougtful! It's a pity that we couldn't meet you in Las Vegas.
> 
> Best regards,
> 
> Ted Liu, 
> 
> 
> 
>  2019 年 9 月 16 日周一 19:27，Kevin A. McGrail 写道：   Someone 
> eat a moon cake for me!  I will have to settle for a moon pie
> 
> https://www.walmart.com/ip/Moon-Pie-Double-Decker-Chocolate-Marshmallow-Sandwich-2-75-Oz-12-Count/46161619
> 
> Best, KAM
> 
> 
>> On Mon, Sep 16, 2019, 02:03 Tan,Zhongyi  wrote:
>> 
>> The same to all
>> 
>> 在 2019/9/14 下午3:40，“Zu Ming” 写入:
>> 
>> ：）
>> 
>> 
>> 
>> 


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

Re: The resources size of ECharts homepage is too big

[Dave Fisher]

Hi Shuang Su,

Infra has enabled image types. Please try to send the image again!

Regards,
Dave

> On Aug 26, 2019, at 12:39 PM, SHUANG SU  wrote:
> 
> Oh, I am using Gmail.
> When I intend to send a picture, I just click "insert a photo" or attach
> files in Gmail,
> and upload the local picture in the popup dialog, and then click "send".
> 
> I can see the uploaded picture in the sent email, but other guys can not.
> The URL of the uploaded picture is, for example:
> 
> https://mail.google.com/mail/u/0?ui=2=ee82337e02=0.1=msg-a:r8125283079584617083=16cce14bd0272b78=fimg=s0-l75-ft=ANGjdJ-1A2fKfFx5FEpWWzi2oaMqVHzCsKPPjE8ZXsyVfmAAzxItjjOL1B83BE3qsZNiUY1ScahM0CUzplzUgLZ-HXsrlJK-pg-LrPO7Cj20k2E2GaFbU6en59bSTYQ=emb=ii_jzsf570p0
> 
> And the "content-type" is "image/png" in the response headers.
> 
> Does this setting disable the attachment feature and the image feature of
> Gmail?
> 
> 
> --
> Su Shuang (100pah)
> --
> 
> 
> 
> On Tue, 27 Aug 2019 at 00:17, Dave Fisher  wrote:
> 
>> Hi -
>> 
>> That is intentional. Infra is open to allowing safe mimetypes, but not
>> .exe, .bat, etc.
>> 
>> What mimetypes do you want to send to dev@?
>> 
>> Regards,
>> Dave
>> 
>>> On Aug 26, 2019, at 11:54 AM, SHUANG SU  wrote:
>>> 
>>> Ye, I've created an issue in
>> https://issues.apache.org/jira/browse/ECHARTS-7
>>> I found that priv...@echarts.apache.org is normal in image and
>> attachment
>>> sending,
>>> but dev@echarts.apache.org is not.
>>> 
>>> --
>>> Su Shuang (100pah)
>>> --
>>> 
>>> 
>>> 
>>> On Mon, 26 Aug 2019 at 23:44, Kevin A. McGrail 
>> wrote:
>>> 
>>>> Not received.
>>>> 
>>>> On 8/26/2019 11:09, SHUANG SU wrote:
>>>>> try to send image again:
>>>>> 
>>>>> unnamed.png
>>>>> 
>>>>> unnamed (1).png
>>>>> 
>>>>> unnamed (2).png
>>>>> 
>>>>> --
>>>>> Su Shuang (100pah)
>>>>> --
>>>>> 
>>>>> 
>>>>> 
>>>>> On Mon, 26 Aug 2019 at 22:35, SHUANG SU >>>> <mailto:sushuang0...@gmail.com>> wrote:
>>>>> 
>>>>>   resent the images (which probably be blocked by gmail):
>>>>> 
>>>>>   (1) Those resources that "not too big but take a too long time" in
>>>>>   the example page:
>>>>>   https://echarts.apache.org/examples/en/ , which cause me to be
>>>>>   unable to
>>>>>   find the target example.
>>>>>   (See attachment 1 & 2)
>>>>> 
>>>>>   (2) The initial request takes a long time (over 10s) sometimes:
>>>>>   (See attachment 3)
>>>>> 
>>>>> 
>>>>>   --
>>>>>Su Shuang (100pah)
>>>>>   --
>>>>> 
>>>>> 
>>>>> 
>>>>>   On Mon, 26 Aug 2019 at 22:00, Kevin A. McGrail
>>>>>   mailto:kmcgr...@apache.org>> wrote:
>>>>> 
>>>>>   I would say an image linking to an interactive demo would be
>>>>>   good.  The
>>>>>   website delays are a big source of issues so streamlining the
>>>>>   homepage
>>>>>   makes sense.
>>>>> 
>>>>>   On 8/26/2019 09:34, Ovilia wrote:
>>>>>> Another thing we should discuss is that whether we need the
>>>>>   interactive
>>>>>> chart in the index.html. It costs 700k for a full version of
>>>>>   ECharts. Even
>>>>>> if it's necessary to have the interactive chart, we should
>>>>>   build a minium
>>>>>> version for this chart.
>>>>>> I think maybe we should probably use an image instead.
>>>>>   Because the
>>>>>> interactive chart shows the feature of cross-platform
>>>>>   behavior rather the
>>>>>> the interaction of ECharts, so an image may well state the
>>>>>   point.
>>>>>> 
>>>>>> Wenli
>>>&

Re: [NOTICE] ECharts Issues need to be fixed ASAP, from my shepherd perspective

[Dave Fisher]

Inline

> On Aug 25, 2019, at 10:47 PM, Yi Shen  wrote:
> 
> Hi Sheng. Really appreciate your patience
> 
> 
>> As I mentioned in IPMC(private), the whole point of the incubating is *NOT*
>> `*mentor/IPMC pick the wrong things, and PPMC reacts and fix*`.
>> It is about *learning Apache Way*, how to do and why they are required.
>> This the key.
>> All the list I mentioned is just my 5 hours review, my knowledge is also
>> limited, the list could be right or wrong,
>> but *the real goal is PPMC could get their own list, discuss with mentors
>> and have their understanding and actions*.
>> 
> 
> You are right. That's the thing we should keep thinking and learning.
> 
> I think echarts.baidu.com should not exist, for me, this is a serious
>> branding issue. Look like Baidu is still holding the project and IP, even
>> with the redirect.
>> Anyway, still I could be wrong, you should ask your mentors, and learn how
>> to request for help from the Foundation.
>> 
> 
> We won't use echarts.baidu.com any more. Redirecting is for the links
> already exists out there, which we have
> no chance to change.

Internal links within the site should be relative. For links to 
ECharts.baidu.com that are redirected to a direct URI path on 
ECharts.apache.org/zh/ then you can have a .htaccess file on echarts.apache.org 
with rewrite rules.

Regards,
Dave

> 
> But still we should discuss more about letting developers know echarts is
> already an Apache project, not Baidu.
> 
> 
> On Sun, Aug 25, 2019 at 10:24 PM Sheng Wu  wrote:
> 
>> Hi inline
>> 
>> 
>> 沈毅  于2019年8月25日周日 下午9:26写道：
>> 
>>> Thanks Sheng. The suggestions are very helpful!
>>> 
>>> We faced a lot issues when changing from a normal GitHub project to an
>>> Apache Project. But we didn’t take enough effort to solve these issues.
>>> There is no excuse for that. We should take it much more seriously.
>>> 
>> 
>> As I mentioned in IPMC(private), the whole point of the incubating is *NOT*
>> `*mentor/IPMC pick the wrong things, and PPMC reacts and fix*`.
>> It is about *learning Apache Way*, how to do and why they are required.
>> This the key.
>> All the list I mentioned is just my 5 hours review, my knowledge is also
>> limited, the list could be right or wrong,
>> but *the real goal is PPMC could get their own list, discuss with mentors
>> and have their understanding and actions*.
>> 
>> 
>>> 
>>> In the next months we will make changed fix the issues you and other
>>> mentors pointed out.
>>> 
>>> Here are my explains on some of these issues.
>>> 
>>> 1. All plans and progress about the coming versions will be discussed in
>>> the mailing list. And developers will be guided to the mailing list to
>>> discuss with us
>>> 
>>> 2. We will remove the Chinese option in the issue template and guide
>>> developers using English to describe the issues.
>>> 
>>> 3. We will redirect from echarts.baidu.com to echarts.apache.org ASAP
>>> when the speed problem is solved. Wenli will focus on this issue
>>> 
>> 
>> I think echarts.baidu.com should not exist, for me, this is a serious
>> branding issue. Look like Baidu is still holding the project and IP, even
>> with the redirect.
>> Anyway, still I could be wrong, you should ask your mentors, and learn how
>> to request for help from the Foundation.
>> 
>> 
>>> 
>>> 4. Community build is a very serious issue for us currently. It is not a
>>> issue can be solved in months. We should take more actions on encouraging
>>> developers making contributions.
>> 
>> 
>> This is not an issue to be solved, this is the thing how open source
>> project works, showing in many different ways.
>> Community over codes is the one key in Apache. I think I am clear in my
>> list.
>> If this concern could not be eased dramatically, the whole incubating is
>> still not working.
>> This is not just about the metrics I mentioned, it is about
>> mentor/IPMC/community feeling. How you build the community.
>> 
>> 
>>> 
>>> 6. Me and Shuang will take the responsibility on the release discussing
>>> and planning.
>>> 
>>> 9.  We did not follow the git flow. Release branch is the branch same
>> with
>>> the latest release and Master is the developing branch. We are going to
>>> start the vote on the next release in next week. It’s a bit confusing and
>>> we will discuss about migrating to the git flow.
>>> 
>> 
>> That is tech. level issue, which depends on your project. I just remind it
>> is unusual, and most likely blocking the potential contributor. Because
>> they even don't know how to start.
>> 
>> Sheng Wu 吴晟
>> 
>> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
>> Twitter, wusheng1108
>> 
>>> 
>>> Other issues about the branding and website will be fixed ASAP. And we
>>> will raised up in mailing list when we have more questions on these
>> issues.
>>> 
>>> Thanks for still standing with us.
>>> 
 On Aug 25, 2019, at 12:03 PM, Sheng Wu 
>>> wrote:
 
 Hi Echarts PPMC and contributor team
 
 From the ECharts 

Re: [GitHub] [incubator-echarts] Emails

[Dave Fisher]

Hi -

As part of being an Apache project there are somethings to discuss in these 
automated messages.

> On Aug 12, 2019, at 8:37 PM, GitBox  wrote:
> 
>   

Concerns with the Community

[Dave Fisher]

Hi -

I have several concerns about the podling.

(1) There was absolutely no discussion about the report on any of the mailing 
lists. There really is little discussion on dev@echarts about anything. Apache 
Way governance requires that there be discussion here on dev@echarts. This is 
how an Apache project is open and global.

(2) "Redirecting echarts.baidu.com to echarts.apache.org. Because we found some 
speed problem of Apache CDN in China, we haven't done the redirecting job yet. 
We will do more test and ask for help if necessary.” KAM and I both worked to 
help you with this. It’s been a couple of months. If there were problems making 
the change then they need to be discussed on the mailing list. You have to let 
the community know what’s happening.

(3) “Nearing Graduation”. Until there is significant improvement in discussing 
the project on the dev@ mailing list you are not close to graduation. Until we 
can see good community building efforts you are not close.

(4) Podling Name Search issue is here: 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153 Reply here if you 
need mentor assistance with it.

Best Regards,
Dave



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

Fwd: [MENTORS] IPMC Policy change work in progress disclaimer

[Dave Fisher]

FYI

> Begin forwarded message:
> 
> From: Justin Mclean 
> Subject: [MENTORS] IPMC Policy change work in progress disclaimer
> Date: August 1, 2019 at 7:25:00 PM PDT
> To: gene...@incubator.apache.org
> Reply-To: gene...@incubator.apache.org
> 
> Hi,
> 
> The work in progress progress disclaimer (DISCLAIMER-WIP) has been added to 
> the IPMC policy page. [1]
> 
> Podlings can now select which disclaimer they want to use. If they want to 
> use the standard disclaimer then their releases must comply with all ASF 
> policy. If they want the incubator to be more lenient in voting on their 
> release or know that the release has some issues not in line with ASF policy 
> then the work in progress disclaimer can be used.
> 
> Unless the release is simple and straightforward, I would recommend that a 
> podling uses the work in progress disclaimer for the first couple of releases.
> 
> For what is allowed under the work in progress disclaimer please see this 
> legal JIRA [2]. This allows a lot more in a release but not everything. 
> Certain things are required like having a LICENSE, NOTICE and DISCLAIMER-WIP, 
> and while it would be OK to include compiled code you still need to comply 
> with any licensing for that code.
> 
> By the time a podling graduates it's expected that they are making releases 
> with the standard disclaimer.
> 
> Here is the text of the DISCLAIMER-WIP where the Incubator is the sponsor:
> 
> Apache  #Podling-Name# is an effort
> undergoing incubation at The Apache Software Foundation (ASF),
> sponsored by the Apache Incubator. Incubation is required of all
> newly accepted projects until a further review indicates that the
> infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF projects.
> While incubation status is not necessarily a reflection of the
> completeness or stability of the code, it does indicate that the
> project has yet to be fully endorsed by the ASF.
> 
> Some of the incubating project's releases may not be fully compliant
> with ASF policy. For example, releases may have incomplete or
> un-reviewed licensing conditions. What follows is a list of known
> issues the project is currently aware of (note that this list, by
> definition, is likely to be incomplete): 
> #List of known issues go here#
> 
> If you are planning to incorporate this work into your
> product/project, please be aware that you will need to conduct a
> thorough licensing review to determine the overall implications of
> including this work. For the current status of this project through the Apache
> Incubator visit: 
> http://incubator.apache.org/project/#Podling-Name#.html
> 
> 
> Just fill in #Podling-Name# with your podling name and list the known issues 
> in the correct place.
> 
> Thanks,
> Justin
> 
> 1. https://incubator.apache.org/policy/incubation.html#disclaimers
> 2. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: Inclusion in mailing list

[Dave Fisher]

Hi Clement,

Excellent point!

This page: http://echarts.apache.org/maillist.html

Could be made into something similar to https://pulsar.apache.org/en/contact/

Regards,
Dave

> On May 23, 2019, at 11:44 AM, Clement Ho  wrote:
> 
> On a side note, I think we should include better instructions in our
> documentation so that users unfamiliar with mailing lists can join without
> asking the entire mailing list how to join :)
> 
> On Thu, May 23, 2019 at 10:41 AM 羡辙 <812793...@qq.com> wrote:
> 
>> Hi. Please send an email to dev-subscr...@echarts.incubator.apache.org .
>> And it will send a confirm email to you. Then you should reply to a
>> specific email address as told in that reply.
>> Hope that helps.
>> 
>> 
>> Wenli
>> 
>> 
>> -- Original --
>> From: Giorgio Pea 
>> Date: Thu,May 23,2019 9:49 PM
>> To: dev 
>> Subject: Re: Inclusion in mailing list
>> 
>> 
>> 
>> Hello there!
>> Can I ask you to include me in the mailing list?
>> 
>> Have a nice day!
>> Giorgio.


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

Website Speed Improvement

[Dave Fisher]

Hi -

Infrastructure is going to switch echarts.apache.org over to a CDN that will 
cache in China.

Please test latency now so that a comparison can be made after the switch over. 
The switch will occur in 7-8 hours.

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

Re: [VOTE] ECharts Website Analytics policy

[Dave Fisher]

Hi -

There are several issues here. Publishing analytics on the website is a good 
idea. Having an account that is accessible to the PPMC is correct.

Moving the domain for the Chinese language site from echarts.baidu.com to 
www.echartsjs.com doesn’t solve the requirement to be on an apache.org website. 
Who controls the echartsjs.com domain?

Apache projects must have their websites on the apache.org domain. There are 
only a few exceptions that have been allowed for large well known projects that 
came to apache with a large user base. Examples are OpenOffice.org and 
groovy-lang.org. ECharts does not qualify. Managing separate domains is 
expensive for Apache Infrastructure and with 250 projects and podlings we can’t 
make many exceptions.

Regards,
Dave


> On Apr 18, 2019, at 8:56 AM, Clement Ho  wrote:
> 
> Have we considered publishing the analytics data publicly? Could be real
> time or monthly or quarterly. It could also be helpful for the community to
> learn about the projects traction.
> 
> As for echartsjs.com as the chinese redirect website, I think it is worth
> considering whether that may skew the perception that this is primarily a
> chinese open source project rather than a global open source project. Just
> some thoughts that came to mind.
> 
> On Thu, Apr 18, 2019 at 10:50 AM SHUANG SU  wrote:
> 
>> The analytics and statistics of the website are only be used by ECharts
>> maintainers to check:
>> "whether our work makes sense." or even "whether the whole project makes
>> sense."
>> 
>> The statistics from the website have been playing a core role in the
>> development
>> of the ECharts project in the past years.
>> There are few approaches to know whether many users are still using
>> ECharts, choosing ECharts,
>> and how to use it, and which charts/components/features are used frequently
>> and which are rarely used.
>> So the website analysis guides the maintainers to make better decisions
>> about out further work,
>> do not based on the imagination but based on some information from the real
>> world.
>> Without them, we, the maintainers, will become more and more blind, which
>> is very harmful to the ECharts project.
>> 
>> So
>> + 1 (binding)
>> 
>> --
>> Su Shuang (100pah)
>> --
>> 
>> 
>> 
>> On Thu, 18 Apr 2019 at 23:06, Ovilia  wrote:
>> 
>>> ECharts Website currently uses Baidu Tongji [1] as the analytics tool.
>>> To make the information accessible to all PMC members, we are going to
>> add
>>> Google Analytics.
>>> 
>>> Please vote for this suggestion:
>>> For the time being, we suggest
>>> 1.0 Making http://echarts.apache.org be the default Website
>>>1.1 Linking it from GitHub project (done)
>>>1.2 Linking it from the "Home" button in the navbar (done)
>>>1.3 Linking it from the "En" button in Chinese Website (done)
>>>1.4 Removing Baidu Tongji
>>>1.5 Creating a Google account that can be accessed by all PMC members
>>> and adding Google Analytics in Website
>>> 2 Making https://www.echartsjs.com be the default Chinese Website
>>>2.1 Linking it from "中文" (Chinese) button in
>> http://echarts.apache.org
>>>2.2 Redirecting https://echarts.baidu.com to it
>>>2.3 Adding Google Analytics in Website
>>>2.4 Creating a Baidu account that can be accessed by all PMC members.
>>> (Although the product is Chinese-only, you can get access to the data if
>>> you wish. And translation tools may offer some help.)
>>> 
>>> When we have the server provided by Huawei, we wish to make the Chinese
>>> Website under http://echarts.apache.org, probably something like
>>> http://zh.echarts.apache.org.
>>> By that time, we will be able to come to a conclusion about whether
>> Google
>>> Analytics lost some information from China (because the access to some
>>> Google products is limited in China), and decide whether to stick only to
>>> Google Analytics or both.
>>> 
>>> [1] http://tongji.baidu.com
>>> 
>>> Wenli Zhang
>>> 
>> 


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

Re: Website changes are required for transition to Apache

[Dave Fisher]

The current policy is here:

https://www.apache.org/foundation/policies/privacy.html 
<https://www.apache.org/foundation/policies/privacy.html>

This allows for google analytics, but that doesn’t work to well in China.

Just because google analytics are allowed it does not mean that every project 
uses GA.

Baidu analytics have not been approved, and I want to know why ECharts needs 
analytics. And how these analytics are being used.

Regards,
Dave

> On Apr 8, 2019, at 10:37 AM, Kevin A. McGrail  wrote:
> 
> Yeah, I have to say Apache uses GA.  What's the concern about the
> analytics?  I'm pretty sure I've mentioned this before as well that I
> don't see the tracking issue in aggregate as a concern.
> 
> On 4/7/2019 11:25 PM, Ovilia wrote:
>> Hi Dave.
>> 
>> I have some doubt about (4).
>> Could we use Google Analytics instead? Should we create an account that can
>> be accessed by PMC members?
>> 
>> (3) We have the control over Twitter and Weibo accounts. Twitter name has
>> been changed into Apache ECharts (incubating), and we have added Apache
>> ECharts (incubating) in Weibo's description. Please let us know if there is
>> anything else we should do.
>> 
>> Zhang Wenli
>> http://zhangwenli.com
>> 
>> 
>> Dave Fisher  于2019年4月8日周一 上午2:30写道：
>> 
>>> Hi -
>>> 
>>> Some changes to the website are required. There are still some connections
>>> on the site that tie back to Baidu that must be removed or altered.
>>> 
>>> If you take a look at the HTML at the end of the main page I’ll show the
>>> changes:
>>> 
>>> mailto:echa...@baidu.com
>>> ?Body=%28Thanks%20for%20using%20ECharts.%20Email%20us%20if%20you%20have%20non-technical%20problems%20using%20ECharts.%20For%20technical%20support%2C%20please%20go%20to%20https%3A//
>>> github.com/ecomfe/echarts/issues%20.%29" class="footer-icon">>> src="images/icon-email.png">https://twitter.com/EChartsJs;
>>> class="footer-icon">https://weibo.com/u/5160877841; class="footer-icon">>> src="images/icon-weibo.png">https://github.com/ecomfe/echarts;
>>> class="footer-icon">>> src="images/icon-github.png">>> type="text/javascript"
>>> src="./vendors/bootstrap/js/bootstrap.min.js">>> type="text/javascript" src="./js/common.js">>> src="./dist/echarts.min.js">>> src="./js/index.js">var _hmt = _hmt
>>> || [];
>>> (function() {
>>> var hm = document.createElement("script");
>>> hm.src = "//hm.baidu.com/hm.js?4bad1df23f079e0d12bdbef5e65b072f";
>>> var s = document.getElementsByTagName("script")[0];
>>> s.parentNode.insertBefore(hm, s);
>>> })();
>>> 
>>> (1) The mailto should be to dev@echarts.apache.org.
>>> (2) The GitHub address should be changed to
>>> GitHub.com/apache/incubator-echarts
>>> (3) Who controls the twitter and Weibo accounts?
>>> (4) The tracking with hm.baidu.com must be removed. We don’t track our
>>> users back to any vendors account. If you think that ECharts needs to do
>>> tracking then we need to discuss it separately. Until that time please
>>> remove this tracking.
>>> 
>>> 
> 
> -- 
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org
> 

Website changes are required for transition to Apache

[Dave Fisher]

Hi -

Some changes to the website are required. There are still some connections on 
the site that tie back to Baidu that must be removed or altered.

If you take a look at the HTML at the end of the main page I’ll show the 
changes:

mailto:echa...@baidu.com?Body=%28Thanks%20for%20using%20ECharts.%20Email%20us%20if%20you%20have%20non-technical%20problems%20using%20ECharts.%20For%20technical%20support%2C%20please%20go%20to%20https%3A//github.com/ecomfe/echarts/issues%20.%29;
 class="footer-icon">https://twitter.com/EChartsJs; class="footer-icon">https://weibo.com/u/5160877841; 
class="footer-icon">https://github.com/ecomfe/echarts; class="footer-icon">var _hmt = _hmt || 
[];
(function() {
var hm = document.createElement("script");
hm.src = "//hm.baidu.com/hm.js?4bad1df23f079e0d12bdbef5e65b072f";
var s = document.getElementsByTagName("script")[0];
s.parentNode.insertBefore(hm, s);
})();

(1) The mailto should be to dev@echarts.apache.org.
(2) The GitHub address should be changed to GitHub.com/apache/incubator-echarts
(3) Who controls the twitter and Weibo accounts?
(4) The tracking with hm.baidu.com must be removed. We don’t track our users 
back to any vendors account. If you think that ECharts needs to do tracking 
then we need to discuss it separately. Until that time please remove this 
tracking.

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Dave Fisher]

Hi Wenli,

I would remove the VOTE thread link and then it looks good to me!

Regards,
Dave

> On Apr 3, 2019, at 8:28 AM, Ovilia  wrote:
> 
> Hi Dave
> 
> Here's the email content I tried to send.
> Please help review. Thanks!
> 
> Hi all,
> 
> The Apache ECharts (incubating) team is proud to announce Apache ECharts
> version 4.2.1-incubating.
> 
> ECharts is a powerful, interactive charting and visualization library.
> 
> Vote thread:
> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
> 
> Download Links:
> https://echarts.apache.org/download.html
> 
> Release Notes:
> http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
> 
> Website: http://echarts.apache.org/
> 
> ECharts Resources:
> - Issue: https://github.com/apache/incubator-echarts/issues
> - Mailing list: d...@echarts.incubator.apache.org
> 
> Thanks
> 
> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> Dave Fisher  于2019年4月3日周三 下午11:01写道：
> 
>> Bcc: general@incubator.
>> 
>> You need to use your ovi...@apache.org email address to send to
>> annou...@apache.org
>> 
>> Before you do send this out I think we should do a review of the note here
>> on dev@echarts.apache.org first.
>> 
>> Regards,
>> Dave
>> 
>>> On Apr 3, 2019, at 7:10 AM, Ovilia  wrote:
>>> 
>>> Hi Craig,
>>> 
>>> Do I need to email an announcement to annou...@apache.org？
>>> I tried so, but it was rejected with the following message:
>>> 
>>> Hi. This is the qmail-send program at apache.org.
>>> I'm afraid I wasn't able to deliver your message to the following
>> addresses.
>>> This is a permanent error; I've given up. Sorry it didn't work out.
>>> 
>>> :
>>> Must be sent from an @apache.org address.
>>> 
>>> Zhang Wenli
>>> http://zhangwenli.com
>>> 
>>> 
>>> Ovilia  于2019年4月1日周一 下午5:47写道：
>>> 
>>>> Sorry. I've fixed that now.
>>>> 
>>>> Zhang Wenli
>>>> http://zhangwenli.com
>>>> 
>>>> 
>>>> sebb  于2019年4月1日周一 下午4:02写道：
>>>> 
>>>>> On Mon, 1 Apr 2019 at 07:58, Ovilia  wrote:
>>>>>> 
>>>>>> Thanks Craig.
>>>>>> 
>>>>>> I've updated the download page. Please help check again.
>>>>>> Thank you!
>>>>> 
>>>>> The page says "please check the md5sum and ...".
>>>>> However MD5 checksums are deprecated and anyway the podling does not
>> use
>>>>> them.
>>>>> The text and the link need to be fixed accordingly please.
>>>>> 
>>>>> Also the KEYS link must be to
>>>>> https://www.apache.org/dist/incubator/echarts/KEYS
>>>>> 
>>>>> The dist.apache.org server is only intended to be used by developers
>>>>> for staging releases.
>>>>> 
>>>>>> Zhang Wenli
>>>>>> http://zhangwenli.com
>>>>>> 
>>>>>> 
>>>>>> Craig Russell  于2019年3月30日周六 下午1:06写道：
>>>>>> 
>>>>>>> The page http://echarts.apache.org/download.html is very close, but:
>>>>>>> 
>>>>>>> The Source link is fine.
>>>>>>> The Signature link and SHA512 link must be changed from
>>>>>>> https://dist.apache.org/repos/dist/release/incubator/echarts/... to
>>>>>>> https://www.apache.org/dist/incubator/echarts/...
>>>>>>> 
>>>>>>> The instructions in step 2 refer to downloading from Apache but these
>>>>>>> links are http links and must be https links.
>>>>>>> 
>>>>>>> Hope this helps,
>>>>>>> 
>>>>>>> Craig
>>>>>>> 
>>>>>>> 
>>>>>>>> On Mar 29, 2019, at 9:46 PM, Ovilia  wrote:
>>>>>>>> 
>>>>>>>> The download link is http://echarts.apache.org/download.html
>>>>>>>> 
>>>>>>>> Zhang Wenli
>>>>>>>> http://zhangwenli.com
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Ovilia  于2019年3月30日周六 下午12:45写道：
>>>>>>>> 
>>>>>>>>> I've updated ECharts download pa

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Dave Fisher]

> On Apr 3, 2019, at 8:57 AM, sebb  wrote:
> 
> On Wed, 3 Apr 2019 at 16:01, Dave Fisher  wrote:
>> 
>> Bcc: general@incubator.
>> 
>> You need to use your ovi...@apache.org email address to send to 
>> annou...@apache.org
>> 
>> Before you do send this out I think we should do a review of the note here 
>> on dev@echarts.apache.org first.
> 
> Also the sentence:
> 
> "For more information, please see the Apache Release FAQ."
> 
> links to a page which is intended for developers, not downloaders, and
> does not appear to relate to the rest of the paragraph.

Wenli - I agree with Sebb, please remove that sentence

Regards,
Dave

> 
>> Regards,
>> Dave
>> 
>>> On Apr 3, 2019, at 7:10 AM, Ovilia  wrote:
>>> 
>>> Hi Craig,
>>> 
>>> Do I need to email an announcement to annou...@apache.org？
>>> I tried so, but it was rejected with the following message:
>>> 
>>> Hi. This is the qmail-send program at apache.org.
>>> I'm afraid I wasn't able to deliver your message to the following addresses.
>>> This is a permanent error; I've given up. Sorry it didn't work out.
>>> 
>>> :
>>> Must be sent from an @apache.org address.
>>> 
>>> Zhang Wenli
>>> http://zhangwenli.com
>>> 
>>> 
>>> Ovilia  于2019年4月1日周一 下午5:47写道：
>>> 
>>>> Sorry. I've fixed that now.
>>>> 
>>>> Zhang Wenli
>>>> http://zhangwenli.com
>>>> 
>>>> 
>>>> sebb  于2019年4月1日周一 下午4:02写道：
>>>> 
>>>>> On Mon, 1 Apr 2019 at 07:58, Ovilia  wrote:
>>>>>> 
>>>>>> Thanks Craig.
>>>>>> 
>>>>>> I've updated the download page. Please help check again.
>>>>>> Thank you!
>>>>> 
>>>>> The page says "please check the md5sum and ...".
>>>>> However MD5 checksums are deprecated and anyway the podling does not use
>>>>> them.
>>>>> The text and the link need to be fixed accordingly please.
>>>>> 
>>>>> Also the KEYS link must be to
>>>>> https://www.apache.org/dist/incubator/echarts/KEYS
>>>>> 
>>>>> The dist.apache.org server is only intended to be used by developers
>>>>> for staging releases.
>>>>> 
>>>>>> Zhang Wenli
>>>>>> http://zhangwenli.com
>>>>>> 
>>>>>> 
>>>>>> Craig Russell  于2019年3月30日周六 下午1:06写道：
>>>>>> 
>>>>>>> The page http://echarts.apache.org/download.html is very close, but:
>>>>>>> 
>>>>>>> The Source link is fine.
>>>>>>> The Signature link and SHA512 link must be changed from
>>>>>>> https://dist.apache.org/repos/dist/release/incubator/echarts/... to
>>>>>>> https://www.apache.org/dist/incubator/echarts/...
>>>>>>> 
>>>>>>> The instructions in step 2 refer to downloading from Apache but these
>>>>>>> links are http links and must be https links.
>>>>>>> 
>>>>>>> Hope this helps,
>>>>>>> 
>>>>>>> Craig
>>>>>>> 
>>>>>>> 
>>>>>>>> On Mar 29, 2019, at 9:46 PM, Ovilia  wrote:
>>>>>>>> 
>>>>>>>> The download link is http://echarts.apache.org/download.html
>>>>>>>> 
>>>>>>>> Zhang Wenli
>>>>>>>> http://zhangwenli.com
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Ovilia  于2019年3月30日周六 下午12:45写道：
>>>>>>>> 
>>>>>>>>> I've updated ECharts download page. Hopefully, it's been fixed
>>>>> correctly
>>>>>>>>> this time.
>>>>>>>>> If so, we will send an email to  annou...@apache.org for the
>>>>> release.
>>>>>>>>> 
>>>>>>>>> Zhang Wenli
>>>>>>>>> http://zhangwenli.com
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Craig Russell  于2019年3月21日周四 上午8:23写道：
>>>>>>>>> 
>>>>>>>>>> Hi Su Shuang,
>>>>>>>>>>

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Dave Fisher]

Bcc: general@incubator.

You need to use your ovi...@apache.org email address to send to 
annou...@apache.org

Before you do send this out I think we should do a review of the note here on 
dev@echarts.apache.org first.

Regards,
Dave

> On Apr 3, 2019, at 7:10 AM, Ovilia  wrote:
> 
> Hi Craig,
> 
> Do I need to email an announcement to annou...@apache.org？
> I tried so, but it was rejected with the following message:
> 
> Hi. This is the qmail-send program at apache.org.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
> 
> :
> Must be sent from an @apache.org address.
> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> Ovilia  于2019年4月1日周一 下午5:47写道：
> 
>> Sorry. I've fixed that now.
>> 
>> Zhang Wenli
>> http://zhangwenli.com
>> 
>> 
>> sebb  于2019年4月1日周一 下午4:02写道：
>> 
>>> On Mon, 1 Apr 2019 at 07:58, Ovilia  wrote:
 
 Thanks Craig.
 
 I've updated the download page. Please help check again.
 Thank you!
>>> 
>>> The page says "please check the md5sum and ...".
>>> However MD5 checksums are deprecated and anyway the podling does not use
>>> them.
>>> The text and the link need to be fixed accordingly please.
>>> 
>>> Also the KEYS link must be to
>>> https://www.apache.org/dist/incubator/echarts/KEYS
>>> 
>>> The dist.apache.org server is only intended to be used by developers
>>> for staging releases.
>>> 
 Zhang Wenli
 http://zhangwenli.com
 
 
 Craig Russell  于2019年3月30日周六 下午1:06写道：
 
> The page http://echarts.apache.org/download.html is very close, but:
> 
> The Source link is fine.
> The Signature link and SHA512 link must be changed from
> https://dist.apache.org/repos/dist/release/incubator/echarts/... to
> https://www.apache.org/dist/incubator/echarts/...
> 
> The instructions in step 2 refer to downloading from Apache but these
> links are http links and must be https links.
> 
> Hope this helps,
> 
> Craig
> 
> 
>> On Mar 29, 2019, at 9:46 PM, Ovilia  wrote:
>> 
>> The download link is http://echarts.apache.org/download.html
>> 
>> Zhang Wenli
>> http://zhangwenli.com
>> 
>> 
>> Ovilia  于2019年3月30日周六 下午12:45写道：
>> 
>>> I've updated ECharts download page. Hopefully, it's been fixed
>>> correctly
>>> this time.
>>> If so, we will send an email to  annou...@apache.org for the
>>> release.
>>> 
>>> Zhang Wenli
>>> http://zhangwenli.com
>>> 
>>> 
>>> Craig Russell  于2019年3月21日周四 上午8:23写道：
>>> 
 Hi Su Shuang,
 
 You will need to modify your download page to conform to
>>> requirements
> (an
 announcement to incubator is not moderated but an announcement to
 annou...@apache.org will be moderated, and this announcement
>>> will not
 pass).
 
 You should never refer in the announcement or your download page
>>> to
 dist.apache.org. For announcement emails, link to your download
>>> page.
 For download pages, link to the mirror chooser and link to the
> checksum and
 signature from www.apache.org/dist/incubator/echarts. Include a
>>> link
> to
 your project KEYS file and instructions how to verify the
>>> download.
 
 There are many download pages you can model, e.g.
 https://hadoop.apache.org/releases.html
 
 If you need help, your mentors will be able to assist.
 
 Best regards
 
 Craig
 
> On Mar 20, 2019, at 1:24 PM, SHUANG SU 
> wrote:
> 
> Hi all,
> 
> The Apache ECharts (incubating) team is proud to announce Apache
> ECharts
> version 4.2.1-incubating.
> 
> ECharts is a powerful, interactive charting and visualization
>>> library.
> 
> Vote thread:
> 
 
> 
>>> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
> 
> Download Links:
> 
>>> https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
> 
> Release Notes:
> 
>>> http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
> 
> Website: http://echarts.apache.org/
> 
> ECharts Resources:
> - Issue: https://github.com/apache/incubator-echarts/issues
> - Mailing list: d...@echarts.incubator.apache.org
> 
> Thanks
> 
> --
> Su Shuang (100pah)
> --
 
 Craig L Russell
 c...@apache.org
 
 
 
>>> -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org

Re: svn commit: r33197 - in /release/incubator/echarts: 4.1.0/ 4.2.1/

[Dave Fisher]

All releases must be on the Apache Distribution system.

Binary releases are separate packages from the source, but can be VOTED on at 
the same time. NOTICE and LICENSE must be adjusted for the binary package 
according to what’s included.

Any packages / tags shown on the GitHub release tab should be marked as 
“pre-release” if they have a readme.

I’ll send some links later.

Regards,
Dave

Sent from my iPhone

> On Mar 27, 2019, at 5:04 AM, Ovilia  wrote:
> 
> Hi Dave,
> 
> If we wish to include binary code, which is the building result of the
> source code, is it correct to link to GitHub file in our download page? Or
> should it be hosted also in the Apache mirrors, which is the way Hadoop
> adopts?
> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> SHUANG SU  于2019年3月26日周二 下午2:07写道：
> 
>> Fix of the last email: the last release candidate of 4.1.0 is rc4.
>> Sorry...
>> 
>> --
>> Su Shuang (100pah)
>> --
>> 
>> 
>> 
>>> On Tue, 26 Mar 2019 at 13:43, SHUANG SU  wrote:
>>> 
>>> Hi Dave
>>> 
>>> I did not modify the artifact we are voted.
>>> 
>>> (1) For 4.1.0, I found that the released file name is still
>>> "apache-echarts-4.1.0-rc3-incubating-src.zip",
>>> that is the name of the last release candidate.
>>> That a mistake because I forgot to rename it to be
>>> "apache-echarts-4.1.0-incubating-src.zip".
>>> So I rename it just now.
>>> 
>>> (2) We are trying hard to fix the download page of echarts website,
>> making
>>> it follow the Apache rule
>>> without loose functionality for echarts users.
>>> The download page of the echarts website needs the binary/prebuilt zip
>>> with sha512 and asc.
>>> Previously the users can get binary/prebuilt zip from the Github release
>>> tag.
>>> But I just add it to svn, named as "apache-echarts-4.2.1-incubating.zip"
>>> and make the signatures.
>>> But I made a mistake that the zip is corrupted. So I fixed it.
>>> 
>>> That is all of the svn logs above.
>>> 
>>> I don't know whether it is necessary to upload the bin/prebuilt to svn.
>>> Can we just link it to the Github release tag on the download page?
>>> Or should the name be "apache-echarts-4.2.1-dist-incubating.zip" to avoid
>>> confusion?
>>> 
>>> 
>>> Thanks,
>>> 
>>> --
>>> Su Shuang (100pah)
>>> --
>>> 
>>> 
>>> 
>>>> On Tue, 26 Mar 2019 at 12:20, Dave Fisher  wrote:
>>>> 
>>>> Hi -
>>>> 
>>>> Why did you need to do this? If these are different than what we VOTED
>> on
>>>> before then you will need to revert this commit and start a new release.
>>>> 
>>>> It is important that we keep clear VOTE threads showing that we VOTED on
>>>> the artifacts that were released. About all that can be allowed is a
>> change
>>>> to the name as it will remain possible to prove we approved of what was
>>>> released. Without this minimal rule the Apache Legal Shield is not
>> properly
>>>> enforced. This is actually your own personal benefit.
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>>> On Mar 25, 2019, at 9:05 PM, sushu...@apache.org wrote:
>>>>> 
>>>>> Author: sushuang
>>>>> Date: Tue Mar 26 04:05:40 2019
>>>>> New Revision: 33197
>>>>> 
>>>>> Log:
>>>>> fix release files
>>>>> 
>>>>> Modified:
>>>>>   release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip
>>>>> 
>>>> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.asc
>>>>> 
>>>> 
>> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.sha512
>>>>>   release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip
>>>>> 
>>>> release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip.asc
>>>>> 
>>>> 
>> release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip.sha512
>>>>> 
>>>>> Modified:
>>>> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip
>>>>> 
>>>> 
>> 

Re: svn commit: r33197 - in /release/incubator/echarts: 4.1.0/ 4.2.1/

[Dave Fisher]

Hi -

Why did you need to do this? If these are different than what we VOTED on 
before then you will need to revert this commit and start a new release.

It is important that we keep clear VOTE threads showing that we VOTED on the 
artifacts that were released. About all that can be allowed is a change to the 
name as it will remain possible to prove we approved of what was released. 
Without this minimal rule the Apache Legal Shield is not properly enforced. 
This is actually your own personal benefit.

Regards,
Dave

> On Mar 25, 2019, at 9:05 PM, sushu...@apache.org wrote:
> 
> Author: sushuang
> Date: Tue Mar 26 04:05:40 2019
> New Revision: 33197
> 
> Log:
> fix release files
> 
> Modified:
>release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip
>release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.asc
>release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.sha512
>release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip
>release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip.asc
>release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip.sha512
> 
> Modified: release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip
> ==
> Binary files 
> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip 
> (original) and 
> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip Tue Mar 
> 26 04:05:40 2019 differ
> 
> Modified: 
> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.asc
> ==
> --- release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.asc 
> (original)
> +++ release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.asc 
> Tue Mar 26 04:05:40 2019
> @@ -1,16 +1,16 @@
> -BEGIN PGP SIGNATURE-
> 
> -iQIzBAABCgAdFiEEmwbZtPo3xN1ScldCdHmF1+POtjUFAlyZld8ACgkQdHmF1+PO
> -tjVwhBAAg0OhX0wMa11Pmp4QdgTVwll9/YVCp691s684t8jeLlHJnUAFDSWdRA6U
> -4MW60N15HW5Wdd2ErA3yGerD8FLQZS+G+G4yzZDplwq1vD/8Y0OHD7tZadO66Wir
> -r70QyZZt4txYDN8vNcYQCW1yGtCrDzwiF/7WmuX4C4kkCfUq72DOsUIiSKQ4bOQb
> -6R4Pnerzxs1oJyqVda8n1I/bU552zNeJ31aVzmVdzo0jCKpMHcoG0ikYe1N3JCDf
> -KW8Iy4bNmVAReZ0O7ADJ65oXqzQeZYeGeHwWRf/rsrvqm4ttEljm5Acc5zrjCFq6
> -jj8dpZS3OsdZIvS0j3pyqTA0DQq4ZHnjCyEmQsBuvWRatzA+0IFfgHySsitMf1WU
> -8SlI4w/rtIWFrgK05j/BFJvwx8Capoyd1ut1V18PBJS9iP1fVEahX+skIB0Tl9DS
> -gVbjACKDiquT90/+Misnl8lCj877PORSMy41ZdyTayrzE++fTr5KyA4kyExb0IJp
> -J1KE2knsHcztP4C0OatAdTsYfQpAw3W3Bw0/4sh0Y0+USYlZB0waB7LGPWXMD0ga
> -dV65yFck5NeziORz6R9DWmHfydfItp5cIeLC9F3l6xhOPYsuKxF7+vV9UsxhvXH/
> -mIihAA4Xwsx9iR4y6lMJfbBma+qD9pbZ2iZFlaNnRmrPNKRAmgo=
> -=fhcz
> +iQIzBAABCgAdFiEEmwbZtPo3xN1ScldCdHmF1+POtjUFAlyZpLAACgkQdHmF1+PO
> +tjXIKBAAy3kyq0fEQBGMefry5Rj4iYJMZn3oPB9SE+4kQeh+QIJpt+S92SJXutIY
> +GHYE9W6VcLp/L/yaSz7uydIrwjWszT3dePnKI2535yNkSXmbqKIldCmQEUnIvX2t
> +s3JM4uINAO1Ph9RGkQcoSya+a1aOQ4Crh7NwzCF9aSp5Iswa5/vIUiZMe2JImYDC
> +bjCkuZFjpC6xReBXDtewUYqak8DVYkWdmujAg9e9rsWNNQyrudEkvHjrbPVMPk3O
> +9q5qe+RjoAq2ngglTNDM337XxXiiHuDintdh4ep89PQHh27d1OD9DKD2MgGKib9x
> +vVt+REf/Tg6Tl3HJpPruEoexnj2QXRC0t4yg8xJIb9CcRPBeXEdR5tdUUCPfoJlU
> +T0kztoi2v7GCbVztQrKB7w13avk2g86M7PsVOYP1+71/0KQQ/Hczzuxs+14ZMbXZ
> +/t6HmIQKyb71web+MZsAoflWrXJRI8iZNkPNIGaZ1ojo847cRSlsNXQv6TiJikeF
> +J5IqiZvxDZLBZNLcXl5IqxjnE30EL4IBBbzL0xwXYmXAxZA+1vowhmuZadP1PcUa
> +axw2v9x0L+gF9U1ALfYy9+5eNq6zanr1AwiRCaIz1khYxQTxgiH4yMiXCoPIdPpX
> +LjoGM23UzT0SWkWBjbUeXFo1fENwZV6dvmq0uvpBT5oUhLRKvkQ=
> +=EnFS
> -END PGP SIGNATURE-
> 
> Modified: 
> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.sha512
> ==
> --- 
> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.sha512 
> (original)
> +++ 
> release/incubator/echarts/4.1.0/apache-echarts-4.1.0-incubating.zip.sha512 
> Tue Mar 26 04:05:40 2019
> @@ -1,4 +1,4 @@
> -apache-echarts-4.1.0-incubating.zip: B8DEDBC4 E869D866 2A4C2100 F20E262C
> - 7061CB14 EBB8AA19 E9E2224F 3F7187DD
> - 8F914E79 BD06DF02 EF216690 DE32C6A4
> - CD4BE604 90FAAF66 8E552F84 2971B86D
> +apache-echarts-4.1.0-incubating.zip: C420072A 4F05384D 404EA415 9784E249
> + 45859318 F71EAEB2 E0190405 C3A55957
> + 755B4494 BEC9188F 5D35631C 050434C7
> + E7D2955E 3D1BCCE9 E98B98A0 6D06757C
> 
> Modified: release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip
> ==
> Binary files 
> release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip 
> (original) and 
> release/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating.zip Tue Mar 
> 26 04:05:40 2019 

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Dave Fisher]

Hi -

A reminder. This one issue needs to be fixed on 
echarts.incubator.apache.org/download.html at the soonest.

>>> 
>>> Also you can look at the sparkling new 
>>> https://incubator.apache.org/clutch/echarts.html 
>>>  under releases for 
>>> compliant links.
>> 
> 
> The Download Page is not compliant with Apache Policy and must be fixed. It 
> must do something along the lines on the clutch/echarts page.

apache-echarts-4.2.1-incubating-src.zip
Download - 
https://www.apache.org/dyn/closer.lua?filename=incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating-src.zip
Keys - https://www.apache.org/dist/incubator/echarts/KEYS
Signature - 
https://www.apache.org/dist/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating-src.zip.asc
Hash - 
https://www.apache.org/dist/incubator/echarts/4.2.1/apache-echarts-4.2.1-incubating-src.zip.sha512

It is essential that you verify the integrity of release downloads. See 
https://www.apache.org/dyn/closer.cgi#verify for instructions

Note that the download /dyn/closer.lua will pick an Apache Mirror that is near 
to the user.

The above is a complaint way to satisfy - 
https://www.apache.org/dev/release-distribution.html#download-links

> 
> The announcement email will not go out until this has been done. You will 
> need to resend a proper announcement to pass the moderators on announce  
> apache.org

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

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Dave Fisher]

Hi -

Sent from my iPhone

> On Mar 21, 2019, at 7:31 PM, Ovilia  wrote:
> 
> Hi Dave,
> 
> Could we have a further discussion about the server provided by Huawei?

I need to have a discussion with Kevin, Ted and others privately. I already 
started looking for answers last week.

> What should we do if we want to use it?

When an offering happens it will come through Apache Infrastructure. It may 
just a mirror of Apache websites which includes ECharts.apache.org.

Regards,
Dave

> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> Dave Fisher  于2019年3月22日周五 上午8:17写道：
> 
>> Hi ECharts Devs -
>> 
>>> On Mar 20, 2019, at 6:25 PM, Craig Russell  wrote:
>>> 
>>> 
>>> 
>>>> On Mar 20, 2019, at 5:43 PM, Dave Fisher  wrote:
>>>> 
>>>> Hi -
>>>> 
>>>> Also you can look at the sparkling new
>> https://incubator.apache.org/clutch/echarts.html <
>> https://incubator.apache.org/clutch/echarts.html> under releases for
>> compliant links.
>>> 
>>> Nice, except for one more minor issue: the current download link should
>> not have the =download in the url. Users need to be able to select
>> their own mirrors.
>> 
>> The Download Page is not compliant with Apache Policy and must be fixed.
>> It must do something along the lines on the clutch/echarts page.
>> 
>> The announcement email will not go out until this has been done. You will
>> need to resend a proper announcement to pass the moderators on announce
>>  apache.org
>> 
>> The IPMC also wants to see progress on moving the Chinese version of the
>> site on the Apache site. (Yes, latency questions remain, but that’s no
>> excuse not to make the repository move.)
>> 
>> Regards,
>> Dave
>> 
>>> 
>>> Regards,
>>> 
>>> Craig
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>>> On Mar 20, 2019, at 5:23 PM, Craig Russell 
>> wrote:
>>>>> 
>>>>> Hi Su Shuang,
>>>>> 
>>>>> You will need to modify your download page to conform to requirements
>> (an announcement to incubator is not moderated but an announcement to
>> annou...@apache.org will be moderated, and this announcement will not
>> pass).
>>>>> 
>>>>> You should never refer in the announcement or your download page to
>> dist.apache.org. For announcement emails, link to your download page. For
>> download pages, link to the mirror chooser and link to the checksum and
>> signature from www.apache.org/dist/incubator/echarts. Include a link to
>> your project KEYS file and instructions how to verify the download.
>>>>> 
>>>>> There are many download pages you can model, e.g.
>> https://hadoop.apache.org/releases.html
>>>>> 
>>>>> If you need help, your mentors will be able to assist.
>>>>> 
>>>>> Best regards
>>>>> 
>>>>> Craig
>>>>> 
>>>>>> On Mar 20, 2019, at 1:24 PM, SHUANG SU 
>> wrote:
>>>>>> 
>>>>>> Hi all,
>>>>>> 
>>>>>> The Apache ECharts (incubating) team is proud to announce Apache
>> ECharts
>>>>>> version 4.2.1-incubating.
>>>>>> 
>>>>>> ECharts is a powerful, interactive charting and visualization library.
>>>>>> 
>>>>>> Vote thread:
>>>>>> 
>> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
>>>>>> 
>>>>>> Download Links:
>>>>>> https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
>>>>>> 
>>>>>> Release Notes:
>>>>>> http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
>>>>>> 
>>>>>> Website: http://echarts.apache.org/
>>>>>> 
>>>>>> ECharts Resources:
>>>>>> - Issue: https://github.com/apache/incubator-echarts/issues
>>>>>> - Mailing list: d...@echarts.incubator.apache.org
>>>>>> 
>>>>>> Thanks
>>>>>> 
>>>>>> --
>>>>>> Su Shuang (100pah)
>>>>>> --
>>>>> 
>>>>> Craig L Russell
>>>>> c...@apache.org
>>>>> 
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>> 
>>>> 
>>> 
>>> Craig L Russell
>>> Secretary, Apache Software Foundation
>>> c...@apache.org <mailto:c...@apache.org> http://db.apache.org/jdo <
>> http://db.apache.org/jdo>
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
>> 


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

Re: Question regarding hiding bars in barchart

[Dave Fisher]

Making sure Tobias is included since he probably is not subscribed.

Sent from my iPhone

> On Mar 21, 2019, at 7:29 PM, Ovilia  wrote:
> 
> Hi Tobias.
> 
> This is a feature that ECharts does not support yet. Please follow
> https://github.com/apache/incubator-echarts/issues/9899 for more
> information.
> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> Svenberg, Tobias  于2019年3月22日周五 上午12:31写道：
> 
>> Hello,
>> 
>> 
>> 
>> I’ve tried to figure this one out but have hit a dead end. The option
>> below creates a lot of empty space on the xAxis. This is, I assume the
>> space taken by empty values. Is there a way to hide/skip these null bars?
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> option = {
>> 
>>legend: {
>> 
>>type: 'scroll',
>> 
>>orient: 'vertical',
>> 
>>right: 10,
>> 
>>top: 20,
>> 
>>bottom: 20,
>> 
>>},
>> 
>>tooltip: {
>> 
>>trigger: 'axis',
>> 
>>// showContent: false
>> 
>>},
>> 
>>dataset: {
>> 
>>sourceHeader: true,
>> 
>>source: [
>> 
>>['Tenant','Plan 01','Plan 02','Plan 03','Plan
>> 04','Plan 05','Plan 06','Plan 07','Plan 08','Plan 09','Plan 10'],
>> 
>>['Real Estate
>> Service',327.15,,null,null,null,null,null,null,null,null],
>> 
>>['Zeus
>> Navigations',null,78.99,null,27.09,46.89,null,null,null,null,null],
>> 
>> 
>> ['Vacant',null,42.29,null,69.39,null,null,null,83.69,26.71,null],
>> 
>>['Golden Road
>> Corporation',null,33,null,null,null,null,null,null,null,null],
>> 
>>['Twister
>> Foods',null,34.11,null,null,null,null,null,null,null,null],
>> 
>> 
>> ['Melonetworks',null,null,69.39,null,null,null,null,null,27.08,null],
>> 
>> 
>> ['Antarts',null,null,33.33,null,null,null,null,null,null,null],
>> 
>> 
>> ['Spicurity',null,null,33.33,null,null,null,null,null,null,null],
>> 
>> 
>> ['Surprisystems',null,null,null,null,52.29,46.89,null,null,null,null],
>> 
>> 
>> ['Soulstones',null,null,null,null,null,52.29,null,null,null,null],
>> 
>> 
>> ['Signalways',null,null,null,null,null,null,46.89,null,null,null],
>> 
>> 
>> ['Shadowshade',null,null,null,null,null,null,52.29,null,null,null],
>> 
>>['Star
>> Gazer',null,null,null,null,null,null,null,null,null,26.71]
>> 
>>],
>> 
>> 
>> 
>> 
>> 
>>},
>> 
>>xAxis: {type: 'category'},
>> 
>>yAxis:{},
>> 
>> 
>> 
>>series: [
>> 
>>// // // These series is in the first cartesian (grid),
>> and each
>> 
>>// // // is mapped to a row.
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>{type: 'bar', seriesLayoutBy: 'row'},
>> 
>>]
>> 
>>};
>> 
>> 
>> 
>> 
>> 
>> Thank you!
>> 
>> 
>> 
>> 
>> 
>> Best regards,
>> 
>> 
>> 
>> Tobias Svenberg
>> 


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

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Dave Fisher]

Hi ECharts Devs -

> On Mar 20, 2019, at 6:25 PM, Craig Russell  wrote:
> 
> 
> 
>> On Mar 20, 2019, at 5:43 PM, Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> Also you can look at the sparkling new 
>> https://incubator.apache.org/clutch/echarts.html 
>> <https://incubator.apache.org/clutch/echarts.html> under releases for 
>> compliant links.
> 
> Nice, except for one more minor issue: the current download link should not 
> have the =download in the url. Users need to be able to select their 
> own mirrors.

The Download Page is not compliant with Apache Policy and must be fixed. It 
must do something along the lines on the clutch/echarts page.

The announcement email will not go out until this has been done. You will need 
to resend a proper announcement to pass the moderators on announce  
apache.org

The IPMC also wants to see progress on moving the Chinese version of the site 
on the Apache site. (Yes, latency questions remain, but that’s no excuse not to 
make the repository move.)

Regards,
Dave

> 
> Regards,
> 
> Craig
>> 
>> Regards,
>> Dave
>> 
>>> On Mar 20, 2019, at 5:23 PM, Craig Russell  wrote:
>>> 
>>> Hi Su Shuang,
>>> 
>>> You will need to modify your download page to conform to requirements (an 
>>> announcement to incubator is not moderated but an announcement to 
>>> annou...@apache.org will be moderated, and this announcement will not pass).
>>> 
>>> You should never refer in the announcement or your download page to 
>>> dist.apache.org. For announcement emails, link to your download page. For 
>>> download pages, link to the mirror chooser and link to the checksum and 
>>> signature from www.apache.org/dist/incubator/echarts. Include a link to 
>>> your project KEYS file and instructions how to verify the download.
>>> 
>>> There are many download pages you can model, e.g. 
>>> https://hadoop.apache.org/releases.html
>>> 
>>> If you need help, your mentors will be able to assist.
>>> 
>>> Best regards
>>> 
>>> Craig
>>> 
>>>> On Mar 20, 2019, at 1:24 PM, SHUANG SU  wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> The Apache ECharts (incubating) team is proud to announce Apache ECharts
>>>> version 4.2.1-incubating.
>>>> 
>>>> ECharts is a powerful, interactive charting and visualization library.
>>>> 
>>>> Vote thread:
>>>> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
>>>> 
>>>> Download Links:
>>>> https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
>>>> 
>>>> Release Notes:
>>>> http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
>>>> 
>>>> Website: http://echarts.apache.org/
>>>> 
>>>> ECharts Resources:
>>>> - Issue: https://github.com/apache/incubator-echarts/issues
>>>> - Mailing list: d...@echarts.incubator.apache.org
>>>> 
>>>> Thanks
>>>> 
>>>> --
>>>> Su Shuang (100pah)
>>>> --
>>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
> 
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org <mailto:c...@apache.org> http://db.apache.org/jdo 
> <http://db.apache.org/jdo>


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

Re: Question regarding hiding bars in barchart

[Dave Fisher]

Added the OP who is not subscribed.

Tobias - The list strips attachments. You may want to upload to a post service 
and provide the link.

You also may wish to subscribe by sending an email to 
dev-subscr...@echarts.apache.org  

Regards,
Dave

> On Mar 21, 2019, at 9:28 AM, Svenberg, Tobias  
> wrote:
> 
> Hello,
>  
> I’ve tried to figure this one out but have hit a dead end. The option below 
> creates a lot of empty space on the xAxis. This is, I assume the space taken 
> by empty values. Is there a way to hide/skip these null bars?
>  
> 
>  
>  
> option = {
> legend: {
> type: 'scroll',
> orient: 'vertical',
> right: 10,
> top: 20,
> bottom: 20,
> },
> tooltip: {
> trigger: 'axis',
> // showContent: false
> },
> dataset: {
> sourceHeader: true,
> source: [
> ['Tenant','Plan 01','Plan 02','Plan 03','Plan 04','Plan 
> 05','Plan 06','Plan 07','Plan 08','Plan 09','Plan 10'],
> ['Real Estate 
> Service',327.15,,null,null,null,null,null,null,null,null],
> ['Zeus 
> Navigations',null,78.99,null,27.09,46.89,null,null,null,null,null],
> 
> ['Vacant',null,42.29,null,69.39,null,null,null,83.69,26.71,null],
> ['Golden Road 
> Corporation',null,33,null,null,null,null,null,null,null,null],
> ['Twister 
> Foods',null,34.11,null,null,null,null,null,null,null,null],
> 
> ['Melonetworks',null,null,69.39,null,null,null,null,null,27.08,null],
> 
> ['Antarts',null,null,33.33,null,null,null,null,null,null,null],
> 
> ['Spicurity',null,null,33.33,null,null,null,null,null,null,null],
> 
> ['Surprisystems',null,null,null,null,52.29,46.89,null,null,null,null],
> 
> ['Soulstones',null,null,null,null,null,52.29,null,null,null,null],
> 
> ['Signalways',null,null,null,null,null,null,46.89,null,null,null],
> 
> ['Shadowshade',null,null,null,null,null,null,52.29,null,null,null],
> ['Star 
> Gazer',null,null,null,null,null,null,null,null,null,26.71]
> ],
> 
> 
> },
> xAxis: {type: 'category'},
> yAxis:{},
>  
> series: [
> // // // These series is in the first cartesian (grid), and 
> each
> // // // is mapped to a row.
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> {type: 'bar', seriesLayoutBy: 'row'},
> ]
> };
>  
>  
> Thank you!
>  
>  
> Best regards,
>  
> Tobias Svenberg

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Dave Fisher]

Hi Craig,

> On Mar 20, 2019, at 6:25 PM, Craig Russell  wrote:
> 
> 
> 
>> On Mar 20, 2019, at 5:43 PM, Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> Also you can look at the sparkling new 
>> https://incubator.apache.org/clutch/echarts.html 
>> <https://incubator.apache.org/clutch/echarts.html> under releases for 
>> compliant links.
> 
> Nice, except for one more minor issue: the current download link should not 
> have the =download in the url. Users need to be able to select their 
> own mirrors.

Thanks for bringing that up. I’ll have that fixed in a couple of days. The 
project page is close….

> 
> Regards,
> 
> Craig
>> 
>> Regards,
>> Dave
>> 
>>> On Mar 20, 2019, at 5:23 PM, Craig Russell  wrote:
>>> 
>>> Hi Su Shuang,
>>> 
>>> You will need to modify your download page to conform to requirements (an 
>>> announcement to incubator is not moderated but an announcement to 
>>> annou...@apache.org will be moderated, and this announcement will not pass).
>>> 
>>> You should never refer in the announcement or your download page to 
>>> dist.apache.org. For announcement emails, link to your download page. For 
>>> download pages, link to the mirror chooser and link to the checksum and 
>>> signature from www.apache.org/dist/incubator/echarts. Include a link to 
>>> your project KEYS file and instructions how to verify the download.
>>> 
>>> There are many download pages you can model, e.g. 
>>> https://hadoop.apache.org/releases.html
>>> 
>>> If you need help, your mentors will be able to assist.
>>> 
>>> Best regards
>>> 
>>> Craig
>>> 
>>>> On Mar 20, 2019, at 1:24 PM, SHUANG SU  wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> The Apache ECharts (incubating) team is proud to announce Apache ECharts
>>>> version 4.2.1-incubating.
>>>> 
>>>> ECharts is a powerful, interactive charting and visualization library.
>>>> 
>>>> Vote thread:
>>>> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
>>>> 
>>>> Download Links:
>>>> https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
>>>> 
>>>> Release Notes:
>>>> http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
>>>> 
>>>> Website: http://echarts.apache.org/
>>>> 
>>>> ECharts Resources:
>>>> - Issue: https://github.com/apache/incubator-echarts/issues
>>>> - Mailing list: d...@echarts.incubator.apache.org
>>>> 
>>>> Thanks
>>>> 
>>>> --
>>>> Su Shuang (100pah)
>>>> --
>>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
> 
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org <mailto:c...@apache.org> http://db.apache.org/jdo 
> <http://db.apache.org/jdo>


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

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Dave Fisher]

Hi -

Also you can look at the sparkling new 
https://incubator.apache.org/clutch/echarts.html 
 under releases for compliant 
links.

Regards,
Dave

> On Mar 20, 2019, at 5:23 PM, Craig Russell  wrote:
> 
> Hi Su Shuang,
> 
> You will need to modify your download page to conform to requirements (an 
> announcement to incubator is not moderated but an announcement to 
> annou...@apache.org will be moderated, and this announcement will not pass).
> 
> You should never refer in the announcement or your download page to 
> dist.apache.org. For announcement emails, link to your download page. For 
> download pages, link to the mirror chooser and link to the checksum and 
> signature from www.apache.org/dist/incubator/echarts. Include a link to your 
> project KEYS file and instructions how to verify the download.
> 
> There are many download pages you can model, e.g. 
> https://hadoop.apache.org/releases.html
> 
> If you need help, your mentors will be able to assist.
> 
> Best regards
> 
> Craig
> 
>> On Mar 20, 2019, at 1:24 PM, SHUANG SU  wrote:
>> 
>> Hi all,
>> 
>> The Apache ECharts (incubating) team is proud to announce Apache ECharts
>> version 4.2.1-incubating.
>> 
>> ECharts is a powerful, interactive charting and visualization library.
>> 
>> Vote thread:
>> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
>> 
>> Download Links:
>> https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
>> 
>> Release Notes:
>> http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
>> 
>> Website: http://echarts.apache.org/
>> 
>> ECharts Resources:
>> - Issue: https://github.com/apache/incubator-echarts/issues
>> - Mailing list: d...@echarts.incubator.apache.org
>> 
>> Thanks
>> 
>> --
>> Su Shuang (100pah)
>> --
> 
> Craig L Russell
> c...@apache.org
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Release Apache ECharts (incubating) 4.2.1 (release candidate 3)

[Dave Fisher]

Hi -

+1 (binding)

I checked:
Signature.
Hash.
RAT Check
DISCLAIMER
LICENSE
NOTICE

Once the VOTE passes we need to discuss the download page setup for the 
ECharts.apache.org website.

Regards,
Dave

> On Mar 5, 2019, at 10:58 PM, SHUANG SU  wrote:
> 
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.2.1 (release candidate 3).
> 
> Apache ECharts community has voted and approved the release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/6f555bdb3bdc23ac9e260116738af779d4dff7b7e21f77c0a3369905@%3Cdev.echarts.apache.org%3E
> 
> Results thread:
> https://lists.apache.org/thread.html/54a63e2208330dd68c39bdcb5bd444301d0eb8580d433d1ac3fe4500@%3Cdev.echarts.apache.org%3E
> 
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/
> 
> 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=1a2e990
> 
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/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.1-rc.3/apache-echarts-4.2.1-rc.3-incubating-src.zip
> -o apache-echarts-4.2.1-rc.3-incubating-src.zip
> unzip apache-echarts-4.2.1-rc.3-incubating-src.zip -d
> apache-echarts-4.2.1-rc.3-incubating-src > /dev/null
> 
> # Rebuild the project (Node.js environment is required):
> cd "apache-echarts-4.2.1-rc.3-incubating-src" && npm install && cd ..
> node "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --release
> # (See help: `node
> "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --help`)
> ```
> 
> 
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.2.1 (release candidate 3)
> by "2019-03-09T07:42:38.040Z".
> 
> [ ] +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)
> --


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

Re: What could we do if no one votes on general mail list

[Dave Fisher]

Please be patient. I’ll take a look at the release tomorrow.

Sent from my iPhone

> On Mar 10, 2019, at 9:23 PM, Ovilia  wrote:
> 
> Dear mentors,
> 
> @SHUANG SU  sent a voting email to general mail
> list 5 days ago [1] and has got no reply ever since.
> What should we do to encourage PMC vote for our release candidate?
> 
> Thanks!
> 
> [1]
> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
> 
> 
> Zhang Wenli
> http://zhangwenli.com


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

Re: New issue creation helper

[Dave Fisher]

The Apache Way is to make sure that any decisions made in an “offline” 
conversation be brought back to dev@ mailing list. This will allow everyone 
interested including those who have little time to keep informed. 

This then becomes an easily searchable archive of the project’s decisions which 
the Foundation maintains in its permanent records. In preparing for one of my 
talks at COSCON I was searching back over 15 years ago to refresh my memory of 
the POI project’s history. If decisions were somewhere else that history would 
be lost.

Consider that a year from now someone new is interested in ECharts they can 
read the email archives and easily follow along.

If the project wants to use slack that is available. I know of one project that 
sends all the conversations for a week to its dev@ mailing list. I think gitter 
is ok, but I’ve never used it.

Regards,
Dave

Sent from my iPhone

> On Feb 28, 2019, at 9:37 PM, Ovilia  wrote:
> 
> Thanks, Dave.
> 
> I actually would like to know if we could have a more informal and short
> conversation form rather than mail list. Because we usually have to write a
> long email to state our point of view. And this may take too much time for
> some cases.
> I'm not sure if ASF would disapprove on this.
> 
> Here's a description about slack: https://slack.com/features
> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> Dave Fisher  于2019年3月1日周五 下午1:30写道：
> 
>> Hi -
>> 
>> Sent from my iPhone
>> 
>>> On Feb 28, 2019, at 9:24 PM, Ovilia  wrote:
>>> 
>>> I would also like to know the opinions of our mentors.
>>> Does ASF suggest we have the discussion in something like slack, or
>> should
>>> it always be in the mail list for more people to access?
>> 
>> The Mailing List allows for global asynchronous communication.
>> 
>> A project may have multiple Git repositories. If there is trouble using
>> Apache Git facilities then that needs discussion too.
>> 
>> Regards,
>> Dave
>>> 
>>> Zhang Wenli
>>> http://zhangwenli.com
>>> 
>>> 
>>> Ovilia  于2019年3月1日周五 下午1:18写道：
>>> 
>>>> Hi Clement.
>>>> 
>>>> Thanks for being interested in participation.
>>>> 
>>>> What kind of discussion do you mean?
>>>> 
>>>> If you wish to contribute code, you may filter issues labeled with "bug"
>>>> [1], "enhancement" or "new-feature".
>>>> If a "bug" issue is not labeled with a "pending" tag, it is checked by
>> our
>>>> committers to be a bug and should be fixed.
>>>> As for "enhancement" or "new-feature", I guess you should send an email
>> to
>>>> the dev mail list asking if this should be supported for now. This is
>>>> because some feature requests are used in a limited scenio, so we should
>>>> discuss about whether we should provide for all developers and increase
>> the
>>>> package size.
>>>> I also created a GitHub project [3] containing issues that are easier to
>>>> be fixed. So they are suggested for the beginners.
>>>> You may also filter with "en" tags for English discription. With the
>> help
>>>> of the new issue helper, the "en" tag is created automatically. But for
>>>> older issues, we may not have the effort to mark them all.
>>>> I'm working on the document about this information. And it will be
>>>> available in GitHub document later.
>>>> 
>>>> If it's about a bigger plan, like what's the next step we should take
>>>> (like features for next primary version v5.0.0), I guess it's the dev
>> mail
>>>> list for now. I'm not sure if we should use something like slack [2] or
>>>> gitter [3]. Slack seems a little closed to dev team rather than open to
>> the
>>>> public like mail lists, while gitter seems more keen on users rather
>> than
>>>> contributors and if we don't have the energy to maintain the how-to
>>>> questions in the channels, it may end up with giving users a higher
>>>> expectation than we could provide.
>>>> I guess slack could be an option for better instant and informal
>>>> communication than mail list, although it is also async, of course.
>> There
>>>> may also be a concern about not having many people participating in the
>>>> discussion. But I guess that is acceptable for the start, and we do
>> wish to
>>>> encourage more developers to particip

Re: New issue creation helper

[Dave Fisher]

Hi -

Sent from my iPhone

> On Feb 28, 2019, at 9:24 PM, Ovilia  wrote:
> 
> I would also like to know the opinions of our mentors.
> Does ASF suggest we have the discussion in something like slack, or should
> it always be in the mail list for more people to access?

The Mailing List allows for global asynchronous communication.

A project may have multiple Git repositories. If there is trouble using Apache 
Git facilities then that needs discussion too.

Regards,
Dave
> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> Ovilia  于2019年3月1日周五 下午1:18写道：
> 
>> Hi Clement.
>> 
>> Thanks for being interested in participation.
>> 
>> What kind of discussion do you mean?
>> 
>> If you wish to contribute code, you may filter issues labeled with "bug"
>> [1], "enhancement" or "new-feature".
>> If a "bug" issue is not labeled with a "pending" tag, it is checked by our
>> committers to be a bug and should be fixed.
>> As for "enhancement" or "new-feature", I guess you should send an email to
>> the dev mail list asking if this should be supported for now. This is
>> because some feature requests are used in a limited scenio, so we should
>> discuss about whether we should provide for all developers and increase the
>> package size.
>> I also created a GitHub project [3] containing issues that are easier to
>> be fixed. So they are suggested for the beginners.
>> You may also filter with "en" tags for English discription. With the help
>> of the new issue helper, the "en" tag is created automatically. But for
>> older issues, we may not have the effort to mark them all.
>> I'm working on the document about this information. And it will be
>> available in GitHub document later.
>> 
>> If it's about a bigger plan, like what's the next step we should take
>> (like features for next primary version v5.0.0), I guess it's the dev mail
>> list for now. I'm not sure if we should use something like slack [2] or
>> gitter [3]. Slack seems a little closed to dev team rather than open to the
>> public like mail lists, while gitter seems more keen on users rather than
>> contributors and if we don't have the energy to maintain the how-to
>> questions in the channels, it may end up with giving users a higher
>> expectation than we could provide.
>> I guess slack could be an option for better instant and informal
>> communication than mail list, although it is also async, of course. There
>> may also be a concern about not having many people participating in the
>> discussion. But I guess that is acceptable for the start, and we do wish to
>> encourage more developers to participate in.
>> 
>> In conclusion, we are still on the way to find a better solution for
>> contributing stuff. And you are always welcomed to give advice on it.
>> And thanks again for asking. :)
>> 
>> [1]
>> https://github.com/apache/incubator-echarts/issues?q=is%3Aopen+is%3Aissue+label%3Abug
>> [2] https://slack.com
>> [3] https://gitter.im
>> [4] https://github.com/apache/incubator-echarts/projects/3
>> 
>> Zhang Wenli
>> http://zhangwenli.com
>> 
>> 
>> Clement Ho  于2019年3月1日周五 下午12:27写道：
>> 
>>> I recently noticed that the issue template for the ECharts GitHub project
>>> now requests all new issues to be filled through
>>> https://ecomfe.github.io/echarts-issue-helper
>>> 
>>> I'm all for better issue management but I was wondering if there was some
>>> kind of open discussion about this that I could participate in or observe?
>>> Is there another mailing list or other form of communication tool that is
>>> being used apart from this dev mailing list?
>>> 
>>> 
>>> Clement
>>> 
>> 


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

Re: Subscribe to the mailing list

[Dave Fisher]

To subscribe, e-mail: dev-subscr...@echarts.apache.org 
 and reply to the confirmation email 
as instructed.

Regards,
Dave

> On Feb 27, 2019, at 11:25 AM, José Iván Vargas López  
> wrote:
> 
> Hi!
> 
> I'd like to subscribe to the dev echarts mailing list
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org

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

[Dave Fisher]

[X] +1 Release this package (BINDING)

I checked:
DISCLAIMER
LICENSE
NOTICE
Signature
 sha512 Hash
RAT Check passed.

Next release let’s discuss where the BSD License is placed. Since there is only 
one extra license the usual location is the end of the main LICENSE file. (Also 
the how to apply portion at the bottom of the LICENSE is not needed.)

Here is how I performed a RAT Check:

Previously I downloaded Apache RAT from creadur.apache.org

java -jar ~/Development/apache-rat-0.12.jar .

Regards,
Dave

> On Feb 25, 2019, at 1:47 AM, SHUANG SU  wrote:
> 
> I am pleased to be calling this vote for the release of Apache ECharts
> 4.2.1 (release candidate 2).
> 
> The major update from 4.2.1 release candidate 1 to 2 is about the license
> statement.
> See more details in
> https://lists.apache.org/thread.html/3817a70b2ec34a25b82f4a1310398ae9df8cdc6728fa289c941c5fde@%3Cdev.echarts.apache.org%3E
> 
> 
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-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=f2d76c9
> 
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-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.1-rc.2/apache-echarts-4.2.1-rc.2-incubating-src.zip
> -o apache-echarts-4.2.1-rc.2-incubating-src.zip
> unzip apache-echarts-4.2.1-rc.2-incubating-src.zip -d
> apache-echarts-4.2.1-rc.2-incubating-src > /dev/null
> 
> # Build the project (Node.js environment is required):
> cd "apache-echarts-4.2.1-rc.2-incubating-src" && npm install && cd ..
> node "apache-echarts-4.2.1-rc.2-incubating-src/build/build.js" --release
> # (See help: `node
> "apache-echarts-4.2.1-rc.2-incubating-src/build/build.js" --help`)
> ```
> 
> 
> Please vote on releasing this package as:
> Apache ECharts 4.2.1 (release candidate 2)
> by "2019-02-28T10:34:16.092Z".
> 
> [ ] +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: Steps to Complete the Move from Baidu to Apache

[Dave Fisher]

> On Feb 21, 2019, at 5:18 PM, Justin Mclean  wrote:
> 
> HI,
> 
>> Not sure what you mean about 3rd party, etc. but there are definitely
>> analytics/urchin tags on some of the ASF Sites.
> 
> In this case the analytics are being collected at 3rd party domains and all 
> the PPMC (I’m assuming) wouldn’t have access to them or may not even know 
> what’s been done with them.
> 
> This is slightly different to say using google where the PPMC has access to 
> the info collected. The domains are hm.baidu.com and echarts.baidu.com.

That’s the issue. It’s not vendor neutral and not in control of a future 
diverse PPMC.

Regards,
Dave


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


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

Re: PODLINGNAMESEARCH-153 Establish whether "Apache ECharts" is a suitable name

[Dave Fisher]

> On Feb 20, 2019, at 10:53 PM, Ovilia  wrote:
> 
> Dave,
> 
> Thanks for the reminding.
> Yes, we wish to use ECharts as our project name, because this is a name
> well known for our users, which is of a great number and I didn't see any
> violation here.
> 
> So what should we do next?

Please see https://incubator.apache.org/guides/names.html 
<https://incubator.apache.org/guides/names.html> for information on how to 
conduct the name search. Note is is the podling that is expected to undertake 
this work

Your enter results on the JIRA issue here 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153 
<https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153>

Ask questions here or on priv...@echarts.apache.org 
<mailto:priv...@echarts.apache.org>

Regards,
Dave

> 
> Zhang Wenli
> http://zhangwenli.com
> 
> 
> On Thu, Feb 21, 2019 at 8:24 AM Dave Fisher  wrote:
> 
>> Hi -
>> 
>> Here is a reminder to complete your research on whether ECharts is a
>> suitable name for the project.
>> 
>> Regards,
>> Dave
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
>> 

PODLINGNAMESEARCH-153 Establish whether "Apache ECharts" is a suitable name

[Dave Fisher]

Hi -

Here is a reminder to complete your research on whether ECharts is a suitable 
name for the project.

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

Steps to Complete the Move from Baidu to Apache

[Dave Fisher]

I wanted to provide guidance on moving the ECharts website to Apache. Both the 
Chinese site and the English site need to be hosted on the echarts.apache.org 
domain and have the source stored in GitHub(GitBox) in the 
apache/incubator-echarts-website repository. There is work to do and that will 
include some that is mandated by Apache policies.

(1) Move echarts.baidu.com . [1][3]

The target here is likely to be something like echarts.apache.org/zh 
 and echarts.apache.org/en 
 with echarts.apache.org/ 
 being smart (or dumb) about picking the best for 
the user. Once the project has that in place then a redirection rule should be 
added to echarts.baidu.com  to properly permanently 
redirect any url to the same resource on echarts.apache.org 
.

The IPMC expects to see movement on this via pull requests soon. If there are 
any differences in support between the Baidu served site and what Apache 
provides then please let us ASAP.

(2) Required navigation links for Apache Projects. [2]

You must include links to www.apache.org  along with 
the Apache License and other requirements. See [2]

(3) Proper attribution of trademarks is required. [4]

You have this mostly correct on the English site.

(4) The Download page needs to follow release distribution policy [5]

Specifically, you must describe where to find the release using the Apache 
mirror system. This mirrors 
https://dist.apache.org/repos/dist/release/incubator/echarts/ 
 and a LUA file 
is provided to select the closest mirror. You must point to the KEYS file and 
describe how to verify the download using the asc, and sha512 found there.

Also, once the Release is approved the RC artifacts should be renamed to remove 
the RC designation.

(5) Who is responsible for these resources and if it is the PPMC then each will 
need discussion.

(a) https://gallery.echartsjs.com/editor.html 

(b) https://twitter.com/EChartsJs  (where 
there’s no indication it’s an ASF project and links to ecomfe.github.io 
)
(c) https://www.weibo.com/echarts  (similar)

(6) Links and pages.

(a) At the bottom of the main page the link is to a Baidu.com mailing list. 
This must be changed to point users and developers to dev@echarts.apache.org 
.
(b) Also the GitHub link must point directly to 
https://github.com/apache/incubator-echarts/ 

(c) On the builder.html the email capture should be replaced with information 
or link to the project mailing list page.
(d) Contributions and FAQ page should include references to the mailing lists.
(e) Top links are not coming from the Apache repos. [6]

(7) User logging is likely not necessary and may be illegal in many countries 
and it should be removed in many locations. These include:

(a) Looks like user tracking via a hm.baidu.com  link on 
several pages. Please remove.
(b) another tracker in log.js again pointing to echarts.baidu.com 
 [7]

(8) On the Builder please explain which release files are used and where they 
are sourced.

Your Mentors are here to help!

Hat tip to Justin Mclean for uncovering several of these issues.

Best Regards,
Dave

[1] https://www.apache.org/foundation/marks/pmcs#websites 

[2] https://www.apache.org/foundation/marks/pmcs#navigation 

[3] https://www.apache.org/foundation/marks/pmcs#nonapache 

[4] https://www.apache.org/foundation/marks/pmcs#attributions 

[5] https://www.apache.org/dev/release-distribution.html 

[6] 
https://raw.githubusercontent.com/ecomfe/echarts/4.1.0/dist/echarts.simple.min.js
 

[7] https://github.com/apache/incubator-echarts-website/blob/asf-site/js/log.js 

Re: [incubator-echarts-website] branch asf-site updated: release 4.2.1-rc1

[Dave Fisher]

Hi -

Additional information.

> On Feb 7, 2019, at 2:44 PM, Dave Fisher  wrote:
> 
> Hi Devs -
> 
> We need to have a clarifying discussion about Releases, RCs and Tags. We also 
> need to be clear on “pre-apache” releases.
> 
> Let’s discuss from lifecycle.
> 
> (1) The repository is tagged as ready for a release candidate to be created.
> (2) The release candidate is created and may be made available to vote on 
> from the dev/incubator/echarts directory on dist.apache.org. It can also be 
> made into a Draft/pre-release Release on GitHub.
> (3) Once an RC has passed the VOTE on dev@echarts and general@incubator it is 
> svn moved to release/incubator/echarts and can be marked as the Latest on 
> Github. Renaming these to remove the RC# is a good idea.
> 
> https://echarts.apache.org/download.html 
> <https://echarts.apache.org/download.html> should not have been updated since 
> 4.2.1-rc1 has not yet passed an IPMC vote. Sorry sometimes it is slow. We can 
> continue to adjust, but… in Incubation the IPMC vote is required. You need to 
> revert to 4.1.0.
> 
> Let’s discuss the current state on Github Releases tab - 
> https://github.com/apache/incubator-echarts/releases
> 
> The only release listed is still an RC which has yet to pass. This needs to 
> be marked as
> Pre-apache releases edited to adjust their title to include “ (pre-Apache 
> release)”.
> Prior IPMC approved ECharts releases can be left in GitHub. RCs that did not 
> pass should be marked as Draft and or have the “pre-release” flag checked.

Releases mentioned here need to be of two varieties.
(a) Pre-Apache releases.
(b) Approved Apache Releases - (Unapproved Releases may be shown if they are 
Draft or “Pre-Release”)

ALSO - NPM.

https://www.npmjs.com/package/echarts <https://www.npmjs.com/package/echarts>

NO RCs - only (a) pre-Apache and (b) Approved Apache Releases.
Please update the license

Releases to non-Apache distributions are termed NOT OFFICIAL RELEASES - non the 
less these must be built from approved official source releases.

See http://www.apache.org/legal/release-policy.html 
<http://www.apache.org/legal/release-policy.html>

Mentors are here to answer questions.

Regards,
Dave

> 
> Please update and ask your Mentors to review.
> 
> Regards,
> Dave
> 
>> On Feb 7, 2019, at 2:06 PM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>> I just saw that this commit added a link to the download page for a release 
>> candidate. [1] Why was this done?
>> 
>> We've just had a long discussion that the PPMC cannot advertise or link to 
>> unreleased material. [2] Again "Do not include any links on the project 
>> website that might encourage non-developers to download and use nightly 
>> builds, snapshots, release candidates, or any other similar package"
>> 
>> Thanks,
>> Justin
>> 
>> 1. https://echarts.apache.org/download.html
>> 2. http://www.apache.org/legal/release-policy.html#what
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
> 

Re: [incubator-echarts-website] branch asf-site updated: release 4.2.1-rc1

[Dave Fisher]

Hi Devs -

We need to have a clarifying discussion about Releases, RCs and Tags. We also 
need to be clear on “pre-apache” releases.

Let’s discuss from lifecycle.

(1) The repository is tagged as ready for a release candidate to be created.
(2) The release candidate is created and may be made available to vote on from 
the dev/incubator/echarts directory on dist.apache.org. It can also be made 
into a Draft/pre-release Release on GitHub.
(3) Once an RC has passed the VOTE on dev@echarts and general@incubator it is 
svn moved to release/incubator/echarts and can be marked as the Latest on 
Github. Renaming these to remove the RC# is a good idea.

https://echarts.apache.org/download.html 
 should not have been updated since 
4.2.1-rc1 has not yet passed an IPMC vote. Sorry sometimes it is slow. We can 
continue to adjust, but… in Incubation the IPMC vote is required. You need to 
revert to 4.1.0.

Let’s discuss the current state on Github Releases tab - 
https://github.com/apache/incubator-echarts/releases

The only release listed is still an RC which has yet to pass. This needs to be 
marked as
Pre-apache releases edited to adjust their title to include “ (pre-Apache 
release)”.
Prior IPMC approved ECharts releases can be left in GitHub. RCs that did not 
pass should be marked as Draft and or have the “pre-release” flag checked.

Please update and ask your Mentors to review.

Regards,
Dave

> On Feb 7, 2019, at 2:06 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> I just saw that this commit added a link to the download page for a release 
> candidate. [1] Why was this done?
> 
> We've just had a long discussion that the PPMC cannot advertise or link to 
> unreleased material. [2] Again "Do not include any links on the project 
> website that might encourage non-developers to download and use nightly 
> builds, snapshots, release candidates, or any other similar package"
> 
> Thanks,
> Justin
> 
> 1. https://echarts.apache.org/download.html
> 2. http://www.apache.org/legal/release-policy.html#what
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org
> 

Re: License for using 3rd-party code (ECharts podling question)

[Dave Fisher]

Sorry wrong podling in the subject.

> On Feb 4, 2019, at 11:28 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> I did a quick look at these files and want to try to state the situation 
> simply.
> 
> (A) <1><2><3><4><6> all represent code that was inspired by the study of D3 
> but are substantially different and never were a direct derivation. As such 
> ALv2 is appropriate while it is inspired by D3 with a BSD-3 license.
> 
> (B) <5> I need clarification. Is this more like the others in case (A) or was 
> it once a D3 copy that is from prior to 2013? If so then the file should 
> remain BSD-3 with a note that it is substantially modified?
> 
> IMO - the podling is doing a reasonable approach.
> 
> Legal peeps - what do you think?
> 
> Regards,
> Dave
> 
>> On Feb 1, 2019, at 11:03 AM, SHUANG SU > <mailto:sushuang0...@gmail.com>> wrote:
>> 
>> 
>> Hi,
>> 
>> Thanks a lot for the attention and checking.
>> 
>> > > To be more specific, here are some types of files:
>> > > 1. Some part of a file (maybe several lines, or a short function) is 
>> > > copied directly from a 3rd-party implementation, but others are 
>> > > implemented by ourselves.
>> > > 2. The code is implemented by us, but the general idea or algorithm is 
>> > > inspired by 3rd-party.
>> 
>> > ASF policy [1] states that you should not add the standard Apache License 
>> > header to the top of third-party source files, and only if major 
>> > modifications are done then the (P)PMC should decide what to do. IMO that 
>> > decision would need to be documented on the mailing list. INAL but from 
>> > what I’ve  seen previously option 2 is generally not enough change to 
>> > change the 3rd party license.
>> 
>> In my opinion, both the cases that a code snippet "copied from a 3rd-party" 
>> or "the idea/algorithm inspired by 3rd-party" 
>> need to follow the third-party license. In fact, in the current source code 
>> of Apache-echarts, there
>> is no case that "a code snippet need to change the origin third-party 
>> license".
>> 
>> But the key point we are confused and discussed here is:
>> "how to arrange the presence of the license statement in the source code 
>> files
>> when some code follows the Apache License and some follows the third-party 
>> license".
>> 
>> To find a practicable way to solve this issue and guide the future coding,
>> I think we need to go deep into these source files:
>> 
>> These source files of the release candidate of Apache-echarts 4.2.1-rc.1
>> ( https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.1/ 
>> <https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.1/> )
>> are questioned about the embedded third-party license:
>> 
>> <1> src/util/number.js
>> <2> src/chart/treemap/treemapLayout.js
>> <3> src/chart/tree/layoutHelper.js
>> <4> src/chart/graph/forceHelper.js
>> <5> src/util/array/nest.js
>> <6> src/scale/Time.js
>> 
>> ASF policy [1] states that you should not add the standard Apache License 
>> header to the top of third-party source files.
>> But in the questioned source files listed above, file <1><2><3><4><6> are 
>> not from the third-party.
>> They are made up by the code of Apache-echarts itself, but including some 
>> "code snippet"
>> copied from or algorithm learned from the third-party library "d3", which is 
>> under BSD 3-Clause.
>> So these files have the Apache License header and embed d3 license next to 
>> the corresponding "code snippet".
>> And for standing out for the users, there is also a statement such as 
>> "the implementation references to d3 and follows d3 license ..." on the top 
>> of the file, next to the Apache License header.
>> 
>> So in my opinion <1><2><3><4><6> does not break the ASF policy [1], because 
>> they are not the third-party source file, 
>> but an Apache-licensed source file with third-party license embedded.
>> 
>> Let's take the file "src/chart/treemap/treemapLayout.js" as an example:
>> The code snippet "squarify" ( 
>> https://github.com/apache/incubator-echarts/blob/9234f0309137250a2561212e8ecd1639551119b1/src/chart/treemap/treemapLayout.js#L166
>>  
>> <https://github.com/apache/incubator-echarts/blob/9234f0309137250a2561212e8ecd163955111

Re: License for using 3rd-party code (Doris podling question)

[Dave Fisher]

Hi -

I did a quick look at these files and want to try to state the situation simply.

(A) <1><2><3><4><6> all represent code that was inspired by the study of D3 but 
are substantially different and never were a direct derivation. As such ALv2 is 
appropriate while it is inspired by D3 with a BSD-3 license.

(B) <5> I need clarification. Is this more like the others in case (A) or was 
it once a D3 copy that is from prior to 2013? If so then the file should remain 
BSD-3 with a note that it is substantially modified?

IMO - the podling is doing a reasonable approach.

Legal peeps - what do you think?

Regards,
Dave

> On Feb 1, 2019, at 11:03 AM, SHUANG SU  wrote:
> 
> 
> Hi,
> 
> Thanks a lot for the attention and checking.
> 
> > > To be more specific, here are some types of files:
> > > 1. Some part of a file (maybe several lines, or a short function) is 
> > > copied directly from a 3rd-party implementation, but others are 
> > > implemented by ourselves.
> > > 2. The code is implemented by us, but the general idea or algorithm is 
> > > inspired by 3rd-party.
> 
> > ASF policy [1] states that you should not add the standard Apache License 
> > header to the top of third-party source files, and only if major 
> > modifications are done then the (P)PMC should decide what to do. IMO that 
> > decision would need to be documented on the mailing list. INAL but from 
> > what I’ve  seen previously option 2 is generally not enough change to 
> > change the 3rd party license.
> 
> In my opinion, both the cases that a code snippet "copied from a 3rd-party" 
> or "the idea/algorithm inspired by 3rd-party" 
> need to follow the third-party license. In fact, in the current source code 
> of Apache-echarts, there
> is no case that "a code snippet need to change the origin third-party 
> license".
> 
> But the key point we are confused and discussed here is:
> "how to arrange the presence of the license statement in the source code files
> when some code follows the Apache License and some follows the third-party 
> license".
> 
> To find a practicable way to solve this issue and guide the future coding,
> I think we need to go deep into these source files:
> 
> These source files of the release candidate of Apache-echarts 4.2.1-rc.1
> ( https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.1/ 
>  )
> are questioned about the embedded third-party license:
> 
> <1> src/util/number.js
> <2> src/chart/treemap/treemapLayout.js
> <3> src/chart/tree/layoutHelper.js
> <4> src/chart/graph/forceHelper.js
> <5> src/util/array/nest.js
> <6> src/scale/Time.js
> 
> ASF policy [1] states that you should not add the standard Apache License 
> header to the top of third-party source files.
> But in the questioned source files listed above, file <1><2><3><4><6> are not 
> from the third-party.
> They are made up by the code of Apache-echarts itself, but including some 
> "code snippet"
> copied from or algorithm learned from the third-party library "d3", which is 
> under BSD 3-Clause.
> So these files have the Apache License header and embed d3 license next to 
> the corresponding "code snippet".
> And for standing out for the users, there is also a statement such as 
> "the implementation references to d3 and follows d3 license ..." on the top 
> of the file, next to the Apache License header.
> 
> So in my opinion <1><2><3><4><6> does not break the ASF policy [1], because 
> they are not the third-party source file, 
> but an Apache-licensed source file with third-party license embedded.
> 
> Let's take the file "src/chart/treemap/treemapLayout.js" as an example:
> The code snippet "squarify" ( 
> https://github.com/apache/incubator-echarts/blob/9234f0309137250a2561212e8ecd1639551119b1/src/chart/treemap/treemapLayout.js#L166
>  
> 
>  ) is learned from d3 ( 
> https://github.com/d3/d3/blob/28acd11a242245b8bd32cfcdaaa8d7d382c6272f/src/layout/treemap.js#L30
>  
> 
>  ) on the skeleton of the algorithm.
> But the entire file is the implementation of the echarts treemap, including 
> not only the learned part but also lots of other logic 
> related to each other and not appropriate to be separated.
> So I think the file "src/chart/treemap/treemapLayout.js" should be under the 
> Apache License header, and have d3 license embedded in some of the code.
> 
> And about the file <5>, the whole file is modified from the previous version 
> of d3 (the version is about 3 years ago, 
> https://github.com/d3/d3/blob/9cc9a875e636a1dcf36cc1e07bdf77e1ad6e2c74/src/arrays/nest.js
>  
> 
>  ). So this file
> probably should be under the d3 license, 

Re: ECharts incubator report

[Dave Fisher]

Please do not use Cordova as an example of a conforming project.

Let’s discuss how to properly use of npm and staying where snapshots require 
explicit user choice.

Regards,
Dave

Sent from my iPhone

> On Feb 2, 2019, at 3:52 PM, Clement Ho  wrote:
> 
> I just want to note that another popular apache project, cordova seems to
> publish nightly builds to npm (
> https://www.npmjs.com/package/cordova)
> 
> But it does look like the ‘latest’ tag is always set to the approved
> release for public use. Perhaps echarts can mimic their exact model?
> 
> Clement
> 
>> On Sun, Feb 3, 2019 at 7:28 AM Justin Mclean  wrote:
>> 
>> Hi,
>> 
>> I can see that nothing has been done about [1]. The PPMC cannot provide
>> unapproved releases to the general public in this manner. [2] All releases
>> must be approved by the PPMC and IPMC while in incubation. As the VP of the
>> Apache Incubator I'm asking you to please remove this unapproved release
>> and any others you have made public since starting graduation.
>> 
>> If you can come up with another solution that complies with the ASF
>> release policy I'm willing to listen to it.
>> 
>> Thanks,
>> Justin
>> V.P. Incubator
>> 
>> 1. https://www.npmjs.com/package/echarts
>> 2. http://www.apache.org/legal/release-policy.html#release-approval
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
>> 


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

Re: Chinese site echarts.baidu.com Was:: [VOTE] Release Apache ECharts 4.2.1 (release candidate 1)

[Dave Fisher]

Hi -

It look like there are several ECharts in the ecomfe repositories - 
https://github.com/ecomfe?utf8=✓=echarts== 
<https://github.com/ecomfe?utf8=%E2%9C%93=echarts==>

Which are essential to ECharts? Those that are ought to become part of this 
project. There are several concerns including licensing, etc. First let’s 
review the list.

Regards,
Dave

> On Jan 30, 2019, at 2:27 PM, Clement Ho  wrote:
> 
> The docs are a little confusing and could use some help:
> 
>   - Google search results vary between ECharts docs originating from the
>   following websites:
>  - https://ecomfe.github.io/echarts-doc/public/en/
>  
>  - http://echarts.apache.org/
>  
>  - http://echarts.baidu.com
>  - http://echarts.apache.org should redirect to
>   https://echarts.apache.org
>   - https://github.com/ecomfe/echarts-doc is the repo for the docs, should
>   that be under apache as well?
> 
> 
> 
> On Wed, Jan 30, 2019 at 4:03 PM Dave Fisher  wrote:
> 
>> Hi Justin,
>> 
>> You are looking at the Chinese version of this: https://echarts.apache.org
>> <https://echarts.apache.org/>
>> 
>> I think that a reasonable solution for the pooling may be to put this
>> website up on https://echarts.apache.org/zh/ <
>> https://echarts.apache.org/zh/> and then redirect. That would fit Apache
>> Branding requirements. ECharts has 32,319 Stars and 9,403 Forks most of
>> which are in China. Performance might be an issue.
>> 
>> Echarts Devs would you please look into moving the Chinese site to ASF
>> Infrastructure. Once that is done properly then we can consider the best
>> way to handle echarts.baidu.com domain. Perhaps there are some creative
>> ways to handle this …
>> 
>> Regards,
>> Dave
>> 
>>> On Jan 30, 2019, at 1:23 PM, Justin Mclean 
>> wrote:
>>> 
>>> There is also possible a more serious issue re branding, trademarks and
>> project independence. Now it possible that this has already been discussed,
>> and there are plans to remove it, but what is being done about this domain
>> name? https://echarts.baidu.com <https://echarts.baidu.com/>. Please add
>> something in your podling report about this.
>> 
>> 

Chinese site echarts.baidu.com Was:: [VOTE] Release Apache ECharts 4.2.1 (release candidate 1)

[Dave Fisher]

Hi Justin,

You are looking at the Chinese version of this: https://echarts.apache.org 


I think that a reasonable solution for the pooling may be to put this website 
up on https://echarts.apache.org/zh/  and then 
redirect. That would fit Apache Branding requirements. ECharts has 32,319 Stars 
and 9,403 Forks most of which are in China. Performance might be an issue.

Echarts Devs would you please look into moving the Chinese site to ASF 
Infrastructure. Once that is done properly then we can consider the best way to 
handle echarts.baidu.com domain. Perhaps there are some creative ways to handle 
this …

Regards,
Dave

> On Jan 30, 2019, at 1:23 PM, Justin Mclean  wrote:
> 
> There is also possible a more serious issue re branding, trademarks and 
> project independence. Now it possible that this has already been discussed, 
> and there are plans to remove it, but what is being done about this domain 
> name? https://echarts.baidu.com . Please add 
> something in your podling report about this.

Re: ECharts incubator report

[Dave Fisher]

Hi -

Also, the project did begin discussions about adding a committer on private@. 
These stalled, but can be restarted now.

Regards,
Dave

Sent from my iPhone

> On Jan 30, 2019, at 7:24 AM, Kevin A. McGrail  wrote:
> 
> Nice response Shuang.  If I can help with the voting process for
> releases, etc., please let me know.
> 
> I can also try to help with adding more committers, writing notices,
> etc. to try and get more interest on Social Media even.
> 
> Regards,
> KAM
>> On 1/30/2019 3:11 AM, SHUANG SU wrote:
>> Hi Justin,
>> 
>> I am afraid it is inevitable to push the rc version to npm. Without that,
>> the build
>> process and some local CI process can not be performed, which causes the
>> developers
>> concerning about this project can not test whether the release candidate is
>> qualified to be released.
>> But the rc version is not tagged as "latest" in npm, so the public can not
>> get this version
>> by `npm install`. So it will not make bad effect, just like publishing the
>> rc pack to the
>> Apache svn dev repo [1].
>> 
>> But the published `4.2.0-rc.2` on npm you saw in [2] is tagged as "latest"
>> and have been
>> published to the public. That is incorrect according to the Apache rule. We
>> should have
>> removed it. But unfortunately we have missed the opportunity to do that.
>> Many outsider
>> projects or systems have depended on that, and the removal will cause some
>> disaster.
>> 
>> This mistake was made because we did not clear enough about the total
>> release process.
>> But having this experience, this mistake will not happen again. Only the
>> official release
>> will be directed to publish in npm from now on.
>> 
>> 1. https://dist.apache.org/repos/dist/dev/incubator/
>> 2. https://www.npmjs.com/package/echarts
>> 
>> 
>> Thanks
>> 
>> --
>> Su Shuang (100pah)
>> --
>> 
>> 
>> 
>>> On Wed, 30 Jan 2019 at 15:14, Justin Mclean  wrote:
>>> 
>>> HI,
>>> 
 As about "When were the last committers or PPMC members elected?", we
>>> don't have new committers or PPMC members elected after the initiation. So
>>> should I fill in NA or the initiation date?
>>> 
>>> Yes, but being a year in incubation without adding any committer or PMC
>>> members is concerning, especially given the number of contributors to the
>>> project. You might want to put in the report what is being done to address
>>> this.There’s some tasks mentioned on the private list that need to be
>>> followed up on by the PPMC I think.
>>> 
 As about release version, we tagged "rc" for release candidate version.
>>> Does that mean rc version can never be available to the public?
>>> 
>>> Release candidates should not be made available to the general public,
>>> they can be made available to people who follow the dev list. [1] They can
>>> be placed here. [2]
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 1. https://www.apache.org/dev/release-distribution#unreleased
>>> 2. http://www.apache.org/legal/release-policy.html#stage
>>> 
>>> 
>>> 
> 
> -- 
> Kevin A. McGrail
> VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org
> 


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

Re: Nominating cuijian-dexter as new committer of incubator-echarts

[Dave Fisher]

Hi -

Nominations to Committer and PMC membership are handled on the private@echarts 
mailing list in order to avoid any embarrassment if anyone has a concern. 
Concerns could be trivial like I’d like to make sure that the person has 
provided a good code review or have they provided sustained help on the mailing 
list.

Discussing what criteria ought to qualify a person to be seriously considered 
can certainly be discussed on dev@echarts.

Regards,
Dave

Sent from my iPhone

> On Jan 8, 2019, at 10:26 PM, Ovilia  wrote:
> 
> Dear all,
> 
> I would like to nominate @cuijian-dexter  
> to
> be our first new committer of incubator-echarts project, who has been
> continuously contributing both to the repo and the community over the past
> several months.
> 
> 
> *Main Contributions*
> 
> 1. He has contributed four pull requests
> 
> by now, three of which have already been merged, and the other one under
> review.
> Take his first PR #8759
>  as example, he
> provided a new funnel layout policy, which enables displaying text inside
> funnels on the left or right side. This could be helpful to others who have
> such chart design.
> During the process of reviewing the PR, he behaved in a well open-minded
> way, quick to response, and willing to help.
> 
> 2. He's also quite active and helpful in issue discussions and helped
> others to solve problems.
> For example, in #9281
> , he made an
> online demo to help the author solve the problem.
> 
> A full list of contributions may be found here
> 
> .
> 
> 
> In conclusion, I would like to nominate him as our new committer, both to
> thank him for the contribution to the community, and also to encourage him
> and other contributors like him to help the community grow.
> 
> Please give your opinion and +1 if you agree.
> 
> Zhang Wenli
> http://zhangwenli.com


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

Re: Criteria for new ECharts committers

[Dave Fisher]

Hi -

> On Nov 7, 2018, at 1:32 AM, SHUANG SU  wrote:
> 
>> 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.
> 
> Different issues require different efforts and different level of tech
> knowledge & skills (about this domain and this project). A PR can be
> as simple as changing a typo of a comment, or as complex as modifying
> the underlying framework of the program. So I am afraid it is not a good
> idea
> to make an accurate number of PR and issues as a standard of becoming a
> committer.
> I agree that a candidate need to send application, and the PMC will
> make discussion and investigate that by the historic contribution and other
> factors.

The PPMC needs to look for contributions, we should not take applications.

There is one way that a contributor can indicate that they wish to be a 
committer. That is submitting an Individual Contributors Agreement and 
indicating that they want to be part of ECharts.


> 
>> 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.
> 
> I agree with that the PR rule, at least in the current stage. Because
> currently
> in practice, the quality of the commits is not good enough to remit the
> code review.
> And a code review makes others think about an issue, that always
> brings some
> issues that not thought of before.

The quality of PRs should be an indication about whether or not a contributor 
is ready to be a committer.

Be ready to consider non-code / documentation / translation help as ways for 
contributors to gain merit.

Regards,
Dave


> 
> 
> --
> Su Shuang (100pah)
> --
> 
> 
> 
> On Wed, 7 Nov 2018 at 16:29, Wenli Zhang  wrote:
> 
>> 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
 
>>> 
>> 


-
To 

Fwd: Beam's recent community development work

[Dave Fisher]

Hi -

Here is a model form the Apache Beam project that may be worth considering for 
ECharts.

Note that identifying people asking good questions starts the process. This can 
be how non-code contributors are identified.

Regards,
Dave

> Begin forwarded message:
> 
> From: Kenneth Knowles 
> Subject: Beam's recent community development work
> Date: June 29, 2018 at 11:15:02 PM PDT
> To: d...@community.apache.org, memb...@apache.org, Griselda Cuevas 
> , dev 
> Reply-To: memb...@apache.org
> 
> Hi all,
> 
> The ASF board suggested that we (Beam) share some of what we've been doing 
> for community development with d...@community.apache.org 
>  and memb...@apache.org 
> . So here is a long description. I have included 
> d...@beam.apache.org  because it is the subject, 
> really, and this is & should be all public knowledge.
> 
> We would love feedback! We based a lot of this on reading the community 
> project site, and probably could have learned even more with more study.
> 
> # Background
> 
> We face two problems in our contributor/committer-base:
> 
> 1. Not enough committers to review all the code being contributed, in part 
> due to recent departure of a few committers
> 2. We want our contributor-base (hence committer-base) to be more spread 
> across companies and backgrounds, for the usual Apache reasons. Our user base 
> is not active and varied enough to make this automatic. One solution is to 
> make the right software to get a varied user base, but that is a different 
> thread :-) so instead we have to work hard to build our community around the 
> software we have.
> 
> # What we did
> 
> ## Committer guidelines
> 
> We published committer guidelines [1] for transparency and as an invitation. 
> We start by emphasizing that there are many kinds of contributions, not just 
> code (we have committers from community development, tech writing, training, 
> etc). Then we have three aspects:
> 
> 1. ASF code of conduct
> 2. ASF committer responsibilities
> 3. Beam-specific committer responsibilities
> 
> The best way to understand is to follow the link at the bottom of this email. 
> The important part is that you shouldn't be proposing a committer for other 
> reasons, and you shouldn't be blocking a committer for other reasons.
> 
> ## Instead of just "[DISCUSS] Potential committer XYZ" we discuss every layer
> 
> Gris (CC'd) outlined this: people go through these phases of relationship 
> with our project:
> 
> 1. aware of it
> 2. interested in it / checking it out
> 3. using it for real
> 4. first-time contributor
> 5. repeat contributor
> 6. committer
> 7. PMC
> 
> As soon as we notice someone, like a user asking really deep questions, we 
> invite discussion on private@ on how we can move them to the next level of 
> engagement.
> 
> ## Monthly cadence
> 
> Every ~month, we call for new discussions and revisit ~all prior discussions. 
> This way we do not forget to keep up this effort.
> 
> ## Individual discussions
> 
> For each person we have a separate thread on private@. This ensures we have 
> quality focused discussions that lead to feedback. In collective discussions 
> that we used to do, we often didn't really come up with actionable feedback 
> and ended up not even contacting potential committers to encourage them. And 
> consensus was much less clear.
> 
> ## Feedback!
> 
> If someone is brought up for a discussion, that means they got enough 
> attention that we hope to engage them more. But unsolicited feedback is never 
> a good idea. For a potential committer, we did this:
> 
> 1. Send an email saying something like "you were discussed as a potential 
> committer - do you want to become one? do you want feedback?"
> 2. If they say yes (so far everyone) we send a few bullet points from the 
> discussion and *most important* tie each bullet to the committer guidelines. 
> If we have no feedback about which guidelines were a concern, that is a red 
> flag that we are being driven by bias.
> 
> We saw a *very* significant increase in engagement from those we sent 
> feedback to, and the trend is that they almost all will become committers 
> over time.
> 
> ## Results
> 
>  - Q1 we had no process and we added no new committers or PMC members.
>  - Q2 when we tried these new things we added 7 committers and 1 PMC member, 
> with ~3~4 obvious committer candidates for next time around, plus positive 
> feedback from other contributors, spread across five companies.
> 
> We've had a pretty major uptick in building Beam as a result.
> 
> ## Review-then-commit
> 
> We are dedicated to RTC as the best way to build software. Reviews not only 
> make the code better, but (with apologies to ASF/GNU differences) as RMS says 
> "The fundamental act of friendship among programmers is the sharing of 
> programs" and reviews are where we do that.
> 
> As a minor point, we also changed our 

Re: ICLA of new committer

[Dave Fisher]

Hi -

It seems that only the mentors are subscribed to priv...@echarts.apache.org 
<mailto:priv...@echarts.apache.org>

If you are an initial committer then please subscribe by sending an email to 
private-subscr...@echarts.apache.org 
<mailto:private-subscr...@echarts.apache.org>

This subscription will moderated by one of your mentors. This may take some 
time. In a few hours I will be on my way to the airport to fly to Shenzhen.

Here are the PPMC/Committers:
deqingli <https://whimsy.apache.org/roster/ppmc/committer/deqingli> 
Deqing Li   
errorrik <https://whimsy.apache.org/roster/ppmc/committer/errorrik> 
Dong Rui
dafo <https://whimsy.apache.org/roster/ppmc/committer/dafo> Houjin 
Huang
wangdd <https://whimsy.apache.org/roster/ppmc/committer/wangdd> Junting 
Wang
kener <https://whimsy.apache.org/roster/ppmc/committer/kener>   Kener 
Linfeng   
shenyi <https://whimsy.apache.org/roster/ppmc/committer/shenyi> Shen Yi 
sushuang <https://whimsy.apache.org/roster/ppmc/committer/sushuang> 
Shuang Su   
ovilia <https://whimsy.apache.org/roster/ppmc/committer/ovilia> Wenli 
Zhang
The PPMC should be able to see all the prior emails to private by logging into 
https://lists.apache.org <https://lists.apache.org/> and then navigating to 
https://lists.apache.org/list.html?priv...@echarts.apache.org 
<https://lists.apache.org/list.html?priv...@echarts.apache.org>

Regards,
Dave


> On Oct 17, 2018, at 7:05 AM, Kevin A. McGrail  
> wrote:
> 
> I do not know how to check the lists but would recommend you open a JIRA
> ticket on that issue.
> 
> The secretary is currently in China at two conferences so I imagine
> things are delayed.  If there is urgency, feel free to email secretary@
> otherwise I would say all is likely in queue.
> 
> Regards,
> KAM
> 
> On 10/17/2018 3:02 AM, Wenli Zhang wrote:
>> 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
>>> 
>>> 
> 
> -- 
> *Kevin A. McGrail*
> 703-798-0171 (wireless)
> https://www.linkedin.com/in/kmcgrail

Re: cant send you email with attachments

[Dave Fisher]

Hi -

Please send ICLAs to secret...@apache.org

Include that this is for ECharts and the Incubator.

Regards,
Dave

Sent from my iPhone

> On Oct 12, 2018, at 12:45 AM, Юрий Гор  wrote:
> 
> Hi, I cant send you email with attachments (signed ICLA), it always rejected
> 
> -- 
> Best, Yuri


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

Re: ICLA of new committer

[Dave Fisher]

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 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
>>> 
> 
> -- 
> Kevin A. McGrail
> 703-798-0171 (wireless)
> https://www.linkedin.com/in/kmcgrail

Re: [incubator-echarts-website] branch asf-site updated: 4.2.0-rc.1

[Dave Fisher]

Does this commit preparing for 4.2 include the appropriate fixes needed to meet 
Apache Release Distribution Policy? [1]

>> Download Links: http://echarts.apache.org/download 
>> 
> 
> The download page does not use the ASF mirror system, there are no
> links to KEYS, sigs or hashes and no details on why/how to verify
> downloads using sigs or hashes.
> 
> Also the online builder is clever, but does not provide any download
> verification.

The download link policy can be found here [2] with the signatures and checksum 
policy here [3]

Regards,
Dave

[1] https://www.apache.org/dev/release-distribution
[2] https://www.apache.org/dev/release-distribution#download-links
[3] https://www.apache.org/dev/release-distribution#sigs-and-sums


signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc4

[Dave Fisher]

Hi -

For this first release I am switching to VOTE +1 since as Justin writes this is 
a documentation issue Cn permissive licenses.

However, it needs to be clearly explained so that users of ECharts can clearly 
understand all of the implications of using it. The ECharts podling and mentors 
(Justin, Dave and Kevin) will need to research the best way to document how to 
license these derivative versions of D3. We should do so on the dev@echarts 
mailing list and the legal affairs committee’s JIRA. [1]

Regards,
Dave

[1] https://issues.apache.org/jira/projects/LEGAL/summary

> On Jun 1, 2018, at 1:50 AM, SHUANG SU  wrote:
> 
> --
> Su Shuang (100pah)
> --
> 
> 
> 2018-06-01 1:07 GMT+08:00 Dave Fisher :
> 
>> Hi -
>> 
>> I’m VOTING +0.
>> 
>> (1) I am rather confused by this D3 license. For example:
>> 
>> src/chart/tree/layoutHelper.js
>> /*
>> * Licensed to the Apache Software Foundation (ASF) under one
>> * or more contributor license agreements.  See the NOTICE file
>> * distributed with this work for additional information
>> * regarding copyright ownership.  The ASF licenses this file
>> * to you under the Apache License, Version 2.0 (the
>> * "License"); you may not use this file except in compliance
>> * with the License.  You may obtain a copy of the License at
>> *
>> *   http://www.apache.org/licenses/LICENSE-2.0
>> *
>> * Unless required by applicable law or agreed to in writing,
>> * software distributed under the License is distributed on an
>> * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
>> * KIND, either express or implied.  See the License for the
>> * specific language governing permissions and limitations
>> * under the License.
>> */
>> 
>> /*
>> * The tree layout implementation references to d3.js
>> * (https://github.com/d3/d3-hierarchy). The use of the source
>> * code of this file is also subject to the terms and consitions
>> * of its license (BSD-3Clause, see ).
>> */
>> 
>> /**
>> * @file The layout algorithm of node-link tree diagrams. Here we using
>> Reingold-Tilford algorithm to drawing
>> *   the tree.
>> * @see https://github.com/d3/d3-hierarchy
>> */
>> 
>> import * as layout from '../../util/layout';
>> ...
>> 
>> Without deep analysis I have no idea what parts are D3. If this whole file
>> is based on D3 then in my opinion this whole source file needs to be BSD-3
>> clause licensed.
>> 
>> I would change my VOTE to +1 if there is a good explanation.
>> 
>> 
> 
> Hi Dave,
> 
> Most of the logic in `src/chart/tree/layoutHelper.js` is based on
> https://github.com/d3/d3-hierarchy/blob/44ba491e8c6d5b8af21280f6507d4d
> 372bc4272d/src/tree.js
> 
> But, basically the file is a collection of layout utils for the tree
> component, in which some other logic
> not relative to d3 also exists, and may be added more in futher. So I think
> it is still a file that under the
> Apache license as other files of this project, and including some code with
> d3 BSD license embeded.
> 
> 
> Thanks.



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache ECharts 4.1.0.rc4

[Dave Fisher]

Hi -

An MD5 should not be provided with new releases. Please see [1]. This is a 
recent change. It is ok to simply delete the MD5 from the archive.

Regards,
Dave

[1] https://www.apache.org/dev/release-distribution.html#sigs-and-sums 



> On May 22, 2018, at 11:29 AM, SHUANG SU  wrote:
> 
> After removing the none source code files from 4.1.0.rc3, I am pleased to
> be calling this vote for the release of Apache ECharts 4.1.0.rc4.
> 
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc4/
> 
> 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=02842e2
> 
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc4/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.1.0.rc4/apache-echarts-4.1.0.rc4-incubating-src.zip
> -o apache-echarts-4.1.0.rc4-incubating-src.zip
> unzip apache-echarts-4.1.0.rc4-incubating-src.zip -d
> apache-echarts-4.1.0.rc4-incubating-src > /dev/null
> 
> # Build the project:
> cd "apache-echarts-4.1.0.rc4-incubating-src" && npm install && cd ..
> node "apache-echarts-4.1.0.rc4-incubating-src/build/build.js" --release
> # (See help: `node "apache-echarts-4.1.0.rc4-incubating-src/build/build.js"
> --help`)
> ```
> 
> 
> Please vote on releasing this package as:
> Apache ECharts 4.1.0.rc4
> 
> This vote will be open until "2018-05-25T19:25:25.418Z" 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)
> --



signature.asc
Description: Message signed with OpenPGP

Re: [vote] ECharts next release time

[Dave Fisher]

Hi -

Sent from my iPhone

> On Apr 16, 2018, at 10:49 PM, SHUANG SU <sushuang0...@gmail.com> wrote:
> 
> Hi Dave,
> 
>> (1) Due to the world wide / volunteer nature of an Apache project VOTEs
> require a minimum of 72 hours.
>> (2) In the Incubator each release will often require two votes.
> 
> Should the two votes be parallel or sequentially? If sequentially, the two
> votes will take 72 * 2 = 6 days, about one week? (I am worried that it is
> too long. 3 days probably be reasonable.)

These are sequential. Six days is a minimum. Once eCharts graduates it will be 
3 days.

> 
> 
> And, @Shenyi and @Wenli,
> I think we may take advantage of the procedure of the 72 hours, if the tag
> to be released can be traded as a "beta version", can be tested by
> volunteers, and eliminate "recovery build" we used to face.
> But, if possible, how the tag to be released can be downloaded by
> volunteers? Should we provide the "download of beta" in echarts website?

The volunteers test the release candidate and VOTE on the result on the dev@ 
list. This is normal. The release candidate is tested to make sure it meets 
both project quality standards and Apache legal standards.

This should all be discussed on this list!

Regards,
Dave


> 
> 
> 
> 
> 2018-04-17 12:24 GMT+08:00 Dave Fisher <dave2w...@comcast.net>:
> 
>> Hi Wenli,
>> 
>> With my mentor hat you should know that in the Incubator it is hard to
>> predict how long it will take to do a release.
>> 
>> A few standards apply:
>> 
>> (1) Due to the world wide / volunteer nature of an Apache project VOTEs
>> require a minimum of 72 hours.
>> 
>> (2) In the Incubator each release will often require two votes. First in
>> podling and second on general@. Often the Incubator vote takes longer.
>> This time can only be compressed if there are three votes from the mentors
>> on the initial vote.
>> 
>> The website can and should proceed in parallel to a release. If timing
>> works then they are simultaneous, but it is nit needed. Either can finish
>> first.
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Apr 16, 2018, at 8:29 PM, Wenli Zhang <oviliazh...@gmail.com> wrote:
>>> 
>>> Hi all,
>>> 
>>> We'd like to vote for the release time of next ECharts version.
>>> 
>>> Plan A: Wait for echarts.apache.org to be ready.
>>> This may take about one week or more.
>>> 
>>> Plan B: Release it ASAP. (Perhaps on Wednesday.)
>>> This is because last release was on 28th Feb, and may bugs have been
>> fixed
>>> since then.
>>> 
>>> Please reply +1 if you prefer Plan A.
>>> 
>>> Zhang Wenli
>>> http://zhangwenli.com
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
>> 


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

Re: [vote] ECharts next release time

[Dave Fisher]

Hi Wenli,

With my mentor hat you should know that in the Incubator it is hard to predict 
how long it will take to do a release.

A few standards apply:

(1) Due to the world wide / volunteer nature of an Apache project VOTEs require 
a minimum of 72 hours.

(2) In the Incubator each release will often require two votes. First in 
podling and second on general@. Often the Incubator vote takes longer. This 
time can only be compressed if there are three votes from the mentors on the 
initial vote.

The website can and should proceed in parallel to a release. If timing works 
then they are simultaneous, but it is nit needed. Either can finish first.

Regards,
Dave

Sent from my iPhone

> On Apr 16, 2018, at 8:29 PM, Wenli Zhang  wrote:
> 
> Hi all,
> 
> We'd like to vote for the release time of next ECharts version.
> 
> Plan A: Wait for echarts.apache.org to be ready.
> This may take about one week or more.
> 
> Plan B: Release it ASAP. (Perhaps on Wednesday.)
> This is because last release was on 28th Feb, and may bugs have been fixed
> since then.
> 
> Please reply +1 if you prefer Plan A.
> 
> Zhang Wenli
> http://zhangwenli.com


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

Re: Podling Report Reminder - April 2018

[Dave Fisher]

Thanks John.

I’ve signed off.

Regards,
Dave

Sent from my iPhone

> On Apr 8, 2018, at 6:47 AM, John D. Ament  wrote:
> 
> Mentors,
> 
> There is now a report posted.  I'll sign off, but would be good to get more
> sign offs.
> 
> John
> 
>> On Sun, Apr 8, 2018 at 9:41 AM John D. Ament  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  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 
>>> 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 
 wrote:
 
> Just following up on the below..  Any takers?
> 
> On Wed, Apr 4, 2018 at 7:11 AM John D. Ament 
> 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  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
>>> 
>>> 
> 
 
 
>>> 


-
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

[Dave Fisher]

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  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  
>> wrote:
>> On Wed, Mar 21, 2018 at 10:00 AM John D. Ament 
>> wrote:
>> 
>> > On Wed, Mar 21, 2018 at 7:34 AM Kevin A. McGrail 
>> > 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 
>> >> 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 
>> >>> 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 Junting

Re: Test (again)

[Dave Fisher]

Got it!

Sent from my iPhone

> On Jan 17, 2018, at 8:54 AM, John D. Ament  wrote:
> 
> Test

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