Mailman 3 August 2012 - Mailman-Developers

Re: [Mailman-Developers] [GSoC 2012] HyperKitty
by Aamir Khan 14 Aug '12

14 Aug '12

Hi! We have reached the end of GSoC. I have pushed all the code to bzr repo. There are tworepositories, one is django application [1] and other one is django standalone project [2]. It's almost the same way postorius manages it's code in two separate repositories. I never worked with django before GSoC. It was one of the greatest learning experience for me. I learnt a lot about Django. When GSoC started the code of HyperKitty was very raw and many things were hard coded (urls) and there was no clear code structure. During my GSoC project I have implemented features in HyperKitty as well as tried to fix these problems. We now have a clear code structure, app is separate from project, urls are not hard coded, unit tests are there in place. Though, HyperKitty is a big project and we are not close to any release candidate yet, there are essential features missing from HyperKitty for example we have to connect it to MM3, plug KittyStore to MM3, cleaner UI. As always you can check the demo here [3]. (We are aware of the issue that it throws 500 errors a lot of times :( ) I would like to thank pingou, toshio and the rest of Mailman community for their help. As my school year had started I won't be able to work full time on this project but I will keep pushing changes to HyperKitty when I will have free time. [1]: bzr.fedorahosted.org/bzr/hyperkitty/hyperkitty [2]: http://bzr.fedorahosted.org/bzr/hyperkitty/hk-app [3]: mm3test.fedoraproject.org On Sun, Jul 8, 2012 at 5:22 AM, Aamir Khan <syst3m.w0rm(a)gmail.com> wrote: > Hi, > > It has been some time since the last update about HyperKitty. I have > deployed[1] the latest code at mm3test.fedoraproject.org for everyone to > take a look. Please file any bugs/missing features here[2] > > HyperKitty offer features like upvoting/downvoting of messages, adding > tags (to be implemented soon!) to threads, user profiles and other user > specific features. We require users to be logged in before using any of > these features. So, the first task for my GSoC project was to implement > login procedure for hyperkitty. It uses django-social-auth application [3] > to implement login functionality. Currently, there are four ways of logging > into hyperkitty test server namely, Google openid, yahoo openid, browserid, > and registering the user on the site itself. I have not enabled other ways > of logging in (e.g, twitter) but it should be fairly easy to enable those. > > I have written a blog post about the essential features an archiver should > posses[4] in my opinion. The second most important thing for me is the > ability to promote good content posted on the list. An archiver should be > intelligent enough to suppress the "spamy" content and bring good content > on the surface. For this we have implemented a feature in which a user can > upvote/downvote a message. The users accessing a particular thread will be > able to sort the messages based on votes of other users. > > I have also implemented the basic user profiles in which you can see your > personal info and the messages you rated. You will be able to edit the user > profiles soon. > > I have also started to write unit tests [5]. > > > Best regards, > Aamir > > > [1] > http://blog.aamirkhan.co.in/post/26723715431/deploying-hyperkitty-using-apa… > [2] https://fedorahosted.org/hyperkitty/ > [3] https://github.com/omab/django-social-auth > [4] > http://blog.aamirkhan.co.in/post/26555164201/hyperkitty-modern-archiver > [5] http://blog.aamirkhan.co.in/post/26723628968/unit-testing-hyperkitty > -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee

1 0

Re: [Mailman-Developers] [GSoC 2012] Metrics
by George Chatzisofroniou 13 Aug '12

13 Aug '12

Hello, This is probably my last report. Any comments about the project are very appreciated. :) ---- GSoC is almost over and i just pushed all the work i’ve done these three months. It was one of the greatest experiences and i’ve learned a ton of stuff. I feel proud of my work and i can’t wait to see it used in Mailman working environments. For those who don’t know what is all about, a live demo of the app exists here [1]. The code is hosted in Launchpad [2] and if you are interested to learn more, i would suggest you start reading the documentation, from the installation [3], to metrics collector [4] and metrics display [5]. To learn even more about the functionality of the app, please check the tests that lie in the ‘test app’ directory for each submodule. I would like to thank Wacky (a great mentor) and the rest of Mailman developers for their help. Mailman has a great community and of course i’ll stay here for anything regarding improvements of my app or anything else Mailman-related. [1]: http://sophron.latthi.com/metrics/ [2]: https://code.launchpad.net/~sophron/mm3-metrics/trunk [3]: http://bazaar.launchpad.net/~sophron/mm3-metrics/trunk/view/head:/installat… [4]: http://bazaar.launchpad.net/~sophron/mm3-metrics/trunk/view/head:/MM3_metri… [5]: http://bazaar.launchpad.net/~sophron/mm3-metrics/trunk/view/head:/MM3_metri… ---- -- George Chatzisofroniou sophron.latthi.com

1 0

Re: [Mailman-Developers] Implementing the IArchiver
by Barry Warsaw 06 Aug '12

06 Aug '12

Hi George, On Jul 20, 2012, at 02:45 PM, George Chatzisofroniou wrote: >For my metrics app (GSoC project), I'm currently using a MM3 simulator >for testing purposes. Proceeding with the development, i think it's >time to implement a connection with a real MM3 environment. > >For the current version of the app, the only information i need is who >posted what to which list on what date. So, as we have already >discussed, the IArchiver should be the origin of the interface. > >But i know nothing on how to implement this. How will i add my app to >the active IA modules? Is there any code that extends the IArchiver >and will help me understand how it works? (I guess HK extends it to >inject the messages into the archiver.) There isn't too much boilerplate you need to write in order to implement IArchiver, or any interface. You can look at the existing implementations in src/mailman/archiving/*.py for examples, but I'll briefly outline what you need here. from zope.interface import implementer from mailman.interfaces.archiver import IArchiver @implementer(IArchiver) class MyArchiver: """This is the docstring.""" name = 'myarchiver' @staticmethod def list_url(mlist): """See `IArchiver`.""" # do something @staticmethod def permalink(mlist, msg): """See `IArchiver`.""" # do something @staticmethod def archive_message(mlist, message): """See `IArchiver`.""" # do something You probably only care about archive_message(). For methods list_url() and permalink() which you don't care about, you can just `raise NotImplemented`. That's about it! Of course the details of archive_message() are up to you. Cheers, -Barry

2 1

MM3 - preventing command summary by email
by Robert Niederreiter 03 Aug '12

03 Aug '12

Hi, Is there a way to disable command summary sent by mail? e.g. after subscription and subscription confirmation. Thanks, Robert -- Robert Niederreiter Squarewave Computing Aflingerstraße 19 A-6176 Völs Tel: +43 699 160 20 192 Web: http://www.squarewave.at

2 1

Event notifications
by George Chatzisofroniou 02 Aug '12

02 Aug '12

Hello everyone, There is a mechanism that is not in place yet and thus some features of my metrics app can't be used. I would like to mention it as feature request. Of' course i'd like to help on its implementation. It looks like the only notification the core provides is that of new postings (through the IArchiver interface). It would be great if core could provide notifications for more events (like someone subscribed or a new thread started) that also carry more information (for postings: number of recipients and message size). I think most of this information would be helpful for other plugins (like HyperKitty) as well. So, what i suggest is basically a message bus that components can register for notifications. I'm not sure if this has been discussed before and is already in the plans. Thanks for your time, -- George Chatzisofroniou sophron.latthi.com

1 0