incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "PonyMailProposal" by SebastianBazley
Date Thu, 04 Feb 2016 12:47:29 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "PonyMailProposal" page has been changed by SebastianBazley:
https://wiki.apache.org/incubator/PonyMailProposal?action=diff&rev1=4&rev2=5

Comment:
Missing spaces; other simple typos

  
  = 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 wants 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.
+ 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)
+ 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 wouldhave had to subscribe to the mailing list, download an mbox, and import
it intoones mail client, in order that I be able to reply to this message with correctthreading.
With Pony Mail, one has to do none of those things, but can simplyreply 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 drivesaway a lot of people (at least, anecdotally, it
does.) and if we can remove thatbarrier I think we'll have an easier time of drawing a new
generation into our projects.
+ 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.
@@ -20, +20 @@

  === Current Status ===
   * '''Meritocracy:'''
  
- The pricipal of the code has been written by Daniel Gruno to date, but has had oversight
from other committers, and mentors.
+ 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.
+   . 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 allcore developers are ASF members, and are already intimately familiar with the
Apache Way.
+ Almost all core developers are ASF members, and are already intimately familiar with the
Apache Way.
  
   * '''Alignment:'''
  
- Pony will be very inline with ASF practices and processes as many of the founding members
are long term ASF members and committers.
+ 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'''
  
@@ -54, +54 @@

    organisations.<<BR>>We see no issues regarding possible strong-arming or otherwise
skewing project focus, nor do we believe that absence of salaries would deter people from
committing to this project.
  
   * '''Relationships with Other Apache Products:'''
-   . Pony Mail uses at least Apache HTTPd with mod_lua as it's end-user facing delivery mechanism.
Many of the commiters are also involved with this PMC.
+   . Pony Mail uses at least Apache HTTPd with mod_lua as its end-user facing delivery mechanism.
Many of the commiters are also involved with this PMC.
    Pony also utilises !ElasticSearch which is based on Lucene.
  
  '''Documentation'''
@@ -68, +68 @@

  
  '''Source and Intellectual Property Submission Plan'''
  
-  . We know of no legal encumberments in the way of transfer of source to Apache. Portions
of the software (sans dependencies) is already owned by the ASF, other portions privately,
but it will be granted to the ASF in it's entirety.
+  . We know of no legal encumberments in the way of transfer of source to Apache. Portions
of the software (sans dependencies) is already owned by the ASF, other portions privately,
but it will be granted to the ASF in its entirety.
  
  '''External Dependencies''':
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message