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

2020-11-07 Thread Kevin A. McGrail
I will abstain from voting here but believe you have the consensus and the
progress needed to call for a vote on the incubator PMC list.

Regards, KAM

On Thu, Nov 5, 2020, 10:57 Clement Ho  wrote:

> +1 from me as well
>
> On Thu, Nov 5, 2020 at 7:33 AM SHUANG SU  wrote:
>
> > +1
> >
> > After the brand issue is resolved, I think we can move forward.
> >
> > Thanks,
> > --
> >  Su Shuang (100pah)
> > --
> >
> >
> >
> > On Thu, 5 Nov 2020 at 18:25, Sheng Qian  wrote:
> >
> > >
> > > My vote is +1.
> > >
> > > Glad to see that branding issue of gallery solved successfully and
> really
> > > appreciated on effort from community to take care on branding of Apache
> > > ECharts(incubating) in external reference.
> > >
> > > Looking forward to see her graduation.
> > >
> > > Best regards,
> > > Quill (Sheng) Qian
> > >
> > > > 在 2020年11月4日,17:33,Ovilia  写道:
> > > >
> > > > Hi all,
> > > >
> > > > In the last few weeks, we have discussed and voted about graduating
> > > > Apache ECharts (incubating) as a top level project. Since it has been
> > > > blocked by the branding issue of the "gallery" for several weeks, I'm
> > > > going to call on a new round of vote now.
> > > >
> > > > 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 and ends at
> > > >
> > >
> >
> https://www.timeanddate.com/countdown/vote?iso=20201107T1735=237=cursive=1
> > > > .
> > > >
> > > >
> > > >
> > > > The "gallery" is a third-party tool so it should not use a domain
> name
> > > > containing "echarts" to mislead visitors to believe this is an
> official
> > > > product. So a new domain name makeapie.com is used for it and the
> > > > previous URL gallery.echartsjs.com redirect to it. See more
> > information
> > > > at [1].
> > > >
> > > > Previous graduation discussion can be found at [2] and the previous
> > > > vote is at [3].
> > > > Our maturity model is available at [4] and checklist is [5].
> > > >
> > > >
> > > > [1]
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r3713fa95086b3faafb86c29ad5b8221c9a885c9de2c99edae60d42fd%40%3Cdev.echarts.apache.org%3E
> > > > [2]
> > > >
> > >
> >
> https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
> > > > [3]
> > > >
> > >
> >
> https://lists.apache.org/thread.html/ref7acdd692feb444996dc9a8e22a232bf3079adcc918d6cc5a530556%40%3Cdev.echarts.apache.org%3E
> > > > [4]
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
> > > > [5]
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/ECHARTS/ECharts+Graduation+Check+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 

Re: Permission to use domain name

2020-09-19 Thread Kevin A. McGrail
To be clear the domain shouldn't use Apache or echarts or anything
confusing.  Branding can help.more.on that.

On Sat, Sep 19, 2020, 22:33 Sheng Wu  wrote:

