On Mon, Apr 16, 2018 at 10:46 PM Wenli Zhang <[email protected]> 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 <[email protected]> > 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 <[email protected]> > > 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 <[email protected]> > > > 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 < > [email protected] > > > > > > > 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 < > [email protected] > > > > > > >> wrote: > > > >> > > > >> > John, do they use echarts.incubator.apache.org to start? > > > >> > > > > >> > On Sun, Apr 15, 2018, 09:24 John D. Ament <[email protected]> > > > >> 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 > > > >> > > > > > >> > > > > >> > > > > > > > > > > > > > >
