Hi all, We have solved the branding issue of the "gallery", using a new domain name makeapie.com for this third-party product and redirecting the old domain https://gallery.echartsjs.com/ to it.
We are going to start a new graduation vote in this mailing list soon if no more discussion is found necessary. Thanks *Ovilia* On Tue, Oct 27, 2020 at 11:45 AM Ovilia <oviliazh...@gmail.com> wrote: > Hi Dave, > > I have corrected the README files and added LICENSE files. > Please let me know if you have any questions. > > Thanks > > *Ovilia* > > > On Sat, Oct 24, 2020 at 12:42 AM Ovilia <oviliazh...@gmail.com> wrote: > >> Hi Dave, >> >> Yes, sure. I will take care of that. >> Thanks! >> >> Dave Fisher <w...@apache.org>于2020年10月24日 周六上午12:34写道: >> >>> Hi Ovilla, >>> >>> This makes sense. >>> >>> I would add a LICENSE.md file at the top level of the four website >>> generating repositories. >>> >>> Also, make sure the README.md file explains the workflow of those >>> repositories into the website repository. >>> >>> These readme files are counting on redirection from ecomfe GitHub space >>> to apache. Please correct them to be direct links. >>> >>> Regards, >>> Dave >>> >>> > On Oct 23, 2020, at 7:15 AM, Ovilia <oviliazh...@gmail.com> wrote: >>> > >>> > Hi Dave, >>> > >>> > Thanks for the check. >>> > >>> > These two projects are used to build ECharts's >>> > official Website, so they may be similar to >>> > https://github.com/apache/incubator-echarts-website >>> > in that: >>> > a) They don't have "releases" [1] by themselves >>> > b) They are not included in Apache ECharts's release distribution >>> > c) They are used only to generate the Website >>> > >>> > The difference between them is that incubator-echarts-www >>> > and incubator-echarts-examples >>> > are used to generate the files in incubator-echarts-website. >>> > >>> > According to [2], >>> >> With few exceptions >>> > <https://www.apache.org/legal/src-headers.html#faq-exceptions>, all >>> > human-readable Apache-developed files that are included within a >>> > distribution must include the header text >>> > <https://www.apache.org/legal/src-headers.html#header-text>. >>> Documentation, >>> > including web site documentation distributed with the release, may >>> include >>> > the header text within some form of metadata (such as HTML comments) >>> or as >>> > a header or footer appearing in the visible documentation. >>> > Since these three projects are not included in the distribution of >>> Apache >>> > ECharts (incubating), >>> > I don't think the header is required in this case. >>> > Please do correct me if I misunderstood the instructions. :) >>> > >>> > [1] https://github.com/apache/incubator-echarts-www/releases >>> > [2] https://www.apache.org/legal/src-headers.html#faq-siteindocs >>> > >>> > Thanks >>> > >>> > *Ovilia* >>> > >>> > >>> > On Thu, Oct 22, 2020 at 2:38 AM Dave Fisher <w...@apache.org> wrote: >>> > >>> >> Hi - >>> >> >>> >> Thanks, I took a look. >>> >> >>> >> Assuming that these will now all be Apache Licensed then there needs >>> to be >>> >> LICENSE files in both repositories. >>> >> >>> >> Also if these are ever released the source files will all need license >>> >> headers. [1] >>> >> >>> >> The examples readme is still pointing to the ecomfe server. >>> >> >>> >> Regards, >>> >> Dave >>> >> >>> >> [1] https://www.apache.org/legal/src-headers.html >>> >> >>> >>> On Sep 23, 2020, at 7:00 PM, Ovilia <oviliazh...@gmail.com> wrote: >>> >>> >>> >>> incubator-echarts-examples and incubator-echarts-www have been moved >>> to >>> >>> Apache org on GitHub: >>> >>> https://github.com/apache/incubator-echarts-examples >>> >>> https://github.com/apache/incubator-echarts-www >>> >>> >>> >>> >>> >>> Thanks >>> >>> >>> >>> *Ovilia* >>> >>> >>> >>> >>> >>> On Thu, Aug 27, 2020 at 5:07 PM Ville Brofeldt < >>> >> ville.v.brofe...@gmail.com> >>> >>> wrote: >>> >>> >>> >>>> Hi, >>> >>>> >>> >>>> the releases are triggered by running `yarn >>> ci:create-minor-version` and >>> >>>> `yarn ci:create-patch-version` for minor and patch releases >>> >> respectively. >>> >>>> After pushing to upstream master, deployment to npm happens >>> >> automatically. >>> >>>> I’m not familiar with the details on how this post push automation >>> has >>> >> been >>> >>>> done in practice, but I can put you in touch with the person who >>> has if >>> >>>> needed. My main point being that this makes it possible to decouple >>> >>>> triggering of deployment from the credentials used for deployment, >>> as >>> >>>> anyone with the necessary rights to the repo can initiate the >>> >> deployment. >>> >>>> >>> >>>> Ville >>> >>>> >>> >>>>> On 26. Aug 2020, at 14.23, SHUANG SU <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 >>> >>>>>> >>> >>>>>> >>> >>>> >>> >>>> >>> >> >>> >> >>> >> --------------------------------------------------------------------- >>> >> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org >>> >> For additional commands, e-mail: dev-h...@echarts.apache.org >>> >> >>> >> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org >>> For additional commands, e-mail: dev-h...@echarts.apache.org >>> >>> -- >> Thanks >> >> *Ovilia* >> >