> I think once you are not using apache.org, it works.
> I seconded KAM's idea about using powered by logo on that website. And
> anyplace on that website mentioning ECharts, please use Apache ECharts, and
> add page footer about the IP.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Ovilia  于2020年9月18日周五 上午11:09写道:
>
>> 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 
>> 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 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 sub-domain for
>>> any third party.
>>>
>>> >
>>> > Thanks
>>> >
>>> > *Ovilia*
>>> >
>>> >
>>> > On Sat, Sep 12, 2020 at 12:13 AM Zhongxiang Wang 
>>> wrote:
>>> >
>>> >> I appreciate using a subdomain of echarts.apache.org.
>>> >>
>>> >> It's simple enough to create a CNAME DNS record `
>>> >> gallery.echarts.apache.org` pointing to the current server of the
>>> domain `
>>> >> gallery.echartsjs.com` and we have no need to do something extra.
>>> >>
>>> >> Thanks,
>>> >> Zhongxiang.
>>> >>
>>> >> On 2020/09/11 08:06:38, Ovilia  wrote:
>>> >>> Thanks Dave!
>>> >>>
>>> >>> In this case, I would personally prefer using
>>> gallery.echarts.apache.org
>>> >>> instead of
>>> >>> gallery.echartsjs.com.
>>> >>>
>>> >>> Hope to hear from other PPMC members' opinions.
>>> >>>
>>> >>> Thanks
>>> >>>
>>> >>> *Ovilia*
>>> >>>
>>> >>>
>>> >>> On Fri, Sep 11, 2020 at 2:56 AM Dave Fisher  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 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
>>> >>&g

Re: Permission to use domain name

2020-09-19 Thread Kevin A. McGrail
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.

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.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
> <http://templates.openoffice.org> is
> >> actually
> >>>> hosted via CNAME on sourceforge.net <http://sourceforge.net>.
> >>>>
> >>>> What Infra and Greg would like to see is the PPMC members
> discussing
> >>>> whether they have trouble with Baidu host

Re: Permission to use domain name

2020-09-17 Thread Kevin A. McGrail


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 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 sub-domain for
any third party.

>
> Thanks
>
> *Ovilia*
>
>
> On Sat, Sep 12, 2020 at 12:13 AM Zhongxiang Wang  wrote:
>
>> I appreciate using a subdomain of echarts.apache.org.
>>
>> It's simple enough to create a CNAME DNS record `
>> gallery.echarts.apache.org` pointing to the current server of the domain `
>> gallery.echartsjs.com` and we have no need to do something extra.
>>
>> Thanks,
>> Zhongxiang.
>>
>> On 2020/09/11 08:06:38, Ovilia  wrote:
>>> Thanks Dave!
>>>
>>> In this case, I would personally prefer using gallery.echarts.apache.org
>>> instead of
>>> gallery.echartsjs.com.
>>>
>>> Hope to hear from other PPMC members' opinions.
>>>
>>> Thanks
>>>
>>> *Ovilia*
>>>
>>>
>>> On Fri, Sep 11, 2020 at 2:56 AM Dave Fisher  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 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 > >>> shenyi@gmail.com>> 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 <http://gallery.echarts.apache.org/>.
>>>>>
>>>>> Regards.
>>>>>
>>>>> On Fri, Sep 4, 2020 at 5:57 AM Greg Stein >>> gst...@gmail.com>> wrote:
>>>>>> On Thu, Sep 3, 2020 at 4:16 AM Ovilia > >>> oviliazh...@gmail.com>> wrote:
>>>>>>> ...
>>>>>>> I don't think we could use the domain name
>>>> gallery.echarts.apache.org <http://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 <http://something-a38cf9.baidu.com/>"
>> ...
>>>> we can simply create a CNAME DNS record
>>>>>> for
>>>>>> gallery.echarts.apache.org <http://gallery.echarts.apache.org/> to
>>>> point to that server. This is actually quite
>>>>>> normal for various apache.org <http://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 <http://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
>>>>
>> -
>> 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: [DISCUSS] Apache ECharts (incubating) Website redirection

2020-09-17 Thread Kevin A. McGrail
+1

On 9/16/2020 10:56 PM, Han Huang wrote:
> Hi all,
>
> Thanks again for maintaining such a nice repo as ECharts. I am still trying 
> to help with the branding issues of ECharts.  I have searched for projects 
> with the keyword "ECharts" and have made more pull requests to fix the readme 
> of each project by referring ECharts as "Apache ECharts (incubating)" rather 
> than "ECharts" or "Baidu ECharts" as well as asked the maintainer to change 
> the description similarly.
>
> This is the list I've made pull requests, and I am still working on other 
> projects and I will keep you informed on the mailing list.
>
> https://github.com/liekkas/ng-echarts/pull/22
> https://github.com/hisune/Echarts-PHP/pull/32
> https://github.com/hellosean1025/node-echarts/pull/36
> https://github.com/xieziyu/ngx-echarts/pull/263
> https://github.com/echarts-maps/echarts-countries-js/pull/17
> https://github.com/lzxue/echartsLayer/pull/10
> https://github.com/luosijie/vue-manager/pull/18
> https://github.com/xlsdg/vue-echarts-v3/pull/112
> https://github.com/twp0217/ngx-echarts/pull/38
> https://github.com/SimonZhangITer/DataVisualization/pull/6
> https://github.com/entronad/flutter_echarts/pull/76
> https://github.com/tomLadder/react-native-echarts-wrapper/pull/63
> https://github.com/giscafer/mapshaper-plus/pull/4
> https://github.com/sakitam-fdd/ol3Echarts/pull/68
> https://github.com/XD-DENG/ECharts2Shiny/pull/63
> https://github.com/Billiballa/grafana-echarts/pull/24
> https://github.com/zrysmt/echarts3/pull/2
> https://github.com/luqin/react-echarts/pull/14
>
> Hope that helps!
>
> Han Huang
>
> On 2020/08/24 09:23:40, Ovilia  wrote: 
>> Hi Kevin,> 
>>
>> The domain transferation is quite complicated if we wish to transfer domain> 
>> service provider. So we may consider it only if there aren't simpler> 
>> solutions.> 
>> Thanks for reminding me though.> 
>>
>>
>>
>> To all,> 
>>
>> Here are a few updates we have done this weekend:> 
>>
>> 1. We updated the description of echartsjs.com with the following> 
>> information:> 
>> ECharts is now under incubation at the Apache Software Foundation. So this> 
>> domain name is no longer in use. Visit echarts.apache.org please> 
>>
>> 2. https://echartsjs.com/theme-editor has the same information above.> 
>>
>> 3. We are working on transferring the following projects to Apache repo on> 
>> GitHub> 
>> (currently working on SGA files)> 
>> https://github.com/ecomfe/echarts-examples> 
>> https://github.com/ecomfe/echarts-www> 
>> https://github.com/ecomfe/echarts-issue-helper> 
>>
>> 4. We changed project descriptions and ReadMe of other echarts related> 
>> projects under> 
>> https://github.com/ecomfe that those projects are extensions of "Apache> 
>> ECharts> 
>> (incubating)".> 
>> https://github.com/ecomfe/vue-echarts/pull/466> 
>> https://github.com/ecomfe/echarts-graph-modularity/pull/3> 
>> https://github.com/ecomfe/echarts-dagre/pull/6> 
>> https://github.com/ecomfe/echarts-boilerplate/pull/1> 
>> https://github.com/ecomfe/echarts-miniBI/pull/1> 
>> https://github.com/ecomfe/zrender/pull/629> 
>> https://github.com/ecomfe/echarts-for-weixin/commit/c7abd3ac7b1accb19104c5fad82b81764d72065a>
>>  
>> https://github.com/ecomfe/echarts-wordcloud/commit/f3f81fda54eaaa32f60a4c332e361f8ec10bfdba>
>>  
>> https://github.com/ecomfe/echarts-stat/commit/8665752d870ba94609f713d991fd47665a03e4c8>
>>  
>> https://github.com/ecomfe/echarts-stat/commit/1cdf6cab5d17d469fcb3fc1f2016e711c669e034>
>>  
>> https://github.com/ecomfe/awesome-echarts/commit/a24f20c4484595a65858567909d5296645f57401>
>>  
>> https://github.com/ecomfe/echarts-map-tool/commit/06ab9189ff76aa1fb4e0968eec45dfc7fcfc520a>
>>  
>> https://github.com/ecomfe/echarts-gallery-feedback/tree/master> 
>> https://github.com/ecomfe/echarts-liquidfill/commit/124542b0ae19a826de4da03b54de61dbcdc1acd0>
>>  
>>
>>
>> The next steps we are going to do:> 
>> 1. Complete transferring those repos> 
>> 2. Check for third-party repos or blog posts and make pull requests or ask> 
>> the maintainer to clarify with the name "Apache ECharts (incubating)".> 
>> 3. Further discuss domain name problem with echartjs.com in this thread> 
>>
>>
>> *Ovilia*> 
>>
>>
>> On Mon, Aug 24, 2020 at 1:15 AM Kevin A. McGrail > 
>> wrote:> 
>>
>>> 

Re: Permission to use domain name

2020-09-03 Thread Kevin A. McGrail
I can help transfer your domain and donate it to Apache.  Dropped a word
there.

On Thu, Sep 3, 2020, 03:16 Kevin A. McGrail  wrote:

> I would defer to trademarks.  I can help the domain and then donate it to
> Apache.
>
> On Thu, Sep 3, 2020, 03:10 Ovilia  wrote:
>
>> Thanks Mark!
>>
>> We plan to buy a new domain name for it and not use gallery.echartsjs.com
>> any more.
>> But the process may take a few more weeks/months for domain name
>> registration
>> and migrating.
>>
>> Can we not take this as a blocker for Apache ECharts (incubating)'s
>> graduation?
>>
>> What do Mark, Justin, and our mentors think about this?
>>
>> Thanks
>>
>> *Ovilia*
>>
>>
>> On Thu, Sep 3, 2020 at 7:08 AM Mark Thomas  wrote:
>>
>> > Hi,
>> >
>> > First of all, I don't see any issues with the current content of
>> > echartsjs.com
>> >
>> > gallery.echartsjs.com is more problematic.
>> >
>> > PMCs are very strongly discouraged from creating focal points for the
>> > project outside of the apache.org domain.
>> >
>> > Has the podling considered requesting INFRA create an
>> > gallery.charts.apache.org domain name and point it to the existing
>> server?
>> >
>> > Has the podling considered moving that service to an ASF provided
>> > project VM?
>> >
>> > To be clear, this isn't an issue that needs to be deal with as a matter
>> > of urgency but it is something that ideally needs to be resolved before
>> > graduation.
>> >
>> > Mark
>> >
>> > Mark Thomas
>> > VP, Brand Management
>> >
>> > On 31/08/2020 05:15, Ovilia wrote:
>> > > Hi,
>> > >
>> > > I'm a member of Apache ECharts (incubating) PPMC and I'm sending this
>> > email
>> > > to ask the permission of the domain name echartsjs.com
>> > > <http://echartsjs.com> .
>> > >
>> > > This domain name is currently owned by one of our PPMC members Yi Shen
>> > and
>> > > was used as EChart's official Website before ECharts joined ASF.
>> > >
>> > > Now, the Website has a link to our official
>> > > Website http://echarts.apache.org/
>> > > and a clear statement that
>> > > "ECharts is now under incubation at the Apache Software Foundation. So
>> > > this domain
>> > > name is no longer in use. Visit echarts.apache.org
>> > > <http://echarts.apache.org> please"
>> > >
>> > > (The reason why we use links instead of redirecting is that the local
>> > > Web policy of
>> > > the echartsjs.com <http://echartsjs.com> has certain restrictions on
>> the
>> > > content if it's redirecting but not
>> > > if it's a link.)
>> > >
>> > > And there is a Website https://gallery.echartsjs.com/ that enables
>> users
>> > > to upload their work
>> > > of ECharts, which also have a clear statement as:
>> > > "This Website is a community contributed work of Apache ECharts
>> > > (incubating) and it is not
>> > > an official Apache ECharts (incubating) product."
>> > >
>> > > We'd like to know if there are any branding issues with how we use the
>> > > domain names
>> > > echartsjs.com <http://echartsjs.com> and gallery.echartsjs.com
>> > > <http://gallery.echartsjs.com> here?
>> > >
>> > > [1] https://www.apache.org/foundation/marks/domains.html
>> > >
>> > > Thanks
>> > > *
>> > > *
>> > > *Ovilia*
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> > For additional commands, e-mail: dev-h...@echarts.apache.org
>> >
>> >
>>
>


Re: Permission to use domain name

2020-09-03 Thread Kevin A. McGrail
I would defer to trademarks.  I can help the domain and then donate it to
Apache.

On Thu, Sep 3, 2020, 03:10 Ovilia  wrote:

> Thanks Mark!
>
> We plan to buy a new domain name for it and not use gallery.echartsjs.com
> any more.
> But the process may take a few more weeks/months for domain name
> registration
> and migrating.
>
> Can we not take this as a blocker for Apache ECharts (incubating)'s
> graduation?
>
> What do Mark, Justin, and our mentors think about this?
>
> Thanks
>
> *Ovilia*
>
>
> On Thu, Sep 3, 2020 at 7:08 AM Mark Thomas  wrote:
>
> > Hi,
> >
> > First of all, I don't see any issues with the current content of
> > echartsjs.com
> >
> > gallery.echartsjs.com is more problematic.
> >
> > PMCs are very strongly discouraged from creating focal points for the
> > project outside of the apache.org domain.
> >
> > Has the podling considered requesting INFRA create an
> > gallery.charts.apache.org domain name and point it to the existing
> server?
> >
> > Has the podling considered moving that service to an ASF provided
> > project VM?
> >
> > To be clear, this isn't an issue that needs to be deal with as a matter
> > of urgency but it is something that ideally needs to be resolved before
> > graduation.
> >
> > Mark
> >
> > Mark Thomas
> > VP, Brand Management
> >
> > On 31/08/2020 05:15, Ovilia wrote:
> > > Hi,
> > >
> > > I'm a member of Apache ECharts (incubating) PPMC and I'm sending this
> > email
> > > to ask the permission of the domain name echartsjs.com
> > >  .
> > >
> > > This domain name is currently owned by one of our PPMC members Yi Shen
> > and
> > > was used as EChart's official Website before ECharts joined ASF.
> > >
> > > Now, the Website has a link to our official
> > > Website http://echarts.apache.org/
> > > and a clear statement that
> > > "ECharts is now under incubation at the Apache Software Foundation. So
> > > this domain
> > > name is no longer in use. Visit echarts.apache.org
> > >  please"
> > >
> > > (The reason why we use links instead of redirecting is that the local
> > > Web policy of
> > > the echartsjs.com  has certain restrictions on
> the
> > > content if it's redirecting but not
> > > if it's a link.)
> > >
> > > And there is a Website https://gallery.echartsjs.com/ that enables
> users
> > > to upload their work
> > > of ECharts, which also have a clear statement as:
> > > "This Website is a community contributed work of Apache ECharts
> > > (incubating) and it is not
> > > an official Apache ECharts (incubating) product."
> > >
> > > We'd like to know if there are any branding issues with how we use the
> > > domain names
> > > echartsjs.com  and gallery.echartsjs.com
> > >  here?
> > >
> > > [1] https://www.apache.org/foundation/marks/domains.html
> > >
> > > Thanks
> > > *
> > > *
> > > *Ovilia*
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> > For additional commands, e-mail: dev-h...@echarts.apache.org
> >
> >
>


Re: [DISCUSS] Apache ECharts (incubating) Website redirection

2020-08-24 Thread Kevin A. McGrail
+1

On 8/24/2020 5:23 AM, Ovilia wrote:
> Hi Kevin,
>
> The domain transferation is quite complicated if we wish to transfer domain
> service provider. So we may consider it only if there aren't simpler
> solutions.
> Thanks for reminding me though.
>
>
>
> To all,
>
> Here are a few updates we have done this weekend:
>
> 1. We updated the description of echartsjs.com with the following
> information:
> ECharts is now under incubation at the Apache Software Foundation. So this
> domain name is no longer in use. Visit echarts.apache.org please
>
> 2. https://echartsjs.com/theme-editor has the same information above.
>
> 3. We are working on transferring the following projects to Apache repo on
> GitHub
> (currently working on SGA files)
> https://github.com/ecomfe/echarts-examples
> https://github.com/ecomfe/echarts-www
> https://github.com/ecomfe/echarts-issue-helper
>
> 4. We changed project descriptions and ReadMe of other echarts related
> projects under
> https://github.com/ecomfe that those projects are extensions of "Apache
> ECharts
> (incubating)".
> https://github.com/ecomfe/vue-echarts/pull/466
> https://github.com/ecomfe/echarts-graph-modularity/pull/3
> https://github.com/ecomfe/echarts-dagre/pull/6
> https://github.com/ecomfe/echarts-boilerplate/pull/1
> https://github.com/ecomfe/echarts-miniBI/pull/1
> https://github.com/ecomfe/zrender/pull/629
> https://github.com/ecomfe/echarts-for-weixin/commit/c7abd3ac7b1accb19104c5fad82b81764d72065a
> https://github.com/ecomfe/echarts-wordcloud/commit/f3f81fda54eaaa32f60a4c332e361f8ec10bfdba
> https://github.com/ecomfe/echarts-stat/commit/8665752d870ba94609f713d991fd47665a03e4c8
> https://github.com/ecomfe/echarts-stat/commit/1cdf6cab5d17d469fcb3fc1f2016e711c669e034
> https://github.com/ecomfe/awesome-echarts/commit/a24f20c4484595a65858567909d5296645f57401
> https://github.com/ecomfe/echarts-map-tool/commit/06ab9189ff76aa1fb4e0968eec45dfc7fcfc520a
> https://github.com/ecomfe/echarts-gallery-feedback/tree/master
> https://github.com/ecomfe/echarts-liquidfill/commit/124542b0ae19a826de4da03b54de61dbcdc1acd0
>
>
> The next steps we are going to do:
> 1. Complete transferring those repos
> 2. Check for third-party repos or blog posts and make pull requests or ask
> the maintainer to clarify with the name "Apache ECharts (incubating)".
> 3. Further discuss domain name problem with echartjs.com in this thread
>
>
> *Ovilia*
>
>
> On Mon, Aug 24, 2020 at 1:15 AM Kevin A. McGrail 
> wrote:
>
>> Do you want to transfer the domain to infra at ASF so you can remove any
>> restrictions on that domains usage?
>> --
>> Kevin A. McGrail
>> Member, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>>
>> On Thu, Aug 20, 2020 at 10:29 PM Ovilia  wrote:
>>
>>> Hi Justin,
>>>
>>> We are working on it but one concern here about
>>>> Again this is generally not allowed. Baidu can't call versions of their
>>> product ECharts, only the PPMC can use that name.
>>>
>>> If previous versions before Apache release cannot be not called
>> "ECharts",
>>> what should
>>> we call it and make sure others understand what we are referring to? IMO
>> we
>>> cannot
>>> just make up a new name like "Baidu Chart" to refer to previous versions
>>> because no
>>> one would know what we are talking about.
>>>
>>> Thanks
>>>
>>> *Ovilia*
>>>
>>>
>>> On Thu, Aug 20, 2020 at 6:46 PM Justin Mclean 
>> wrote:
>>>> Hi,
>>>>
>>>>> Gallery [1] is a platform to show the community's works with ECharts.
>>> It
>>>> is
>>>>> not owned by  ECharts PPMC.
>>>> Which is the issue here, domain names in general can't include
>> "echarts",
>>>> unless approved by the PPMC and trademarks. I suggest you ask for
>> advice
>>>> from trademarks.
>>>>
>>>>> awesome-echarts and vue-echarts are under an organization of Baidu.
>> But
>>>>> neither of them claim to be an official ECharts project.
>>>> Again that is an issue as it creates confusion with users. These
>> projects
>>>> are not respecting Apache brands and making it clear that this is an an
>>>> Apache project. In general other projects can't use Apache names in
>> their
>>>> names. The PPMC member need to ensure that ASF branding policy is being
>>>> fo

Re: [DISCUSS] Apache ECharts (incubating) Website redirection

2020-08-23 Thread Kevin A. McGrail
Do you want to transfer the domain to infra at ASF so you can remove any
restrictions on that domains usage?
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Thu, Aug 20, 2020 at 10:29 PM Ovilia  wrote:

> Hi Justin,
>
> We are working on it but one concern here about
> > Again this is generally not allowed. Baidu can't call versions of their
> product ECharts, only the PPMC can use that name.
>
> If previous versions before Apache release cannot be not called "ECharts",
> what should
> we call it and make sure others understand what we are referring to? IMO we
> cannot
> just make up a new name like "Baidu Chart" to refer to previous versions
> because no
> one would know what we are talking about.
>
> Thanks
>
> *Ovilia*
>
>
> On Thu, Aug 20, 2020 at 6:46 PM Justin Mclean  wrote:
>
> > Hi,
> >
> > > Gallery [1] is a platform to show the community's works with ECharts.
> It
> > is
> > > not owned by  ECharts PPMC.
> >
> > Which is the issue here, domain names in general can't include "echarts",
> > unless approved by the PPMC and trademarks. I suggest you ask for advice
> > from trademarks.
> >
> > > awesome-echarts and vue-echarts are under an organization of Baidu. But
> > > neither of them claim to be an official ECharts project.
> >
> > Again that is an issue as it creates confusion with users. These projects
> > are not respecting Apache brands and making it clear that this is an an
> > Apache project. In general other projects can't use Apache names in their
> > names. The PPMC member need to ensure that ASF branding policy is being
> > follow, particular with companies they may also work for.
> >
> > > I'm not sure if this seems to be OK.
> >
> > IMO this is not OK, but perhaps your mentors have something to say on
> this?
> >
> > > Post incubation Baidu versions of ECharts are officially called ECharts
> >
> > Again this is generally not allowed. Baidu can't call versions of their
> > product ECharts, only the PPMC can use that name.
> >
> > Thanks,
> > Justin
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> > For additional commands, e-mail: dev-h...@echarts.apache.org
> >
> >
>


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

2020-08-18 Thread Kevin A. McGrail
+1 Binding from me.
Regards,
KAM
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Aug 18, 2020 at 1:24 PM Kener Linfeng 
wrote:

> +1
>
> As more and more people join in Apache ECharts, this community has become
> more prosperous and healthy. I look forward to the graduation of this
> project and become a top level project.
>
> Thanks all for the great efforts on making echarts better ~
>
> Cheers for everyone ~
>
> Kener Linfeng  于2020年8月19日周三 上午1:22写道:
>
> >
> >
> > On 2020/08/17 03:36:54, 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
> > >
> > > R

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

2020-08-02 Thread Kevin A. McGrail
t;>>> 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?
>>>>> Also, the releasing script in the release guide [4] depends on the
>>>> password
>>>>> of the CDN
>>>>> private key. How should we distribute it?
>>>>>
>>>>> 3. PMCs and Committers
>>>>> We have to discuss what to do with the initial PPMCs that had no
>> clear
>>>>> contribution to
>>>>> the project during incubation. We should decide on each of them, do
>> we
>>>> wish
>>>>> to make
>>>>> him a PMC or Committer or neither. Basically, it's decided by the
>>>> project,
>>>>> so please talk about how you feel about this.
>>>>> a. Lin Zhifeng https://github.com/kener
>>>>> b. Dong Rui https://github.com/erik168
>>>>> c. Huang Houjin https://github.com/chriswong
>>>>>
>>>>>
>>>>> [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
>>>>> <
>> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Guide
>>>>> [5]
>>>>>
>> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
>>>>> [6] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
>>>>> [7] http://echarts.apache.org/
>>>>> [8] https://incubator.apache.org/guides/sites.html
>>>>> [9] Using `git shortlog -sn --since="20 Jan, 2018"` on the master
>>> branch
>>>>> and merging
>>>>> alias
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> *Ovilia*
>>>>>
>>>> -
>>>> 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: [DISCUSS] Graduate Apache ECharts (incubating) as a TLP

2020-07-28 Thread Kevin A. McGrail
I would ask your PMC to review it.  Then if they agree send that to each
mentor and cc the PMC requesting a review from the mentors.

Regards KAM

On Tue, Jul 28, 2020, 00:07 Ovilia  wrote:

> Hi Kevin,
>
> I've created a checklist at [1].
> Things like resolution and vote should be prepared after this discussion so
> it's not done yet.
> Anything else I need to do now?
>
> [1]
>
> https://cwiki.apache.org/confluence/display/ECHARTS/ECharts+Graduation+Check+List
>
> Thanks
>
> *Ovilia*
>
>
> On Tue, Jul 28, 2020 at 4:06 AM Kevin A. McGrail 
> wrote:
>
> > Thanks Ovilia.
> >
> > Did you do a graduation checklist review?  See
> >
> https://incubator.apache.org/guides/graduation.html#graduation_check_list
> >
> > Regards,
> > KAM
> > --
> > Kevin A. McGrail
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> >
> > On Mon, Jul 27, 2020 at 1:08 AM 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?
> > > Also, the releasing script in the release guide [4] depends on the
> > password
> > > of the CDN
> > > private key. How should we distribute it?
> > >
> > > 3. PMCs and Committers
> > > We have to discuss what to do with the initial PPMCs that had no clear
> > > contribution to
> > > the project during incubation. We should decide on each of them, do we
> > wish
> > > to make
> > > him a PMC or Committer or neither. Basically, it's decided by the
> > project,
> > > so please talk about how you feel about this.
> > > a. Lin Zhifeng https://github.com/kener
> > > b. Dong Rui https://github.com/erik168
> > > c. Huang Houjin https://github.com/chriswong
> > >
> > >
> > > [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
> > > <
> > >
> >
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Guide
> > > >
> > > [5]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
> > > [6] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
> > > [7] http://echarts.apache.org/
> > > [8] https://incubator.apache.org/guides/sites.html
> > > [9] Using `git shortlog -sn --since="20 Jan, 2018"` on the master
> branch
> > > and merging
> > > alias
> > >
> > >
> > > Thanks
> > >
> > > *Ovilia*
> > >
> >
>


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

2020-07-27 Thread Kevin A. McGrail
Thanks Ovilia.

Did you do a graduation checklist review?  See
https://incubator.apache.org/guides/graduation.html#graduation_check_list

Regards,
KAM
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Jul 27, 2020 at 1:08 AM 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?
> Also, the releasing script in the release guide [4] depends on the password
> of the CDN
> private key. How should we distribute it?
>
> 3. PMCs and Committers
> We have to discuss what to do with the initial PPMCs that had no clear
> contribution to
> the project during incubation. We should decide on each of them, do we wish
> to make
> him a PMC or Committer or neither. Basically, it's decided by the project,
> so please talk about how you feel about this.
> a. Lin Zhifeng https://github.com/kener
> b. Dong Rui https://github.com/erik168
> c. Huang Houjin https://github.com/chriswong
>
>
> [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
> <
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Guide
> >
> [5]
>
> https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
> [6] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
> [7] http://echarts.apache.org/
> [8] https://incubator.apache.org/guides/sites.html
> [9] Using `git shortlog -sn --since="20 Jan, 2018"` on the master branch
> and merging
> alias
>
>
> Thanks
>
> *Ovilia*
>


Re: Apache Software Foundation, Trillions and Trillions Served with Chinese subtitle LIVE!

2020-07-16 Thread Kevin A. McGrail
Awesome!

On Thu, Jul 16, 2020, 21:40 Sheng Wu  wrote:

> Hi Sally, Michael, Dominik, DevCom, and ALC Beijing
>
> First of all, thank you to make the video `Apache Software Foundation,
> Trillions and Trillions Served`, provide helps to me.
> I am here glad to share, with the supports from the SkyWalking community,
> ALC Beijing community, and Kaiyuanshe, we have this video online hosted on
> bilibili which is China's local friendly platform. And we have provided
> Chinese subtitles on that.
>
> https://www.bilibili.com/video/BV1Uz411i7MH
>
> In this short time, we already have 200+ watches, and we expect more.
> Thank you all to make this happens.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>


Re: [INFO] 7th birthday of ECharts project

2020-06-30 Thread Kevin A. McGrail
Happy Birthday!  I also let pr...@apache.org know.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Jun 30, 2020 at 9:42 AM Ovilia  wrote:

> Dear all,
>
> Seven years ago, on 30th June 2013, ECharts 1.0 was released on GitHub and
> made open sourced. So, today is the seventh birthday of ECharts and we
> would like take this opportunity to say thank you to everyone in this
> community. Only with your continuous help and contribution can this project
> go so far.
>
> We are working on the next big release and hope to continue this wonderful
> journey with you guys.
>
> Thank you!
>
>
> P. S. You may retweet
> https://twitter.com/echartsjs/status/1277960148149891075 if you wish.
>
> --
> Thanks
>
> *Ovilia*
>


Re: Website with or without CDN

2020-04-26 Thread Kevin A. McGrail
Yikes, I just added some technical info to the Jira ticket:


Seeing it working from Firefox but Digicert agrees it is expired from
their SSL testing tool, https://www.digicert.com/help/ shows the TLS
cert expired on 4/24/2020

DNS resolves echarts.apache.org to 13.107.246.10

HTTP Server Header: Apache/2.4.18 (Ubuntu)
TLS Certificate

Common Name = echarts.apache.org

Subject Alternative Names = echarts.apache.org

Issuer = DigiCert SHA2 Secure Server CA

Serial Number = 0FCEF55C8F3D01B48D6CA2EA0CCF56CE

SHA1 Thumbprint = 8CEFE6D13DAF704C4A1EAC3862D1D6CD53CC3035

Key Length = 2048

Signature algorithm = SHA256-RSA

Secure Renegotiation:
TLS Certificate has not been revoked
OCSP Staple:     Not Enabled
OCSP Origin:     Good
CRL Status:     Good

TLS Certificate is expired.

The certificate was valid from 24/Apr/2019 through 24/Apr/2020.
Certificate Name matches echarts.apache.org
Subject    echarts.apache.org
Valid from 24/Apr/2019 to 24/Apr/2020
Issuer    DigiCert SHA2 Secure Server CA
     
Subject    DigiCert SHA2 Secure Server CA
Valid from 08/Mar/2013 to 08/Mar/2023
Issuer    DigiCert Global Root CA

On 4/26/2020 12:37 AM, Ovilia wrote:
> Yesterday, we noticed that ECharts apache Website domain has an HTTPS CA
> expired error and blocking users from accessing it.
>
> We reported this on JIRA [1] and this has not been fixed for now. So we
> temporarily cancelled the redirection from echartsjs.com to
> echarts.apache.org.
>
> [1] https://issues.apache.org/jira/browse/INFRA-20185
>
> Thanks
>
> Wenli
>
>
> On Tue, Apr 21, 2020 at 4:39 PM Ovilia  wrote:
>
>> Shuang Su has just redirected echartsjs.com to echarts.apache.org.
>> If anyone find the speed is slow, please let us know.
>>
>> Thanks
>>
>> Wenli
>>
>>
>> On Tue, Apr 21, 2020 at 1:27 PM Ovilia  wrote:
>>
>>> Yes, it's definitely much quicker than a few months ago.
>>> I agree with Yi on the redirecting thing.
>>>
>>> Thanks
>>>
>>> Wenli
>>>
>>>
>>> On Tue, Apr 21, 2020 at 11:12 AM Yi Shen  wrote:
>>>
>>>> It seems a lot faster now.
>>>>
>>>> Can we try redirecting www.echartsjs.com to echarts.apache.org, and keep
>>>> collecting developers' feedback about inaccessible of the website?
>>>>
>>>> Thanks
>>>>
>>>> On Thu, Apr 16, 2020 at 4:11 PM Kevin A. McGrail 
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Thu, Apr 16, 2020, 04:04 Ovilia  wrote:
>>>>>
>>>>>> Hi Kevin,
>>>>>>
>>>>>> That's a good idea.
>>>>>>
>>>>>> We will test it again and find out the bottleneck with the updated
>>>> CDN
>>>>>> status.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Wenli
>>>>>>
>>>>>>
>>>>>> On Thu, Apr 16, 2020 at 3:52 PM Kevin A. McGrail <
>>>> kmcgr...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> This month is a reporting month for echarts.  Let's try and get a
>>>> full
>>>>>>> status on the cdn and any other blockers to migrating to
>>>>>>> echarts.apache.org,
>>>>>>> please?
>>>>>>>
>>>>>>> On Wed, Apr 15, 2020, 22:53 Yi Shen  wrote:
>>>>>>>
>>>>>>>> Perhaps we can remove the videos when designing the new main
>>>> page for
>>>>>> the
>>>>>>>> 5.0 release. Ovilia has proposed this idea several times.
>>>>>>>>
>>>>>>>> On Thu, Apr 16, 2020 at 2:45 AM Kevin A. McGrail <
>>>>> kmcgr...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> The issue is significantly subpar access especially inside of
>>>> China
>>>>>>> that
>>>>>>>>> a CDN can help mitigate.
>>>>>>>>>
>>>>>>>>> On 4/15/2020 1:30 PM, Dave Fisher wrote:
>>>>>>>>>> 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
>&

Re: Website with or without CDN

2020-04-16 Thread Kevin A. McGrail
+1

On Thu, Apr 16, 2020, 04:04 Ovilia  wrote:

> Hi Kevin,
>
> That's a good idea.
>
> We will test it again and find out the bottleneck with the updated CDN
> status.
>
> Thanks
>
> Wenli
>
>
> On Thu, Apr 16, 2020 at 3:52 PM Kevin A. McGrail 
> wrote:
>
> > This month is a reporting month for echarts.  Let's try and get a full
> > status on the cdn and any other blockers to migrating to
> > echarts.apache.org,
> > please?
> >
> > On Wed, Apr 15, 2020, 22:53 Yi Shen  wrote:
> >
> > > Perhaps we can remove the videos when designing the new main page for
> the
> > > 5.0 release. Ovilia has proposed this idea several times.
> > >
> > > On Thu, Apr 16, 2020 at 2:45 AM Kevin A. McGrail 
> > > wrote:
> > >
> > > > The issue is significantly subpar access especially inside of China
> > that
> > > > a CDN can help mitigate.
> > > >
> > > > On 4/15/2020 1:30 PM, Dave Fisher wrote:
> > > > > 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
> > > > >
> > > > --
> > > > 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
> > > >
> > > >
> > >
> > > --
> > > Yi Shen
> > > Apache ECharts(incubating) PPMC
> > >
> >
>


Re: Website with or without CDN

2020-04-16 Thread Kevin A. McGrail
This month is a reporting month for echarts.  Let's try and get a full
status on the cdn and any other blockers to migrating to echarts.apache.org,
please?

On Wed, Apr 15, 2020, 22:53 Yi Shen  wrote:

> Perhaps we can remove the videos when designing the new main page for the
> 5.0 release. Ovilia has proposed this idea several times.
>
> On Thu, Apr 16, 2020 at 2:45 AM Kevin A. McGrail 
> wrote:
>
> > The issue is significantly subpar access especially inside of China that
> > a CDN can help mitigate.
> >
> > On 4/15/2020 1:30 PM, Dave Fisher wrote:
> > > 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
> > >
> > --
> > 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
> >
> >
>
> --
> Yi Shen
> Apache ECharts(incubating) PPMC
>


Re: Website with or without CDN

2020-04-15 Thread Kevin A. McGrail
The issue is significantly subpar access especially inside of China that
a CDN can help mitigate.

On 4/15/2020 1:30 PM, Dave Fisher wrote:
> 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
>
-- 
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: [Blog] GitHub Star Breaking 40K, ECharts Is Now Working On The Next Big Release!

2020-04-02 Thread Kevin A. McGrail
Congrats!
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Thu, Apr 2, 2020 at 4:14 AM Ovilia  wrote:

> Sure. We are working on a list of issues that we have been thinking of as a
> start and will post a new thread to discuss about it and ask the community
> to add and discuss.
>
> Thanks
>
> Wenli
>
>
> On Thu, Apr 2, 2020 at 1:03 PM Dave Fisher  wrote:
>
> > 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
> >
> >
>


Re: [Review Needed] Incubator board reports of Feb 2020

2020-01-31 Thread Kevin A. McGrail
It's a great exercise even if you aren't ready this report.

On 2/1/2020 12:34 AM, Ovilia wrote:
> Hi Kevin and Sheng,
> I need a few more days to create the checklist for graduation readiness. So
> let's mark the state to be "Community building" for this report now.
>
>
> Hi Shen,
> Thanks for reminding me. I will add the npm issue to the report.
>
>
> Does anyone else have anything to comment about the report? Otherwise, I
> should submit it soon.
>
> Thanks
>
> Wenli
>
>
> On Sat, Feb 1, 2020 at 12:48 PM Yi Shen  wrote:
>
>> Thanks, Wenli.
>>
>> Besides updating the status page and redirecting the website. I just
>> noticed the npm account is also an issue needs to be fixed a few days ago.
>> Currently the echarts npm package[1] is still under ecomfe org, which is
>> not managed by the echarts PPMC. And we can only publish the latest release
>> with ecomfe account
>> I think we should transfer the package from the ecomfe account, and more
>> PPMC should have the authority of publishing echarts package to npm.
>> cordova[2] is a good example.
>>
>> Also, we still need more active PPMC before we can graduate
>>
>> Regards.
>>
>> [1] https://www.npmjs.com/package/echarts
>> [2] https://www.npmjs.com/package/cordova
>>
>> On Fri, Jan 31, 2020 at 11:08 PM Kevin A. McGrail 
>> wrote:
>>
>>> Thanks!  Let me know when this is on the wiki for signoff.  In the
>>> meantime, I have asked about a checklist for graduation readiness.  I
>> will
>>> be happy to go down that and give my feedback.
>>> --
>>> Kevin A. McGrail
>>> Member, Apache Software Foundation
>>> Chair Emeritus Apache SpamAssassin Project
>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>>
>>>
>>> On Mon, Jan 27, 2020 at 8:23 AM Ovilia  wrote:
>>>
>>>> The following is the report I'm going to send as ECharts's Incubator
>>> board
>>>> reports of Feb 2020. Please help review and give advice on it.
>>>>
>>>> I'm not sure if we are near graduation or not. I've checked The Apache
>>>> Project Maturity Model [1] and it seems to be near graduation to me.
>> But
>>> I
>>>> think we need mentors' comments on this.
>>>>
>>>> As about the status page and the official Website, I think it should be
>>>> fixed within a month.
>>>>
>>>> Please comment if you have other concerns.
>>>> Thanks!
>>>>
>>>> [1]
>>>>
>> http://community.apache.org/apache-way/apache-project-maturity-model.html
>>>> ECharts
>>>> <
>>>>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#echarts
>>>> ECharts is a charting and data visualization library written in
>>> JavaScript.
>>>> ECharts has been incubating since 2018-01-18.
>>>> Three most important unfinished issues to address before graduating:
>>>> <
>>>>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#three-most-important-unfinished-issues-to-address-before-graduating-4
>>>>1. Status page ( https://incubator.apache.org/projects/echarts.html
>> )
>>>>has not been updated and we are going to do this within a month.
>>>>2. Official Website: We have redirected echarts.baidu.com to
>>>>echartsjs.com and put a banner in echartsjs.com stating that the
>>>>official Website is echarts.apache.org but we still need to come
>> to a
>>>>conclusion about whether CDN still has a problem with the access in
>>>> China.
>>>>If so, we should probably make echartsjs.com as a mirror site with
>> a
>>>>clear specification about the main site. If not, we should redirect
>>>>echartsjs.com to echarts.apache.org.
>>>>
>>>> Are there any issues that the IPMC or ASF Board need to be aware of?
>>>> <
>>>>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#are-there-any-issues-that-the-ipmc-or-asf-board-need-to-be-aware-of-4
>>>> No.
>>>> How has the community developed since the last report?
>>>> <
>>>>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#how-has-the-community-developed-since-the-last-report-4
>>>> More people from the community become contributors, either in the form
>> of
>>>> answering questions in the issues, fixing

Re: [Review Needed] Incubator board reports of Feb 2020

2020-01-31 Thread Kevin A. McGrail
Thanks!  Let me know when this is on the wiki for signoff.  In the
meantime, I have asked about a checklist for graduation readiness.  I will
be happy to go down that and give my feedback.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Jan 27, 2020 at 8:23 AM Ovilia  wrote:

> The following is the report I'm going to send as ECharts's Incubator board
> reports of Feb 2020. Please help review and give advice on it.
>
> I'm not sure if we are near graduation or not. I've checked The Apache
> Project Maturity Model [1] and it seems to be near graduation to me. But I
> think we need mentors' comments on this.
>
> As about the status page and the official Website, I think it should be
> fixed within a month.
>
> Please comment if you have other concerns.
> Thanks!
>
> [1]
> http://community.apache.org/apache-way/apache-project-maturity-model.html
> ECharts
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#echarts
> >
>
> ECharts is a charting and data visualization library written in JavaScript.
>
> ECharts has been incubating since 2018-01-18.
> Three most important unfinished issues to address before graduating:
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#three-most-important-unfinished-issues-to-address-before-graduating-4
> >
>
>1. Status page ( https://incubator.apache.org/projects/echarts.html )
>has not been updated and we are going to do this within a month.
>2. Official Website: We have redirected echarts.baidu.com to
>echartsjs.com and put a banner in echartsjs.com stating that the
>official Website is echarts.apache.org but we still need to come to a
>conclusion about whether CDN still has a problem with the access in
> China.
>If so, we should probably make echartsjs.com as a mirror site with a
>clear specification about the main site. If not, we should redirect
>echartsjs.com to echarts.apache.org.
>
> Are there any issues that the IPMC or ASF Board need to be aware of?
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#are-there-any-issues-that-the-ipmc-or-asf-board-need-to-be-aware-of-4
> >
> No.
> How has the community developed since the last report?
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#how-has-the-community-developed-since-the-last-report-4
> >
> More people from the community become contributors, either in the form of
> answering questions in the issues, fixing the document or making pull
> requests with the code. We did more public introduction about the community
> and welcome others to contribute and it did show some positive effects
> recently.
> How has the project developed since the last report?
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#how-has-the-project-developed-since-the-last-report-4
> >
> The monthly release became quite on time recently and in each release, we
> have several pull requests from the community.
> How would you assess the podling's maturity?
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#how-would-you-assess-the-podlings-maturity-4
> >
>
> Please feel free to add your own commentary.
>
>- [ ] Initial setup
>- [ ] Working towards first release
>- [x] Community building
>- [ ] Nearing graduation
>- [ ] Other:
>
> Date of last release:
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#date-of-last-release-4
> >
>
> 2019.12.29
> When were the last committers or PPMC members elected?
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#when-were-the-last-committers-or-ppmc-members-elected-4
> >
> 2020.01.15
> Have your mentors been helpful and responsive?
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#have-your-mentors-been-helpful-and-responsive-4
> >
> Yes, m
> entors are very helpful and responsive.
> Is the PPMC managing the podling's brand / trademarks?
> <
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#is-the-ppmc-managing-the-podlings-brand--trademarks-4
> >
>
> Yes.
>
> Wenli
>


Re: [Mentor] Review needed for November's report

2019-11-04 Thread Kevin A. McGrail
Thanks Wenli, I have signed off on the report.  Please keep the growth
going.  I would love to see discussions on list about the CDN issue and
how to get more community members as well as bugs/features, etc.

On 11/4/2019 6:56 AM, Ovilia wrote:
> Dear mentors,
>
> I've updated the incubator report [1], please check it out when you have
> time.
> Please tell me if there's anything I need to change.
>
> I'm also working on updating [2] these days.
>
> Thanks!
>
> [1]
> https://cwiki.apache.org/confluence/display/INCUBATOR/November2019#echarts
> [2] https://incubator.apache.org/projects/echarts.html
>
> Wenli
>
-- 
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: [DISCUSS] How about holding an ECharts offline meetup?

2019-09-18 Thread Kevin A. McGrail
You can request financial support from the asf and work on targeted
corporate sponsors for meetups and hackathons with fundraising.

You can request stickers as well.  There is a budget for that too!

Sounds like you are working on this well!

On Wed, Sep 18, 2019, 03:53 Ovilia  wrote:

> I'd suggest we start in Shanghai because there are more developers in
> Shanghai, Beijing, and Shenzhen, and I have more resources here in
> Shanghai.
>
> I've asked some friends about the site fees.
> Normally, the price for a meeting room for 200 people is about
> ¥10,000-15,000 (USD $ 1500-2000) half-day.
> A friend from Microsoft offered a free meeting room with 100 seats in 漕河泾.
> Or we could consider conference rooms inside universities. For example, the
> price of a 250-seat room in Shanghai Jiao Tong University, which was the
> university I graduated from, is about ¥1,200 (USD $170) half day. This
> could save much money and more students can join the event. But the
> location is in 闵行 so it may be a little remote.
> *Which one do you prefer?*
>
> Other costs include providing drinking water and printed stickers or
> posters.
> I think the overall budget could be under ¥2000 (USD $300). So we could
> raise the money by ourselves and it could work even without sponsorship.
>
>
>
> About the topic, I'm thinking of keynotes from the PPMC and speeches from
> call-for-speakers, and lightning talks, whose durations are about 20-30min,
> 15-20min, and 5-10min.
> Here are some ideas of keynote topics:
> 1. Community and the Apache Way
> 2. ECharts products and what you can do with it
> 3. Algorithm and performance insights with ECharts
> 4. Cross-platform solution
> 5. 3D rendering with ECharts GL
> 6. How to make ECharts extensions
>
>
> Everyone, please give advice with your ideas!
>
> Wenli
>
>
> On Wed, Sep 18, 2019 at 3:24 PM Zu Ming  wrote:
>
> > Great idea!
> >
> >
> > ECharts can introduce the design of the framework on meetup, so that
> > potential contributors can better understand how to do pr for ECharts.
> You
> > can also post the next demand plan and ask the developer what they need.
> >
> >
> > I look forward to further action. If there are more detailed plans could
> > be discussed  together, such as content preparation, location, frequency
> of
> > activities, promotion plan, budget cost and so on.
> >
> >
> >
> >
> >
> > --
> > Zu Ming
> >
> >
> >
> > At 2019-09-18 14:19:18, "Ovilia"  wrote:
> > >Hi all,
> > >
> > >I've been thinking about holding an ECharts offline meetup recently to
> > know
> > >more about our users and encourage more to join our community.
> > >
> > >I heard about many open source projects hold monthly or yearly events. I
> > >think we could start with one, and then see if it works.
> > >
> > >We can share about technical topics like code structure to help others
> > >understand the source code, and non-technical topics like the Apache
> Way,
> > >how to contribute, and etc. We could also learn from the community about
> > >what they used ECharts for and what do they need help with.
> > >
> > >What do you guys think about this?
> > >
> > >Wenli
> >
>


Re: Happy Mid-Autumn Festival!

2019-09-16 Thread 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” 写入:
>
> :)
>
>
>
>


Re: [DISCUSS] Update on the Website transferation

2019-09-05 Thread Kevin A. McGrail
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: [DISCUSS] Update on the Website transferation

2019-09-05 Thread Kevin A. McGrail
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



Re: [VOTE] Add a banner in non-official websites temporarily

2019-08-27 Thread Kevin A. McGrail
+1 great idea.

On 8/27/2019 05:28, 沈毅 wrote:
> +1 I think it’s a good idea.
>
> Sent from my iPhone
>
>> On Aug 27, 2019, at 5:12 PM, Ovilia  wrote:
>>
>> We are working hard to transfer https://echarts.baidu.com to Apache domain 
>> https://echarts.apache.org .
>> Although we wish to do the transferring job ASAP, I think we all agree that 
>> considering the current situation, the network problem cannot be fixed 
>> within one day or two.
>>
>> So, I have a suggestion that before we complete the transferring job, we 
>> could add a fixed position banner on EVERY PAGE of https://echarts.baidu.com 
>> so that:
>> 1. Branding: It would be obvious for the visitors that ECharts is a project 
>> under ASF.
>> 2. Progressive Enhancement: Obviously, this is better than not doing so. 
>> 3. Community Feedback: In this transition time, we can get feedback from the 
>> community if they really have the problem with the Apache Website.
>>
>> 
>> The text in the banner is:
>> Apache ECharts is an effort undergoing incubation at The Apache Software 
>> Foundation (ASF), sponsored by the Apache Incubator.
>> We are working on redirecting this Website to https://echarts.apache.org.You 
>> may visit our new official Website now for the latest information.
>> Apache ECharts 是一个正在由 Apache 孵化器赞助的 Apache 开源基金会孵化的项目。
>> 我们正在处理将本站跳转到 https://echarts.apache.org 的迁移工作。您可以现在就前往我们的 Apache 
>> 官网以获取最新版的网站信息。
>>  
>>
>>
>> Please vote for this suggestion.
>> PPMC is binding.
>>
>> P.S. We will still try our best to do the transferring job and communicate 
>> with infra about it. This vote has nothing to do with that.
>>
>> Wenli

-- 
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: The resources size of ECharts homepage is too big

2019-08-27 Thread Kevin A. McGrail
I would open a jira to ask.  Note: I do not know if Huawei's offer still
stands.  At this point, it is an old offer and Infra was very negative
about the idea.

On 8/27/2019 00:52, Ovilia wrote:
> I asked the infra about the following question. I copied here in case
> anyone knows.
> I also found that http://doris.apache.org/ routes to a Microsoft
> server, which seems to be more stable than http://echarts.apache.org .
> Are they at a different server or CDN nodes?
>
> I thought we talked about the possibility for us to use the server
> Huawei donated to Apache, but rearched no conclusion.
> Any update on this? Would it be possible for us to have a further
> discussion on this?
>
-- 
Kevin A. McGrail
kmcgr...@apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171



Re: The resources size of ECharts homepage is too big

2019-08-26 Thread Kevin A. McGrail
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
> >
> >
> > On Mon, Aug 26, 2019 at 9:19 PM SHUANG SU
> mailto:sushuang0...@gmail.com>> wrote:
> >
> >> Thanks Wenli.
> >>
> >> Next, we should resolve the problems:
> >>
> >> (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.
> >>
> >> [image: image.png]
> >>
> >> [image: image.png]
> >>
> >> (2) The initial request takes a long time (over 10s) sometimes:
> >> [image: image.png]
> >>
> >>
> >>
> >>
> >> --
> >>  Su Shuang (100pah)
> >> --
> >>
> >>
> >>
> >> On Mon, 26 Aug 2019 at 20:56, Kevin A. McGrail
> mailto:kmcgr...@apache.org>>
> >> wrote:
> >>
> >>> Thanks Wenli.  Do you know in the new version how small it
> is now
> >>> compared to the 10.3MB?
> >>>
> >>> On 8/26/2019 08:49, Ovilia wrote:
> >>>> The change is available at
> >>>>
> >>>
> 
> https://github.com/apache/incubator-echarts-website/commit/f266cfffa1ced1965ad02b1e71482ce4d26dc928
> >>>>  .
> >>>> I compressed most of the images losslessly. For some very
> large ones, I
> >>>> shrunk the image sizes if possible.
> >>>> For example, the largest file scatterGL4.png was 932KB
> with the width of
>     >>>> 800px. I shrunk it into the width of 400px because it's a
> placeholder
> >>> image
> >>>> for a video, so a little blurry is acceptable. The size
> after the
> >>> change is
> >>>> 214KB.
> >>>>
> >>>> But I don't think the website has updated due to expire
> time setting. It
> >>>> was set to be 30 days.
> >>>> I've set it to be one hour a few hours ago, but it seems
> not to be
> >>> updated
> >>>> yet.
> >>>> I'll ask infra for help if it doesn't work tomorr

Re: The resources size of ECharts homepage is too big

2019-08-26 Thread Kevin A. McGrail
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
>
>
> On Mon, Aug 26, 2019 at 9:19 PM SHUANG SU  wrote:
>
>> Thanks Wenli.
>>
>> Next, we should resolve the problems:
>>
>> (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.
>>
>> [image: image.png]
>>
>> [image: image.png]
>>
>> (2) The initial request takes a long time (over 10s) sometimes:
>> [image: image.png]
>>
>>
>>
>>
>> --
>>  Su Shuang (100pah)
>> --
>>
>>
>>
>> On Mon, 26 Aug 2019 at 20:56, Kevin A. McGrail 
>> wrote:
>>
>>> Thanks Wenli.  Do you know in the new version how small it is now
>>> compared to the 10.3MB?
>>>
>>> On 8/26/2019 08:49, Ovilia wrote:
>>>> The change is available at
>>>>
>>> https://github.com/apache/incubator-echarts-website/commit/f266cfffa1ced1965ad02b1e71482ce4d26dc928
>>>>  .
>>>> I compressed most of the images losslessly. For some very large ones, I
>>>> shrunk the image sizes if possible.
>>>> For example, the largest file scatterGL4.png was 932KB with the width of
>>>> 800px. I shrunk it into the width of 400px because it's a placeholder
>>> image
>>>> for a video, so a little blurry is acceptable. The size after the
>>> change is
>>>> 214KB.
>>>>
>>>> But I don't think the website has updated due to expire time setting. It
>>>> was set to be 30 days.
>>>> I've set it to be one hour a few hours ago, but it seems not to be
>>> updated
>>>> yet.
>>>> I'll ask infra for help if it doesn't work tomorrow.
>>>>
>>>> Wenli
>>>>
>>>>
>>>> On Mon, Aug 26, 2019 at 8:41 PM Kevin A. McGrail 
>>>> wrote:
>>>>
>>>>> Thanks.  Some of the images have been compressed from your initial
>>> report.
>>>>> I think 10.3MB is too big too!
>>>>>
>>>>> Is it better (or at least slightly smaller) now?  Which URL are you
>>>>> using to make sure I check the right place?
>>>>>
>>>>>
>>>>> Best,
>>>>>
>>>>> KAM
>>>>>
>>>>> On 8/26/2019 08:38, Zu Ming wrote:
>>>>>> The index page:
>>>>>>   Network Data: 79 request, 10.3MB transferred, it's too big
>>>>>>
>>>>>>
>>>>>> Some image files should be compressed, like:
>>>>>>   scatterGL4.png: 932KB
>>>>>>   index-4.jpg: 452KB
>>>>>>   map.png: 278KB
>>>>>>   pipeline.png: 215KB
>>>>>>   ……
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> thank you
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> At 2019-08-26 20:28:31, "Kevin A. McGrail" 
>>> wrote:
>>>>>>> Zu, I'm afraid the image (screenshot?) did not make it through via
>>>>>>> email.  Can you elaborate on what you are seeing, please?
>>>>>>>
>>>>>>> On 8/26/2019 01:01, Zu Ming wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> Kevin A. McGrail
>>>>>>> kmcgr...@apache.org
>>>>>>>
>>>>>>> Member, Apache Software Foundation
>>>>>>> Chair Emeritus Apache SpamAssassin Project
>>>>>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>>>>>>
>>>>> --
>>>>> 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
>>>>>
>>>>>
>>> --
>>> 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
>>>
>>>
-- 
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: The resources size of ECharts homepage is too big

2019-08-26 Thread Kevin A. McGrail
Thanks Wenli.  Do you know in the new version how small it is now
compared to the 10.3MB?

On 8/26/2019 08:49, Ovilia wrote:
> The change is available at
> https://github.com/apache/incubator-echarts-website/commit/f266cfffa1ced1965ad02b1e71482ce4d26dc928
>  .
> I compressed most of the images losslessly. For some very large ones, I
> shrunk the image sizes if possible.
> For example, the largest file scatterGL4.png was 932KB with the width of
> 800px. I shrunk it into the width of 400px because it's a placeholder image
> for a video, so a little blurry is acceptable. The size after the change is
> 214KB.
>
> But I don't think the website has updated due to expire time setting. It
> was set to be 30 days.
> I've set it to be one hour a few hours ago, but it seems not to be updated
> yet.
> I'll ask infra for help if it doesn't work tomorrow.
>
> Wenli
>
>
> On Mon, Aug 26, 2019 at 8:41 PM Kevin A. McGrail 
> wrote:
>
>> Thanks.  Some of the images have been compressed from your initial report.
>>
>> I think 10.3MB is too big too!
>>
>> Is it better (or at least slightly smaller) now?  Which URL are you
>> using to make sure I check the right place?
>>
>>
>> Best,
>>
>> KAM
>>
>> On 8/26/2019 08:38, Zu Ming wrote:
>>> The index page:
>>>   Network Data: 79 request, 10.3MB transferred, it's too big
>>>
>>>
>>> Some image files should be compressed, like:
>>>   scatterGL4.png: 932KB
>>>   index-4.jpg: 452KB
>>>   map.png: 278KB
>>>   pipeline.png: 215KB
>>>   ……
>>>
>>>
>>>
>>>
>>> thank you
>>>
>>>
>>> --
>>>
>>> At 2019-08-26 20:28:31, "Kevin A. McGrail"  wrote:
>>>> Zu, I'm afraid the image (screenshot?) did not make it through via
>>>> email.  Can you elaborate on what you are seeing, please?
>>>>
>>>> On 8/26/2019 01:01, Zu Ming wrote:
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Kevin A. McGrail
>>>> kmcgr...@apache.org
>>>>
>>>> Member, Apache Software Foundation
>>>> Chair Emeritus Apache SpamAssassin Project
>>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>>>
>> --
>> 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
>>
>>
-- 
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: The resources size of ECharts homepage is too big

2019-08-26 Thread Kevin A. McGrail
Thanks.  Some of the images have been compressed from your initial report.

I think 10.3MB is too big too!

Is it better (or at least slightly smaller) now?  Which URL are you
using to make sure I check the right place?


Best,

KAM

On 8/26/2019 08:38, Zu Ming wrote:
> The index page:
>   Network Data: 79 request, 10.3MB transferred, it's too big
>
>
> Some image files should be compressed, like:
>   scatterGL4.png: 932KB
>   index-4.jpg: 452KB
>   map.png: 278KB
>   pipeline.png: 215KB
>   ……
>
>
>
>
> thank you
>
>
> --
>
> At 2019-08-26 20:28:31, "Kevin A. McGrail"  wrote:
>> Zu, I'm afraid the image (screenshot?) did not make it through via
>> email.  Can you elaborate on what you are seeing, please?
>>
>> On 8/26/2019 01:01, Zu Ming wrote:
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>>  
>>>
>> -- 
>> Kevin A. McGrail
>> kmcgr...@apache.org
>>
>> Member, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
-- 
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: The resources size of ECharts homepage is too big

2019-08-26 Thread Kevin A. McGrail
Zu, I'm afraid the image (screenshot?) did not make it through via
email.  Can you elaborate on what you are seeing, please?

On 8/26/2019 01:01, Zu Ming wrote:
>
>
>
>
>
> --
>
>
>
>  
>
-- 
Kevin A. McGrail
kmcgr...@apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171



Re: Re: Concerns with the Community

2019-08-22 Thread Kevin A. McGrail
Thanks Wenli



On Thu, Aug 22, 2019, 03:01 Ovilia  wrote:

> Hi Dave,
>
> Thank you for pointing out these concerns.
>
> We have already seriously realized ECharts' issues and are acting to
> address them with some more detailed changes and hopefully, help us get
> back on the right track to getting graduated.
>
> 1. Mailing list activity
> The mailing list is not active right now. Here are some changes we did and
> are going to do:
> a. I've just added mailing list and dev@echarts.apache.org in the Readme
> file of GitHub and in the GitHub bot reply.
> b. We are going to discuss our developing plans of each release in the
> mailing list, and ask the community to join the discussion through Twitter
> and other social media, starting right next week.
> c. Technical questions should also be discussed more in the mailing list to
> reach for a better solution.
>
> 2. Website
> Our only concern is CDN speed now. I've opened a ticket in Jira.
> Once this problem has been fixed, we will redirect ASAP.
> I should follow this problem more closely and push it when necessary.
>
> 3. Name search
> We will complete the name search within this month.
>
> 4. Releases
> Currently, it takes about 3-4 months for us to release a version. From the
> next month, we will plan what issues to fix and what features to add and
> control the release period to be about one month.
>
> 5. Better communication with mentors
> We should let mentors and the community know more about what have done and
> what we are doing.
>
> Your continuous guidance and mentorship are critical to our ongoing
> learning and improvement.
>
> Wenli
>
>
> On Thu, Aug 22, 2019 at 2:58 PM Liu Ted  wrote:
>
> > I have had some in-depth coversation with Olivia, with Sheng Wu's help,
> > about these concerns which they have also realized and will take actions
> to
> > rectify them.
> >
> >
> > Best regards,
> >
> > Ted Liu
> >
> >
> >
> > 2019 年 8 月 22 日周四 14:18,Ovilia
> >  写道:
> > I created a ticket in Jira:
> > https://issues.apache.org/jira/browse/INFRA-18919
> >
> > Wenli
> >
> >
> > On Thu, Aug 22, 2019 at 9:54 AM Ovilia  wrote:
> >
> > > OK. I will do that.
> > > Thanks, Kevin.
> > >
> > > Wenli
> > >
> > >
> > > On Wed, Aug 21, 2019 at 11:03 PM Kevin A. McGrail  >
> > > wrote:
> > >
> > >> I would recommend opening a ticket in Jira for INFRA who is handling
> the
> > >> CDN.
> > >>
> > >> Regards,
> > >> KAM
> > >>
> > >> On 8/21/2019 2:15 AM, Ovilia wrote:
> > >> > About the Website loading speed, who should ask for help to have a
> > >> better
> > >> > understanding?
> > >> >
> > >> > Wenli
> > >> >
> > >> >
> > >> > On Thu, Aug 15, 2019 at 2:07 PM Ovilia 
> wrote:
> > >> >
> > >> >> Thanks Dave.
> > >> >>
> > >> >> 1. We are sure to discuss more in the mail list. Sorry for that.
> > >> >>
> > >> >> 2. Currently, the loading speed on some CDN nodes in China is
> > >> acceptable
> > >> >> and some not. We don't know exactly, but from my observation, the
> > >> speed in
> > >> >> Shanghai is quick and the speed in Beijing is slow, where
> > >> >> https://echarts.apache.org/en/option.html takes more than 30
> seconds
> > >> to
> > >> >> load.
> > >> >>
> > >> >> Wenli
> > >> >>
> > >> >>
> > >> >> On Tue, Aug 13, 2019 at 1:54 AM Dave Fisher 
> wrote:
> > >> >>
> > >> >>> 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 

Re: Concerns with the Community

2019-08-21 Thread Kevin A. McGrail
I would recommend opening a ticket in Jira for INFRA who is handling the
CDN.

Regards,
KAM

On 8/21/2019 2:15 AM, Ovilia wrote:
> About the Website loading speed, who should ask for help to have a better
> understanding?
>
> Wenli
>
>
> On Thu, Aug 15, 2019 at 2:07 PM Ovilia  wrote:
>
>> Thanks Dave.
>>
>> 1. We are sure to discuss more in the mail list. Sorry for that.
>>
>> 2. Currently, the loading speed on some CDN nodes in China is acceptable
>> and some not. We don't know exactly, but from my observation, the speed in
>> Shanghai is quick and the speed in Beijing is slow, where
>> https://echarts.apache.org/en/option.html takes more than 30 seconds to
>> load.
>>
>> Wenli
>>
>>
>> On Tue, Aug 13, 2019 at 1:54 AM Dave Fisher  wrote:
>>
>>> 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
>>>
>>>

-- 
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



Re: Project Incubator Problems for Addressing

2019-05-07 Thread Kevin A. McGrail
On 5/7/2019 5:20 AM, SHUANG SU wrote:
> Thanks a lot, Kevin!
>
> Just explain one issue:
>
>> What can be done to increase the Review of PRs? Or move to a
> Commit-Then-Review (CTR) model except near releases.
>
> PR is very important for the project.
> It is inevitable that PR can be merged only after fully reviewed.
> Most of the PR have some defeats (e.g., makes some extra bug, missing test
> cases,
> bad code style, adding code in an inappropriate place, ...).
> And some new feature proposed in PR needs to be discussed thoroughly, that
> probably spend lots of time.
> And some PR resolves only the scenario the contributor meet, not less of
> consideration of general cases.
> Even if the PR is provided by the echarts committer ourselves, it still
> should be reviewed.
> If merged before reviewed and enhanced, it is hard to be reverted.
>
> We should make the code review work more periodically and frequently.
> And make priorities for PR.
> Next, some historical PR need to be collected processed.

I understand.  As long as you discuss it as a project, it's ok.  But let
the project decide.  A vote on discussing a CTR model would be a good
idea and let your voice be one vote.

Regards,

KAM


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



Re: Project Incubator Problems for Addressing

2019-05-07 Thread Kevin A. McGrail
On 5/6/2019 10:42 PM, Ovilia wrote:
> Thanks Kevin!
> That helps a lot.
> I will spend some time diving into it.

Good luck.  And glad to hear the CDN seems to be helping speed a lot.

-- 
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



Project Incubator Problems for Addressing

2019-05-06 Thread Kevin A. McGrail
Hi All,


I've spent some time with other mentors and incubator leadership getting a
handle on some problems to give echarts some clearer guidance. I hope this
is helpful!


-KAM


Problem 1: echarts.apache.org and echarts.apache.org/cn or zh should be
used instead of echartsjs.com.  Is there a Jira open about moving away from

this domain, transferring the domain to the ASF, redirecting to

echarts.apache.org, etc.? If not, please open one and let's discuss
blockers on these issues on list, please.

Problem 2: If these are project sites, they should be redirected as
discussed above:

https://echarts.baidu.com

https://ecomfe.github.io/echarts-doc/public/en/index.html

And the branding issues here:

https://cdnjs.com/libraries/echarts

Are their other project sites, domains, repositories?

Please capture these items in a Jira and add any blockers as well.

NOTE: Did the CDN switchover help times at all in China?


Problem 3: If you are going to use Baidu's analytics, please create a
privacy policy / Terms & Conditions that explains what is collected, how it
is used, etc. using https://www.apache.org/foundation/policies/privacy.html
as a baseline.

Also, if there is a way to opt out, please document that.

Additionally, please discuss on list how the project uses the Baidu
analytics to make decisions.


Problem 4: Omissions in board report.  Please consider things like the
release policy issues and be a little more detailed in your reports.  I
encourage you to work on the report in the open before the due date. This
month again it was a surprise to see it in the wiki but I don’t think I
ever saw the report discussed.


Problem 5: You have a lot of contributors listed in GitHub.  Are you
reviewing these for merit and discussions on list about voting in new PMC
members?

To date, you have only voted in one committer.  That does not indicate a
healthy and diverse community.  Don’t forget to include non-code
contributions like documentation, website work, etc.

What can be done to increase the Review of PRs? Or move to a
Commit-Then-Review (CTR) model except near releases.

For example - https://github.com/apache/incubator-echarts/pull/9388/files
is from the person who was made a committer and it is open waiting for a
review by Shuang Su. Active people appear to be gating on each other.

--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


Fwd: [jira] [Commented] (INFRA-18180) Need a way to make echarts.apache.org quicker for users in China

2019-05-03 Thread Kevin A. McGrail
See below and someone please relay the decision from the project to
Infra :-)


 Forwarded Message 
Subject:[jira] [Commented] (INFRA-18180) Need a way to make
echarts.apache.org quicker for users in China
Date:   Fri, 3 May 2019 16:26:00 + (UTC)
From:   Daniel Gruno (JIRA) 
To: kmcgr...@apache.org




[
https://issues.apache.org/jira/browse/INFRA-18180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832632#comment-16832632
]
Daniel Gruno commented on INFRA-18180:
--

ping - do we have a decision?

> Need a way to make echarts.apache.org quicker for users in China
> 
>
> Key: INFRA-18180
> URL: https://issues.apache.org/jira/browse/INFRA-18180
> Project: Infrastructure
> Issue Type: Planned Work
> Components: TLP Admin, Website
> Reporter: Kevin A. McGrail
> Assignee: Daniel Gruno
> Priority: Major
>
> Users in China accessing echarts.apache.org has a significant
> multi-second latency.
> The project would like to utilize a mirror or similar solution hosted
> in China to help mitigate this issue.
> In the past, Huawei has offered credits for their cloud service before.
> What can we do to support Fundraising and Infra to get something
> ramped up?
> One thought is to use a machine from Huawei with a CDN or a simple
> redirect for  echarts.apache.org/cn/ with a local mirror of the site
> running geo-locally for faster access for
> people in China
> Please advise.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] Switch echarts.apache.org to CDN

2019-04-27 Thread Kevin A. McGrail
Ok so normally the person who calls for a vote is considered an implicit
+1 so this gives you at least 3 +1's and no negatives and it's been a
few days.  I recommend you consider the vote passed and update Jira that
the project approves the move and will test as soon as it's deployed. 

I also ask/recommend that you add the before testing and screenshots to
the Jira for the before and after.

Regards,
KAM

On 4/27/2019 8:23 AM, 沈毅 wrote:
> +1
>
>> 在 2019年4月27日,上午7:05,Ovilia  写道:
>>
>> +1
>>
>> SHUANG SU 于2019年4月26日 周五下午11:54写道:
>>
>>> Start a vote: switch echarts.apache.org to CDN
>>>
>>> Check:
>>>
>>> https://issues.apache.org/jira/browse/INFRA-18180?focusedCommentId=16826353=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16826353
>>> and
>>>
>>> https://lists.apache.org/thread.html/d73a5f085e3ae3bd5599890e871d761b20f4b1af1f617322f166d501@%3Cdev.echarts.apache.org%3E
>>> for details, please.
>>>
>>>
>>>
>>>
>>> --
>>> Su Shuang (100pah)
>>> --
>>>
>> -- 
>> Wenli
> -----
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org
>

-- 
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



Re: CDN for echarts.apache.org

2019-04-26 Thread Kevin A. McGrail
Unbelievably slow times yikes...

Regards,
KAM
On 4/26/2019 10:33 AM, SHUANG SU wrote:
>
>
>
> Thanks a lot !!
>
> I just tested these two pages in Beijing:
>
> http://echarts.apache.org/    totally 7.8 min
> Screen Shot 2019-04-26 at 22.13.14.png
>
> http://echarts.apache.org/option.html#title  totally 1.8 min
> Screen Shot 2019-04-26 at 22.13.49.png
>
> For comparison: loading these two pages
> on https://www.echartsjs.com/ takes less than 3s.
>
> I will test it again after it is switched to CDN and compare it.
>
>
>
>
> --
>  Su Shuang (100pah)
> --
>
>
>
>
> On Fri, 26 Apr 2019 at 21:31, Ovilia  <mailto:oviliazh...@gmail.com>> wrote:
>
> We are very glad to see that. And thank you all for moving this
> forward.
> I'm currently on vacation and Shuang Su (100pah) will check it out.
>
> Kevin A. McGrail  <mailto:kmcgr...@apache.org>>于2019年4月26日 周五上午3:40写道:
>
> > All:
> >
> > To help with the issues with speed for echarts.apache.org
> <http://echarts.apache.org>, Infra is
> > exploring CDN options and they have a viable option available at the
> > moment. I just need the green light and I can get you transferred if
> > that's okay.
> >
> > Can you please let me know when the project is ready for this
> move? It
> > should happen without any downtime, but I would like the project
> to be
> > aware of the switch, so they can properly test the before and after.
> >
> > In short, this will move you from standard TLP servers to a CDN
> solution
> > for echarts.apache.org <http://echarts.apache.org>.
> >
> > It's an anycast CDN solution we're using. the pros should be
> much lower
> > latency outside of our usual EU/US areas (up to three times
> faster in
> > China, our tests show). The cons would be slower loading time
> for the
> > very first visitor, as it is a caching proxy, and that's about it.
> >
> > This is a very manual process, and not something we can automate
> for all
> > TLPs, so this is, for now, a sort of one-off for echarts.
> >
> >
> > We are pretty much ready to go now, so whenever you wish, we can
> switch
> > over to the CDN (and it'll go live within an hour after that)
> >
> > Recommendations:
> >
> > 1 - Please test the speed of echarts.apache.org
> <http://echarts.apache.org> now so we have a
> > baseline to compare
> > 2 - Please take a vote on the PMC about moving to this CDN
> > 3 - Please update
> >
> >
> 
> https://issues.apache.org/jira/browse/INFRA-18180?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16826230#comment-16826230
> > when/if
> >
> 
> <https://issues.apache.org/jira/browse/INFRA-18180?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16826230#comment-16826230when/if>
> > your project greenlights the move
> >
> > Regards,
> >
> > KAM
> >
> > --
> > 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: private-unsubscr...@echarts.apache.org
> <mailto:private-unsubscr...@echarts.apache.org>
> > For additional commands, e-mail: private-h...@echarts.apache.org
> <mailto:private-h...@echarts.apache.org>
> >
> > --
> Wenli
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171



CDN for echarts.apache.org

2019-04-25 Thread Kevin A. McGrail
All:

To help with the issues with speed for echarts.apache.org, Infra is
exploring CDN options and they have a viable option available at the
moment. I just need the green light and I can get you transferred if
that's okay.
   
Can you please let me know when the project is ready for this move? It
should happen without any downtime, but I would like the project to be
aware of the switch, so they can properly test the before and after.

In short, this will move you from standard TLP servers to a CDN solution
for echarts.apache.org.

It's an anycast CDN solution we're using. the pros should be much lower
latency outside of our usual EU/US areas (up to three times faster in
China, our tests show). The cons would be slower loading time for the
very first visitor, as it is a caching proxy, and that's about it.

This is a very manual process, and not something we can automate for all
TLPs, so this is, for now, a sort of one-off for echarts.


We are pretty much ready to go now, so whenever you wish, we can switch
over to the CDN (and it'll go live within an hour after that)

Recommendations:

1 - Please test the speed of echarts.apache.org now so we have a
baseline to compare
2 - Please take a vote on the PMC about moving to this CDN
3 - Please update
https://issues.apache.org/jira/browse/INFRA-18180?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16826230#comment-16826230
when/if your project greenlights the move

Regards,

KAM

-- 
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



Re: [VOTE] ECharts Website Analytics policy

2019-04-18 Thread Kevin A. McGrail
The big issue here is fixing the speed with which the current site loads
for Chinese users.  Infra is against the vm in China based on the jira
ticiet I opened but is investigating other ideas like cdn models.  Please
email Greg Stein directly for more information per the ticket.

As for Tongij vs GA, I don't see the difference.  I would stay with BT and
create a policy about what you are tracking and why as well as get everyone
access to it.

We all know the gfw will block a lot of Google stuff.

I really like that you are discuss this and on list to try and figure stuff
out.

Regards, KAM

On Thu, Apr 18, 2019, 13:34 Dave Fisher  wrote:

> 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 

Re: Website changes are required for transition to Apache

2019-04-12 Thread Kevin A. McGrail
The new VP of privacy is John Kinsella , fyi.
Recommend you ask for guidance on how the projects can use other analytic
tools like Baidu analytics as well as Google analytics.

On Mon, Apr 8, 2019, 22:35 Ovilia  wrote:

> The reason why we need analytics is that we need to get the page view and
> download number over time so that we can make sure our product is under a
> healthy growth.
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> Dave Fisher  于2019年4月9日周二 上午2:34写道:
>
> > The current policy is here:
> >
> > 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
> > 
> >
> >
> >
>


Re: Website changes are required for transition to Apache

2019-04-08 Thread Kevin A. McGrail
On 4/8/2019 2:34 PM, Dave Fisher wrote:
> The current policy is here:
>
> 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.


I'm not sure any approval process happened for this for Google
Analytics, I think it just organically occurred.  We have a VP, Data
Privacy.  Jim, did that position get filled at the last board meeting? 
If so, can you weigh in on echarts use of Baidu Analytics?

Regards,

KAM


-
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

2019-04-08 Thread Kevin A. McGrail
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



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

2019-03-26 Thread Kevin A. McGrail
I think a Jira ticket is best to keep the ball moving.

Please take a look at https://issues.apache.org/jira/browse/ECHARTS-2
and feel free to add comments.

Regards,
KAM

On 3/25/2019 2:28 AM, Ovilia wrote:
> Thanks Kevin.
>
> Please let us know if there's anything we should do.
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> Kevin A. McGrail  于2019年3月23日周六 上午6:22写道:
>
>> On 3/21/2019 10:44 PM, Dave Fisher wrote:
>>>> 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.
>>
>> I'm happy to discuss this.  The roadshow is on Monday which I'm chairing
>> so I need some breathing room but:
>>
>> - Huawei has offered credits for their cloud service before.  I'm happy
>> to liaise with Fundraising and Infra to see if we can get something
>> ramped up.
>>
>> - We need to move everything to our infrastructure though and I would
>> start that.
>>
>> - To fix the latency, I'd like to figure out either some use of a CDN
>> running on Huawei or perhaps when you go to echarts.apache.org/cn/ you
>> get a mirror of the site running on huawei for super fast access for
>> people in China
>>
>> That's my overall thought process right now.  I believe it's pretty
>> close to the off the cuff responses I've written before and love
>> supporting your project!
>>
>> Regards,
>>
>> KAM
>>
>> --
>> Kevin A. McGrail
>> Member, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>>

-- 
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



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

2019-03-22 Thread Kevin A. McGrail
On 3/21/2019 10:44 PM, Dave Fisher wrote:
>> 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.

I'm happy to discuss this.  The roadshow is on Monday which I'm chairing
so I need some breathing room but:

- Huawei has offered credits for their cloud service before.  I'm happy
to liaise with Fundraising and Infra to see if we can get something
ramped up.

- We need to move everything to our infrastructure though and I would
start that.

- To fix the latency, I'd like to figure out either some use of a CDN
running on Huawei or perhaps when you go to echarts.apache.org/cn/ you
get a mirror of the site running on huawei for super fast access for
people in China

That's my overall thought process right now.  I believe it's pretty
close to the off the cuff responses I've written before and love
supporting your project!

Regards,

KAM

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171



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

2019-03-04 Thread Kevin A. McGrail
Yes, I think so.  See
https://incubator.apache.org/guides/releasemanagement.html at the bottom
under Podling Constraints.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Mar 4, 2019 at 1:25 AM Yi Shen  wrote:

> My vote is +1 binding.
>
> Do we need the (incubating) in the release note?
>
> SHUANG SU  于2019年3月1日周五 上午2:19写道:
>
> > I am pleased to be calling this vote for the release of Apache ECharts
> > 4.2.1 (release candidate 3).
> >
> > The major update from 4.2.1 release candidate 1 to candidate 2 is about
> the
> > license statement.
> > See more details in
> >
> >
> https://lists.apache.org/thread.html/3817a70b2ec34a25b82f4a1310398ae9df8cdc6728fa289c941c5fde@%3Cdev.echarts.apache.org%3E
> >
> > The major update from 4.2.1 release candidate 2 to candidate 3 is a fix
> of
> > a non-negligible bug.
> >
> > 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
> >
> > # Build 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 4.2.1 (release candidate 3)
> > by "2019-03-03T19:05:39.353Z".
> >
> > [ ] +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.
> >
> > --
> >
> > Thanks,
> > --
> >  Su Shuang (100pah)
> > --
> >
>
>
> --
> Yi Shen
> Senior Developer
> Baidu, Inc.
>


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

2019-03-01 Thread Kevin A. McGrail
NOTE that I am out of pocket for a few days so I cannot contribute to
this vote but I'll be working on building a dev system so I can work on
echarts without risking my production system!

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



Re: Steps to Complete the Move from Baidu to Apache

2019-02-28 Thread Kevin A. McGrail
Thank you for that detailed explanation. I will endeavor to remember
this because in English we would typically write it as First Nickname
Lastname so like Wenli "Ovilia" Zhang or Kevin "KAM" McGrail in my
case!   Thanks, Wenli.

Regards,
KAM

On 2/28/2019 3:17 AM, Ovilia wrote:
> Sorry for the late reply.
>
> Wenli is my First name, and Zhang is my Last name / Family name.
> In the Chinese language, I'm called Zhang Wenli.
> I'm not sure whether I should be called Zhang Wenli or Wenli Zhang in
> English. English teachers would prefer Wenli Zhang. But the names on my
> credit cards and passport are all "Zhang Wenli". So generally I use Zhang
> Wenli to avoid misunderstandings.
>
> Ovilia is my nickname online. I coined this name from Olivia since Ovilia
> sounds quite like "Oh, Wenli Ah!" in Chinese...
>
> In conclusion, I would prefer to be called Wenli or Ovilia. :)
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> On Fri, Feb 22, 2019 at 10:44 PM Kevin A. McGrail 
> wrote:
>
>> Hi Ovilia,
>>
>> BTW, odd Westerner question.  You write your name as Zhang Wenli and
>> your email as Ovilia.  Could you please tell me more about that?  Which
>> is your First Name, Last Name and possibly a Nickname?  For me, for
>> example, Kevin is my first name, Andrew is my middle name, McGrail is my
>> last name (or family name) and KAM is my initials / nickname in one.
>> I'm trying to learn what name you like to be called and I'm worried
>> sometimes I have no idea if I am calling you by your last name, first
>> name, nickname or something else :-)
>>
>>> We choose Baidu Tongji (meaning Analytics) out of the consideration of
>> the
>>> accessibility to Google products in China.
>> One 3rd party versus another as far as I'm concerned so the same
>> question I would ask if it was Google Analytics.  Question: is the
>> account for that a role-based account shared for the podling PMC to
>> access so that it is accessible to all and stays with the project?
>>
>>
>>> As Kevin suggested, Huawei provided servers for Apache that we may use.
>>> That's a great idea.
>>> But just to be clear, are the servers provided in the form of Huawei
>> Cloud
>>> [1] that can be assumed to be accessed all the time, or something like an
>>> SSH account which Huawei could deauthorize afterward? If it's in the
>> latter
>>> form, I guess that's pretty much like we are facing today, only that the
>>> server is on Baidu rather than Huawei.
>> Yes and no. If we went that route of using Huawei, we would be formally
>> asking them under the ASF targeted sponsorship policy
>> (
>> https://docs.google.com/document/d/1JhZEcty2fSx7ZxiBs41j3qOUrqsA7TvKmQ13ZZ61lJY/edit
>> )
>> and a formal agreement would be created so it couldn't just be pulled
>> out from under.  This is one of the reasons we ask for 3 year agreements
>> for hosting donations to promote stability.
>>
>> If Baidu is willing to donate some services, that's feasible to pursue
>> especially echarts as a PMC is requesting and will use it.  I just
>> didn't know they, Baidu, provided those services too.  If Baidu is
>> willing to donate things, you could get root access to the box over to
>> infra, use resources from Baidu and as I described, we could use a
>> different URL for that mirror server to give faster access to the people
>> in China.  It will have to be an alternate URL though like we discussed
>> and it should be a mirror of the same info on the main URL, but faster :-)
>>
>> Regards,
>>
>> KAM
>>
>> --
>> 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
>>
>>

-- 
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



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

2019-02-25 Thread Kevin A. McGrail


> [X] +1 Release this package

I like seeing the steady improvements you are making and vote +1 on this.

Regards,

KAM


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



Re: Draw chart

2019-02-23 Thread Kevin A. McGrail
Interesting POV.  I don't know if that's good or bad but in general, I
try and promote our users@ list.  But if users are getting good answers,
perhaps that's best and you have a lot on your plate already.

Regards,
KAM
On 2/23/2019 5:28 AM, Ovilia wrote:
> Sorry. I actually meant Stack
> Overflow. https://stackoverflow.com/questions/tagged/echarts
>
> Because I don't think mail list is a great place for asking questions
> about how to use ECharts. Otherwise, we would end up with tons of
> emails asking how-to questions and we don't have time to answer them
> all and to develop new features. The number of persons following the
> mail list is quite limited, and for those who have similar questions
> in the future, Stack Overflow provides a better SEO result and user
> experience.
>
> That's what I thought, but I'm willing to know about what other
> popular projects solve such problems, both from Apache and GitLab,
> which I think Clement may also have some comments.
>
> Thanks for raising up this topic and we do wish to find a better
> solution for this.
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> On Fri, Feb 22, 2019 at 11:33 PM Kevin A. McGrail  <mailto:kmcgr...@apache.org>> wrote:
>
> On 2/21/2019 10:20 PM, Ovilia wrote:
> > Hi, sorry I cannot see your image.
> > Although we do wish to help, questions in the form of *how to
> use ECharts
> > to ...* should be issued at https://segmentfault.com/t/echarts
> to let more
> > people help and make it accessible to others who later search.
>
> Why would you push them to segmentfault rather than a users@ list
> at apache?
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> <mailto:dev-unsubscr...@echarts.apache.org>
> For additional commands, e-mail: dev-h...@echarts.apache.org
> <mailto:dev-h...@echarts.apache.org>
>

-- 
*Kevin A. McGrail*
703-798-0171 (wireless)
https://www.linkedin.com/in/kmcgrail


Re: Draw chart

2019-02-22 Thread Kevin A. McGrail
On 2/21/2019 10:20 PM, Ovilia wrote:
> Hi, sorry I cannot see your image.
> Although we do wish to help, questions in the form of *how to use ECharts
> to ...* should be issued at https://segmentfault.com/t/echarts to let more
> people help and make it accessible to others who later search.

Why would you push them to segmentfault rather than a users@ list at apache?



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



Re: Steps to Complete the Move from Baidu to Apache

2019-02-22 Thread Kevin A. McGrail
Hi Ovilia,

BTW, odd Westerner question.  You write your name as Zhang Wenli and
your email as Ovilia.  Could you please tell me more about that?  Which
is your First Name, Last Name and possibly a Nickname?  For me, for
example, Kevin is my first name, Andrew is my middle name, McGrail is my
last name (or family name) and KAM is my initials / nickname in one. 
I'm trying to learn what name you like to be called and I'm worried
sometimes I have no idea if I am calling you by your last name, first
name, nickname or something else :-)

> We choose Baidu Tongji (meaning Analytics) out of the consideration of the
> accessibility to Google products in China.

One 3rd party versus another as far as I'm concerned so the same
question I would ask if it was Google Analytics.  Question: is the
account for that a role-based account shared for the podling PMC to
access so that it is accessible to all and stays with the project?


> As Kevin suggested, Huawei provided servers for Apache that we may use.
> That's a great idea.
> But just to be clear, are the servers provided in the form of Huawei Cloud
> [1] that can be assumed to be accessed all the time, or something like an
> SSH account which Huawei could deauthorize afterward? If it's in the latter
> form, I guess that's pretty much like we are facing today, only that the
> server is on Baidu rather than Huawei.

Yes and no. If we went that route of using Huawei, we would be formally
asking them under the ASF targeted sponsorship policy
(https://docs.google.com/document/d/1JhZEcty2fSx7ZxiBs41j3qOUrqsA7TvKmQ13ZZ61lJY/edit)
and a formal agreement would be created so it couldn't just be pulled
out from under.  This is one of the reasons we ask for 3 year agreements
for hosting donations to promote stability.

If Baidu is willing to donate some services, that's feasible to pursue
especially echarts as a PMC is requesting and will use it.  I just
didn't know they, Baidu, provided those services too.  If Baidu is
willing to donate things, you could get root access to the box over to
infra, use resources from Baidu and as I described, we could use a
different URL for that mirror server to give faster access to the people
in China.  It will have to be an alternate URL though like we discussed
and it should be a mirror of the same info on the main URL, but faster :-)

Regards,

KAM

-- 
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



Re: Steps to Complete the Move from Baidu to Apache

2019-02-21 Thread Kevin A. McGrail
Ah.  For a non apache.org domain / sub domain I see your point.

On Thu, Feb 21, 2019, 20:30 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
> >
>
>


Re: Steps to Complete the Move from Baidu to Apache

2019-02-21 Thread Kevin A. McGrail
On 2/21/2019 6:10 PM, Justin Mclean wrote:
> Hi,
>
>> Re: #7 Google Analytics at the moment is fine but there are tracking
>> concerns and the Apache VP of Privacy has just been re-filled.  Things
>> like GDPR and data breaches are really shaking things like this up so I
>> don't have an easy answer other than for now, I think it's fine because
>> of what it's used for.
> I'm not sure I agree given it's a 3rd party tracking use in an ASF site. It 
> might be OK for the PPMC to track usage and the whole PPMC have access to 
> those stats, but for a 3rd party where only some the PPMC have access?
Not sure what you mean about 3rd party, etc. but there are definitely
analytics/urchin tags on some of the ASF Sites.

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



Re: Steps to Complete the Move from Baidu to Apache

2019-02-21 Thread Kevin A. McGrail
 for Apache Projects. [2]
>
> You must include links to www.apache.org
> <http://www.apache.org> <http://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/
> <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
> <https://gallery.echartsjs.com/editor.html>
> (b) https://twitter.com/EChartsJs
> <https://twitter.com/EChartsJs> (where there’s no indication
> it’s an ASF project and links to ecomfe.github.io
> <http://ecomfe.github.io> <http://ecomfe.github.io/>)
> (c) https://www.weibo.com/echarts
> <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
> <mailto:dev@echarts.apache.org> <mailto:dev@echarts.apache.org
> <mailto:dev@echarts.apache.org>>.
> (b) Also the GitHub link must point directly to
> https://github.com/apache/incubator-echarts/
> <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
> <http://hm.baidu.com> <http://hm.baidu.com/> link on several
> pages. Please remove.
> (b) another tracker in log.js again pointing to
> echarts.baidu.com <http://echarts.baidu.com>
> <http://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
> <https://www.apache.org/foundation/marks/pmcs#websites>
> [2] https://www.apache.org/foundation/marks/pmcs#navigation
> <https://www.apache.org/foundation/marks/pmcs#navigation>
> [3] https://www.apache.org/foundation/marks/pmcs#nonapache
> <https://www.apache.org/foundation/marks/pmcs#nonapache>
> [4] https://www.apache.org/foundation/marks/pmcs#attributions
> <https://www.apache.org/foundation/marks/pmcs#attributions>
> [5] https://www.apache.org/dev/release-distribution.html
> <https://www.apache.org/dev/release-distribution.html>
> [6]
> 
> https://raw.githubusercontent.com/ecomfe/echarts/4.1.0/dist/echarts.simple.min.js
> 
> <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
> 
> <https://github.com/apache/incubator-echarts-website/blob/asf-site/js/log.js>
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171



Re: Steps to Complete the Move from Baidu to Apache

2019-02-19 Thread Kevin A. McGrail
On 2/19/2019 5:14 PM, Dave Fisher wrote:
> Your Mentors are here to help!

+1 for this statement.  It never hurts to squeak to get my help.

-- 
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



Re: Anything I can help with to get your incubator report in ASAP?

2019-02-07 Thread Kevin A. McGrail
No I think this is good.  I will continue to work to guide you towards
appropriate release procedures and I think you are making good strides
as a project.  Rome wasn't built in a day!

Regards,
KAM

On 2/7/2019 2:51 AM, Ovilia wrote:
> Thanks Kevin.
>
> I missed some detail in the report that we are discussing in mail list.
> Now I have updated the report.
> Please tell me if there's anything I should do.
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> On Thu, Feb 7, 2019 at 10:49 AM Kevin A. McGrail 
> wrote:
>
>> Hi All, I believe your draft was close but there were some comments to
>> get it finalized for mentor signoff.  Anything I can do to help?
>>
>> Happy New Year,
>>
>> KAM
>>
>> --
>> 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
>>
>>

-- 
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



Anything I can help with to get your incubator report in ASAP?

2019-02-06 Thread Kevin A. McGrail
Hi All, I believe your draft was close but there were some comments to
get it finalized for mentor signoff.  Anything I can do to help?

Happy New Year,

KAM

-- 
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



Fwd: Draft incubator report

2019-02-05 Thread Kevin A. McGrail
Good news that there is a nuance here about advertised vs. available. 
So the previous email I wrote should work to get you guys into compliance.

Let me know if you have more questions and Happy New Year,

KAM



 Forwarded Message 
Subject:Re: Draft incubator report
Date:   Wed, 6 Feb 2019 07:52:37 +1100
From:   Justin Mclean 
Reply-To:   gene...@incubator.apache.org
To: gene...@incubator.apache.org



HI,

> "A reminder to all incubating projects and mentors that all releases
> and distributions advertised to the general public need to be approved by
> the PPMC and IPMC. This includes docker, github, PyPi, npm and any
> other platform for publishing releases, and also covers release
> candidates.
> Nightly builds for project-internal use clearly marked as "snapshot" or
> "prerelease" (or similar) can be made available to project
> contributors. If
> in doubt please ask your mentors or on the incubator general list."
>
> Objections?

None from me. I’ll make the change.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: ECharts incubator report

2019-02-03 Thread Kevin A. McGrail
As a mentor, I've been following this.  There is a legal concern here so
it is best if we get on the right track as soon as possible.

I understand removing things from npm is a PITA.  But retagging is easy.

The biggest issue seems to be retagging the rc1.  Can you get an rc2 or
ideally a proper release voted on and up on npm ASAP and then tag rc1 as
deprecated?

Is there concern about using the deprecated tag?

Even if rc2 is just a more formally voted release with a version change,
getting it up there and tagged with rc seems to be a good fix.

I would recommend not going to the board.  That will just be discussed
and likely kicked back for more discussion causing you months of delay.

Regards,
KAM

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



Re: ECharts incubator report

2019-01-30 Thread Kevin A. McGrail
Are you talking about the email with subject: "Re: [VOTE] Release Apache
ECharts 4.2.1 (release candidate 1)" from 1/29 started by you?

I haven't dug in and checked everything like LICENSES and headers or the
signatures and but overall it looks really strong and I would vote +1
but you need to have sha256 or sha512 signatures to verify the zip file.

I will setup a suitable node.js environment for this so I can test
future builds and be more involved.

Regards,
KAM

On 1/30/2019 11:05 AM, Ovilia wrote:
> Dear mentors,
>
> We've published our release vote on general@, but it has got no reply by
> now.
> Could you have a look at it, and give a +1 perhaps?
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> On Wed, Jan 30, 2019 at 11:34 PM Dave Fisher  wrote:
>
>> 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
>>>
>>

-- 
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



Re: ECharts incubator report

2019-01-30 Thread Kevin A. McGrail
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



Fwd: Google Summer of Code 2019 is coming

2019-01-25 Thread Kevin A. McGrail
Podlings, please take a look at this and ask me questions.  This can be
a great way of getting some fresh eyes on a project.


Regards,
KAM



 Forwarded Message 
Subject:Google Summer of Code 2019 is coming
Date:   Fri, 25 Jan 2019 20:50:23 +0700
From:   Maxim Solodovnik 
Reply-To:   ment...@community.apache.org
To: ment...@community.apache.org



Hello PMCs (incubator Mentors, please forward this email to your podlings),

Google Summer of Code [1] is a program sponsored by Google allowing
students to spend their summer
working on open source software. Students will receive stipends for
developing open source software
full-time for three months. Projects will provide mentoring and
project ideas, and in return have
the chance to get new code developed and - most importantly - to
identify and bring in new committers.

The ASF will apply as a participating organization meaning individual
projects don't have to apply separately.

If you want to participate with your project we ask you to do the
following things by no later than
2019-01-31 19:00 UTC (applications from organizations close a week later)

1. understand what it means to be a mentor [2].

2. record your project ideas.

Just create issues in JIRA, label them with gsoc2019, and they will
show up at [3]. Please be as
specific as possible when describing your idea. Include the
programming language, the tools and
skills required, but try not to scare potential students away. They
are supposed to learn what's
required before the program starts.

Use labels, e.g. for the programming language (java, c, c++, erlang,
python, brainfuck, ...) or
technology area (cloud, xml, web, foo, bar, ...).

Please use the COMDEV JIRA project for recording your ideas if your
project doesn't use JIRA (e.g.
httpd, ooo). Contact d...@community.apache.org if you need assistance.

[4] contains some additional information (will be updated for 2019 shortly).

3. subscribe to ment...@community.apache.org; restricted to potential
mentors, meant to be used as a
private list - general discussions on the public
d...@community.apache.org list as much as possible
please). Use a recognized address when subscribing (@apache.org or one
of your alias addresses on
record).

Note that the ASF isn't accepted as a participating organization yet,
nevertheless you *have to*
start recording your ideas now or we might not get accepted.

Over the years we were able to complete hundreds of projects
successfully. Some of our prior
students are active contributors now! Let's make this year a success again!

P.S.: this email is free to be shared publicly if you want to.

[1] https://summerofcode.withgoogle.com/
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] https://issues.apache.org/jira/issues/?jql=labels+%3D+gsoc2019
[4] http://community.apache.org/gsoc.html


Re: Criteria for new ECharts committers

2018-11-06 Thread Kevin A. McGrail
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
>


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

2018-11-05 Thread Kevin A. McGrail
I have been holding off hoping you got 3 binding from the community.  I
think you do now, yes?

On Sun, Nov 4, 2018, 10:01 PM Deqing Li  +1  binding
>
> Yi Shen  于2018年11月1日周四 上午1:07写道:
>
> > +1 binding
> >
> > checked:
> > - distribution files are correct.
> > - No files missing license.
> >
> > SHUANG SU  于2018年10月27日周六 下午4:23写道:
> >
> > > I am pleased to be calling this vote for the release of Apache ECharts
> > > 4.2.0 (release candidate 2).
> > >
> > > The release candidate to be voted over is available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.0-rc.2/
> > >
> > > The release candidate is signed with a GPG key available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> > >
> > > The Git commit for this release is:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=1a566de
> > >
> > > The Release Note is available in:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.0-rc.2/RELEASE_NOTE.txt
> > >
> > > Some shell commands for validating the release:
> > >
> > > ```shell
> > > # Download the release:
> > > curl
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.0-rc.2/apache-echarts-4.2.0-rc.2-incubating-src.zip
> > > -o apache-echarts-4.2.0-rc.2-incubating-src.zip
> > > unzip apache-echarts-4.2.0-rc.2-incubating-src.zip -d
> > > apache-echarts-4.2.0-rc.2-incubating-src > /dev/null
> > >
> > > # Build the project (Node.js environment is required):
> > > cd "apache-echarts-4.2.0-rc.2-incubating-src" && npm install && cd ..
> > > node "apache-echarts-4.2.0-rc.2-incubating-src/build/build.js"
> --release
> > > # (See help: `node
> > > "apache-echarts-4.2.0-rc.2-incubating-src/build/build.js" --help`)
> > > ```
> > >
> > >
> > > Please vote on releasing this package as:
> > > Apache ECharts 4.2.0 (release candidate 2)
> > > by "2018-10-30T09:12:13.512Z".
> > >
> > > [ ] +1 Release this package
> > > [ ] 0 I don't feel strongly about it, but don't object
> > > [ ] -1 Do not release this package because...
> > >
> > > Anyone can participate in testing and voting, not just committers,
> please
> > > feel free to try out the release candidate and provide your votes.
> > >
> > >
> > > --
> > >  Su Shuang (100pah)
> > > --
> > >
> >
> >
> > --
> > Yi Shen
> > Senior Developer
> > Baidu, Inc.
> >
>


