Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Amol Kekre]

+1 (non-binding)

Thks
Amol

On Fri, May 27, 2016 at 6:35 AM, Shane Curcuru  wrote:

> +1 (binding)
>
> Daniel Gruno wrote on 5/24/16 1:56 AM:
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> ...
>
> > Affiliations
> >
> > Daniel Gruno - Quenda IvS
> > Tony Stevenson - pctony ltd, VocalIQ Ltd
> > Richard Bowen - Redhat, inc.
> > Ulises Beresi - Datastax, inc.
> > David P Kendal - Quenda IvS
> > Francesco Chicchiriccò - Tirasa S.r.l.
> > Sam Ruby - IBM
> > Shane Curcuru - IBM(?)
> > Jim Jagielski - Capital One
>
> Please note I will (very, very soon) be independent, as my last day with
> $Employer is Tuesday, so we should take off my affiliation.
>
> Thanks,
> - Shane
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Shane Curcuru]

+1 (binding)

Daniel Gruno wrote on 5/24/16 1:56 AM:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
> 
> This vote will run for the usual 72 hours.
> 
> ### PROPOSAL BELOW ###
> 
> Abstract
> 
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
...

> Affiliations
> 
> Daniel Gruno - Quenda IvS
> Tony Stevenson - pctony ltd, VocalIQ Ltd
> Richard Bowen - Redhat, inc.
> Ulises Beresi - Datastax, inc.
> David P Kendal - Quenda IvS
> Francesco Chicchiriccò - Tirasa S.r.l.
> Sam Ruby - IBM
> Shane Curcuru - IBM(?)
> Jim Jagielski - Capital One

Please note I will (very, very soon) be independent, as my last day with
$Employer is Tuesday, so we should take off my affiliation.

Thanks,
- Shane

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Jim Jagielski]

+1 (binding)
> On May 24, 2016, at 1:56 AM, Daniel Gruno  wrote:
> 
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
> 
> This vote will run for the usual 72 hours.
> 
> ### PROPOSAL BELOW ###
> 
> Abstract
> 
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
> 
> Proposal
> 
> Background
> 
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
> 
> As Rich writes in a very short essay:
> 
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
> 
> Rationale
> 
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
> 
> Initial Goals
> 
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
> 
> Current Status
> 
>Meritocracy:
> 
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
> 
>All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
> 
>Community:
>The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
> 
>Core Developers:
> 
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
> 
>Alignment:
> 
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
> 
> Known Risks
> 
>Orphaned products:
> 
> We are not aware of any issues with orphaned products related to this
> project.
> 
>Pony Mail relies on a set of CSS3 templates as well as some very stable
>programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
> 
>Inexperience with Open Source:
>Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
> 
>   

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Bertrand Delacretaz]

On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno  wrote:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator...

+1

-Bertrand

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Jake Farrell]

+1 (binding)

-Jake

On Tue, May 24, 2016 at 1:56 AM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Roman Shaposhnik]

On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.

An enthusiastic +1

Roman.

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Mattmann, Chris A (3980)]

+1 binding

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++










On 5/24/16, 5:03 PM, "Henry Saputra"  wrote:

