I like CottonSQL! #shipit "CottonSQL is an elastic MySQL and PostgreSQL framework running on Apache Mesos"
Any other input here? It'd be great to wrap up the discussion soon and hold a vote on a new name. On Mon, Jun 22, 2015, at 04:33 PM, Yan Xu wrote: > Sorry about the delay but we've come up with a few more names last week. > > How about > - *Cotton*? If this raises trademark concerns, *CottonSQL*? (Cotton is > elastic and looking like the cloud) > - *Spawn*? As in this is the service that spawns DB clusters in Mesos. > > Would love to hear your feedback! > > -- > Jiang Yan Xu <y...@jxu.me> @xujyan <http://twitter.com/xujyan> > > On Tue, Jun 16, 2015 at 12:47 PM, Jake Farrell <jfarr...@apache.org> > wrote: > > > If we are going to change the name then I like the idea of branching away > > from the Mesos name like other frameworks have done > > > > -Jake > > > > On Tue, Jun 16, 2015 at 3:12 PM, Vinod Kone <vinodk...@apache.org> wrote: > > > > > MesoSQL sounds ok to me considering PostgreSQL follows that naming > > > convention, although in the latter case the vernacular form is Postgres, > > > which doesn't work for us. How do we plan to pronounce MesoSQL? Meso > > > sea-quell? Mesos sea-quell? Mesos es-queue-el? All forms sound harder to > > > pronounce than Mysos, but oh well. > > > > > > Too bad we cannot use CloudSQL (already used by Google) or ElasticSQL > > > <https://github.com/rore/ElasticSQL>. > > > > > > Do we need to have Mesos in the framework name? None of the frameworks > > that > > > were written purely for Mesos have Mesos in their name (e.g., Aurora, > > > Marathon, Chronos). > > > > > > > > > On Tue, Jun 16, 2015 at 11:57 AM, Yan Xu <y...@jxu.me> wrote: > > > > > > > + Vinod > > > > > > > > What do you think? > > > > > > > > BTW, Tobi gave a thumbs up offline. > > > > > > > > -- > > > > Jiang Yan Xu <y...@jxu.me> @xujyan <http://twitter.com/xujyan> > > > > > > > > On Fri, Jun 12, 2015 at 4:50 PM, Ted Dunning <ted.dunn...@gmail.com> > > > > wrote: > > > > > > > > > That looks much better to me. > > > > > > > > > > I would point out also that the key worry about confusion is on the > > > part > > > > of > > > > > people *outside* the project. Those inside are likely to learn to > > > > > distinguish the nuances of any name. > > > > > > > > > > > > > > > > > > > > On Fri, Jun 12, 2015 at 11:15 AM, Yan Xu <y...@jxu.me> wrote: > > > > > > > > > > > Thanks Dave for following up on this discussion! > > > > > > > > > > > > +1 for MesoSQL, abbreviated from Mesos SQL (note the single 's' in > > > the > > > > > > middle). > > > > > > > > > > > > I think its OK for project names to evolve and we cannot predict > > too > > > > far > > > > > > into the future but this name is the least controversial at this > > > point > > > > > and > > > > > > it's not too bad. :) > > > > > > > > > > > > -- > > > > > > Jiang Yan Xu <y...@jxu.me> @xujyan <http://twitter.com/xujyan> > > > > > > > > > > > > On Fri, Jun 12, 2015 at 10:42 AM, Dave Lester <d...@davelester.org > > > > > > > > wrote: > > > > > > > > > > > > > Hi Jake, > > > > > > > > > > > > > > Personally, I am fine with the Mysos name -- I don't foresee it > > > being > > > > > > > confusing to members of the community, and we've also begun to > > > > promote > > > > > > > the project so continuing to use the name would be the > > > > least-disruptive > > > > > > > path forward. With that said, folks within the larger Apache > > > > community > > > > > > > (outside of Mesos and Mysos) have expressed some concern here. > > > > > > > > > > > > > > One alternative name that Yan suggested that is MesoSQL. I'm > > > > definitely > > > > > > > +1 for the idea, and think it's great for a few reasons: > > > > > > > > > > > > > > * It clearly attributes the framework to Apache Mesos, which is > > > > > similar > > > > > > > to the Mysos name we currently use. > > > > > > > * It's slightly broader than just relating to MySQL, which as > > > we've > > > > > > > seen in a recent email thread there's already interest among > > > > community > > > > > > > members in broadening the framework to support PostgreSQL > > > > > > > > > > > > > > The MesoSQL name was also run by the Mesos private@ list with no > > > > > > > objections -- perhaps we should consider it as an alternative and > > > run > > > > > > > with it? > > > > > > > > > > > > > > Dave > > > > > > > > > > > > > > On Mon, Jun 1, 2015, at 08:58 PM, Jake Farrell wrote: > > > > > > > > During the incubator vote thread [1] for the Mysos proposal the > > > > > project > > > > > > > > name came up as a potential issue due to its similarity with > > > Apache > > > > > > > > Mesos. > > > > > > > > This was carried over and also raised on the board@ and > > > > > private@mesos > > > > > > > > mailing lists. As a follow up to those discussions I have > > > created a > > > > > > > > podling > > > > > > > > name search [2] and would like to open up the discussion > > > regarding > > > > > the > > > > > > > > project name here on our dev list. Before any additional > > project > > > > > setup > > > > > > > > occurs I would like to make sure we have closed any outstanding > > > > > issues > > > > > > > > with > > > > > > > > the Mysos name or proposed and voted on a new name (if > > > necessary). > > > > > > > > > > > > > > > > -Jake > > > > > > > > > > > > > > > > > > > > > > > > [1]: http://s.apache.org/EjOH > > > > > > > > [2]: > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-78 > > > > > > > > > > > > > > > > > > > > > > > > > > >