IMPORTANT: OSS Employment Survey - Now Open to Self-Employed and Retired

2018-10-22 Thread Kevin A. McGrail
Good morning everyone,

After the feedback from ComDev and discussions with Dr. Daniel, I'm
happy to report that Self-Employed and Retired people are now eligible. 
Also, the survey now allows for skipping any questions that are too
personal.

We need more samples and would appreciate if you could spread the word
on this to your PMC.  We need more info about careers in OSS and this is
a great way to get it.  I'm also hoping they have enough responses to
report on the preliminary findings at the Apache Washington DC Roadshow
on Dec 4th (http://apachecon.com/usroadshow18)

They now invite anyone over 18 years old, with experience in the Apache
community to fill out the survey.  -KAM

Please click the following link to start the survey:
http://cincinnati.ca1.qualtrics.com/jfe/form/SV_3h3D0bMEHrQ47xr

The survey should take 10-15 minutes and you can skip any questions you
find to be too personal. Upon completion
· you will be placed in a lottery where you have TWO chances to
win $250
· we’ll donate $5 to Apache—up to $1000 total

We believe in the importance of the work that you do and we want to
support it. Thanks for engaging with us.

 -Sherae, Liwei, and Jaime

 

-- 
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



Re: ICLA of new committer

2018-10-17 Thread Kevin A. McGrail
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


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

2018-10-15 Thread Kevin A. McGrail
Hi All,

We should be looking at people to add to the PMC.  You guys do a ton of
work on the product and need to focus on the community growth too!

It's amazing to login to my computer and see all the work you do overnight!

Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


-- Forwarded message -
From: Dave Fisher 
Date: Mon, Oct 15, 2018 at 2:26 PM
Subject: At Least 10 Podling Rosters are Messed Up in Whimsy
To: Apache Incubator PMC 


Hi IPMC,

I’ve reviewed whimsy rosters and have found that 10 of 51 podlings rosters
are definitely messed up and show either no or very few PPMC members.

These are:
Gearpump
Gobblin
Hivemall
Marvin-AI
Nemo
Omid
Quickstep
Unomi
Spot
Annotator
I’m not sure that Livy is updated properly.

These probably missed an update to the roster:
Pagespeed
BatchEE
Joshua
Sensoft
Superset

The following show no growth:
Crail
Daffodil
Doris
ECharts
Milagro
Tephra
Weex
Regards,
Dave


Re: cant send you email with attachments

2018-10-12 Thread Kevin A. McGrail
Yeah, I think you need to email that ICLA only to secret...@apache.org and
that limit won't apply.  Mention that it's for echarts and the incubator as
Mr. Fisher mentioned.
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Fri, Oct 12, 2018 at 10:59 AM Юрий Гор  wrote:

> I tried grayscale gifs 747 KiB total
> reject message said maximum is 1MB
>
> пт, 12 окт. 2018 г. в 17:43, Kevin A. McGrail :
>
> > Perhaps it's too large.  How big is the file?
> >
> > On 10/12/2018 3:45 AM, Юрий Гор wrote:
> > > Hi, I cant send you email with attachments (signed ICLA), it always
> > rejected
> > >
> >
> > --
> > 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
> >
> >
>
> --
> Best, Yuri
>


Re: cant send you email with attachments

2018-10-12 Thread Kevin A. McGrail
Perhaps it's too large.  How big is the file?

On 10/12/2018 3:45 AM, Юрий Гор wrote:
> Hi, I cant send you email with attachments (signed ICLA), it always rejected
>

-- 
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



Re: ICLA of new committer

2018-10-11 Thread Kevin A. McGrail
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: ICLA of new committer

2018-10-08 Thread Kevin A. McGrail
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  <mailto:oviliazh...@gmail.com>> wrote:
>
> Dear mentors,
>
> We have merged a pull request
> (https://github.com/apache/incubator-echarts/pull/8759) from the
> community, and his ICLA file is attached in this email.
>
> This is the first time we merge a PR after we joined Apache. So
> please tell us if there's anything else we need to do.
>
> Thanks!
>
> Zhang Wenli
> http://zhangwenli.com
>

-- 
*Kevin A. McGrail*
703-798-0171 (wireless)
https://www.linkedin.com/in/kmcgrail


Re: How to add new committers

2018-09-03 Thread Kevin A. McGrail
Hi Wenli,

I do not know if incubator has a specific process but here are a few
thoughts:

- See https://community.apache.org/newcommitter.html

- Is the patch trivial?  If not, they will need an ICLA. 
https://www.apache.org/licenses/icla.pdf  When in doubt, ask the
Secretary at ASF's opinion.

- Community is more important than code so this is awesome.  Promoting
community growth is one of the best things to invest your time in and
something I did not appreciate for too long.

- If their code is good, and the PR is sane, and a CLA is filed, use it
as a way to perhaps pair them with another committer.

They do NOT have to be a committer to be a contributor. 

Regards,
KAM
On 9/3/2018 2:47 AM, Wenli Zhang wrote:
> Dear mentors,
>
> We are considering merging new PR at
> https://github.com/apache/incubator-echarts/pull/8966 . Since this is the
> first time we accept commit from community, I have a few questions to ask:
>
> 1. Does he need to become a committer (so that he need to follow
> https://www.apache.org/dev/new-committers-guide.html ) before or after we
> merge the pull request?
>
> 2. Is there anything else we need to do before and after we merge the PR?
>
> Thanks!
>
> Zhang Wenli
> http://zhangwenli.com
>

-- 
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



Re: [RESULTS] [VOTE] Release Apache ECharts 4.1.0.rc3

2018-05-11 Thread Kevin A. McGrail
John how do binding votes work?  Do the ipmc members it get binding votes?
Do They need 3 binding for a release?

On Fri, May 11, 2018, 07:20 SHUANG SU <sushuang0...@gmail.com> wrote:

> This vote passes with 5 [+1] binding votes and no [0] or [-1] votes.
>
> +1 binding: [5]
> Tan,Zhongyi
> 李木子
> Kevin A. McGrail
> 沈毅
> Wenli Zhang
>
> Vote thread:
> https://lists.apache.org/thread.html/67dffef28ecffd66689ac991ca027c
> 0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E
>
> I'll continue with the release process on general@ and the release
> announcement will follow in the next few days.
>
>
>
> --
>  Su Shuang (100pah)
> --
>


Re: [VOTE] Release Apache ECharts 4.1.0.rc1

2018-05-03 Thread Kevin A. McGrail
Hi Shuang, I don't know that John will have the cycles to respond but there
is nothing stopping you from proposing a new RC and taking a vote though of
course, you generally only want to do so when you believe issues have been
hammered out.

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 Wed, May 2, 2018 at 2:18 AM, SHUANG SU <sushuang0...@gmail.com> wrote:

> John,
>
> Could I release rc2 now?
>
>
> --
>  Su Shuang (100pah)
> --
>
>
> 2018-04-30 1:23 GMT+08:00 SHUANG SU <sushuang0...@gmail.com>:
>
> > John,
> >
> > I think that Apache Rat is used to check which files are missing license
> > and add licenses for them. (Do I understand it right?)
> >
> > Before we know the tool Apache Rat, another tool,
> `echarts/build/addHeader.js`,
> > has been created to do that job:
> >
> > Run it in the Node.js environment:
> > `node build/addHeader.js`
> > Then the source files that are missing license will be added an Apache
> > License.
> >
> > I have also tried Apache Rat just now to check the license, got the same
> > result.
> > (but got some trouble when trying to add a license, have not followed up
> > on this issue yet.)
> >
> > For most of the JavaScript project developers, Java environment is not
> > necessarily installed,
> > but the Node.js usually already installed for building projects. So could
> > we use the
> > `build/addHeader.js` to do the jobs of checking and adding the license?
> >
> >
> >
> >
> >
> >
> > --
> >  Su Shuang (100pah)
> > --
> >
> >
> >
> > 2018-04-29 20:25 GMT+08:00 John D. Ament <johndam...@apache.org>:
> >
> >> Su,
> >>
> >> Did you ever see my question about running Apache Rat against the
> project?
> >> Please let me know.
> >>
> >> John
> >>
> >> On Sun, Apr 29, 2018 at 6:27 AM SHUANG SU <sushuang0...@gmail.com>
> wrote:
> >>
> >> > Thanks John ~
> >> >
> >> > I've updated the LICENSE file and added a DISCAIMER and updated the
> >> license
> >> > statements in the files that using 3rd party code,
> >> > and then packed
> >> > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc2/.
> >> >
> >> > Would you please check that is there any other defeat in rc2?
> >> >
> >> > Thanks :)
> >> >
> >> >
> >> >
> >> >
> >> > 
> >> > Su Shuang (100pah)
> >> > 
> >> >
> >> >
> >> >
> >> > 2018-04-29 1:56 GMT+08:00 John D. Ament <john.d.am...@gmail.com>:
> >> >
> >> > > On Sat, Apr 28, 2018 at 10:31 AM SHUANG SU <sushuang0...@gmail.com>
> >> > wrote:
> >> > >
> >> > > > > Our definition of import is
> >> > > > > that you have copied the source code from the project (zrender)
> >> into
> >> > > > > echarts.
> >> > > >
> >> > > > Oh, I get it~
> >> > > > echarts does not copy zrender code to its source code file (that
> is,
> >> > all
> >> > > of
> >> > > > the file under the directory "echarts/src/").
> >> > > > But the zrender code is actually included in the "echarts dist
> file"
> >> > > (that
> >> > > > is, all of the file under the directory "echarts/dist"),
> >> > > > which are auto generated by the build tool
> (echarts/build/build.js)
> >> > when
> >> > > > echarts is about to be released.
> >> > > > The dist files can be used in the production environment.
> >> > > >
> >> > > > So if the "dist file" is not considered as "source code", do we
> >> still
> >> > > need
> >> > > > to add zrender license to echarts LICENSE file?
> >> > > > Or we might list all of the "dist files" in echarts LICENSE file
> >> that
> >> > is
> >> > > > using zrender?
> >> > > >
&g

Re: [VOTE] Release Apache ECharts 4.1.0

2018-04-26 Thread Kevin A. McGrail
The RC just means release candidate so the real release is 4.1.0

You might get RC1, rc2, rc3  if you find issues that make the build a
problem and have to propose another release candidate.

--
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 Thu, Apr 26, 2018 at 6:15 AM, SHUANG SU <sushuang0...@gmail.com> wrote:

> Kevin,
>
> If the release "apache-echarts-4.1.0.rc0-incubating" approved via voting
> in
> both dev@echarts.apache.org and gene...@incubator.apache.org,
> which is the final release version, "4.1.0.rc0" or "4.1.0"?
> (Actually "4.1.0" is expected, but I am not sure whether I am using "RC" in
> right way.)
>
>
>
> ----
> Su Shuang (100pah)
> 
>
>
>
> 2018-04-26 7:45 GMT+08:00 Kevin A. McGrail <kmcgr...@apache.org>:
>
> > I'll defer to John and others but it's definitely moving closer to being
> a
> > good release in the spirit of moving towards the right processes IMO.
> >
> > --
> > 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 Wed, Apr 25, 2018 at 4:02 PM, SHUANG SU <sushuang0...@gmail.com>
> wrote:
> >
> > > Hi, John and Kevin,
> > >
> > > After adding the licenses in details and including the "RC" and
> > > "incubeting" in the release name,
> > > I have prepared the artifacts in
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc0/.
> > >
> > > Would you please check is there anything else I am missing yet before a
> > > vote can be initialized?
> > >
> > > Thanks very much :)
> > >
> > >
> > >
> > >
> > > 
> > > Su Shuang (100pah)
> > > 
> > >
> > >
> > >
> > > 2018-04-25 19:46 GMT+08:00 John D. Ament <johndam...@apache.org>:
> > >
> > > > You also need to name the artifacts as "apache-echarts-4.1.0-
> > incubating"
> > > >
> > > > On Wed, Apr 25, 2018, 7:34 AM Kevin A. McGrail <kmcgr...@apache.org>
> > > > wrote:
> > > >
> > > > > No worries!  Live and learn.  Depending on how you handle it, the
> RC
> > > > might
> > > > > be "used" and you need to increment the release number.
> > > > >
> > > > > --
> > > > > 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 Wed, Apr 25, 2018 at 1:20 AM, SHUANG SU <sushuang0...@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Sorry it's my fault. I am fixing it and to restart the vote.
> > > > > >
> > > > > > 2018-04-25 2:31 GMT+08:00 Kevin A. McGrail <kmcgr...@apache.org
> >:
> > > > > >
> > > > > > > When I try and download the RC, I get a file that says:
> > > > You
> > > > > > are
> > > > > > > being https://codeload.github.com/apache/incubator-echarts/tar.
> > gz/4.1.0
> > > > > > > ">redirected.
> > > > > > >
> > > > > > > --
> > > > > > > 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 Tue, Apr 24, 2018 at 2:13 PM, SHUANG SU <
> > sushuang0...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > I am pleased to be calling this vote for the release of
> Apache
> > > > > ECharts
> > > > > > > > 4.1.0.
> > > > > > > >
> > > > > > > > The release candidate to be voted over is available at:
> > > > > > &

Re: [VOTE] Release Apache ECharts 4.1.0

2018-04-24 Thread Kevin A. McGrail
When I try and download the RC, I get a file that says: You are
being https://codeload.github.com/apache/incubator-echarts/tar.gz/4.1.0
">redirected.

--
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 Tue, Apr 24, 2018 at 2:13 PM, SHUANG SU <sushuang0...@gmail.com> wrote:

> I am pleased to be calling this vote for the release of Apache ECharts
> 4.1.0.
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0/
>
> SHA512 checksums:
> echarts.tar.gz: 94A91D03 51127573 BF3E7F46 FB436E00 C7F1A92D ECE59942
> E4C481D1 B86E77DD 94EDD599 5C757748 84EC011E F087FB52 2A1988D9 E32CCF7E
> A397882C 12239568
>
> MD5 checksums:
> echarts.tar.gz: eac47ab092a3a30bea98378e5172ec19
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> A tagged git repository is available for review at:
> https://github.com/apache/incubator-echarts/releases/tag/4.1.0
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=
> 097e093a2e488adb0feb286283cf8e6e3ee31847
>
>
>
> [Release note]
>
> + [Feature] Enable candlestick and bar chart chart rendering and zooming in
> large amount of data (200K). Add option `series.progressiveChunkMode` to
> enhance the effect when progressively rendering.
> + [Feature] Add zoom and drag interactions for tree diagram.
> + [Feature] Support keeping-aspect for legend path. #7831
> + [Feature] Support node dragging for sankey chart.
>
> + [Enhance] Category axis enhancement:
> + Optimize the performance in large amount of data (> 100K ~ 1M)
> + Enhance the auto interval strategy.
> + Enhance the animation when zooming and moving the data window of
> cartesian.
> + [Enhance] In line chart, enhance symbol display strategy when using
> category axis (see `showAllSymbol:'auto'`).
> + [Enhance] Support that lift the brushed elements to the top (add option
> `visualMap.inRange.liftZ`).
> + [Enhance] Enhance the category axis ticks and labels when there was no
> enough space to display all labels.
> + [Enhance] Enhance the order of nodes for sankey diagram. #3390 #3543
> #6365 #4880 #4986
> + [Enhance] Enhance sampling performance in progressive mode.
> + [Enhance] Enhance parallel performance in progressive mode.
> + [Enhance] Currently do not filter empty data item in data zoom, which
> makes line chart keeping broken. #7955
> + [Enhance] Support toolbox.feature merge.
> + [Enhance] Add tree directions from right to left, from bottom to top for
> tree series. #7351 #7154
>
> + [Fix] Resolve browser become unresponsive when the data of sankey series
> has cycle. #7495 #8117 #7583 #7325 #6555
> + [Fix] `yAxis` extent did not update when some of the stacked bar series
> hide. #8003
> + [Fix] Currently we fetch name from `dateItem.name` firstly in list. #7966
> + [Fix] Typed array incorrect usage in WeChat app.
> + [Fix] `option` in axis data item did not work. #7954
> + [Fix] `markArea` only displayed the last one. #7902
> + [Fix] Fixed the WeChat environment imprecise detection.
> + [Fix] Rounding error in clip symbol for line chart. #7913
> + [Fix] The default tooltip in candlestick only showed one item. #8149
> + [Fix] Bar chart start point was incorrect when multiple axes exist. #7412
> + [Fix] `markArea` did not display when using ordinal string. #7849
> + [Fix] `dataZoom` threw error when series was empty. #7666
> + [Fix] Add compatibility of data exceptions for sankey series. #2867
> + [Fix] Fix error when removing node or rendering again for the tree
> series. #8038 #8040 #7720 #7363 #7315
> + [Fix] `sunburst` chart roll-up element was not removed when
> chart.setOption called. #8132
> + [Fix] SVG axisPointer text position bug. #7947
> + [Fix] Large lines chart render bug in large mode.
> + [Fix] The last day of a month was not displayed in calendar. #8045
> + [Fix] Data sampling of line chart caused incorrect extent when data had
> NaN.
> + [Fix] Data sampling of line chart worked abnormally when using
> `series.encode`. #8017
> + [Fix] `legendHoverLink: false` did not work appropriately when multiple
> series had the same name. #8010
> + [Fix] Some of the graph hover style did not work.
>
>
>
> Please vote on releasing this package as:
> Apache ECharts 4.1.0
>
> This vote will be open until "Sat Apr 28 2018 03:07:46 GMT+0800 (CST)" 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.
>


Re: ECharts Website

2018-04-15 Thread Kevin A. McGrail
John, do they use echarts.incubator.apache.org to start?

On Sun, Apr 15, 2018, 09:24 John D. Ament  wrote:

> All,
>
> We've received a media request about our website.  Currently there is no
> website for ECharts.  What are the plans for building a website?
>
> John
>


Re: ECharts todo list of next release

2018-04-13 Thread Kevin A. McGrail
FYI, Wenli, please try and login to
https://issues.apache.org/jira/projects/ECHARTS/ and see if you can.  It
might have worked, not sure as you saw from my selfserve ticket.

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Fri, Apr 13, 2018 at 10:50 AM, Kevin A. McGrail <kmcgr...@apache.org>
wrote:

> Thanks Wenli, I'll try to remember which is correct.  I don't really think
> there is a "correct" order but for me, the most common order I see is
> firstname, lastname.  In fact, it's really something with the reverse order
> I've noticed with people from China.  Also, sometimes it's very confusing
> for me because they'll have 3 names, someimes only use two and sometimes
> concatenate them.  My only goal is not to offend and to call people by
> their prefence.  Otherwise I'll just call you Ovilia :-)
>
> So I tried to submit the request for a Jira for echarts with
> kmcgrail,johndament,wave,ovilia as admins to start the ball rolling.  But
> the selfserve system is timing out.  I opened a ticket for that at
> https://issues.apache.org/jira/browse/INFRA-16353
>
> Do you also want to get a website for echarts.apache.org going as well?
> John, do they use echarts.incubator.apache.org to start?
>
> 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 Fri, Apr 13, 2018 at 9:56 AM, Wenli Zhang <oviliazh...@gmail.com>
> wrote:
>
>> Hi Kevin,
>>
>> Please help create a project for echarts since I don't have the right to
>> do
>> so.
>>
>> As about my name, sorry for the confusion.
>> My lastname is Zhang and firstname is Wenli.
>> Yes, we Chinese sometimes do switch the order since we are confused which
>> one is the correct order. I've heard of two versions of ordering for
>> foreign names to be translated into English. One says that firstname goes
>> first in English name (and I guess that's why it's called firstname haha)
>> so it should be Wenli Zhang. Another saying is that, foreign names should
>> follow the custom order of foreign languages, which makes it Zhang Wenli.
>> Anyway, I would prefer to be called Wenli. And do please tell me if there
>> is a correct order. :)
>>
>>
>> Zhang Wenli
>> http://zhangwenli.com
>>
>> On Fri, Apr 13, 2018 at 9:42 PM, Kevin A. McGrail <kmcgr...@apache.org>
>> wrote:
>>
>> >  Great point.  I didn't know the self serve had gone live.  I thought it
>> > was still in testing.  Wenli, you'll see the ability to create a Jira
>> > project there.  John, not sure what you meant about git repo.  Was that
>> a
>> > different issue or a Fruedian slip?
>> >
>> > --
>> > Kevin A. McGrail
>> > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> > Chair Emeritus Apache SpamAssassin Project
>> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> >
>> > On Fri, Apr 13, 2018 at 8:31 AM, John D. Ament <johndam...@apache.org>
>> > wrote:
>> >
>> > > On Fri, Apr 13, 2018 at 7:51 AM Kevin A. McGrail <kmcgr...@apache.org
>> >
>> > > wrote:
>> > >
>> > > > Zhang,
>> > > >
>> > > > First, I have a dumb question.  Your email address is Wenli Zhang
>> and
>> > > your
>> > > > signature is Zhang Wenli.  I see this often with names in China.
>> Can
>> > you
>> > > > tell me more about this?  Is Zhang your given name and Wenli your
>> > > surname?
>> > > > Why do you switch them?  In English, I would expect a command like
>> > > McGrail,
>> > > > Kevin if it was my lastname/firstname.
>> > > >
>> > > > Second, to add a project for echarts to Jira, what I would do is
>> open a
>> > > > Jira ticket with infrastructure.  Then you can search echarts
>> issues in
>> > > > jira and retag them.  They might also use different jira instances
>> for
>> > > > projects, I don't know but I'll leave that to infrastructure.  The
>> key
>> > > > point is ask them for what you need.
>> > > >
>> > > >
>> > > If you're not aware, Infra now supports a large number of features as
>> > self
>> > > serve options.  Last I checked, they're open for A

