Mailman 3 March 2015 - Mailman-Developers

GSoC 15 - Interested in contributing to Postorius
by Akshay Shah 23 Mar '15

23 Mar '15

Hi My name is Akshay Shah. I'm currently pursuing my undergraduate degree at PES University, Bangalore (India). I have 2 years of experience with python and 3 years of experience with Javascript and HTML. I am interested in contributing to the Postorius Web UI. Some of the ideas on the 'Ideas Page' took my interest. More specifically, the Dashboard for admins/owners/moderators, Mailman client written in Javascript and the subscriber-profile pages. Regarding these, I have the following questions: 1. Can the Dashboard and Subscriber profile page be done together within the GSoC timeline? Is there any way that I can display my ability to pursue both of these? 2. I have fairly good amount of experience with NodeJs, will my resume be a good enough factor for you to decide or would you rather have me do a pre-project (I would love to do a pre-project)? 3. [NEW IDEA] Introducing search feature in the Web UI. Search lists, members, settings, and/or domains. Would introduction of Elastic Search with NodeJs be a feasible option for the GSoC Timeline? How detailed should I get about introduction of this topic? Sincerely Akshay

1 0

GSoC 15 - Interested in contributing to Postorius
by Akshay Shah 23 Mar '15

23 Mar '15

Hi My name is Akshay Shah. I'm currently pursuing my undergraduate degree at PES University, Bangalore (India). I have 2 years of experience with python and 3 years of experience with Javascript and HTML. I am interested in contributing to the Postorius Web UI. Some of the ideas on the 'Ideas Page' took my interest. More specifically, the Dashboard for admins/owners/moderators, Mailman client written in Javascript and the subscriber-profile pages. Regarding these, I have the following questions: 1. Can the Dashboard and Subscriber profile page be done together within the GSoC timeline? Is there any way that I can display my ability to pursue both of these? 2. I have fairly good amount of experience with NodeJs, will my resume be a good enough factor for you to decide or would you rather have me do a pre-project (I would love to do a pre-project)? 3. [NEW IDEA] Introducing search feature in the Web UI. Search lists, members, settings, and/or domains. Would introduction of Elastic Search with NodeJs be a feasible option for the GSoC Timeline? How detailed should I get about introduction of this topic? Sincerely Akshay

1 0

Re: [Mailman-Developers] How do I turn on/off moderation of subscription requests?
by Aurelien Bompard 23 Mar '15

23 Mar '15

> > Nope. It needs to be hooked up. The branch wasn't merged because it was > > incomplete. Oh, and the _send_confirmation method is also not implemented. Could you briefly explain how does the confirmation system work? (or point me to the doc, I didn't find it) Thanks Aurélien

1 0

Re: [Mailman-Developers] How do I turn on/off moderation of subscription requests?
by Barry Warsaw 23 Mar '15

23 Mar '15

On Mar 23, 2015, at 12:17 PM, Aurelien Bompard wrote: >But there's something else: the SubscriptionWorkflow class does not seem to >be used anywhere except in the current unit test. Am I missing something ? Nope. It needs to be hooked up. The branch wasn't merged because it was incomplete. Cheers, -Barry

2 1

Re: [Mailman-Developers] How do I turn on/off moderation of subscription requests?
by Barry Warsaw 23 Mar '15

23 Mar '15

On Mar 21, 2015, at 10:50 AM, Aurelien Bompard wrote: >Hmm, could you point me to this Dia file please, I can't find it. Thanks! Oops. Looks like I'd forgotten to push them. They should now be available in lp:~barry/mailman/subpolicy Cheers, -Barry

2 1

GSoC 15 - Interested in contributing to Hyperkitty
by David Udelson 22 Mar '15

22 Mar '15

