Re: ECharts Website Update Progress

[Ovilia]

The INFRA has not replied on the JIRA yet. It has been 16 hours.

And this may cause big concerns in the future. If we redirect
echarts.baidu.com to apache domain, there would be more than 35k UV every
day.
If we have some problems when releasing the website, and the JIRA response
time is about 16 hours, that may seem quite unacceptable.

Is that anything we can do to deal with things like this, besides waiting
for JIRA to respond?

[1] https://issues.apache.org/jira/browse/INFRA-18519

Wenli


Ovilia  于2019年5月29日周三 下午11:48写道：

> Hi, everyone. It has been some while since we last discussed our Website
> transferring topic.
>
> I've updated a version today to https://echarts.apache.org .
> Chinese version is under /zh/ and English version is under /en/.
> https://echarts.apache.org/index.html shall redirect to /zh/ or /en/
> depending on Web browser's language. But I don't know why, but the
> index.html is not yet updated. I've created a JIRA ticket to ask the infra
> [1].
> *So please visit https://echarts.apache.org/en/index.html
>  instead
> of https://echarts.apache.org  to check for
> now.*
>
> I'm sending this email to you so that you can check if the contents are
> all correct. If there's anything worth discussing, please let me know.
>
> I haven't change the analytics yet, which I will do in the following days.
> All other things should be expected to be correct.
> If we agree on the content, then we will make other domains like
> echarts.baidu.com redirect to this one.
>
> Anyway, feel free to let me know if you have any questions.
>
> [1] https://issues.apache.org/jira/browse/INFRA-18519
>
> Wenli
>

ECharts Website Update Progress

[Ovilia]

Hi, everyone. It has been some while since we last discussed our Website
transferring topic.

I've updated a version today to https://echarts.apache.org .
Chinese version is under /zh/ and English version is under /en/.
https://echarts.apache.org/index.html shall redirect to /zh/ or /en/
depending on Web browser's language. But I don't know why, but the
index.html is not yet updated. I've created a JIRA ticket to ask the infra
[1].
*So please visit https://echarts.apache.org/en/index.html
 instead
of https://echarts.apache.org  to check for
now.*

I'm sending this email to you so that you can check if the contents are all
correct. If there's anything worth discussing, please let me know.

I haven't change the analytics yet, which I will do in the following days.
All other things should be expected to be correct.
If we agree on the content, then we will make other domains like
echarts.baidu.com redirect to this one.

Anyway, feel free to let me know if you have any questions.

[1] https://issues.apache.org/jira/browse/INFRA-18519

Wenli

Re: [VOTE] ECharts Website Analytics policy

[Ovilia]

Kevin's right. We are mainly considering the accessing speed when moving
the Chinese version to Apache server. Otherwise, we would be more than
willing to do the job.
So could we do the redirecting thing after we have solved the server
problem?

BTW, I'm going on a vacation from 21st to 29th April. Slow email response
is expected.

Zhang Wenli
http://zhangwenli.com


Kevin A. McGrail  于2019年4月19日周五 上午7:56写道：

> 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

Re: [VOTE] ECharts Website Analytics policy