>+1 (binding)
>
>Have fun guys!
>
>On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:
>
>> Since it seems the discussion has died down, I am now calling a vote on
>> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>>
>> This vote will run for the usual 72 hours.
>>
>> ### PROPOSAL BELOW ###
>>
>> Abstract
>>
>> Pony Mail is a mail-archiving, archive viewing, and interaction service,
>> that can be integrated with many email platforms.
>>
>> Proposal
>>
>> Background
>>
>> Pony Mail began as a response to two things; the lack of diversity in
>> mailing list archives that are less bureaucratic all-or-nothing and more
>> fluid way to interact with mailing lists than what is typically offered,
>> and the lack of a performant system that solves this issue. Modern users
>> of software want to jump right into a discussion they see, but cannot
>> normally do so in a mailing list driven environment because of the rules
>> generally surrounding said environment. Pony Mail, along with a select
>> handful of newer archive systems, provides an interface that allows
>> people to just hop into a thread, and take part. Without the need to
>> subscribe, download the mbox archive, load it into your MTA, and respond.
>>
>> As Rich writes in a very short essay:
>>
>> You see a thread in which someone is WRONG ON THE INTERNET! You need to
>> correct them. How do you do this today? You kinda don't. If you really
>> wanted, you could download mbox files (and who the hell knows where they
>> are?) and then try to get them into your mail client (which never works)
>> and then reply to it. Which will break threading, because you did
>> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
>> (sound of hoof beats)
>>
>> Rationale
>>
>> One of the oft-heard complaints about Apache's development model is that
>> mailing lists are an old person's tool, and web-based communication -
>> forums - are the way to go in the 21st Century. Providing a
>> full-featured forum-like interface to mailing lists is one goal,while
>> keeping all of the enormous benefits that mailing lists already provide.
>> Asecond goal is to provide the ability to "jump in" to a mailing list
>> conversation - even one that was a while back, without the convolutions
>> that a mailing list requires. That is, to join this conversation the old
>> way, one would have had to subscribe to the mailing list, download an
>> mbox, and import it into ones mail client, in order that I be able to
>> reply to this message with correct threading. With Pony Mail, one has to
>> do none of those things, but can simply reply using the Web UI. To us,
>> this is a HUGE benefit for building community. The requirement to jump
>> through hoops to join a mailing list conversation drives away a lot of
>> people (at least, anecdotally, it does) and if we can remove that
>> barrier I think we'll have an easier time of drawing a new generation
>> into our projects.
>>
>> Initial Goals
>>
>> The initial goals of transitioning to the ASF is to expand and grow both
>> the Pony codebase and community, and ensure the project's continued
>> growth and stability through forming a diverse and reliable community,
>> in which the various facets of developers and contributors help keep the
>> project up to date with latest developments and technical as well as
>> social needs.
>>
>> Current Status
>>
>> Meritocracy:
>>
>> The bulk of the code has been written by Daniel Gruno to date, but has
>> had oversight from other committers, and mentors.
>>
>> All members of the Pony project and wider community have a deep
>> understanding and appreciation for the ASF meritocracy ideals, and are
>> almost solely current ASF Members.
>>
>> Community:
>> The community is currently heavily focused within the ASF, and
>> more specifically the Infrastructure group. This is to be expected given
>> the nature of how the code came into existence in the first place. It
>> should be noted that we have started reaching out to other groups who we
>> know are using mailing list systems and therefore also rely on mailing
>> list archive interfaces.
>>
>> Core 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Henry Saputra]

+1 (binding)

Have fun guys!

On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
>  

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On May 24, 2016, at 1:56 AM, Daniel Gruno  wrote:
> 
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
> 
> This vote will run for the usual 72 hours.
> 
> ### PROPOSAL BELOW ###
> 
> Abstract
> 
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
> 
> Proposal
> 
> Background
> 
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
> 
> As Rich writes in a very short essay:
> 
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
> 
> Rationale
> 
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
> 
> Initial Goals
> 
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
> 
> Current Status
> 
>Meritocracy:
> 
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
> 
>All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
> 
>Community:
>The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
> 
>Core Developers:
> 
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
> 
>Alignment:
> 
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
> 
> Known Risks
> 
>Orphaned products:
> 
> We are not aware of any issues with orphaned products related to this
> project.
> 
>Pony Mail relies on a set of CSS3 templates as well as some very stable
>programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
> 
>Inexperience with Open Source:
>Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Christopher]

+1 (non-binding)

On Tue, May 24, 2016 at 7:41 PM Drew Farris  wrote:

