Mailman 3 March 2015 - Mailman-Developers

Invitation to "adopt pytest month"
by Brianna Laugher March 19, 2015

March 19, 2015

Hello, I am a contributor to the testing library pytest, and in April we are holding "adopt pytest month". We are inviting open source projects who are interested in possibly taking up pytest, to be paired with experienced pytest users, who can help them convert and write tests, and show ways to make the most of pytest. More info here: https://pytest.org/latest/adopt.html Pytest tests typically require much less boilerplate and feel more "Pythonic" than unittest style tests, and there are … [View More]

1 0

GitHub/Development tools integration project Gsoc'15
by Prabhanshu Abhishek March 19, 2015

March 19, 2015

Hi, I am Prabhanshu Abhishek, second year undergraduate student at Indian Institute of Technology,Kanpur (IIT Kanpur), studying Computer Science and Engineering. I am very much interested in the project GitHub/Development tools integration under Gsoc'15. I have given much thought on how it can be implemented, can i get feedback on my implementation. The draft for the proposal: Creating a tool that will take a thread from a Mailman mailing list and turn it into a thread on a GitHub issue. In … [View More]short: I propose to make a user interface which will be accessible to the list administrator. If the administrator thinks that a thread or multiple threads could be an issue for his/her development organisation's repository, he/she can mark the thread for posting, and the backend will process it with the GitHub API to send it to the repository as an issue. In detail: 1) User interface: A simple webpage that will have an option to mark threads and a send_to_github button which initiates the backend process to convert the thread into a series of comments used to raise the issue. 2) Processing emails: The UI for the administrator will have an interface to edit emails so as to discard any unwanted piece of the emails (such as the reply emails containing the previous mails' conversation). The backend process will also be able to do the initial work for this on its own (as the previous mail conversation probably starts with ">"). 3) Github API: The thread's subject will be, by default, used as the main title for the issue, or the administrator can provide an alternate title. The backend will find out which other emails are to be posted as comments (as the emails header contains an "in reply to:" field). The tool will use the administrator's GitHub username as the creator of the issue. It will use OAuth2 authentication with GitHub. The issue comment will contain content of the email within the original mailing list thread. The tool will use this information to post the issue to the GitHub repository's issue tracker, using the GitHub API. Actually, the user interface can be made available to all the users subscribed to that mailing list. 4) The backend will be written in Python, which will interact with the REST API and the GitHub APIs to do all its work. I have some specific questions also, like: Should this be a standalone web interface, or should it be a plugin for HyperKitty or Postorius, or should it be a command-line tool. Hoping for some feedback on the proposal'draft. Also, I think there is no mentor specified to the project, so, i want to ask if some of you might be interested in this project. Thanks, Prabhanshu Abhishek [View Less]

1 0

Re: [Mailman-Developers] GitHub/development tools integration project Gsoc'15
by Florian Fuchs March 19, 2015

March 19, 2015

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 18.03.2015 um 16:29 schrieb Prabhanshu Abhishek: > 2)the gsoc idea page says that it is necessary to fix at least one > bug, but i have not been able to find some bug that is beginner > friendly and related to my project, can you give me some bug to > work on that will help me on my project. It doesn't have to be related to that particular project idea. If you don't find a bug in our bug trackers, it can be also be a small feature … [View More]

1 0

Dynamic Sublist Proposal Queries
by Pranjal Yadav March 19, 2015

March 19, 2015

Hello I recently submitted my proposal for Dynamic Sublists, since I haven't had much discussion on this idea with mentors it would be nice to have some reviews. I request Terri, Barry and Steve to have a look whenever they find suitable and other mentors can also help me if they wish too. There are many sections in the proposal for which I particularly need reviews like 1. Dealing with two different delimiter inside rules and I'm confused in selecting between command runners and new Dlist … [View More]

1 0

Re: [Mailman-Developers] MIME footers
by Stephen J. Turnbull March 19, 2015

March 19, 2015

Murray S. Kucherawy writes: > I had forgotten about message headers (i.e., prepended text). Are > those common? I had thought pretty much everyone uses footers > only. They're sometimes useful on lists that only get occasional distribution. I've used them in situations where I have an emergency announce list which feeds into the main ML, and the content is "This is important!" :-) I don't bother any more, and I doubt much would be lost if there were no header. The other use … [View More]

2 1

How do I turn on/off moderation of subscription requests?
by Andrew Stuart March 19, 2015

March 19, 2015

I want to be able to turn off and on the need for moderator to approve subscription requests. Would someone mind please pointing out where this is configured? thanks as

3 3

Re: [Mailman-Developers] GSOC'15: Improving styles for lists
by prakhar joshi March 19, 2015

March 19, 2015

