Hi all, I would like to share some considerations about why we prefer not to donate the gallery product.
The gallery has a NodeJS server which is running on an internal Baidu server and so as the user data. The server can only be accessed using internal methods so I'm afraid it can hardly be donated. And only Baidu OAuth is supported for account login and only Chinese is supported which may look weird if it's an official Apache product. (We do wish to support English or other login methods in the future but it seems we have little time to do this in the near future. ) I don't think we could use the domain name gallery.echarts.apache.org but keep the server in Baidu company inside (correct me if I'm wrong), so I think the donation may technically be hard. The gallery is not a part of ECharts project and it's only a place people put their works using ECharts. But we do think the domain name gallery.echartsjs.com may mislead the users to believe this is an official product, so it's reasonable to use a new domain name. So my proposal on this would be: 1. Choose a few candidate new domain names for the gallery product 2. Ask the Apache trademark for permission before purchasing 3. Use the new domain name for the gallery Would this plan have any branding issues? And I would like to confirm if the current statement [1] on the gallery Website is no longer necessary to cut off the trademark relationship. Would a "powered by" statement in the about page be more proper? We would make sure the gallery Website would not misuse any of the Apache logo, trademarks and so on. [1] "This Website is a community contributed work of Apache ECharts (incubating) and it is not an official Apache ECharts (incubating) product." Thanks *Ovilia* On Thu, Sep 3, 2020 at 3:52 PM Greg Stein <gst...@gmail.com> wrote: > On Thu, Sep 3, 2020 at 2:17 AM Kevin A. McGrail <kmcgr...@apache.org> > wrote: > > > I can help transfer your domain and donate it to Apache. Dropped a word > > there. > > > > That is not a "donation" but an imposition of a liability for ongoing > domain fees. > > As MarkT notes, the Foundation would not accept a domain that has seen zero > historical usage. Projects should stick to apache.org rather than create > new domains. Domains other than apache.org are acceptable for transfer, on > a case-by-case basis, where that decision focuses on historical/community > usage (of many years, and millions of users). Creating one "today" means > zero history. > > Cheers, > Greg > InfraAdmin, ASF >