Re: ECharts todo list of next release

2018-04-13 Thread Kevin A. McGrail
 Great point.  I didn't know the self serve had gone live.  I thought it
was still in testing.  Wenli, you'll see the ability to create a Jira
project there.  John, not sure what you meant about git repo.  Was that a
different issue or a Fruedian slip?

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Fri, Apr 13, 2018 at 8:31 AM, John D. Ament <johndam...@apache.org>
wrote:

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


Re: ECharts todo list of next release

2018-04-13 Thread Kevin A. McGrail
Zhang,

First, I have a dumb question.  Your email address is Wenli Zhang and your
signature is Zhang Wenli.  I see this often with names in China.  Can you
tell me more about this?  Is Zhang your given name and Wenli your surname?
Why do you switch them?  In English, I would expect a command like McGrail,
Kevin if it was my lastname/firstname.

Second, to add a project for echarts to Jira, what I would do is open a
Jira ticket with infrastructure.  Then you can search echarts issues in
jira and retag them.  They might also use different jira instances for
projects, I don't know but I'll leave that to infrastructure.  The key
point is ask them for what you need.

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 Fri, Apr 13, 2018 at 3:07 AM, Wenli Zhang <oviliazh...@gmail.com> wrote:

> Hi all,
>
> I've created a todo list of our next release, ECharts 4.1.0 at
> https://issues.apache.org/jira/browse/INCUBATOR-211 .
> I'm not quite sure if I did it right?
>
> I wonder if we could have a project called echarts on JIRA so that we can
> better filter this kind of issues later? I didn't find the way/access to do
> so, could anyone give a hand?
>
> Thanks!
>
> Zhang Wenli
> http://zhangwenli.com
>


