I'm +1 on the incubating Mysos into Apache, under whatever name we settle on. As a member of the Mesos PMC, I'm not terribly concerned about the name confusion, especially given that Pesos (https://github.com/wickman/pesos) and Jesos (https://github.com/groupon/jesos) already have similar names to Mesos. But I'd also be open to another name, given the potential confusion for non-English speakers. +1 on figuring the name out ASAP, which could be immediately after starting incubation.
Minor tweaks: Under "Relationships with Other Apache Products" it says "will work closely with the Apache Mesos community to ensure the proper stateless primitives are in place", but we really mean "stateful" not "stateless" Also, under Documentation, it says "Additional will continue to be added to the project." and I think it should be "Additional documentation..." On Sat, May 30, 2015 at 4:15 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > My fear is that with all the concerns that given all the concerns that > have been raised, the board my not accept it come time for graduation. > > During incubation, presumably the project will be taking steps to > establish the Mysos name/brand. If at graduation time the board rejects the > name, the project will have to change the name and work to re-establish the > associated brand. > > That's not trivial. I'm just saying that if the project can take steps now > to eliminate that possibility, it could save the project some pain in the > future. > > I don't think the naming issue should block Mysos from entering > incubation; I just think the project should address the issue early. Maybe > make the podling name search step a first priority upon entering incubation? > > In retrospect, with Storm we waited far too long to deal with the name > search (my fault), basically doing it right before graduation. At the time > I thought "Holy shit, what if we have to change the name now?" > > Luckily we didn't have to. It would have sucked. I don't want to see that > happen to Mysos. > > -Taylor > > > > On May 30, 2015, at 5:54 PM, Chris Aniszczyk <caniszc...@gmail.com> > wrote: > > > > Again, how isn't this a viable name? > > > > There is no trademark on the word Mysos and it's not like we didn't do > our > > homework before bringing the project to Apache. > > > > You're welcome to consult TESS in the US ( http://tmsearch.uspto.gov/) > and > > the EU equivalent (https://oami.europa.eu/eSearch/#basic/1+1+1+1/mysos) > > > > Thanks. > > > >> On Sat, May 30, 2015 at 3:05 PM, P. Taylor Goetz <ptgo...@gmail.com> > wrote: > >> > >> It looks like the project already has a Twitter account and a logo [1]. > >> > >> One thing to keep in mind is how difficult it can be to re-brand > something > >> after a brand has been established. > >> > >> IMHO, it would be best to figure out a viable name as early as possible > to > >> avoid having to re-brand later in order to graduate. Based on this and > >> other threads, it seems entirely possible that the board may not accept > >> "Mysos" as a TLP name. > >> > >> -Taylor > >> > >> [1] https://twitter.com/apachemysos > >> > >> > >>>> On May 30, 2015, at 11:21 AM, Chris Aniszczyk <caniszc...@gmail.com> > >>> wrote: > >>> > >>> Personally, I would let the project decide how to move forward with the > >>> name than a bunch of us who aren't trademark lawyers. If it was > something > >>> obvious, than that would make sense, but I briefly consulted our legal > >> team > >>> internally and the name was cleared for usage since there are no marks > >>> registered and there was no likelihood of confusion. > >>> > >>> > >>> > >>>>> On Sat, May 30, 2015 at 7:45 AM, Joe Brockmeier <j...@zonker.net> > wrote: > >>>>> > >>>>> On Fri, May 29, 2015, at 12:00 PM, Jake Farrell wrote: > >>>>> Bringing back comments from a separate thread on board@ > >>>>> > >>>>> Sorry to see your vote of a -1 on the proposal due to the name. This > >> was > >>>>> raised during the discussion phase and as stated in the discussion we > >> are > >>>>> not against a name change, but saw it as something that was not a > >> blocker > >>>>> to entering incubation. > >>>>> > >>>>> We did an initial name search on our own and there are no collisions > on > >>>>> Mysos externally and we have two Mesos PMC members on the project > that > >>>>> did > >>>>> not see any problems with the name, Dave and Vinod are both on the > >> Mesos > >>>>> PMC. > >>>>> A note has been sent to the Mesos PMC private@ list regarding the > >> Mysos > >>>>> proposal and the project name and asked that comments be brought back > >> to > >>>>> here. > >>>> > >>>> I agree with Bertrand - might as well change the name *now* rather > than > >>>> dealing with it at a later date. > >>>> > >>>> AIUI, Mysos is a combination of MySQL and Mesos -- which also could > mean > >>>> potential TM headaches for the podling. > >>>> > >>>> Best, > >>>> > >>>> jzb > >>>> -- > >>>> Joe Brockmeier > >>>> j...@zonker.net > >>>> Twitter: @jzb > >>>> http://www.dissociatedpress.net/ > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>>> For additional commands, e-mail: general-h...@incubator.apache.org > >>> > >>> > >>> -- > >>> Cheers, > >>> > >>> Chris Aniszczyk > >>> http://aniszczyk.org > >>> +1 512 961 6719 > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > -- > > Cheers, > > > > Chris Aniszczyk > > http://aniszczyk.org > > +1 512 961 6719 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