> +1 (binding)
>
> On Tue, May 24, 2016, 5:27 PM Andrew Purtell  wrote:
>
> > +1 (binding)
> >
> >
> > On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno 
> > wrote:
> >
> > > Since it seems the discussion has died down, I am now calling a vote on
> > > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> > >
> > > This vote will run for the usual 72 hours.
> > >
> > > ### PROPOSAL BELOW ###
> > >
> > > Abstract
> > >
> > > Pony Mail is a mail-archiving, archive viewing, and interaction
> service,
> > > that can be integrated with many email platforms.
> > >
> > > Proposal
> > >
> > > Background
> > >
> > > Pony Mail began as a response to two things; the lack of diversity in
> > > mailing list archives that are less bureaucratic all-or-nothing and
> more
> > > fluid way to interact with mailing lists than what is typically
> offered,
> > > and the lack of a performant system that solves this issue. Modern
> users
> > > of software want to jump right into a discussion they see, but cannot
> > > normally do so in a mailing list driven environment because of the
> rules
> > > generally surrounding said environment. Pony Mail, along with a select
> > > handful of newer archive systems, provides an interface that allows
> > > people to just hop into a thread, and take part. Without the need to
> > > subscribe, download the mbox archive, load it into your MTA, and
> respond.
> > >
> > > As Rich writes in a very short essay:
> > >
> > > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > > correct them. How do you do this today? You kinda don't. If you really
> > > wanted, you could download mbox files (and who the hell knows where
> they
> > > are?) and then try to get them into your mail client (which never
> works)
> > > and then reply to it. Which will break threading, because you did
> > > something wrong. Then you tear out your hair. PONY MAIL TO THE
> RESCUE!!!
> > > (sound of hoof beats)
> > >
> > > Rationale
> > >
> > > One of the oft-heard complaints about Apache's development model is
> that
> > > mailing lists are an old person's tool, and web-based communication -
> > > forums - are the way to go in the 21st Century. Providing a
> > > full-featured forum-like interface to mailing lists is one goal,while
> > > keeping all of the enormous benefits that mailing lists already
> provide.
> > > Asecond goal is to provide the ability to "jump in" to a mailing list
> > > conversation - even one that was a while back, without the convolutions
> > > that a mailing list requires. That is, to join this conversation the
> old
> > > way, one would have had to subscribe to the mailing list, download an
> > > mbox, and import it into ones mail client, in order that I be able to
> > > reply to this message with correct threading. With Pony Mail, one has
> to
> > > do none of those things, but can simply reply using the Web UI. To us,
> > > this is a HUGE benefit for building community. The requirement to jump
> > > through hoops to join a mailing list conversation drives away a lot of
> > > people (at least, anecdotally, it does) and if we can remove that
> > > barrier I think we'll have an easier time of drawing a new generation
> > > into our projects.
> > >
> > > Initial Goals
> > >
> > > The initial goals of transitioning to the ASF is to expand and grow
> both
> > > the Pony codebase and community, and ensure the project's continued
> > > growth and stability through forming a diverse and reliable community,
> > > in which the various facets of developers and contributors help keep
> the
> > > project up to date with latest developments and technical as well as
> > > social needs.
> > >
> > > Current Status
> > >
> > > Meritocracy:
> > >
> > > The bulk of the code has been written by Daniel Gruno to date, but has
> > > had oversight from other committers, and mentors.
> > >
> > > All members of the Pony project and wider community have a deep
> > > understanding and appreciation for the ASF meritocracy ideals, and are
> > > almost solely current ASF Members.
> > >
> > > Community:
> > > The community is currently heavily focused within the ASF, and
> > > more specifically the Infrastructure group. This is to be expected
> given
> > > the nature of how the code came into existence in the first place. It
> > > should be noted that we have started reaching out to other groups who
> we
> > > know are using mailing list systems and therefore also rely on mailing
> > > list archive interfaces.
> > >
> > > Core Developers:
> > >
> > > Almost all core developers are ASF members, and are already intimately
> > > familiar with the Apache Way.
> > >
> > > Alignment:
> > >
> > > Pony will be very in line with ASF practices and processes as many of
> > > the founding members are long term ASF 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Drew Farris]

+1 (binding)

On Tue, May 24, 2016, 5:27 PM Andrew Purtell  wrote:

> +1 (binding)
>
>
> On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno 
> wrote:
>
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> >
> > Proposal
> >
> > Background
> >
> > Pony Mail began as a response to two things; the lack of diversity in
> > mailing list archives that are less bureaucratic all-or-nothing and more
> > fluid way to interact with mailing lists than what is typically offered,
> > and the lack of a performant system that solves this issue. Modern users
> > of software want to jump right into a discussion they see, but cannot
> > normally do so in a mailing list driven environment because of the rules
> > generally surrounding said environment. Pony Mail, along with a select
> > handful of newer archive systems, provides an interface that allows
> > people to just hop into a thread, and take part. Without the need to
> > subscribe, download the mbox archive, load it into your MTA, and respond.
> >
> > As Rich writes in a very short essay:
> >
> > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > correct them. How do you do this today? You kinda don't. If you really
> > wanted, you could download mbox files (and who the hell knows where they
> > are?) and then try to get them into your mail client (which never works)
> > and then reply to it. Which will break threading, because you did
> > something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> > (sound of hoof beats)
> >
> > Rationale
> >
> > One of the oft-heard complaints about Apache's development model is that
> > mailing lists are an old person's tool, and web-based communication -
> > forums - are the way to go in the 21st Century. Providing a
> > full-featured forum-like interface to mailing lists is one goal,while
> > keeping all of the enormous benefits that mailing lists already provide.
> > Asecond goal is to provide the ability to "jump in" to a mailing list
> > conversation - even one that was a while back, without the convolutions
> > that a mailing list requires. That is, to join this conversation the old
> > way, one would have had to subscribe to the mailing list, download an
> > mbox, and import it into ones mail client, in order that I be able to
> > reply to this message with correct threading. With Pony Mail, one has to
> > do none of those things, but can simply reply using the Web UI. To us,
> > this is a HUGE benefit for building community. The requirement to jump
> > through hoops to join a mailing list conversation drives away a lot of
> > people (at least, anecdotally, it does) and if we can remove that
> > barrier I think we'll have an easier time of drawing a new generation
> > into our projects.
> >
> > Initial Goals
> >
> > The initial goals of transitioning to the ASF is to expand and grow both
> > the Pony codebase and community, and ensure the project's continued
> > growth and stability through forming a diverse and reliable community,
> > in which the various facets of developers and contributors help keep the
> > project up to date with latest developments and technical as well as
> > social needs.
> >
> > Current Status
> >
> > Meritocracy:
> >
> > The bulk of the code has been written by Daniel Gruno to date, but has
> > had oversight from other committers, and mentors.
> >
> > All members of the Pony project and wider community have a deep
> > understanding and appreciation for the ASF meritocracy ideals, and are
> > almost solely current ASF Members.
> >
> > Community:
> > The community is currently heavily focused within the ASF, and
> > more specifically the Infrastructure group. This is to be expected given
> > the nature of how the code came into existence in the first place. It
> > should be noted that we have started reaching out to other groups who we
> > know are using mailing list systems and therefore also rely on mailing
> > list archive interfaces.
> >
> > Core Developers:
> >
> > Almost all core developers are ASF members, and are already intimately
> > familiar with the Apache Way.
> >
> > Alignment:
> >
> > Pony will be very in line with ASF practices and processes as many of
> > the founding members are long term ASF members and committers.
> >
> > Known Risks
> >
> > Orphaned products:
> >
> > We are not aware of any issues with orphaned products related to this
> > project.
> >
> > Pony Mail relies on a set of CSS3 templates as well as some very
> stable
> > programming languages. We have no reason to believe these would
> > 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Andrew Purtell]