Re: About how to track features of next release

2018-04-09 Thread Kevin A. McGrail
I recommend Jira tickets STRONGLY because that way the ideas can be done
any time by anyone.

With a volunteer community, you might have someone new from the internet be
interested and jump on one of the ideas.

Regards,
KAM

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Sun, Apr 8, 2018 at 11:04 PM, Wenli Zhang <oviliazh...@gmail.com> wrote:

> Hi mentors,
>
> I was informed that we should discuss what features to include in next
> release. And I would like to ask how this should be done.
>
> Should we send an email for each feature for others to discuss and vote, or
> open a JIRA ticket for each feature?
>
> Thanks!
>
> Zhang Wenli
> http://zhangwenli.com
>


Re: Could your add us as committer in incubator-echarts

2018-04-04 Thread Kevin A. McGrail
I think Daniel has been working on this.   https://issues.apache.
org/jira/browse/INFRA-16224 can be closed, yes?

--
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 Wed, Apr 4, 2018 at 7:09 AM, John D. Ament <johndam...@apache.org> wrote:

> BTW it looks like Daniel did the original committer setup.  Thanks Daniel!
>
> On Wed, Apr 4, 2018 at 7:00 AM SHUANG SU <sushuang0...@gmail.com> wrote:
>
> > Thanks John ~ I will find the accounts of Lin Zhifeng and Dong Rui.
> >
> >
> > 2018-04-04 18:43 GMT+08:00 John D. Ament <johndam...@apache.org>:
> >
> >> Hi,
> >>
> >> I went into the roster, and i believe all were already listed.  I did
> >> move all into the PPMC.
> >>
> >> I don't see accounts yet for Lin Zhifeng and Dong Rui
> >>
> >> John
> >>
> >> On Wed, Apr 4, 2018 at 2:47 AM SHUANG SU <sushuang0...@gmail.com>
> wrote:
> >>
> >>>
> >>> Hi, Daniel Gruno, David Fisher, John D. Ament, Kevin A. McGrail
> >>>
> >>> The Github repo of echarts has been migrated to
> >>> https://github.com/apache/incubator-echarts the day before yesterday.
> >>>
> >>> But we lost the authorities to commit code, close issue and manage
> >>> collaborators in this repo.
> >>>
> >>> Could you add
> >>>   sushu...@apache.org
> >>>   ovi...@apache.org
> >>>   she...@apache.org
> >>>   deqin...@apache.org
> >>> as committers via the Whimsy Roster:
> >>> https://whimsy.apache.org/roster/ppmc/echarts ?
> >>>
> >>> See details in the thread:
> >>> https://issues.apache.org/jira/browse/INFRA-16224
> >>>
> >>> (All of the four guys have already 2FA enabled and linked Github ID and
> >>> ASF ID and joined in https://github.com/apache/ )
> >>>
> >>> Thanks very much :)
> >>>
> >>> sushuang
> >>>
> >>
> >
>


