| <!DOCTYPE html><html><head><meta charset="utf-8"><title>Apache Pony Mail (Incubating)</title> |
| <link rel="stylesheet" type="text/css" href="/css/default.css"/> |
| <link rel="stylesheet" type="text/css" href="/css/fa/fa.css"/> |
| <link rel="apple-touch-icon" sizes="57x57" href="/icons/apple-icon-57x57.png"> |
| <link rel="apple-touch-icon" sizes="60x60" href="/icons/apple-icon-60x60.png"> |
| <link rel="apple-touch-icon" sizes="72x72" href="/icons/apple-icon-72x72.png"> |
| <link rel="apple-touch-icon" sizes="76x76" href="/icons/apple-icon-76x76.png"> |
| <link rel="apple-touch-icon" sizes="114x114" href="/icons/apple-icon-114x114.png"> |
| <link rel="apple-touch-icon" sizes="120x120" href="/icons/apple-icon-120x120.png"> |
| <link rel="apple-touch-icon" sizes="144x144" href="/icons/apple-icon-144x144.png"> |
| <link rel="apple-touch-icon" sizes="152x152" href="/icons/apple-icon-152x152.png"> |
| <link rel="apple-touch-icon" sizes="180x180" href="/icons/apple-icon-180x180.png"> |
| <link rel="icon" type="image/png" sizes="192x192" href="/android-icon-192x192.png"> |
| <link rel="icon" type="image/png" sizes="32x32" href="/icons/favicon-32x32.png"> |
| <link rel="icon" type="image/png" sizes="96x96" href="/icons/favicon-96x96.png"> |
| <link rel="icon" type="image/png" sizes="16x16" href="/icons/favicon-16x16.png"> |
| <link rel="manifest" href="/icons/manifest.json"> |
| <meta name="msapplication-TileColor" content="#ffffff"> |
| <meta name="msapplication-TileImage" content="/icons/ms-icon-144x144.png"> |
| <meta name="theme-color" content="#ffffff"> |
| </head><body> |
| <div id="titlebar"> |
| <a href="/contribute.html"><img align='left' style="width: 130px; height: 125px; position: relative; left: -6px; top: -6px; border: 0;" src="/images/devme.png" alt="Fork/Hack on Pony Mail"></a> |
| <img src="/images/ponymail.svg" style="width: 110px; margin-left: -10px; margin-right: 20px; height: auto;" align="left"/> |
| <h1><a id="title" href="/" style="color: #FFF !important;">Apache Pony Mail™ (Incubating)</a></h1> |
| <div id="menubar"> |
| <ul> |
| <li><a href="/docs.html"><i class="fa fa-book"></i><span>Documentation</span></a></li> |
| <li><a href="/source.html"><i class="fa fa-git-square"></i><span>Source</span></a></li> |
| <li><a href="/downloads.html"><i class="fa fa-cloud-download"></i><span>Download</span></a></li> |
| <li><a href="/support.html"><i class="fa fa-question-circle"></i><span>Get support</span></a></li> |
| <li><a href="/contribute.html"><i class="fa fa-share-alt"></i><span>Contribute</span></a></li> |
| <li><a href="/about.html"><i class="fa fa-users"></i><span>About</span></a></li> |
| <li><a href="/apache.html"><i class="fa fa-info-circle"></i><span>ASF</span></a></li> |
| </ul> |
| </div> |
| </div> |
| <h1 id='aboutponymailanditscontributors'>About Pony Mail and its Contributors<a href='#aboutponymailanditscontributors' style='color: rgba(0,0,0,0);'>¶</a></h1> |
| <h3 id='background'>Background<a href='#background' style='color: rgba(0,0,0,0);'>¶</a></h3> |
| <p>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.</p> |
| <p><em>As Rich writes in a very short essay:</em></p> |
| <p><q>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)</q></p> |
| <h3 id='rationale'>Rationale<a href='#rationale' style='color: rgba(0,0,0,0);'>¶</a></h3> |
| <p>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.</p> |
| <h3 id='whoarewe'>Who are we?<a href='#whoarewe' style='color: rgba(0,0,0,0);'>¶</a></h3> |
| <p>We're a small bunch of people committed to making mailing list interaction as easy as possible.<br/> |
| Currently, we consist of (in alphabetical order):<br/> |
| <ul> |
| <li>Andrew Bayer / abayer - mentor</li> |
| <li>Daniel Gruno / humbedooh - committer</li> |
| <li>Francesco Chicchiriccò / ilgrosso - committer</li> |
| <li>Jim Jagielski / jimjag - committer</li> |
| <li>John D. Ament / johndament - mentor</li> |
| <li>Rich Bowen / rbowen - committer</li> |
| <li>Sam Ruby / rubys - committer</li> |
| <li>Sebastian Bazley / sebb - committer</li> |
| <li>Shane Curcu / curcuru - committer</li> |
| <li>Tony Stevenson / pctony - committer</li> |
| <li>Ulises Cerviño Beresi / ucb - committer</li> |
| </ul></p> |
| <h4><a id="disclaimer"></a>Disclaimer</h4> |
| <p style="line-height: 12pt;"> |
| <a href="https://incubator.apache.org"><img src="/images/podling.svg" align="right" width="220px" style="margin-left: 6px;"/></a> |
| Apache Pony Mail (Incubating) is an effort undergoing incubation at |
| The Apache Software Foundation (ASF), sponsored by the <a href="https://incubator.apache.org"> |
| Apache Incubator</a>. Incubation is required of all newly accepted projects |
| until a further review indicates that the infrastructure, |
| communications, and decision making process have stabilized in a |
| manner consistent with other successful ASF projects. While |
| incubation status is not necessarily a reflection of the |
| completeness or stability of the code, it does indicate that the |
| project has yet to be fully endorsed by the ASF. |
| </p> |
| <p style="font-size: 9pt; line-height: 12pt; text-align: center;"> |
| Copyright 2016, the <a href="http://www.apache.org/">Apache Software Foundation</a>.<br/> |
| Apache Pony Mail and the Apache Pony Mail logo are trademarks of the Apache Software Foundation. |
| Apache and the Apache feather are registered trademarks of the |
| Apache Software Foundation. |
| </p> |
| </body></html> |