+1 (binding)


On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Luciano Resende]

+1 (binding)

On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Luke Han]

+1 (binding)

Very great experience, people love the lists.apache.org when I introduced
it to them!

Thanks.
Luke


Best Regards!
-

Luke Han

On Tue, May 24, 2016 at 10:51 AM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:

> +1 (binding)
>
> All the best,
> Venkatesh
>
> On Tue, May 24, 2016 at 10:05 AM Leif Hedstrom  wrote:
>
> >
> > > On May 23, 2016, at 11:56 PM, Daniel Gruno 
> wrote:
> > >
> > > Since it seems the discussion has died down, I am now calling a vote on
> > > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> > >
> > > This vote will run for the usual 72 hours.
> >
> >
> > +1 (binding).
> >
> > — leif
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Seetharam Venkatesh]

+1 (binding)

All the best,
Venkatesh

On Tue, May 24, 2016 at 10:05 AM Leif Hedstrom  wrote:

>
> > On May 23, 2016, at 11:56 PM, Daniel Gruno  wrote:
> >
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
>
>
> +1 (binding).
>
> — leif
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Leif Hedstrom]

> On May 23, 2016, at 11:56 PM, Daniel Gruno  wrote:
> 
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
> 
> This vote will run for the usual 72 hours.


+1 (binding).

— leif


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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[James Taylor]

+1 (binding)

On Tue, May 24, 2016 at 7:48 AM, Billie Rinaldi  wrote:

