Mailman 3 March 2016 - Mailman-Developers

Willing to contribute to GitLab/development tools integration project in GSoC
by Stephen J. Turnbull 25 Mar '16

25 Mar '16

翁学平 writes: > I have sent this email for serval days before, but have not received any > response for this, I sent a response, addressed to you and to the list, so you should have received two copies. Try your spam folder. Here it is again: For project details, you should check the archives of mailman-developers for the last 2 months. Both have been mentioned frequently, and the list template project in some detail. If you have not registered with summerofcode.withgoogle.com and submitted a proposal, I advise you to do something quickly. While I do not expect it to crash, that has happened in the past, and Google has never extended the application period due to system problems. It is also much easier to give you help if you provide us with a document that we can read and comment on. Don't forget to enable comments on the document. As far as I know only mentors can see it, so globally enabling comments should be safe. Steve

3 3

Interest in "Implement module to process ARC headers" project GSoc
by nitish salwan 24 Mar '16

24 Mar '16

Hello, I am interested in ARC headers project and want to discuss about it . I know that this is late but If stephan or anybody can help me then please respond. Thank you, Regards, Nitish Salwan

1 0

REVIEW NEEDED: Mailman and Discourse Integration
by Stephen J. Turnbull 24 Mar '16

24 Mar '16

Ojas Shirekar writes: > I have officially submitted a proposal for GSoC for this feature as > this is something I really found interesting and felt like doing. > Please take a look and do let me know OK, it's visible under the Mailman project. I only had time to make a couple of comments, sorry. It's not something I can mentor in any case, perhaps someone else will pick itup and give you some additional help. Steve

1 0

GitLab/development tools integration GSoC Participaring
by Stephen J. Turnbull 24 Mar '16

24 Mar '16

Nosikov Konstantin writes: > Hello, I am from Russia, Saints Petersbutg, ITMO University > I am interested in Mailman project Welcome! > GitLab/development tools integration > What do I need to do to get started? Is there any special points in > proposal to be mentioned? I'm not going to be mentoring the project and don't have a grasp of requirements, but I can offer the following generic advice. For project details, you should check the archives of mailman-developers for the last 2 months. It has been mentioned frequently. If you have not registered with summerofcode.withgoogle.com and submitted a proposal, I advise you to do something quickly. While I do not expect it to crash, that has happened in the past, and Google has never extended the application period due to system problems. It is also much easier to give you help if you provide us with a document that we can read and comment on. Don't forget to enable comments on the document. As far as I know only mentors can see it, so globally enabling comments should be safe. Steve

1 0

Mailman and Discourse Integration
by Ojas Shirekar 24 Mar '16

24 Mar '16

Hello, Although really late, it would be greatly appreciated if someone can help me with the proposal for Mailman and Discourse integration. I am reading up on the Discourse API and would love some help and suggestions. Ojas Shirekar > On 24-Mar-2016, at 12:25 PM, Ojas Shirekar <oshirekar(a)hotmail.com> wrote: > > Hello, > > I have officially submitted a proposal for GSoC for this feature as this is something I really found interesting and felt like doing. > Please take a look and do let me know > > Ojas Shirekar > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > https://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/oshirekar%40hotm… > > Security Policy: http://wiki.list.org/x/QIA9

1 0

Willing to contribute to GitLab/development tools integration project in GSoC
by Stephen J. Turnbull 24 Mar '16

24 Mar '16

翁学平 writes: > I have sent this email for serval days before, but have not received any > response for this, I sent a response, addressed to you and to the list, so you should have received two copies. Try your spam folder. Here it is again: For project details, you should check the archives of mailman-developers for the last 2 months. Both have been mentioned frequently, and the list template project in some detail. If you have not registered with summerofcode.withgoogle.com and submitted a proposal, I advise you to do something quickly. While I do not expect it to crash, that has happened in the past, and Google has never extended the application period due to system problems. It is also much easier to give you help if you provide us with a document that we can read and comment on. Don't forget to enable comments on the document. As far as I know only mentors can see it, so globally enabling comments should be safe. Steve

1 0

Mailman and Discourse Integration
by Ojas Shirekar 24 Mar '16

24 Mar '16

Hello, I have officially submitted a proposal for GSoC for this feature as this is something I really found interesting and felt like doing. Please take a look and do let me know Ojas Shirekar

1 0

GitLab/development tools integration GSoC Participaring
by Nosikov Konstantin 23 Mar '16

23 Mar '16

Hello, I am from Russia, Saints Petersbutg, ITMO University I am interested in Mailman project GitLab/development tools integration What do I need to do to get started? Is there any special points in proposal to be mentioned? Best regards, Konstantin

1 0

(no subject)
by jdanielfandino＠gmail.com 23 Mar '16

23 Mar '16

Hello, This mail is to introduce myself. My name is Jose Daniel Fandiño, I study Computer and Systems Engenieering at the University of Los Andes and I am courrently coursing my 4th semester (2nd year). I have experience with Java, REST services in Java, HTML, CSS, JS, AngularJS, basicly for University assignments. I’m also interested in competitive programming (in Java). I learned Python by my own and I am fairly new to it but I found it easy to understand. About the ideas for Mailman, I read the propoused ones and found interesting the Preset list settings templates one really interesting. It is also very important because lists may have different purposes, so having different styles with different functionalities may be really useful for the users. I know it is a bit late for the deadline, but still I would like to keep up to date with this Project (Mailman in general) and even if I’m not selected I would love to contribute to Mailman with everything I can from now on, specially because this is my first aproach to open source contribution (but still I do have experience with github and team development, mainly for academic purpouses). Thank you for your attention, I’ll be attentive to the community.

1 0

Re: [Mailman-Developers] Discussion On Project Idea "Preset List Settings Templates" .
by Harshit Bansal 23 Mar '16

23 Mar '16

Hi Barry, >The point of this break down is because some things (and it's not a perfect >separation) really won't be shared between mailing lists. OTOH, you might >want site-wide bounce settings that all lists will inherit and shouldn't be >able to change. Other sub-styles give the list its "flavor", i.e. an open >discussion list where anyone can join just by confirming their email, or a >one-way announcement list that can't be unsubscribed from because it's an >"all-employees" roster. I already had this idea in my mind and that's why I have divided all the styleable attributes into three categories: 1: Site owner level attributes. 2: Domain owner level attributes. 3: List owner level attributes. Suppose attributes related to bounce-settings come into site owner level attributes(I have not yet decided which attribute will fall in which category) then only site-owners would be able to set them and once these are set, the list owners would be having only two options. Either apply the existing style as it is or create a sub-style and adjust the list owner level(not site-owner level) attributes(to give their list "flavor") and then apply it. This way they would be able to make their list an "open discussion list" or an "one-way announcement list" without being able to edit the bounce-settings. Regards, Harshit Bansal.

1 0