[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
&g

Re: [VOTE] ECharts Website Analytics policy

[Dave Fisher]

Hi -

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

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

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

Regards,
Dave


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


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

Re: [VOTE] ECharts Website Analytics policy

[Clement Ho]

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

Re: [VOTE] ECharts Website Analytics policy

[SHUANG SU]

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
>

[VOTE] ECharts Website Analytics policy

[Ovilia]

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

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

[Justin Mclean]

Hi,

> I just removed the rc release from https://echarts.apache.org/download.html 
>  , alongside Chinese website link 
> to www.echartsjs.com  .

Thanks for doing that.

Justin

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

[Ovilia]

Hi Justin,

I just removed the rc release from https://echarts.apache.org/download.html
, alongside Chinese website link to www.echartsjs.com .

We'll have a further discussion after the holidays.
Hope you a nice day!

Zhang Wenli
http://zhangwenli.com


On Sat, Feb 9, 2019 at 2:10 PM Ovilia  wrote:

> Hi Justin,
>
> We will remove the rc release from
> https://echarts.apache.org/download.html ASAP, and have a discussion
> after that. But we are having the Chinese Spring Festival right now, and
> many of us may not take a laptop with us. I will find someone to do this
> job ASAP.
>
> Zhang Wenli
> http://zhangwenli.com
>
>
> On Fri, Feb 8, 2019 at 7:31 AM Justin Mclean  wrote:
>
>> HI Dave,
>>
>> Thanks for exam-lin that in detail.
>>
>> > Let’s discuss the current state on Github Releases tab -
>> https://github.com/apache/incubator-echarts/releases
>> >
>> > The only release listed is still an RC which has yet to pass.
>>
>> It looks like there is at least 7 RC's listed on that page and one
>> approved release 4.1.0 that was made after they entered incubation.
>> Versions 4.0.4 and 4.03 and 4.0.2  and 4.0.0 are also listed, that's after
>> incubation (on 2018-01-16) but I can not find any vote threads for them.
>> 3.8.5 and below would be pre Apache releases AFAICS.
>>
>> Thanks,
>> Justin
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>>
>>

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

[Ovilia]

Hi Justin,

We will remove the rc release from
https://echarts.apache.org/download.html ASAP,
and have a discussion after that. But we are having the Chinese Spring
Festival right now, and many of us may not take a laptop with us. I will
find someone to do this job ASAP.

Zhang Wenli
http://zhangwenli.com


On Fri, Feb 8, 2019 at 7:31 AM Justin Mclean  wrote:

> HI Dave,
>
> Thanks for exam-lin that in detail.
>
> > Let’s discuss the current state on Github Releases tab -
> https://github.com/apache/incubator-echarts/releases
> >
> > The only release listed is still an RC which has yet to pass.
>
> It looks like there is at least 7 RC's listed on that page and one
> approved release 4.1.0 that was made after they entered incubation.
> Versions 4.0.4 and 4.03 and 4.0.2  and 4.0.0 are also listed, that's after
> incubation (on 2018-01-16) but I can not find any vote threads for them.
> 3.8.5 and below would be pre Apache releases AFAICS.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
> For additional commands, e-mail: dev-h...@echarts.apache.org
>
>

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

[Dave Fisher]

Hi -

Additional information.

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

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

ALSO - NPM.

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

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

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

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


Mentors are here to answer questions.

Regards,
Dave

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

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

[Justin Mclean]

HI Dave,

Thanks for exam-lin that in detail.

> Let’s discuss the current state on Github Releases tab - 
> https://github.com/apache/incubator-echarts/releases
> 
> The only release listed is still an RC which has yet to pass. 

It looks like there is at least 7 RC's listed on that page and one approved 
release 4.1.0 that was made after they entered incubation. Versions 4.0.4 and 
4.03 and 4.0.2  and 4.0.0 are also listed, that's after incubation (on 
2018-01-16) but I can not find any vote threads for them. 3.8.5 and below would 
be pre Apache releases AFAICS.

Thanks,
Justin

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

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

[Dave Fisher]

Hi Devs -

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

Let’s discuss from lifecycle.

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

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

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

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

Please update and ask your Mentors to review.

Regards,
Dave

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

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

[Justin Mclean]

Hi,

I just saw that this commit added a link to the download page for a release 
candidate. [1] Why was this done?

We've just had a long discussion that the PPMC cannot advertise or link to 
unreleased material. [2] Again "Do not include any links on the project website 
that might encourage non-developers to download and use nightly builds, 
snapshots, release candidates, or any other similar package"

Thanks,
Justin

1. https://echarts.apache.org/download.html
2. http://www.apache.org/legal/release-policy.html#what


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

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

[Justin Mclean]

Hi,

And I’m still seeing release candidates marked as released here [1]. Please 
remove them.

Thanks,
Justin

1. https://github.com/apache/incubator-echarts/releases
-
To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
For additional commands, e-mail: dev-h...@echarts.apache.org

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

[Dave Fisher]

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

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

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

Regards,
Dave

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


signature.asc
Description: Message signed with OpenPGP

Re: ECharts Website

[John D. Ament]

On Mon, Apr 16, 2018 at 10:46 PM Wenli Zhang  wrote:

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

I'm not sure what you mean by this.  Our websites are built in jenkins, and
typically send emails to the dev list when they fail.  Why do you need to
contact admin?


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