> +1 (binding)
>
> On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno 
> wrote:
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> >
> > Proposal
> >
> > Background
> >
> > Pony Mail began as a response to two things; the lack of diversity in
> > mailing list archives that are less bureaucratic all-or-nothing and more
> > fluid way to interact with mailing lists than what is typically offered,
> > and the lack of a performant system that solves this issue. Modern users
> > of software want to jump right into a discussion they see, but cannot
> > normally do so in a mailing list driven environment because of the rules
> > generally surrounding said environment. Pony Mail, along with a select
> > handful of newer archive systems, provides an interface that allows
> > people to just hop into a thread, and take part. Without the need to
> > subscribe, download the mbox archive, load it into your MTA, and respond.
> >
> > As Rich writes in a very short essay:
> >
> > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > correct them. How do you do this today? You kinda don't. If you really
> > wanted, you could download mbox files (and who the hell knows where they
> > are?) and then try to get them into your mail client (which never works)
> > and then reply to it. Which will break threading, because you did
> > something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> > (sound of hoof beats)
> >
> > Rationale
> >
> > One of the oft-heard complaints about Apache's development model is that
> > mailing lists are an old person's tool, and web-based communication -
> > forums - are the way to go in the 21st Century. Providing a
> > full-featured forum-like interface to mailing lists is one goal,while
> > keeping all of the enormous benefits that mailing lists already provide.
> > Asecond goal is to provide the ability to "jump in" to a mailing list
> > conversation - even one that was a while back, without the convolutions
> > that a mailing list requires. That is, to join this conversation the old
> > way, one would have had to subscribe to the mailing list, download an
> > mbox, and import it into ones mail client, in order that I be able to
> > reply to this message with correct threading. With Pony Mail, one has to
> > do none of those things, but can simply reply using the Web UI. To us,
> > this is a HUGE benefit for building community. The requirement to jump
> > through hoops to join a mailing list conversation drives away a lot of
> > people (at least, anecdotally, it does) and if we can remove that
> > barrier I think we'll have an easier time of drawing a new generation
> > into our projects.
> >
> > Initial Goals
> >
> > The initial goals of transitioning to the ASF is to expand and grow both
> > the Pony codebase and community, and ensure the project's continued
> > growth and stability through forming a diverse and reliable community,
> > in which the various facets of developers and contributors help keep the
> > project up to date with latest developments and technical as well as
> > social needs.
> >
> > Current Status
> >
> > Meritocracy:
> >
> > The bulk of the code has been written by Daniel Gruno to date, but has
> > had oversight from other committers, and mentors.
> >
> > All members of the Pony project and wider community have a deep
> > understanding and appreciation for the ASF meritocracy ideals, and are
> > almost solely current ASF Members.
> >
> > Community:
> > The community is currently heavily focused within the ASF, and
> > more specifically the Infrastructure group. This is to be expected given
> > the nature of how the code came into existence in the first place. It
> > should be noted that we have started reaching out to other groups who we
> > know are using mailing list systems and therefore also rely on mailing
> > list archive interfaces.
> >
> > Core Developers:
> >
> > Almost all core developers are ASF members, and are already intimately
> > familiar with the Apache Way.
> >
> > Alignment:
> >
> > Pony will be very in line with ASF practices and processes as many of
> > the founding members are long term ASF members and committers.
> >
> > Known Risks
> >
> > Orphaned products:
> >
> > We are not aware of any issues with orphaned products related to this
> > project.
> >
> > Pony Mail relies on a set of CSS3 templates as well as some very
> stable
> > programming languages. We have no reason to believe these would
> > be 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Billie Rinaldi]

+1 (binding)

On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno  wrote:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very
stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Ralph Goers]

+1 (binding)

Ralph

> On May 23, 2016, at 10:56 PM, Daniel Gruno  wrote:
> 
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
> 
> This vote will run for the usual 72 hours.
> 
> ### PROPOSAL BELOW ###
> 
> Abstract
> 
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
> 
> Proposal
> 
> Background
> 
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
> 
> As Rich writes in a very short essay:
> 
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
> 
> Rationale
> 
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
> 
> Initial Goals
> 
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
> 
> Current Status
> 
>Meritocracy:
> 
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
> 
>All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
> 
>Community:
>The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
> 
>Core Developers:
> 
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
> 
>Alignment:
> 
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
> 
> Known Risks
> 
>Orphaned products:
> 
> We are not aware of any issues with orphaned products related to this
> project.
> 
>Pony Mail relies on a set of CSS3 templates as well as some very stable
>programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
> 
>Inexperience with Open Source:
>Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[John D. Ament]

+1

On Tue, May 24, 2016 at 1:56 AM Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous Developers:
> 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Sam Ruby]

On Tue, May 24, 2016 at 1:56 AM, Daniel Gruno  wrote:
> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.

+1 (binding)

- Sam Ruby

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Pierre Smits]

+1 (non-binding)

This is a good approach. In the past we have seen a few TopLevel projects
spawned on the basis of its core product being in use as an ASF internal
solution without having gone through the incubation proces. Some of these
projects lead a marginal existence, don't do releases and don't work on
community building and expansion.

