[Hamara-devel] Try mailman 3.0 and if that fulfills our e-mail to forum and vice-versa ?

[shirish]

Reply in-line :-

On 04/28/2015 12:40 AM, Vikas Tara wrote:
> On 27/04/15 17:12, shirish wrote:
>> Hi all,
>> Mailman 3.0 is out .  Please see https://code.launchpad.net/mailman
>> for more info. Unlike yesteryear's monolithic single binary mailman
>> 3.0 is now split into 5 separate binaries i.e. Mailman core,
>> mailman.client, HyperKitty, Postorius and bundler  . While as can be
>> seen it will take a few days for mailman 3.0 to make its début, if we
>> have a person or two who can play with it,  will be easier for us to
>> take a decision.
>>
>> What do you guys think ?
>>
> If it gives us the functionality that the forum offers - but via a web
> interface to the mailing list - then it would make sense to drop the
> forum altogether.
>
> I guess we need to take it for a spin - unless you can find the
> functionality we need in the features list?

We seem to be running into a spate of good co-incidences.

See 
https://mail.python.org/pipermail/mailman-developers/2015-April/024959.html

It's great news that Mailman 3 just got released today. As shared here's 
the feature-list :-

"Some things you won't miss, like passwords in clear text, monthly 
password reminders, having multiple accounts to manage subscriptions 
with different email addresses, no built-in archive searching, 
restrictions on naming lists in multiple domains, etc." - Barry Warsaw

Sharing the announce mail of Mailman 3 as shouted out today :-

Twenty years ago, I attended the first Python Workshop at NIST with 
about 20 other old school Pythonistas.  Earlier this month I attended 
PyCon 2015 in Montreal. PyCon is always exhilarating, but this one was 
incredibly special for me personally, because my son was on spring break 
and joined me for the first half of the conference.

Both the Python language and its community have grown a little bit 
<wink> in the intervening years, but what hasn't changed is our love of 
the language, and the truly amazing people we share that love with.  The 
Python community really is one of the very best open source communities 
on the planet.

The best community inside that great Python family has to be the GNU 
Mailman team. They're all smart and cool, fun to hang out with, and fun 
to hack with. With diverse backgrounds, each and every one are good 
friends and valued technical peers. As has been the case for the last 
few years, we've sprinted on Mailman 3, getting lots of great work done, 
but never quite getting something we were satisfied enough with to 
release. The first alpha of Mailman 3 was released a little over 7 years 
ago.

And so I'm here --and on behalf of Abhilash, Aurélien, Florian, John, 
Mark, Stephen, Sumana, Terri, our GSoC students, and all the great 
people who have contributed over the years-- to proudly announce the 
official release of GNU Mailman 3.0, code named "Show Don't Tell".

Mailman 3 is really a suite of 5 tools:

  * The core, which provides the mail delivery engine, the unified user 
model, moderation and modification of email messages, and interfaces to 
external archivers;

  * Postorius, our new Django-based web user interface for users and list
    administrators;

  * HyperKitty, our new Django-based web archiver, providing rich access 
to the historical record of mailing list traffic;

  * mailman.client, the official Python bindings to the core's REST API;

  * mailman-bundler, a set of scripts to make it easy to deploy the full
    suite inside Python virtual environments.

What's new about Mailman 3?  Well, lots!  Some highlights include:

  * Backed by a relational database;

  * True support for multiple domains, with no cross-domain mailing list 
naming restrictions;

  * One user account to manage all your subscriptions on a site;

  * The core's functionality exposed through an administrative REST+JSON 
API;

  * All passwords hashed by default, and no monthly password reminders!

  * Users can post to lists via the web interface;

This is the feature that we needed/wanted.

  * Built-in archive searching!

and more.  Tons more.

There will be things you love about Mailman 3, and things you don't 
like. You'll glimpse great possibilities and glaring holes.  You'll be 
excited and frustrated. Such is life with an all-volunteer free software 
project.

For the things you like, and the exciting possibilities, we encourage 
you to experiment, to do wacky things we haven't thought of, integrate 
it with your own tools, or just carefully go about deploying a Mailman 3 
system.  Tell us how you're using it!

For the things you don't like, we invite you to join us.  Come to the 
mailing list <mailman-developers at python.org> and talk with us.  Submit 
bug reports and pull requests.  Help us close the gaps and make Mailman 
3 better.

Whether your interests are for Internet RFCs, web site development,
operations, or you just want to find a fun Python project to hack on 
with cool people, as they say, contributions are welcome.

See the release notes, as well as links to download each component:

     http://wiki.list.org/Mailman3

You probably want to start with the bundler and let it grab and install 
all the other parts.

More information is available at:

     http://www.list.org
     http://wiki.list.org
     http://launchpad.net/mailman
     #mailman on freenode
     mailman-developers at python.org

Happy Mailman Day,
-Barry & the Mailman Cabal

The "manual" can be found out at 
http://gnu-mailman.readthedocs.org/en/latest/

Right now only the 7.6 MB HTML one is usable so please download that.


minor bugs being found and fixed :-

[15:29:17] <abompard> florianf: found two minor bugs in the 
mailman.client release (not in the code)
[15:29:56] <abompard> florianf: first, the COPYING.LESSER file is not in 
MANIFEST.in, so it's not in the PyPI tarball
[15:30:28] <abompard> florianf: second, the PyPI tarball contains the 
.tox subfolder and all its venvs...
[15:46:27] <florianf> abompard: oh jeez.
[15:46:37] <florianf> abompard: thanks! :-)
[15:46:43] <abompard> florianf: no problem :-)
[15:47:28] <florianf> abompard: I'll add a new release file.
[15:47:42] <abompard> florianf: cool :-)
[15:48:20] <abompard> FYI I'm currently building packages for Fedora 21 
& RHEL 7
[15:48:20] <abompard> so I'm finding all those little oversights ;-)
[15:49:12] <florianf> abompard: That's what happens if you upload stuff 
to pypi from the airport gate...
[15:49:22] <abompard> haha :-)
[15:50:18] <florianf> abompard: But great to hear we're getting packages 
soon! A friend of mine is planning on building gentoo packages.
[15:50:28] <abompard> cool!
[15:50:54] <florianf> I wonder if someone has .deb on the radar...?
[17:56:40] <florianf> abompard: fyi: updated mailman.client tarballs on 
pypi and lp
[17:56:55] <abompard> florianf: thanks!
[18:53:34] <barry> maxking: hi!  i have a new gitified core repo that i 
think is good, but i want to blow away the one on gitlab and push this 
new one.  i couldn't find how to do that.  do you know?  if not, I’ll 
ask those folks (i should push it to staging for you to take a look)

So things are happening, meanwhile I will also file a mailman 3 wnpp 
request on the Debian BTS if somebody hasn't filed it till yet so 
hopefully somebody does take that up.

What I would suggest is to let's take it for a spin, have a different 
domain and let it mirror all the messages from the old one and see how 
it works, looks etc. If we are happy, let it replace the old one.

Also if this works out, then we will have to make at least one more 
mailing list hamara-users at lists.hamaralinux.org

Looking forward to ideas and feedback.

-- 
Regards,
Shirish Agarwal,
Community Lead,
Hamaralinux.org