Re: [VOTE] Accept Mysos into the Apache Incubator

[Justin Erenkrantz]

On Thu, May 28, 2015 at 12:14 PM, 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...

+1.  -- justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Blog policy for poddlings

[Dave Lester]

My understanding is that only TLPs can publish to blogs.a.o.

With that said, I know several projects have published their own blogs
during incubation (including Apache Mesos and Apache Aurora) on their
websites during incubation using Middleman CMS. For example, here's a
post that was generated for Aurora when it was still part of the
incubator:
http://aurora.apache.org/blog/aurora-0-7-0-incubating-released/

The full source of the middleman CMS is available on the Aurora SVN
directory: https://svn.apache.org/repos/asf/aurora/site/, with the
necessary blog module installed -- happy to help generalize this if it's
something you'd like to reuse.

Hope that helps!

Dave

On Thu, May 28, 2015, at 06:36 PM, Roman Shaposhnik wrote:
> Hi!
> 
> can someone please remind me what's the policy
> for letting poddlings use blogs.apache.org as a
> blogging platform?
> 
> Thanks,
> Roman.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Blog policy for poddlings

[Roman Shaposhnik]

Hi!

can someone please remind me what's the policy
for letting poddlings use blogs.apache.org as a
blogging platform?

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Need people.

[Ted Dunning]

Stefan,

The j...@apache.org mailing list might be what you are looking for.



On Thu, May 28, 2015 at 10:24 AM, Stefan Reich <
stefan.reich.maker.of@googlemail.com> wrote:

> I believe Apache should be a dating facilitator between projects and
> people. Helps everyone.
>
> I am REALLY looking for some people right now. MySQL+ PHP will make an
> insane difference, right away.
>
> We are building the *smartest database ever*. Put code in there, it is
> run automatically. Open any page and your editing is guided
> automatically. We can do it.
>
> Cheers,
> Stefan
>
> http://tinybrain.blog.de
> http://snippets.tinybrain.de
>
> -
> 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

[Suresh Marru]

+ 1 (binding)

Suresh

> On May 28, 2015, at 12:14 PM, 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 ev

Re: [VOTE] Accept Mysos into the Apache Incubator

[Ralph Goers]

+1

Ralph

> On May 28, 2015, at 9: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 sala

Re: [VOTE] Accept Mysos into the Apache Incubator

[Henry Saputra]

+1 (binding)

On Thu, May 28, 2015 at 9: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 p

Re: [VOTE] Accept Mysos into the Apache Incubator

[Dallas Marlow]

+1

On Thu, May 28, 2015 at 1:30 PM, jan i  wrote:

> +1
>
> jan i
>
> On 28 May 2015 at 18:50, Timothy Chen  wrote:
>
> > +1
> >
> > Tim
> >
> > On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk  >
> > wrote:
> > > +1
> > >
> > > On Thu, May 28, 2015 at 11: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 proc

Re: [VOTE] Accept Mysos into the Apache Incubator

[Yan Xu]

+1

--
Jiang Yan Xu  @xujyan 

On Thu, May 28, 2015 at 10:30 AM, jan i  wrote:

> +1
>
> jan i
>
> On 28 May 2015 at 18:50, Timothy Chen  wrote:
>
> > +1
> >
> > Tim
> >
> > On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk  >
> > wrote:
> > > +1
> > >
> > > On Thu, May 28, 2015 at 11: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
> > wer

Re: [VOTE] Accept Mysos into the Apache Incubator

[jan i]

+1

jan i

On 28 May 2015 at 18:50, Timothy Chen  wrote:

> +1
>
> Tim
>
> On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk 
> wrote:
> > +1
> >
> > On Thu, May 28, 2015 at 11: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,
> >> 

Need people.

[Stefan Reich]

I believe Apache should be a dating facilitator between projects and
people. Helps everyone.

I am REALLY looking for some people right now. MySQL+ PHP will make an
insane difference, right away.

We are building the *smartest database ever*. Put code in there, it is
run automatically. Open any page and your editing is guided
automatically. We can do it.

Cheers,
Stefan

http://tinybrain.blog.de
http://snippets.tinybrain.de

-
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

[Timothy Chen]

+1

Tim

On Thu, May 28, 2015 at 9:26 AM, Chris Aniszczyk  
wrote:
> +1
>
> On Thu, May 28, 2015 at 11: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 empl

Re: [VOTE] Accept Mysos into the Apache Incubator

[Chris Aniszczyk]

+1

On Thu, May 28, 2015 at 11: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. 

Re: [VOTE] Accept Mysos into the Apache Incubator