Hello, My name is David Udelson. I am a freshman Computer Science undergraduate at Cornell University. I have 3 years of experience with python under my belt, but I've never contributed to an open source project because I've never known where to begin. I'm hoping GSoC will provide me with that starting point, as well as an opportunity to make some meaningful contributions to the open source community. I'm interested in contributing to the Hyperkitty archiver. Specifically, it looks like some requested features for Hyperkitty include rss syndication for entire mailing lists/specific users/specific threads, and the ability to view entire threads as plaintext and download that plaintext. I have the following questions regarding these features: 1) Are these features definitely expected to be in future releases, or are they just "nice-to-haves"? If there are more important/pressing issues that the Hyperkitty devs think I could implement instead, I would prefer to work on those. 2) Are both of these features implementable within the GSoC timeline, or should I only pursue one of them? Thanks, David

1 0

GSOC 2015 :Mailman Client written in Javascript
by Abhishek Kumar 21 Mar '15

21 Mar '15

Hi, I am Abhishek (irc: abhishek17) and i have submitted my proposal on the melange. Please provide your valuable feedback and suggestions to improve it..! -- Thanks, Abhishek Kumar CSE, IIIT Hyderabad

1 0

GSOC'15
by prakhar joshi 21 Mar '15

21 Mar '15

hi, I am prakhar (pjoshi) . I have submitted my proposal on melenge site. Hoping for feedback. thanks, Prakhar Joshi DA-IICT,Gandhinagar

1 0

Re: [Mailman-Developers] GSOC'15: Improving styles for lists
by Stephen J. Turnbull 21 Mar '15

21 Mar '15

I think we're pretty much in agreement on most things. Please update your proposal on melange to reflect this discussion. (The quoting has gotten too fragmented to be very useful in understanding what progress has been made.)

2 1

Re: [Mailman-Developers] GSOC'15: Improving styles for lists
by Stephen J. Turnbull 21 Mar '15

21 Mar '15

prakhar joshi writes: > So you want to store only changed attributes under a specific list > style in the table ? Isn't that make the table dynamic in width as > sometimes only one attribute is stored and sometimes 3-4 attributes > are stored ? That's a feature of object-relational managers (ORM) like SQLAlchemy. In the background there will be a special value in the backing RDBMS such as 'inherit' or perhaps NULL. But NULL is risky because it has assorted interpretations. > By extensibility you mean to add new attributes ? Attributes. > or add new class as there are few classes in the > mailman/src/mailma/styles/base.py (but that can't be possible > through web interface, I guess? ) Anything's possible, but Zope's experience with that level of through-the-web extensibility was pretty bad. We don't need it. > > { name: <list specific>, read-only: no, notmetoo_default: no } > > { name: anonymous_overlay, read-only: yes, redact_all_addresses: yes } > > { name: discussion, read-only: yes, <usual discussion list options ...> } > > > > If there are more than 1 attributes in the last section of above list style > configuration then the list table will not have the same width ? I'm not sure what you're asking. Tables have to have the same width by definition. You use NULLs or other special values to simulate absence of a value, or a table join with optional attributes in a separate table. Object-oriented DBs can have different attributes for each object. > unspecified attributes ? You mean attributes other than that of mailing > list table ? No, I mean the attributes I was too lazy to write in the schematic example above. > I think we are still not on same page for list style storage as > still there are few things that I have in my mind like admin can't > create its own new attribute, he/she can just change the value of > the attribute, right ? Probably. What I had in mind was that site admins could add new Handlers that define attributes that aren't in the standard set, or somebody could want to import a style from a later version of Mailman that has such attributes. > And if that is true(admin can't add new attributes) than how can we > just store only changed/modified attributes in the styles table as > than the table will not have same width, lets assume for style A we > will store one attributes and for style B we will store two/more > attribute. To create attributes on the fly is easy, even in RDBMS. You have a table user_defined_attributes with columns foreign_key, attribute_id, and attribute_value. Then do a select on the foreign key. > Basically the style table will be copy of mailing list table and > will have same number of column same as mailing list table with one > more column about permission (read_only or editable). You need to be more careful about this. I'm not sure exactly how this is implemented in Mailman 3, but a mailing list has attributes (such as the owner and the moderator list) that are not relevant to styles. There is going to be a question of whether to refactor the list schema into a "stylable" part and a "list-specific" part (so that the stylable part is literally a copy of the style) or to copy the individual attributes from styles to the list configuration.

2 1