Best regards,


Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, May 24, 2016 at 9:26 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> +1 (not binding)
>
> Jacques
>
>
>
> Le 24/05/2016 à 07:56, Daniel Gruno a écrit :
>
>> Since it seems the discussion has died down, I am now calling a vote on
>> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>>
>> This vote will run for the usual 72 hours.
>>
>> ### PROPOSAL BELOW ###
>>
>> Abstract
>>
>> Pony Mail is a mail-archiving, archive viewing, and interaction service,
>> that can be integrated with many email platforms.
>>
>> Proposal
>>
>> Background
>>
>> Pony Mail began as a response to two things; the lack of diversity in
>> mailing list archives that are less bureaucratic all-or-nothing and more
>> fluid way to interact with mailing lists than what is typically offered,
>> and the lack of a performant system that solves this issue. Modern users
>> of software want to jump right into a discussion they see, but cannot
>> normally do so in a mailing list driven environment because of the rules
>> generally surrounding said environment. Pony Mail, along with a select
>> handful of newer archive systems, provides an interface that allows
>> people to just hop into a thread, and take part. Without the need to
>> subscribe, download the mbox archive, load it into your MTA, and respond.
>>
>> As Rich writes in a very short essay:
>>
>> You see a thread in which someone is WRONG ON THE INTERNET! You need to
>> correct them. How do you do this today? You kinda don't. If you really
>> wanted, you could download mbox files (and who the hell knows where they
>> are?) and then try to get them into your mail client (which never works)
>> and then reply to it. Which will break threading, because you did
>> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
>> (sound of hoof beats)
>>
>> Rationale
>>
>> One of the oft-heard complaints about Apache's development model is that
>> mailing lists are an old person's tool, and web-based communication -
>> forums - are the way to go in the 21st Century. Providing a
>> full-featured forum-like interface to mailing lists is one goal,while
>> keeping all of the enormous benefits that mailing lists already provide.
>> Asecond goal is to provide the ability to "jump in" to a mailing list
>> conversation - even one that was a while back, without the convolutions
>> that a mailing list requires. That is, to join this conversation the old
>> way, one would have had to subscribe to the mailing list, download an
>> mbox, and import it into ones mail client, in order that I be able to
>> reply to this message with correct threading. With Pony Mail, one has to
>> do none of those things, but can simply reply using the Web UI. To us,
>> this is a HUGE benefit for building community. The requirement to jump
>> through hoops to join a mailing list conversation drives away a lot of
>> people (at least, anecdotally, it does) and if we can remove that
>> barrier I think we'll have an easier time of drawing a new generation
>> into our projects.
>>
>> Initial Goals
>>
>> The initial goals of transitioning to the ASF is to expand and grow both
>> the Pony codebase and community, and ensure the project's continued
>> growth and stability through forming a diverse and reliable community,
>> in which the various facets of developers and contributors help keep the
>> project up to date with latest developments and technical as well as
>> social needs.
>>
>> Current Status
>>
>>  Meritocracy:
>>
>> The bulk of the code has been written by Daniel Gruno to date, but has
>> had oversight from other committers, and mentors.
>>
>>  All members of the Pony project and wider community have a deep
>> understanding and appreciation for the ASF meritocracy ideals, and are
>> almost solely current ASF Members.
>>
>>  Community:
>>  The community is currently heavily focused within the ASF, and
>> more specifically the Infrastructure group. This is to be expected given
>> the nature of how the code came into existence in the first place. It
>> should be noted that we have started reaching out to other groups who we
>> know are using mailing list systems and therefore also rely on mailing
>> list archive interfaces.
>>
>>  Core Developers:
>>
>> Almost all core developers are ASF members, and are already intimately
>> familiar with the Apache Way.
>>
>>  Alignment:
>>
>> Pony will be very in line with ASF 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Justin Mclean]

+1 (binding)

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

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Jacques Le Roux]

+1 (not binding)

Jacques


Le 24/05/2016 à 07:56, Daniel Gruno a écrit :

Since it seems the discussion has died down, I am now calling a vote on
accepting Pony Mail into the Incubator. Sorry in advance for potato.

This vote will run for the usual 72 hours.

### PROPOSAL BELOW ###

Abstract

Pony Mail is a mail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.

Proposal

Background

Pony Mail began as a response to two things; the lack of diversity in
mailing list archives that are less bureaucratic all-or-nothing and more
fluid way to interact with mailing lists than what is typically offered,
and the lack of a performant system that solves this issue. Modern users
of software want to jump right into a discussion they see, but cannot
normally do so in a mailing list driven environment because of the rules
generally surrounding said environment. Pony Mail, along with a select
handful of newer archive systems, provides an interface that allows
people to just hop into a thread, and take part. Without the need to
subscribe, download the mbox archive, load it into your MTA, and respond.

As Rich writes in a very short essay:

You see a thread in which someone is WRONG ON THE INTERNET! You need to
correct them. How do you do this today? You kinda don't. If you really
wanted, you could download mbox files (and who the hell knows where they
are?) and then try to get them into your mail client (which never works)
and then reply to it. Which will break threading, because you did
something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
(sound of hoof beats)

Rationale

One of the oft-heard complaints about Apache's development model is that
mailing lists are an old person's tool, and web-based communication -
forums - are the way to go in the 21st Century. Providing a
full-featured forum-like interface to mailing lists is one goal,while
keeping all of the enormous benefits that mailing lists already provide.
Asecond goal is to provide the ability to "jump in" to a mailing list
conversation - even one that was a while back, without the convolutions
that a mailing list requires. That is, to join this conversation the old
way, one would have had to subscribe to the mailing list, download an
mbox, and import it into ones mail client, in order that I be able to
reply to this message with correct threading. With Pony Mail, one has to
do none of those things, but can simply reply using the Web UI. To us,
this is a HUGE benefit for building community. The requirement to jump
through hoops to join a mailing list conversation drives away a lot of
people (at least, anecdotally, it does) and if we can remove that
barrier I think we'll have an easier time of drawing a new generation
into our projects.