[Vinod Kone]

+1

@vinodkone

> On May 28, 2015, at 9: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

Re: [VOTE] Accept Mysos into the Apache Incubator

[Dave Lester]

+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 ar

[VOTE] Accept Mysos into the Apache Incubator

[Jake Farrell]

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 to

Re: [DISCUSS] Freemarker Incubation proposal

[Bertrand Delacretaz]

Hi,

On Thu, May 28, 2015 at 4:07 PM, Jacopo Cappellato
 wrote:
> ...PS: who should start the vote?..

In general that's the role of the podling's champion.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Freemarker Incubation proposal

[Jacopo Cappellato]

Hi,

On May 28, 2015, at 11:39 AM, Bertrand Delacretaz  
wrote:

> Hi,
> 
> On Thursday, May 28, 2015, Jacopo Cappellato 
> wrote:
> 
>> ...Should we move to the next step (that I think is starting a vote)?...
> 
> 
> I think so, with two comments:
> 
> Having just two committers is very small but that can hopefully be solved
> during incubation.

Indeed this will be the main challenge that this project will have to tackle 
during incubation!

> 
> The proposal does not mention how the Freemarker name/trademark donation
> will be handled, if the copyright owners also own the name that won't be a
> problem. And anyway that can be solved during incubation, but if you can
> make sure before entering incubation that the name can be donated that's
> easier.

I think this is the case and the process of requesting/filing the SLG to the 
three owners has been already initiated.

Thank you, Bertrand.

PS: who should start the vote? I guess someone already in the IPMC (we have 3 
mentors that are already in it).

> 
> -Bertrand
> 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Apache Ignite 1.1.0 release (RC7)

[Yakov Zhdanov]

Hello!

The vote has been finished with 4 "+1" votes and 0 "0" and 0 "-1".

Thanks to all who voted:
1. Cos
2. Brane
3. Jan
4. Roman

Here is the link to the thread:
http://mail-archives.apache.org/mod_mbox/incubator-general/201505.mbox/%3CCAGcMBHhoSGOrNEe2jE6P-vJ5ux971do%2BKzm1Qg9sPkszigiaaA%40mail.gmail.com%3E

--Yakov

2015-05-25 13:14 GMT+03:00 Yakov Zhdanov :

> Hello!
>
> The Apache Ignite  PPMC has voted to release Apache Ignite
> 1.1.0-incubating.
> The vote was based on the release candidate and thread described below.
> We now request the IPMC to vote on this release.
>
> Apache Ignite 1.1.0 release (RC7) has been accepted with 7 votes for (1
> binding vote):
> 1. Konstantin (binding)
> 2. Brane
> 3. Yakov
> 4. Sergi
> 5. Alex Kuznetsov
> 6. Vladimir
> 7. Valentin
>
> We have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc7
>
> Tag name is
> ignite-1.1.0-incubating-rc7
>
> RC7 changes:
> Fixed unexpected LICENSE, NOTICE and DEPENDENCIES files in sources zip.
> Fixed LICENSE, NOTICE files content inside ignite-core jar.
> Binaries names now ends with "-bin".
> Aggregate project and all its artifacts names contains "apache" prefix.
> And many more changes which are described in devnotes (link below).
>
> DEVNOTES
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc7
>
> RELEASENOTES
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.1.0-incubating-rc7
>
> Please start voting.
>
> +1 - to accept Apache Ignite (incubating) 1.1.0
> 0 - don't care either way
> -1 - DO NOT accept Apache Ignite (incubating) 1.1.0 (explain why)
>
> Here is the PPMC vote thread -
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-1-0-release-RC7-td618.html
>
> This vote will go for 72 hours.
>
> Thanks!
>
> --Yakov
>

Re: [DISCUSS] Freemarker Incubation proposal

[Bertrand Delacretaz]

Hi,

On Thursday, May 28, 2015, Jacopo Cappellato 
wrote:

> ...Should we move to the next step (that I think is starting a vote)?...


I think so, with two comments:

Having just two committers is very small but that can hopefully be solved
during incubation.

The proposal does not mention how the Freemarker name/trademark donation
will be handled, if the copyright owners also own the name that won't be a
problem. And anyway that can be solved during incubation, but if you can
make sure before entering incubation that the name can be donated that's
easier.

-Bertrand

>

Re: [DISCUSS] Freemarker Incubation proposal

[Jacopo Cappellato]

Ok, I have updated the proposal to include the feedback received (there is a 
new paragraph about the relationship with Velocity, Commons and I have added 
Ralph and Sergio as mentors). Thanks to all of you.

