Mailman 3 March 2015 - Mailman-Developers

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

20 Mar '15

prakhar joshi writes: > 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. Who are these "users" (subscribers? admins?) and why do you want to associate styles with users? Please use more descriptive terms unless you really need to describe something generic. But here IIRC the styles are for lists, and therefore the relevant users are list admins. However, why would a style be associated with a list admin? The same admin might have announce lists and discussion lists as well as anonymous lists, and so on.

2 1

GitHub/development tools integration project Gsoc'15
by Stephen J. Turnbull 20 Mar '15

20 Mar '15

Prabhanshu Abhishek writes: > but the thing i want to know is, > 1) what are the other feature you want to implement through this.other than > the mailing a thread,or pull requests. The fact that the project doesn't have a mentor listed probably means you'll need to flesh out the requirements yourself. > 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. Since this is a new feature, there probably are no directly related bugs. For "easy", some of the bugs in launchpad have an "easy" tag; you should look at those. > 3)some other necessary things that i should work upon before > submitting my proposal. Read the first four sections of the ideas page again, and read the references there, especially "How to SPAM". > 4)and lastly who will be my mentor, can you tell me? I don't know; perhaps the person who suggested this project will step forward in a few hours.

2 2

Invitation to "adopt pytest month"
by Stephen J. Turnbull 20 Mar '15

20 Mar '15

This is spam. Don't do it without checking with the list owner (coursemailman-developers-owner(a)python.org) first. Brianna Laugher writes: [spam deleted]

1 0

GitHub/Development tools integration project Gsoc'15
by Stephen J. Turnbull 20 Mar '15

20 Mar '15

Please don't repost material you've already mostly posted. Just put your proposal in Melange and we'll get to it. Unless you're getting close to your limit of 5 (or whatever, that was the limit last year), in which case you should ask the GSoC staffers how to withdraw proposals you aren't going to implement. See also "Use of the mailing list during the application period" which I just posted to this list. Prabhanshu Abhishek writes: > I have given much thought on how it can be implemented, can i get feedback > on my implementation. The draft for the proposal: Note that some of this actually concerns requirements, and that would be appropriate for the ML. But I don't have time to disentangle that.

1 0

Message threading - requesting some wisdom
by Andrew Stuart 20 Mar '15

20 Mar '15

Hi folks I assume a great deal of thought has gone into message threading and how it works. Is there anyone willing to share the basics with me - specifically as it relates to Mailman and related projects? There is of course plenty of information on google which I am researching including the seminal http://www.jwz.org/doc/threading.html but if there is anyone on the Mailman team willing to give me a Mailman oriented understanding that would be great. It appears to me there are a number of ways to implement threading, and how it is done is somewhat arbitrary. For example, this description of Gmail threading http://xkahn.zoned.net/software/evolution/threads/ seems to suggest that Gmail includes arbitrary business rules for threading based on message content (i.e. subject prefix). In particular I want to know the basics of message threading - i.e. ** What data defines how emails are connected to one another? ** How is that connecting data organised (i.e. in a tree, a flat list, by date, whatever)? ** What happens when thread data is missing (i.e. a message in a thread is deleted)? ** Are there any algorithms/mechanisms/patterns that are effective for implementing threading? ** Any code in Mailman/Hyperkitty/elsewhere that is particularly good to study? ** Anything else I should know? I’m wanting to find the most simple and effective way to deal with threading which of course has the potential to be complex if I get it wrong. thanks! as

2 1

Use of the mailing list during the application period
by Stephen J. Turnbull 20 Mar '15

20 Mar '15

Hi! First, let me thank you all for your applications. I was a little worried when were approved as an org ourselves, but we've got a bunch of good ideas and nicely done applications here, so we aren't going to have trouble filling our slots, I think. Second, I don't necessarily speak for the other mentors, but I have a reasonably good track record in channeling Barry and Mark and Terri at least. So judge for yourself if my "rules of the list" make sense for you. Now, to the main topic. As I see it, you should use the mailing lists: 1. *Before* you have filed an application at all. (However, at this point I would suggest filing *something*. Remember, we can't accept any student who is unknown to Melange no matter how much he or she contributes on the list. We will make the decision based on what's on Melange at the deadline, and you can edit until then.) 2. If Melange is unavailable. 3. For asking about requirements. What is it that Mailman doesn't do that it should? What do subscribers, moderators, list owners and site admins want it to do? What does it do that is annoying and should stop, or should be optional? Of course your opinions are relevant, but in the end if you're the only user, you can fork and be happy. So the lists are where you'll get opinions from real users, and know what will benefit the whole community. 4. For communicating with others about parts of Mailman *not* directly related to your project, such as installation, testing, use of the VCS, how to write schedules, etc. 5. To poke the mentors when they really seem to be asleep (no activity for 36-48 hours). 6. (Maybe) To announce that your initial proposal has been posted. But see #1 under "should not". 7. To announce "important" updates to your *blog* that may be of general interest. For example, you could post your proposal there for non-mentors to see (I don't necessarily recommend that, see #2 below). You should *not* use the mailing lists, but rather use Melange: 1. To announce updates to your proposal. Mentors will get pings from Melange about changes to your proposal, and should be looking frequently anyway. Other participants in the mailing list have no need to know and probably don't care to know. And I'm really busy and getting a ton of mail right now, and so are several other mentors. There's a good chance that anything on the list will get dropped on the floor if I don't address it right away. I will be looking at all Mailman proposals (as well as some PSF and Systers proposals) daily in any case. 2. To ask about design and scheduling issues. There are two reasons for this. First, most of you are concentrated on two or three projects, and so are competing with each other. Personally, I give extra points to people who openly discuss their ideas in the spirit of "may the best proposal win", but realistically, you may not want to depend on that, and keep your proposal between you and the mentors until acceptance decisions are made. Second, this is the same division of responsibility as between MLs and issue trackers. If you post to the ML and a mentor replies there, both the question and the answer stand a fair chance of getting dropped on the floor and not helping to improve your proposal. If the Q & A take place in comments on the proposal, or even in the proposal itself, points that didn't get addressed early on will be right there for your later review, etc. Hope this helps. Steve