Initial Goals

The initial goals of transitioning to the ASF is to expand and grow both
the Pony codebase and community, and ensure the project's continued
growth and stability through forming a diverse and reliable community,
in which the various facets of developers and contributors help keep the
project up to date with latest developments and technical as well as
social needs.

Current Status

 Meritocracy:

The bulk of the code has been written by Daniel Gruno to date, but has
had oversight from other committers, and mentors.

 All members of the Pony project and wider community have a deep
understanding and appreciation for the ASF meritocracy ideals, and are
almost solely current ASF Members.

 Community:
 The community is currently heavily focused within the ASF, and
more specifically the Infrastructure group. This is to be expected given
the nature of how the code came into existence in the first place. It
should be noted that we have started reaching out to other groups who we
know are using mailing list systems and therefore also rely on mailing
list archive interfaces.

 Core Developers:

Almost all core developers are ASF members, and are already intimately
familiar with the Apache Way.

 Alignment:

Pony will be very in line with ASF practices and processes as many of
the founding members are long term ASF members and committers.

Known Risks

 Orphaned products:

We are not aware of any issues with orphaned products related to this
project.

 Pony Mail relies on a set of CSS3 templates as well as some very stable
 programming languages. We have no reason to believe these would
be orphaned or, should they become orphaned, that it would impact the
development of the project.

 Inexperience with Open Source:
 Most of the current committers are already ASF members and
committers, we do not believe there to be any concerns around OSS
inexperience.

 Homogenous Developers:
 While the current mix of people involved in the project spans
several continents with a wide variety of skills and experience, a long
standing relation with the ASF applies to all 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Myrle Krantz]

+1 (non-binding)

(Thank you guys for doing this.)


*Myrle Krantz*
Solutions Architect
RɅĐɅЯ, The Mifos Initiative
mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
  


On Tue, May 24, 2016 at 8:36 AM, Sergio Fernández  wrote:

> +++1 (binding)
>
> On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno 
> wrote:
>
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> >
> > Proposal
> >
> > Background
> >
> > Pony Mail began as a response to two things; the lack of diversity in
> > mailing list archives that are less bureaucratic all-or-nothing and more
> > fluid way to interact with mailing lists than what is typically offered,
> > and the lack of a performant system that solves this issue. Modern users
> > of software want to jump right into a discussion they see, but cannot
> > normally do so in a mailing list driven environment because of the rules
> > generally surrounding said environment. Pony Mail, along with a select
> > handful of newer archive systems, provides an interface that allows
> > people to just hop into a thread, and take part. Without the need to
> > subscribe, download the mbox archive, load it into your MTA, and respond.
> >
> > As Rich writes in a very short essay:
> >
> > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > correct them. How do you do this today? You kinda don't. If you really
> > wanted, you could download mbox files (and who the hell knows where they
> > are?) and then try to get them into your mail client (which never works)
> > and then reply to it. Which will break threading, because you did
> > something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> > (sound of hoof beats)
> >
> > Rationale
> >
> > One of the oft-heard complaints about Apache's development model is that
> > mailing lists are an old person's tool, and web-based communication -
> > forums - are the way to go in the 21st Century. Providing a
> > full-featured forum-like interface to mailing lists is one goal,while
> > keeping all of the enormous benefits that mailing lists already provide.
> > Asecond goal is to provide the ability to "jump in" to a mailing list
> > conversation - even one that was a while back, without the convolutions
> > that a mailing list requires. That is, to join this conversation the old
> > way, one would have had to subscribe to the mailing list, download an
> > mbox, and import it into ones mail client, in order that I be able to
> > reply to this message with correct threading. With Pony Mail, one has to
> > do none of those things, but can simply reply using the Web UI. To us,
> > this is a HUGE benefit for building community. The requirement to jump
> > through hoops to join a mailing list conversation drives away a lot of
> > people (at least, anecdotally, it does) and if we can remove that
> > barrier I think we'll have an easier time of drawing a new generation
> > into our projects.
> >
> > Initial Goals
> >
> > The initial goals of transitioning to the ASF is to expand and grow both
> > the Pony codebase and community, and ensure the project's continued
> > growth and stability through forming a diverse and reliable community,
> > in which the various facets of developers and contributors help keep the
> > project up to date with latest developments and technical as well as
> > social needs.
> >
> > Current Status
> >
> > Meritocracy:
> >
> > The bulk of the code has been written by Daniel Gruno to date, but has
> > had oversight from other committers, and mentors.
> >
> > All members of the Pony project and wider community have a deep
> > understanding and appreciation for the ASF meritocracy ideals, and are
> > almost solely current ASF Members.
> >
> > Community:
> > The community is currently heavily focused within the ASF, and
> > more specifically the Infrastructure group. This is to be expected given
> > the nature of how the code came into existence in the first place. It
> > should be noted that we have started reaching out to other groups who we
> > know are using mailing list systems and therefore also rely on mailing
> > list archive interfaces.
> >
> > Core Developers:
> >
> > Almost all core developers are ASF members, and are already intimately
> > familiar with the Apache Way.
> >
> > Alignment:
> >
> > Pony will be very in line with ASF practices and processes as many of
> > the founding members are long term ASF members and committers.
> >
> > Known Risks
> >
> > Orphaned products:
> >
> > We are not aware of 

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Sergio Fernández]