Any other feedback? Should we move to the next step (that I think is starting a 
vote)?

Cheers,

Jacopo

On May 26, 2015, at 8:17 AM, Ralph Goers  wrote:

> While that is certainly a valid option, I would think that would be a topic 
> for determine how to exit the incubator.  
> 
> Ralph
> 
>> On May 22, 2015, at 11:13 AM, Siegfried Goeschl 
>>  wrote:
>> 
>> Hi Daniel,
>> 
>> regarding “lower bar for project sexiness and buzzwordyness” - another 
>> options would be using an existing ASF umbrella project, e.g. Apache 
>> Commons. There you find a lot “unsexy but heavily used stuff” … ;-)
>> 
>> Cheers,
>> 
>> Siegfried Goeschl
>> 
>>> On 22 May 2015, at 19:31, Daniel Dekany  wrote:
>>> 
>>> Technically (i.e., in source code), I don't think Velocity and
>>> Freemarker can share much. It seems that they kind of share fate
>>> though. Apparently, everyone has something more important to
>>> contribute to. And that's fine, I say, because what put these template
>>> engines into the spotlight 15(?) years ago was Web MVC, and legacy
>>> JSP's deficiencies to server that paradigm. It was a hot topic back
>>> then. But nowadays, just like in the case of Velocity (apparently),
>>> finding guys who want to hack this project for free after coding all
>>> day at the workplace, and instead of being with their families and all
>>> that, is, well... challenging. And it seems companies don't care to
>>> invest either by putting paid developers on it. (Certainly the same
>>> companies wouldn't be too happy if Freemarker is suddenly EOL-ed,
>>> though.) I guess there's some kind lower bar in project sexiness and
>>> buzzwordyness under which life just stops when it comes to
>>> contributions. Those same properties aren't needed for the project
>>> being heavily used though.
>>> 
>>> So that's where we stand. But does it mean these projects should die?
>>> I don't think so. Does it mean that these projects are not for Apache?
>>> I don't know that, you tell me! Surely I don't want FM to go into
>>> incubation if failure is the most probable outcome. Can the
>>> requirements for getting out from incubation successfully be
>>> quantified? For the kind of project like this?
>>> 
>>> -- 
>>> Thanks,
>>> Daniel Dekany
>>> 
>>> 
>>> Friday, May 22, 2015, 2:44:03 AM, Ralph Goers wrote:
>>> 
 I used to use Apache Velocity. However, it hasn’t had a release
 since 2010 and the overall project activity has been minimal for
 years. As a consequence of that, and a feature that was missing, I
 recently switched to using Freemarker for some templating work I
 needed to do. The only reason I mention Velocity is I am wondering
 what relationship these two projects should have, if any.  I am also
 concerned that if interest in development of Freemarker is
 decreasing is it going to suffer the same fate?  I guess what I am
 wondering is if there is some way these two communities and/or 
 technologies could combine?
 
 FWIW, I’d be happy to mentor this project. If I had the time I know
 I’d want to commit, but that has been in extremely short supply of late.
 
 Ralph
 
 
> On May 21, 2015, at 4:38 PM, Marvin Humphrey  
> wrote:
> 
> On Thu, May 21, 2015 at 7:11 AM, Bertrand Delacretaz
>  wrote:
>> Hi,
>> 
>> On Thu, May 21, 2015 at 3:38 PM, Sergio Fernández  
>> wrote:
>>> ...If you'd need any other mentor, I'm happy to help there (I'm 
>>> Incubator PMC
>>> and ASF Member)...
>> 
>> Currently I see three mentors and two committers at
>> https://wiki.apache.org/incubator/FreemarkerProposal, I'm not involved
>> in that podling but it looks to me that additional committers might be
>> more useful than more mentors.
> 
> 4 Mentors is a good number, though!
> 
> It's true that there aren't many initial committers, but the proposal
> addresses this issue at length.
> 
> https://wiki.apache.org/incubator/FreemarkerProposal#Known_Risks
> 
> While it continues to have a large user base, the active developer
> community has become rather small at this point, and we think that the
> "Apache Way" governance model and being part of the ASF (together with
> other projects that are already using Freemarker) would help to bring new
> life and energy to the project to better support the maintenance and
> improvements of the Freemarker codebase.
> 
> I think this is a reasonable plan and definitely worth a shot at 
> incubating.
> The Incubator has a mixed history with podlings that start small, but
> Freemarker has an advantage over many of those because it begins with a 
> large
> user base and wide adoption.
> 
> Marvin Humphr