Re: ECharts @ The ASF - Next Steps

2018-03-24 Thread Kevin A. McGrail
Thanks Zhang. I am happy to be helpful.

To be clear I meant ask infra for their if so pissang can add then with
full rights to make the transfer.

On Sat, Mar 24, 2018, 09:35 Wenli Zhang <oviliazh...@gmail.com> wrote:

> Hi Kevin,
>
> Thank you for the guide!
>
> Shen Yi's GitHub id is pissang and we are ready to transfer it to ASF.
>
> I'll open more tickets later.
> Thanks!
>
> Zhang Wenli
> http://zhangwenli.com
>
> On Fri, Mar 23, 2018 at 7:59 PM, Kevin A. McGrail <kmcgr...@apache.org>
> wrote:
>
> > It's a little vague perhaps but a good start. Congrats on your first jira
> > ticket!  It is a milestone as minor as it seems and you can open more for
> > things your project needs.
> >
> > To nitpick, I would have titled it something like move repositories for
> > echarts from XYZ to ASF.  I am sure they will ask questions and guide you
> > along.  It also never hurts to say please and say good things to appease
> > the computer gods lest they become angry and smite us with their wrath.
> :-)
> >
> > Is Shen Yi ready to give admin rights to Infra when they ask for that?
> You
> > might want to ask for their ID so that can be done with as little time
> > wasted as possible!
> >
> > 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 Fri, Mar 23, 2018 at 5:28 AM, Wenli Zhang <oviliazh...@gmail.com>
> > wrote:
> >
> > > Hi John,
> > >
> > > I created this ticket and I'm not sure if I did it right.
> > > https://issues.apache.org/jira/browse/INFRA-16224
> > >
> > > Please have a look?
> > > Thanks!
> > >
> > > Zhang Wenli
> > > http://zhangwenli.com
> > >
> > > On Thu, Mar 22, 2018 at 9:26 PM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > >> Your project is under "Incubator" so just choose Incubator in the
> > project
> > >> list.
> > >>
> > >> https://issues.apache.org/jira/browse/INFRA to file a JIRA ticket
> with
> > >> Infra.  Request to migrate the git repos over.
> > >>
> > >> John
> > >>
> > >> On Thu, Mar 22, 2018 at 2:49 AM Wenli Zhang <oviliazh...@gmail.com>
> > >> wrote:
> > >>
> > >> > Thanks Dave,
> > >> >
> > >> > It seems that ECharts is not in JIRA projects. Is this what you mean
> > by
> > >> > *JIRA ticket*?
> > >> >
> > >> > Shen Yi has the admin rights of ecomfe/echarts project on GitHub.
> His
> > >> JIRA
> > >> > id is shenyi.
> > >> >
> > >> > Thanks!
> > >> >
> > >> > Zhang Wenli
> > >> > http://zhangwenli.com
> > >> >
> > >> > On Thu, Mar 22, 2018 at 2:34 PM, Dave Fisher <dave2w...@comcast.net
> >
> > >> > wrote:
> > >> >
> > >> > > Hi -
> > >> > >
> > >> > > Welcome to the ASF.
> > >> > >
> > >> > > To move the github repository a member of the Apache Infra team
> > needs
> > >> > > temporary admin rights in the original, contributing github
> > >> repository in
> > >> > > order to move it to the Apache Incubator. If you know the Admin
> > please
> > >> > > provide in the Infra JIRA ticket.
> > >> > >
> > >> > > If you need help then one of your mentors can create the ticket
> for
> > >> you
> > >> > > tomorrow.
> > >> > >
> > >> > > Regards,
> > >> > > Dave
> > >> > >
> > >> > > Sent from my iPhone
> > >> > >
> > >> > > On Mar 21, 2018, at 11:03 PM, Wenli Zhang <oviliazh...@gmail.com>
> > >> wrote:
> > >> > >
> > >> > > Thanks John and Kevin for your reply.
> > >> > >
> > >> > > So right now I shall just wait for Kevin to contact Infra. Right?
> > >> > >
> > >> > > Zhang Wenli
> > >> > > http://zhangwenli.com
> > >> > >
> > >> > > On Wed, Mar 21, 2018 at 10:04 PM, John D. A