what if we create separate tables for each class in the mailman/src/mailman/styles/base.py and store the name and their attributes in it with user_name with it. I think the attributes for the classes defined already will be fixed? So now if we feel the requirement of including new things to style (like an additional class in that file ) Then we will add new table for that also. And now the flow will be like.. the mailing list table will be same as right now. And each of the new table we will … [View More]get the attributes filled by the admin. So the list styles will be stored in that way. And we have user name also so only that user will get the styles which are created by him/her. Thanks, Prakhar Joshi DA-IICT,Gandhinagar On Thu, Mar 19, 2015 at 1:40 PM, prakhar joshi <prakhar126(a)gmail.com> wrote: > hi, > so we should have templates already created in a folder with default > values of the attributes in it. the templates will be of "BASIC OPERATION", > "BOUNCES" etc. and under each of the template we will gonna have > attributes for it and then we can apply these templates on the list and > even user can edit these templates, right ? > > One thing how these templates will be stored for the user is still a doubt > for me ? Can you please help me with that ? > > Thanks, > > Prakhar Joshi > DA-IICT,Gandhinagar > > On Thu, Mar 19, 2015 at 12:01 PM, Stephen J. Turnbull <stephen(a)xemacs.org> > wrote: > >> prakhar joshi writes: >> >> > I am thinking of storing the styles in the database by creating a >> > table for the styles in the db >> >> Mailman's databases are not relational dbs, they're object-oriented. >> Underneath the objects are stored in relational dbs and managed by an >> ORM (SQLAlchemy), of course, but the Mailman API is object-based. >> >> If you want to think of your schema in terms of tables, I don't think >> you'll have any trouble in design, but when you get to the >> implementation stage you'll have to shift gears to OODB style. >> >> > and this table will contain all the attributes of a style and these >> > entries can be null too. So a table which will contain a style name >> > with all its attributes. Now as we have table for mailing list >> > containing all the attributes in the mailing list table. So now the >> > style table will contain all these attributes and in the mailing >> > list table we will just store the mailing list name and the style >> > name and this way we can connect the two table by providing foreign >> > key of style_id to the mailing list table? >> >> I think this is probably not the best way to go. Some of the >> attributes change over time, some attributes flip back and forth, and >> so on. Some lists may have a unique combination not very useful for >> other lists/list owners. So I think a library of templates so that >> you can set many attributes at once by applying a template is a better >> way to go. Also, I suspect it would be useful to allow very incomplete >> templates so that you could apply template A to get the basic >> character, then apply template B (which is very incomplete and only >> changes two attributes) to get the effect you want. >> >> I haven't thought about it carefully, so don't just assume everything >> I wrote is right. Maybe it will be useful for refining your proposal. >> >> >> > [View Less]

1 0

GSOC '15 : Student applications start today
by Abhilash Raj March 19, 2015

March 19, 2015

GSoC Applicants, The student application period for Google Summer of Code 2015 starts from today (March 16 at 19:00 UTC). We encourage each of you to submit your proposal as soon as possible on melange, since it has been known to crash in the days near to deadline. You can edit your proposal as many times you like till the deadline. In past we have been following the application template from PSF and this year too there is no change in that front. You can find it here[1]. Remember that … [View More]

1 1

GSoC 15 - Regarding "A Dashboard for Admins/Owners/Moderators" project
by Shreyas Lakhe March 18, 2015

March 18, 2015

Hi guys, I have uploaded my proposal for the "A Dashboard for Admins/Owners/Moderators" project. Review on it are welcome. Regards, Shreyas Lakhe

1 0

Re: [Mailman-Developers] Regarding Subscriber profile pages project
by Stephen J. Turnbull March 18, 2015

March 18, 2015

Ashish Kumar writes: > 1. Use of different email addresses - so called aliases - for sending > emails: This is a good point as a user perspective. We will give user an > option to save an email address and out of the entered email address we > will ask which email address he/she want to use for sending email. I think > we can extend this feature for moderators and owners too. I don't see how you plan to do this. Picking the right alias is a MUA function, not a list … [View More]function. Please be more specific about the workflow you have in mind. "Have aliases" sounds good, but what does this mean for the user's actions and the system's responses? If you just mean multiple subscriptions under different addresses, Mailman has always allowed that (it's impossible to prevent), and made it convenient by providing a "no mail" flag for the address. > 2. Dynamic list: It is also another idea for subscribers. This is a separate project. > 3. There is also a feature about essay. The essay feature can be enabled by > the list creator when creating the list, and at the same time the list > creator can choose which questions to ask. The default when enabling this > feature are the questions used for the Systers maillist but by simply > editing the field with the questions the list creator can choose to have > other questions instead. [ Reference : Above link] I think you'll find that editing is not so simple. Users will not do this right. Many cannot handle simple formatting rules like reStructuredText or Markdown. So you will need to provide an interface that automatically numbers the questions, allows the user to insert, delete, edit, and reorder questions, and "cleans" the question (eg stripping leading and trailing whitespace) as well as allowing an optional/required setting per question. Bonus points for a device that allows the questions asked to depend on previous answers. Perhaps content length constraints (maximum for most questions, minimum for essay) per question. Image uploads (must be able to validate!!) All answers must be validated. > I have a doubt if essay feature can be part of subscriber's profile > page. Yes, it should be. Systers has been a good citizen in our community, it would be bad if we borrowed some of their ideas but didn't provide a pretty complete set of their features and they had to continue their fork just to get basic features. Barry also has dreams of making Mailman a community center that obsoletes web fora and maybe even Facebook. Even though we were just joking when we talked about that, I think these features make a lot of sense for many communities, not just Systers. Please submit a proposal on Melange, addressing most of the points above. If you're still not sure this is the project you want to do, check GSoC but I believe you're allowed to submit up to 5 proposals total and no rule against more than one to same org. If you feel very unsure about it, say so, but putting it in Melange makes it a lot easier to manage because it's a single design and plan. ML discussions without such a focus don't work well. [View Less]

2 1