[Mailman-Developers] [Mailman-Developters] GSoC support

[Abhilash Raj]

Hi,

Please try to always include -developers list in all discussions related
to GSoC, unless it is something very personal that you want to ask or
discuss with the mentors.

Second, try to use formal English for all communications on this channel
(First letter capital). It is important that you learn that very first
before we go down working on the problems related to programming.

On 03/06/2016 12:19 AM, amil shanaka wrote:
> Hi,
> thank you for your reply. other than that can we use any open source
> packages like netty and what prototype do we need to implement regarding
> pub/sub .. MQTT or AMQP ? 

The idea is to make a common interface that can use any messaging
back-end that does the Job. I guess MQTT is meant for high latency and
unreliable network, not much of our use case, so AMQP should be more
relevant. However, I am not very aware about the current trends in the
message passing and pub/sub models out there right now.

It would be your job to choose the framework that you think is best for
the purpose, after you have clearly define the *purpose*. And the
explain why you chose it over other alternatives.

> Thank you,
> amil
> 
> On 6 March 2016 at 02:20, Abhilash Raj <raj.abhilash1 at gmail.com
> <mailto:raj.abhilash1 at gmail.com>> wrote:
> 
>     Hi Amil,
> 
>     On 03/05/2016 03:22 AM, amil shanaka wrote:
>     > Hi,
>     > I'm a 3rd year under graduate in the department of Computer Science and
>     > Engineering at University of Moratuwa, Sri Lanka
>     >
>     > I tried to connect with mailing list in Mainman but it doesn't work.
>     >
>     > I did my Internship In WSO2 Message Broker Team. so i learned  about
>     > MQTT(with netty) and AMQP protocols about how message broker work with
>     > sub/pub with topic,durable topics and also i did a research about off-heap
>     > implementation for mb.
>     >
>     > So I want to know more details regarding* Message queue based email
>     > archiver *Project which i can proceed through.
> 
>     Right now, Mailman sends each email it receives to the (enabled)
>     Archivers through a POST request. We want to have a pub/sub kind of
>     model for the emails as well as some of the events that other archivers
>     or apps built on top of mailman can consume. Events like ListCreated,
>     ListRemoved or something like that.
> 
>     The above is just a very basic idea of what we want. You need to focus
>     your application around how we can do this. Florian and Aurelien would
>     be able to help you better if you come up with some ideas. You might
>     want to go through the current codebase for Mailman, looking for the
>     parts of code that are concerned with Archivers. A general idea about
>     the complete architecture would also be a good idea.
> 
>     There are several design documentation about the architecture of Mailman
>     3 core. You can find article in the mailman3 docs, there is a chapter in
>     Architecture of Open Source Applications book v2 and also there is a
>     talk that Barry gave in PyCon 2012.
> 
>     Just as a reminder, you need to submit atleast one merge request fixing
>     any of the issues mentioned in the bug tracker of any mailman projects.
> 
>     Let us know if you have more questions.
> 
> 
>     >
>     > Please Refer My LinkedIn: (amil shanaka
>     > <https://lk.linkedin.com/in/amilshanaka>) for more detail about me
>     and the
>     > projects I've done so far.
>     >
>     > Hope you will help me with this.
>     >
>     > Thanks,
>     >
> 
>     --
>     thanks,
>     Abhilash Raj
> 
> 
> 
> 
> -- 
> 
> *Amil shanaka*
> 
> *Integrated Computer Engineering | University Of Moratuwa*
> 
> mobile : (+94)* **718548973 *|  email : *catchamil at gmail.com*
> <mailto:catchamil at gmail.com> | *amil.12 at cse.mrt.ac.lk
> <mailto:amil.12 at cse.mrt.ac.lk>*
> 
> skype  : *amilshanaka*
> 

-- 
thanks,
Abhilash Raj