+++1 (binding)

On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno  wrote:

> Since it seems the discussion has died down, I am now calling a vote on
> accepting Pony Mail into the Incubator. Sorry in advance for potato.
>
> This vote will run for the usual 72 hours.
>
> ### PROPOSAL BELOW ###
>
> Abstract
>
> Pony Mail is a mail-archiving, archive viewing, and interaction service,
> that can be integrated with many email platforms.
>
> Proposal
>
> Background
>
> Pony Mail began as a response to two things; the lack of diversity in
> mailing list archives that are less bureaucratic all-or-nothing and more
> fluid way to interact with mailing lists than what is typically offered,
> and the lack of a performant system that solves this issue. Modern users
> of software want to jump right into a discussion they see, but cannot
> normally do so in a mailing list driven environment because of the rules
> generally surrounding said environment. Pony Mail, along with a select
> handful of newer archive systems, provides an interface that allows
> people to just hop into a thread, and take part. Without the need to
> subscribe, download the mbox archive, load it into your MTA, and respond.
>
> As Rich writes in a very short essay:
>
> You see a thread in which someone is WRONG ON THE INTERNET! You need to
> correct them. How do you do this today? You kinda don't. If you really
> wanted, you could download mbox files (and who the hell knows where they
> are?) and then try to get them into your mail client (which never works)
> and then reply to it. Which will break threading, because you did
> something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> (sound of hoof beats)
>
> Rationale
>
> One of the oft-heard complaints about Apache's development model is that
> mailing lists are an old person's tool, and web-based communication -
> forums - are the way to go in the 21st Century. Providing a
> full-featured forum-like interface to mailing lists is one goal,while
> keeping all of the enormous benefits that mailing lists already provide.
> Asecond goal is to provide the ability to "jump in" to a mailing list
> conversation - even one that was a while back, without the convolutions
> that a mailing list requires. That is, to join this conversation the old
> way, one would have had to subscribe to the mailing list, download an
> mbox, and import it into ones mail client, in order that I be able to
> reply to this message with correct threading. With Pony Mail, one has to
> do none of those things, but can simply reply using the Web UI. To us,
> this is a HUGE benefit for building community. The requirement to jump
> through hoops to join a mailing list conversation drives away a lot of
> people (at least, anecdotally, it does) and if we can remove that
> barrier I think we'll have an easier time of drawing a new generation
> into our projects.
>
> Initial Goals
>
> The initial goals of transitioning to the ASF is to expand and grow both
> the Pony codebase and community, and ensure the project's continued
> growth and stability through forming a diverse and reliable community,
> in which the various facets of developers and contributors help keep the
> project up to date with latest developments and technical as well as
> social needs.
>
> Current Status
>
> Meritocracy:
>
> The bulk of the code has been written by Daniel Gruno to date, but has
> had oversight from other committers, and mentors.
>
> All members of the Pony project and wider community have a deep
> understanding and appreciation for the ASF meritocracy ideals, and are
> almost solely current ASF Members.
>
> Community:
> The community is currently heavily focused within the ASF, and
> more specifically the Infrastructure group. This is to be expected given
> the nature of how the code came into existence in the first place. It
> should be noted that we have started reaching out to other groups who we
> know are using mailing list systems and therefore also rely on mailing
> list archive interfaces.
>
> Core Developers:
>
> Almost all core developers are ASF members, and are already intimately
> familiar with the Apache Way.
>
> Alignment:
>
> Pony will be very in line with ASF practices and processes as many of
> the founding members are long term ASF members and committers.
>
> Known Risks
>
> Orphaned products:
>
> We are not aware of any issues with orphaned products related to this
> project.
>
> Pony Mail relies on a set of CSS3 templates as well as some very stable
> programming languages. We have no reason to believe these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous