Re: [VOTE] Accept Mysos into the Apache Incubator
On Thu, Jun 4, 2015 at 3:54 AM, Justin Erenkrantz jus...@erenkrantz.com wrote: On Sat, May 30, 2015 at 6:42 PM, Ted Dunning ted.dunn...@gmail.com wrote: It is vexed because when pronounced by many people, it sounds almost identical to how those same people would pronounce Mesos. That can lead to confusion. As there has been no trademark confusion raised, I would strongly prefer that we provide a tremendous amount of deference towards the desire of the contributors/community to the naming of the project. Actually, I believe that there has been TM issues raised. Read the Oracle guidelines which, as I remember, specifically call out portmanteaus with Oracle product names. Perhaps we would prevail in a catfight on that subject, but I would really rather stay out of any fight with the big O.
Re: [VOTE] Accept Mysos into the Apache Incubator
On Sat, May 30, 2015 at 6:42 PM, Ted Dunning ted.dunn...@gmail.com wrote: It is vexed because when pronounced by many people, it sounds almost identical to how those same people would pronounce Mesos. That can lead to confusion. As there has been no trademark confusion raised, I would strongly prefer that we provide a tremendous amount of deference towards the desire of the contributors/community to the naming of the project. They've expressed their desire to keep Mysos as their name. That is more than sufficient for me. -- justin P.S. FWIW, I definitely don't pronounce Mysos the same as Mesos...but, YMMV. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Mysos into the Apache Incubator
On Sun, May 31, 2015 at 1:15 AM, 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 Indeed. The separate thread on board@ that Jake mentions was me polling the board to see if there might be objections to the name at graduation time. Although the answer is not black and white, a lot of concerns have been raised regarding the high potential for confusion between the Mesos and Mysos names. So I'd say the're a reasonable probability of the board rejecting the name at graduation time. But depending on how long incubation goes it might not be the same board as today, so that's all hypothetical anyway. This is not about trademarks or lawyers, just a practical concern as the confusion is not helpful for either project. ...I don't think the naming issue should block Mysos from entering incubation; I just think the project should address the issue early Absolutely, changing the name later is fine and I'm not against the project incubating, not at all. But if the name has to change anyway, it's much easier to change it before any infrastructure is created. The goal of my -1 is just to express my disapproval of the name, and I've made it clear that that -1 does not prevent the project from entering incubation, as this is a majority vote. It just felt wrong to me to vote +1 as I think the name Mysos is a bad idea. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Mysos into the Apache Incubator
According to the incubator proposal guide for project naming [1] it is important to ensure a suitable project name http://incubator.apache.org/guides/graduation.html#notes-names and product names sometime during incubation, it is not necessary to do this prior to entering incubation. In fact, be careful not to disrupt your proposal and entry process. Since Bertrand has stated his concerns and that his -1 is not blocking to the project entering incubation and we have had no other objections (both here, board@, and private@mesos) I see no reason to not continue to move forward with this proposal. I will leave the vote window open until the end of today to give anyone who has not voted the chance to do so and weigh in and cast a vote. In doing so I ask that everyone please keep votes and comments focused to the proposal and projects purpose and no additional bikeshedding around the project name. -Jake [1]: http://incubator.apache.org/guides/proposal.html#name On Mon, Jun 1, 2015 at 3:29 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sun, May 31, 2015 at 1:15 AM, 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 Indeed. The separate thread on board@ that Jake mentions was me polling the board to see if there might be objections to the name at graduation time. Although the answer is not black and white, a lot of concerns have been raised regarding the high potential for confusion between the Mesos and Mysos names. So I'd say the're a reasonable probability of the board rejecting the name at graduation time. But depending on how long incubation goes it might not be the same board as today, so that's all hypothetical anyway. This is not about trademarks or lawyers, just a practical concern as the confusion is not helpful for either project. ...I don't think the naming issue should block Mysos from entering incubation; I just think the project should address the issue early Absolutely, changing the name later is fine and I'm not against the project incubating, not at all. But if the name has to change anyway, it's much easier to change it before any infrastructure is created. The goal of my -1 is just to express my disapproval of the name, and I've made it clear that that -1 does not prevent the project from entering incubation, as this is a majority vote. It just felt wrong to me to vote +1 as I think the name Mysos is a bad idea. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Accept Mysos into the Apache Incubator
With 14 positive votes (6 binding and 8 non-binding) and 1 negative vote, which was stated as non-blocking to the project entering incubation and negative only in context to the name, the vote to accept Mysos into the incubator passes. For initial project setup I will be submitting the account requests for the new project committers and creating a dev@ list. I plan to initiate a name search request with trademark@ and will start a thread on the new dev@ list regarding the projects name so the community can have a discussion around this topic. Anyone wishing to join in on the discussion will be encouraged to do so on the soon to be dev@ list. -Jake +1 Binding (6) - Jake Farrell Dave Lester Jan Iversen Henry Saputra Ralph Goers Suresh Marru +1 Non-binding (8) - Vinod Kone Chris Aniszczyk Timothy Chen Yan Xu Dallas Marlow Justin Erenkrantz Luke Han Adam Bordelon -1 Binding - Bertrand Delacretaz - stated in vote that -1 was non blocking to entering incubation and was in reference to project name only On Thu, May 28, 2015 at 12:14 PM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora
Re: [RESULT][VOTE] Accept Mysos into the Apache Incubator
Following up on this, the d...@mysos.incubator.apache.org list has been created and a thread has been started about the project name. A name search has also been created [1] and linked on the project status page [2]. -Jake [1]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-78 [2]: http://incubator.apache.org/projects/mysos.html On Mon, Jun 1, 2015 at 9:55 PM, Jake Farrell jfarr...@apache.org wrote: With 14 positive votes (6 binding and 8 non-binding) and 1 negative vote, which was stated as non-blocking to the project entering incubation and negative only in context to the name, the vote to accept Mysos into the incubator passes. For initial project setup I will be submitting the account requests for the new project committers and creating a dev@ list. I plan to initiate a name search request with trademark@ and will start a thread on the new dev@ list regarding the projects name so the community can have a discussion around this topic. Anyone wishing to join in on the discussion will be encouraged to do so on the soon to be dev@ list. -Jake +1 Binding (6) - Jake Farrell Dave Lester Jan Iversen Henry Saputra Ralph Goers Suresh Marru +1 Non-binding (8) - Vinod Kone Chris Aniszczyk Timothy Chen Yan Xu Dallas Marlow Justin Erenkrantz Luke Han Adam Bordelon -1 Binding - Bertrand Delacretaz - stated in vote that -1 was non blocking to entering incubation and was in reference to project name only On Thu, May 28, 2015 at 12:14 PM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed
Re: [VOTE] Accept Mysos into the Apache Incubator
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
Re: [VOTE] Accept Mysos into the Apache Incubator
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
Re: [VOTE] Accept Mysos into the Apache Incubator
It's ... rather presumptive to have gotten a Twitter account that includes apache given that the project hasn't been accepted into the incubator yet. On Sat, May 30, 2015, at 04:05 PM, P. Taylor Goetz 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 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
Re: [VOTE] Accept Mysos into the Apache Incubator
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
Re: [VOTE] Accept Mysos into the Apache Incubator
It is vexed because when pronounced by many people, it sounds almost identical to how those same people would pronounce Mesos. That can lead to confusion. On Sat, May 30, 2015 at 2: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
Re: [VOTE] Accept Mysos into the Apache Incubator
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
Re: [VOTE] Accept Mysos into the Apache Incubator
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
Re: [VOTE] Accept Mysos into the Apache Incubator
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
Re: [VOTE] Accept Mysos into the Apache Incubator
On Thu, May 28, 2015 at 6:14 PM, Jake Farrell jfarr...@apache.org wrote: [X ] -1 Do not accept Mysos into the Apache Incubator because... As mentioned before I think the name is too close to Mesos, especially taking into account the ways those names are pronounced in various languages. This is not a veto of course as this is a majority vote, and I don't object to the podling creation anyway, it's just the name that's problematic IMO. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 2015-05-29 11:34 GMT+08:00 Justin Erenkrantz jus...@erenkrantz.com: On Thu, May 28, 2015 at 12:14 PM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... +1. -- justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Mysos into the Apache Incubator
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. -Jake On Fri, May 29, 2015 at 4:58 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Thu, May 28, 2015 at 6:14 PM, Jake Farrell jfarr...@apache.org wrote: [X ] -1 Do not accept Mysos into the Apache Incubator because... As mentioned before I think the name is too close to Mesos, especially taking into account the ways those names are pronounced in various languages. This is not a veto of course as this is a majority vote, and I don't object to the podling creation anyway, it's just the name that's problematic IMO. -Bertrand
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 -- Jiang Yan Xu y...@jxu.me @xujyan http://twitter.com/xujyan On Thu, May 28, 2015 at 10:30 AM, jan i j...@apache.org wrote: +1 jan i On 28 May 2015 at 18:50, Timothy Chen tnac...@gmail.com wrote: +1 Tim On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk z...@twitter.com.invalid wrote: +1 On Thu, May 28, 2015 at 11:14 AM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 jan i On 28 May 2015 at 18:50, Timothy Chen tnac...@gmail.com wrote: +1 Tim On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk z...@twitter.com.invalid wrote: +1 On Thu, May 28, 2015 at 11:14 AM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 (binding) On Thu, May 28, 2015 at 9:14 AM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employers to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers.
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 Ralph On May 28, 2015, at 9:14 AM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employers to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including
Re: [VOTE] Accept Mysos into the Apache Incubator
+ 1 (binding) Suresh On May 28, 2015, at 12:14 PM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employers to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 On Thu, May 28, 2015 at 1:30 PM, jan i j...@apache.org wrote: +1 jan i On 28 May 2015 at 18:50, Timothy Chen tnac...@gmail.com wrote: +1 Tim On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk z...@twitter.com.invalid wrote: +1 On Thu, May 28, 2015 at 11:14 AM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by
Re: [VOTE] Accept Mysos into the Apache Incubator
On Thu, May 28, 2015 at 12:14 PM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... +1. -- justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 On Thu, May 28, 2015, at 09:14 AM, Jake Farrell wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employers to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. Relationships with Other Apache Products
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 @vinodkone On May 28, 2015, at 9:14 AM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employers to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 On Thu, May 28, 2015 at 11:14 AM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employers to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. Relationships with
[VOTE] Accept Mysos into the Apache Incubator
Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employers to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. Relationships with Other Apache Products Mysos depends on Apache Mesos. The Mysos team will work closely with the Apache Mesos community to ensure the proper stateless primitives are in place
Re: [VOTE] Accept Mysos into the Apache Incubator
+1 Tim On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk z...@twitter.com.invalid wrote: +1 On Thu, May 28, 2015 at 11:14 AM, Jake Farrell jfarr...@apache.org wrote: Based on the earlier discussion in thread [1], I would like to call a VOTE to accept Mysos, an Apache Mesos framework for running MySQL instances, as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached below The VOTE is open for at least the next 72 hours: [ ] +1 Accept Mysos into the Apache Incubator [ ] ±0 [ ] -1 Do not accept Mysos into the Apache Incubator because... I would like to get the voting started with my own +1 Thank you -Jake [1]: http://s.apache.org/2vm [2]: https://wiki.apache.org/incubator/MysosProposal Mysos Proposal Abstract Mysos is an Apache Mesos framework for running MySQL instances. Proposal Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the management of MySQL instances. It is designed to offer: Efficient hardware utilization through multi-tenancy (in performance-isolated containers) High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS An automated self-service option for bringing up new MySQL clusters High availability through automatic MySQL master failover An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances Background Initial development of Mysos was done at Twitter, and its codebase was recently open sourced. This proposal is for Mysos to join the Apache Incubator. Rationale Mysos is built to be used by anyone who desires to run MySQL on Apache Mesos, and in the near-future it will take advantage of state primitives that are being added to the Mesos core: https://issues.apache.org/jira/browse/MESOS-1554 Furthermore, the rapid growth of Mysos community is empowered by open source. We believe the Apache Foundation is a great fit as the long-term home for Mysos, as it provides an established process for community-driven development and decision making by consensus. Initial Goals Move the existing codebase to Apache Integrate with the Apache development process Ensure all dependencies are compliant with Apache License version 2.0 Strengthen and grow the Mysos community Incremental development and releases per Apache guidelines Current Status Mysos was originally born out of a project within Twitter. The original committers (Twitter) are working with Mesosphere and Percona to fully open source the code and make it ready for incubation at Apache. The Mysos source is currently hosted at GitHub, which will be used to seed the Apache git repository. Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Community By bringing Mysos into Apache, we believe that the community will grow even bigger. Core Developers Mysos was initially developed as a collaboration between Twitter and Mesosphere. Alignment We believe that having Mysos at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Mesos. Known Risks Orphaned Products Mysos is being used and developed by companies we work for so the companies have an interest in its continued vitality. Given strong interest we've had since open sourcing Mysos, we anticipate we'll grow a sustainable community that will expand contributors and keep it active as the Mesos core evolves. Inexperience with Open Source Most of the committers have experience at Apache, whether it's through Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were both shepherded through the ASF incubator process and have graduated to become successful and diverse open source projects. We also have Jake Farrell as an ASF Champion to help us through incubation. Homogenous Developers Initial committers come from a number of companies. Our intention is increase the diversity of contributing developers and their affiliations, and we'll recognize contributions and contributors as the community grows at Apache. We encouraged by interest in the project thus far. Reliance on Salaried Developers It is expected that Mysos development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employers to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed
