incubator-echarts-examples and incubator-echarts-www have been moved to Apache org on GitHub: https://github.com/apache/incubator-echarts-examples https://github.com/apache/incubator-echarts-www
Thanks *Ovilia* On Thu, Aug 27, 2020 at 5:07 PM Ville Brofeldt <ville.v.brofe...@gmail.com> wrote: > Hi, > > the releases are triggered by running `yarn ci:create-minor-version` and > `yarn ci:create-patch-version` for minor and patch releases respectively. > After pushing to upstream master, deployment to npm happens automatically. > I’m not familiar with the details on how this post push automation has been > done in practice, but I can put you in touch with the person who has if > needed. My main point being that this makes it possible to decouple > triggering of deployment from the credentials used for deployment, as > anyone with the necessary rights to the repo can initiate the deployment. > > Ville > > > On 26. Aug 2020, at 14.23, SHUANG SU <sushuang0...@gmail.com> wrote: > > > > Thanks for your review and suggestion Ville ~ > > > > I've tried to learn the publish script of > > https://github.com/apache-superset/superset-ui . But still not think of > > some ideas from it. It seems to publish to some free CDN? > > At present we are using a third-party CDN with certain credentials > needed, > > and needs to make only PPMC know the pwd. > > > >> We have updated the Website with a sponsored CDN to improve speed in > China > > and created an account for all PPMCs. But we are not sure how we > > should distribute the password of that account? Should we send the > password > > on the private > > mailing list? Is that safe enough? > > > > For this original issue, I think another possible solution might be: > > Add the accounts of PPMCs as the admin of the third-party CDN. Then PPMCs > > are able to get the pwd from the admin console website of the third-party > > CDN. > > > > > > Thanks, > > ------------------------------ > > Su Shuang (100pah) > > ------------------------------ > > > > > > > > On Tue, 25 Aug 2020 at 15:07, Ville Brofeldt <ville...@apache.org> > wrote: > > > >> Hi ECharts community, > >> > >> I reviewed the graduation documents, and everything looks good at quick > >> glance. > >> > >> With regards to CDN usernames/passwords, would it be possible to > automate > >> the CDN deployment to avoid having to pass around credentials? On > >> https://github.com/apache-superset/superset-ui there is a flow where > any > >> admin is able to initiate deployment by issuing a single command and > >> pushing to the main upstream repo, after which deployment to npm is > >> performed automatically. Using this type of flow there wouldn't be a > need > >> to manage separate user credentials to the CDN, and it would also make > the > >> deployment process less error prone. > >> > >> Ville > >> > >> On 2020/07/27 05:07:23, Ovilia <oviliazh...@gmail.com> 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* > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > >> For additional commands, e-mail: dev-h...@echarts.apache.org > >> > >> > >