Jenkins.


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


I would recommend having the website moved over before a release occurs.
But its only a recommendation.  You would then have an apache hosted
downloads page that is valid.


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

Re: ECharts Website

[Wenli Zhang]

Hi John,

Thanks for the detailed explanation.

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

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

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

Thanks!

Zhang Wenli
http://zhangwenli.com

On Mon, Apr 16, 2018 at 6:01 PM, John D. Ament 
wrote:

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

[John D. Ament]

Hi Wenli,

We can host that at Apache.  We do need to make a few changes to work
within the branding policies.  Please review
https://incubator.apache.org/guides/branding.html and
https://incubator.apache.org/guides/sites.html

Was the website included in the SGA?  If not, would you be able to get
another SGA put together that includes the website?  If it was included,
please just file another infra request to move the git repo over.

It looks like you're using jade to build the website.  I think that's
already a supported tool, if not I'm sure we can install it.

Typically we maintain two branches, but jade may work differently.  On the
"master" or "develop" branch is where the source code for the website
lives.  Typically there is a build script that would be created that wraps
the actual build from master into a "asf-site" branch.  That branch
contains the final build output for the website.  If everything is on a
single branch, that should still work, just gets a little confusing since
somehow it needs to be built.  Do you build it manually?  We can do Jenkins
jobs or Buildbot jobs to do it (I personally prefer Jenkins, much more self
serve).

You can take a look at what I put together for the incubator website, which
uses jbake and velocity to run:
https://github.com/apache/incubator/blob/master/build_site.sh

John

On Sun, Apr 15, 2018 at 11:16 PM Wenli Zhang  wrote:

> We are currently using https://github.com/ecomfe/echarts-www to generate
> website https://ecomfe.github.io/echarts-doc/public/en/index.html . Could
> we have another project like
> https://github.com/apache/incubator-echarts-www
> for the podling website?
>
> Where is the server then, and how should we build and release the website?
>
>
> Zhang Wenli
> http://zhangwenli.com
>
> On Mon, Apr 16, 2018 at 10:39 AM, Wenli Zhang 
> wrote:
>
> > Hi John,
> >
> > We are currently using https://ecomfe.github.io/echarts-doc/public/en/
> > index.html for website.
> > Is this podling website required before we release a new version?
> >
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
> > On Mon, Apr 16, 2018 at 12:31 AM, John D. Ament 
> > wrote:
> >
> >> Both URLs will end up working for them (echarts.apache.org and
> >> echarts.incubator.apache.org).  I personally don't care which is used
> >> regularly, and it helps projects to not use the incubator suffixed one
> >> when
> >> graduating.  As long as the website complies with branding policies and
> >> release download policies.
> >>
> >> John
> >>
> >> On Sun, Apr 15, 2018 at 9:53 AM Kevin A. McGrail 
> >> wrote:
> >>
> >> > 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 Website

[Wenli Zhang]

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

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


Zhang Wenli
http://zhangwenli.com

On Mon, Apr 16, 2018 at 10:39 AM, Wenli Zhang  wrote:

> Hi John,
>
> We are currently using https://ecomfe.github.io/echarts-doc/public/en/
> index.html for website.
> Is this podling website required before we release a new version?
>
>
> Zhang Wenli
> http://zhangwenli.com
>
> On Mon, Apr 16, 2018 at 12:31 AM, John D. Ament 
> wrote:
>
>> Both URLs will end up working for them (echarts.apache.org and
>> echarts.incubator.apache.org).  I personally don't care which is used
>> regularly, and it helps projects to not use the incubator suffixed one
>> when
>> graduating.  As long as the website complies with branding policies and
>> release download policies.
>>
>> John
>>
>> On Sun, Apr 15, 2018 at 9:53 AM Kevin A. McGrail 
>> wrote:
>>
>> > 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 Website

[John D. Ament]

Both URLs will end up working for them (echarts.apache.org and
echarts.incubator.apache.org).  I personally don't care which is used
regularly, and it helps projects to not use the incubator suffixed one when
graduating.  As long as the website complies with branding policies and
release download policies.

John

On Sun, Apr 15, 2018 at 9:53 AM Kevin A. McGrail 
wrote:

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

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

ECharts Website

[John D. Ament]

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