1 0

GSoC 2015 Introduction
by Ana Badescu 20 Mar '15

20 Mar '15

Hello, I'm Ana Badescu, and I'm a first year Artificial Intelligence graduate at Polytechnic University of Bucharest, Faculty of Automatic Control and Computer Science, looking to participate in GSOC 2015, hopefully with Mailman! You might believe that I arrived late. However, I have just installed the mailman client, mailman core and the Postorius and got them up and running in their own env. Can't believe how straight-forward it was! Once I'm done reading the contribution guides, I'll pick a few bugs to get a better idea of how the codebase is structured. As this is my first GSoC try, I admit I was a bit at a loss facing the huge diversity of organisations and projects. Honestly, there are three reasons that I chose Mailman over: - it involves areas that I am familiar with and I enjoy working on (Python) - I started looking at the organisation list and project list on day one. At least in my opinion, Mailman has one of the most friendly getting-started guides out there. - I found the Javascript client project being interesting to me. I do have quite a lot of experience with node.js, enough to say there is a love-hate relationship when it comes down to using it in projects. I'm actually doing my graduation thesis in node. I think it's great idea to get a Javascript client going, it will be well received by the community as there are a lot of devs that work solely with js and maybe a few frontend technologies. Kind of sad but true. I've also set up a number of RESTful interfaces before, specially in hackathons where the team members are each using different technologies. I have mentioned this because I am definitely willing to learn and work, but I'm trying my best not to do this in the wrong direction. This project is the one that interests me the most, any advice on what should I do after getting a few patches in? Should I get a small working client going? Could you please advice me regarding this matter? Thank you, Ana

1 0

Re: [Mailman-Developers] MIME footers
by Stephen J. Turnbull 20 Mar '15

20 Mar '15

Murray S. Kucherawy writes: > The difference between this idea and "l=" is that there's still a > signature covering the added part, that of the MLM. No, there isn't, not when it leaves the poster's MTA. This is the same for your proposal and for "l=". People have learned to deal with top-posting, they could have learned to deal with adding all new content at the end, too. But they haven't. > By contrast, "l=" leaves the appended bit unsigned. But it need not. The MLM (or its MTA) can sign the whole message on the way out. So this too is the same for your proposal and for "l=". > This scheme does sign individual parts as well, OK. As long as individual parts are signed, we can have a way to get at the trust-per-part issue, and MUAs and Mediators have a way to partially quote preserving upstream signatures (although the granularity of the trimming is awfully coarse!) Steve

1 0

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

20 Mar '15

prakhar joshi writes: > One thing how these templates will be stored for the user is still a doubt > for me ? Can you please help me with that ? Not until late next week. I haven't thought about the problem at all. Anyway, designing the implementation is really your job. Here's how I would go about thinking about it. First, let's try to reuse existing structure in Mailman. What's most similar to a template for a list? Probably a list. So consider using the same structure. Next question is whether a template should be a list with inputs to things like list name disabled, or whether the list record/object should be refactored into a template copy plus list-specific components like name and membership list. Next problem for you is to find where the list object is defined, and find out what all is in there. Regards,

1 0

Re: [Mailman-Developers] Invitation to "adopt pytest month"
by Andrew Stuart 19 Mar '15

19 Mar '15

I’m working on a large project closely related to Mailman and I use pietist currently for my 700 tests. On 20 Mar 2015, at 8:57 am, Brianna Laugher <brianna.laugher(a)gmail.com> wrote: 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 also 100+ plugins available, as well as many API hooks for writing your own customisations. (Although, it can run unittest style tests by default, as well as nose and doctests.) So... we think it's pretty cool and have lots of volunteers eager to help spread the love. This is a bit of a cold call email, so please excuse me for butting in. It looks like everyone is quite busy preparing 3.0 and GSOC. However if there is someone who would be interested in working with a pytest volunteer on this...please let me know/sign up! Thanks, Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/ _______________________________________________ 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/andrew.stuart%40… Security Policy: http://wiki.list.org/x/QIA9

1 0