Mailman-Developers April 2015

mailman-developers@python.org

22 participants
54 discussions

Regarding Csv Export for list owner in postorius
by Ashish Kumar 16 Apr '15

16 Apr '15

Hi Everyone, Recently My branch for feature request of csv export option for list owner to get the members of a list got merged. I was thinking of extending this feature request to pdf and sharing the list of members on drive, as It will be very helpful for communities which have a lot of volunteers, organizers. Scenario: Suppose a team of volunteers working in a country/state like bloodconnect in india. For an activity like camps [in case of blood connect], Owner need to send a pdf of all the volunteers working in a specific area to the area head either by drive or mail. It would be very convenient if we provide these option as a UI in postorius itself. Thanks Ashish Kumar

1 0

Re: [Mailman-Developers] Mailman3 Suite in Docker! (Also: probably decent recipe for ubuntu 14.04)
by Terri Oda 16 Apr '15

16 Apr '15

Oh, right. Change 'source' to '.' I did that last night but apparently didn't update the wiki. And it's a wiki, you can update it without needing pull requests :) On April 16, 2015 1:35:41 AM EDT, Pranjal Mittal <mittalp(a)onid.oregonstate.edu> wrote: >Hi Terri, > >There seems to be an issue in the step that activates the venv in the >Dockerfile i.e.: >RUN source venv/bin/activate > >Here is the last part of from my docker build logs which shows the >error: >http://dpaste.com/2PG8THT > >The error happens because while building the docker image the default >shell >used is not bash. /bin/sh need not be bash which makes the source >command >fail (because it will only work in bash). > >I have updated the docker file which should fix this issue: >http://dpaste.com/0ZGFR51 > >I can help with docker integration but keeping a little busy with >catching >up on academics after Pycon; will work on it from next week. Can we add >this file to some github repo to be able to send PR's, etc >conveniently? > > >Thanks, >- Pranjal > >On Wed, Apr 15, 2015 at 8:14 PM, Terri Oda <terri(a)toybox.ca> wrote: > >> Hey all, >> >> I've got a Dockerfile up here for those of you who might want to try >> dumping Mailman3 suite into a container and watching it go: >> >> >http://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile >> >> This gets everything running with some default configs, and I can >tell >> that it at least gets the websites up inside the container. >> >> (If you do a little mental translation, you can use those same >> instructions to set up on a fresh Ubuntu 14.04 install, I presume.) >> >> The problem is that I'm both very tired after PyCon+sprints and very >new >> to Docker, and I don't know what instructions I need for people to >run that >> and wire the ports up so you can connect to postorius and hyperkitty >on >> your local machine. >> >> Can anyone help with that? >> >> Terri >> >> _______________________________________________ >> 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/mittal.pranjal%40gmail.com >> >> Security Policy: http://wiki.list.org/x/QIA9 >>

1 0

Mailman3 Suite in Docker! (Also: probably decent recipe for ubuntu 14.04)
by Terri Oda 15 Apr '15

15 Apr '15

Hey all, I've got a Dockerfile up here for those of you who might want to try dumping Mailman3 suite into a container and watching it go: http://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile This gets everything running with some default configs, and I can tell that it at least gets the websites up inside the container. (If you do a little mental translation, you can use those same instructions to set up on a fresh Ubuntu 14.04 install, I presume.) The problem is that I'm both very tired after PyCon+sprints and very new to Docker, and I don't know what instructions I need for people to run that and wire the ports up so you can connect to postorius and hyperkitty on your local machine. Can anyone help with that? Terri

1 0

Help us release Mailman suite 3.0 tomorrow
by Sumana Harihareswara 15 Apr '15

15 Apr '15

Hello from Montreal (PyCon sprints, day 3). You've probably seen a flurry of updates to Mailman core, Postorius, HyperKitty, and even the client and bundler. We've finished all the must-have changes in HyperKitty, we've improved subscriber address options in Postorius, and we're nearly done with the new subscription policy. But we still have to test the installation more -- and we'd love your help doing that. And we're not 100% done with the subscription policy work, and we need to write release notes and update installation HOWTOs. You can help! Try to reproduce: * https://bugs.launchpad.net/postorius/+bug/1036207 mailman.client hangs accessing moderation queue * https://bugs.launchpad.net/postorius/+bug/1062963 Admin notification not received Write some nice-to-have bugfixes: * https://fedorahosted.org/hyperkitty/ticket/90 display of poster's email address overlaps with message excerpt * https://fedorahosted.org/hyperkitty/ticket/91 search result page should include name of list * https://fedorahosted.org/hyperkitty/ticket/96 When displaying a post, include a link to parent post * https://bugs.launchpad.net/postorius/+bug/1443643 Test for invalid email addresses in mass subscribe * https://bugs.launchpad.net/postorius/+bug/1444699 I can't add a single member (non-owner, non-moderator) from the Members page. * https://bugs.launchpad.net/postorius/+bug/1443995 Need tests for list moderator views -- Sumana Harihareswara http://brainwane.net

1 0

Outstanding postorius merge requests (was Re: [ Query ] Some bugs in postorius that needs to be addressed)
by Terri Oda 14 Apr '15

14 Apr '15

On 2015-04-13 3:49 PM, Ankush Sharma wrote: > The above bugs have been discussed in detail with Bhavesh Goyal with > involvement of Terri. I think fixing > https://code.launchpad.net/~bhavesh-goyal093/postorius/fixed-nav-role-ident… > would > work ! This has been merged, thanks all! Incidentally, I spent most of yesterday and some of today reviewing outstanding postorius merge proposals. You can see the list of ones that I got in here: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/changes And I've sent out fix required notes to a few folk because I couldn't get things running easily. There's still a few I haven't looked at as well. I'm switching over to doing some work on a docker image for mailman so I won't be doing as many merge requests tomorrow, but if any of you are hoping to have a merge happen while I'm at PyCon, I'd totally appreciate it if you could check your merge against the latest updates (as you can see, there's been a few commits) and make sure to run the tox tests. Once you've got it all working, hit me up on IRC and I'll see what I can do! And, of course, helping try out other people's merge proposals and do any initial debugging is always awesome. As is adding more tests! :) Terri

1 0

Re: [Mailman-Developers] [ Query ] Some bugs in postorius that needs to be addressed
by Ankush Sharma 13 Apr '15

13 Apr '15

The above bugs have been discussed in detail with Bhavesh Goyal with involvement of Terri. I think fixing https://code.launchpad.net/~bhavesh-goyal093/postorius/fixed-nav-role-ident… would work ! On Mon, Apr 13, 2015 at 7:05 PM, Ankush Sharma < ankush.sharma.ece12(a)iitbhu.ac.in> wrote: > Sorry for the typo `good` is not required in the first line. > > On Mon, Apr 13, 2015 at 7:01 PM, Ankush Sharma < > ankush.sharma.ece12(a)iitbhu.ac.in> wrote: > >> Hello everyone, >> >> I have found a good some bugs in postorius. Needs your review before >> fixing them. >> >> *1.* The *list_moderator* is not able to access the list of held >> messages as visiting at <base-url>/postorius/lists/<list-id>*/held_messages >> *gives a *403 *i.e *Forbidden* Status code because it is simply not >> allowed to access it. I have discussed the cause and fix for this issue >> here https://bugs.launchpad.net/postorius/+bug/1443433 . >> I am assuming the *list_owner* to be a *list_moderator* in my fix as >> indicated by >> http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… >> >> *2. *At >> http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… ; why >> a *list_moderator *is allowed to view the `*Mass Subscribe`* link on the >> list navigation bar ? Though clicking it will give a *403* again as he >> has not permission for it. I think it should be *list_owner. * >> >> *3. *The *list_navigation menu *containing the links to Info, Settings, >> Mass Subscribe, Delete etc. options for a list are only visible to the *super_user. >> *Though, a *list_owner *should be able to see these for his *owned >> lists *and similarly a *list_moderator *should be able to see the *held >> messages *option in his navigation menu. This can be fixed by replacing >> the line: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… >> by >> >> % if user.is_superuser or user.is_list_owner or user.is_moderator %} >> >> As we have a second level permission check before rendering the >> respective options implemented in the file : >> http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… >> <http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/…> . >> Doing this will cause proper person to see the options that he is allowed >> to do in his navigation menu. More on this here : >> https://bugs.launchpad.net/postorius/+bug/1443400 >> >> Thanks, >> >> Ankush Sharma >> IIT-BHU,Varanasi >> India >> github.com/black-perl >> >> > >

1 0

Update from Day 1 of the PyCon sprints
by Sumana Harihareswara 13 Apr '15

13 Apr '15

Hi all! Eight of us have started on our first day of the PyCon sprints and have started our push towards the Mailman suite 3.0 release, which will also include Postorius 1.0 and HyperKitty 1.0 releases. http://wiki.list.org/DEV/PyCon%202015%20Sprint lists what we are trying to finish up this week; we've moved some nice-to-have stuff to the "3.1" section in http://wiki.list.org/DEV/Mailman%203.0 (probably the 3.1 version of the Mailman Suite will include HyperKitty 1.1 and Postorius 1.1; mailman-bundler will help enforce this sort of component version alignment). Our goal for the 3.0 release is: We're blessing this as working, we encourage people to install it fresh, and we think new installations will work well. You might be able to upgrade existing lists, but if you're upgrading from 2.x, test and make backups first. We do not promise feature parity with 2.x. Also, probably not this week, but soon, we're going to move the HyperKitty bug tracker and wiki content from fedorahosted to a new Launchpad project and to wiki.list.org, to reduce the number of different places we do bugtracking and documentation. I'll be leading that, probably in May. -- Sumana Harihareswara http://brainwane.net

1 0

Re: [Mailman-Developers] [ Query ] Some bugs in postorius that needs to be addressed
by Ankush Sharma 13 Apr '15

13 Apr '15

Sorry for the typo `good` is not required in the first line. On Mon, Apr 13, 2015 at 7:01 PM, Ankush Sharma < ankush.sharma.ece12(a)iitbhu.ac.in> wrote: > Hello everyone, > > I have found a good some bugs in postorius. Needs your review before > fixing them. > > *1.* The *list_moderator* is not able to access the list of held messages > as visiting at <base-url>/postorius/lists/<list-id>*/held_messages *gives > a *403 *i.e *Forbidden* Status code because it is simply not allowed to > access it. I have discussed the cause and fix for this issue here > https://bugs.launchpad.net/postorius/+bug/1443433 . > I am assuming the *list_owner* to be a *list_moderator* in my fix as > indicated by > http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… > > *2. *At > http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… ; why > a *list_moderator *is allowed to view the `*Mass Subscribe`* link on the > list navigation bar ? Though clicking it will give a *403* again as he > has not permission for it. I think it should be *list_owner. * > > *3. *The *list_navigation menu *containing the links to Info, Settings, > Mass Subscribe, Delete etc. options for a list are only visible to the *super_user. > *Though, a *list_owner *should be able to see these for his *owned lists *and > similarly a *list_moderator *should be able to see the *held messages *option > in his navigation menu. This can be fixed by replacing the line: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… > by > > % if user.is_superuser or user.is_list_owner or user.is_moderator %} > > As we have a second level permission check before rendering the respective > options implemented in the file : > http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… > <http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/…> . > Doing this will cause proper person to see the options that he is allowed > to do in his navigation menu. More on this here : > https://bugs.launchpad.net/postorius/+bug/1443400 > > Thanks, > > Ankush Sharma > IIT-BHU,Varanasi > India > github.com/black-perl > >

1 0

[ Query ] Some bugs in postorius that needs to be addressed
by Ankush Sharma 13 Apr '15

13 Apr '15

Hello everyone, I have found a good some bugs in postorius. Needs your review before fixing them. *1.* The *list_moderator* is not able to access the list of held messages as visiting at <base-url>/postorius/lists/<list-id>*/held_messages *gives a *403 *i.e *Forbidden* Status code because it is simply not allowed to access it. I have discussed the cause and fix for this issue here https://bugs.launchpad.net/postorius/+bug/1443433 . I am assuming the *list_owner* to be a *list_moderator* in my fix as indicated by http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… *2. *At http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… ; why a *list_moderator *is allowed to view the `*Mass Subscribe`* link on the list navigation bar ? Though clicking it will give a *403* again as he has not permission for it. I think it should be *list_owner. * *3. *The *list_navigation menu *containing the links to Info, Settings, Mass Subscribe, Delete etc. options for a list are only visible to the *super_user. *Though, a *list_owner *should be able to see these for his *owned lists *and similarly a *list_moderator *should be able to see the *held messages *option in his navigation menu. This can be fixed by replacing the line: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… by % if user.is_superuser or user.is_list_owner or user.is_moderator %} As we have a second level permission check before rendering the respective options implemented in the file : http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/… <http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/…> . Doing this will cause proper person to see the options that he is allowed to do in his navigation menu. More on this here : https://bugs.launchpad.net/postorius/+bug/1443400 Thanks, Ankush Sharma IIT-BHU,Varanasi India github.com/black-perl

1 0

Approach for making Editable fields in user profile
by Ankush Sharma 13 Apr '15

13 Apr '15

Hello everyone, I need to discuss in context with the feature request https://bugs.launchpad.net/postorius/+bug/1432383. The point is to make the fields like irc handle, first-name, last-name etc. editable in the user profile. User registration is currently done using *django-browserid *with the default *User Model. *There are no schema rules for these *extra *fields in the *auth_user *table of the underlying Postorius database due to the use of the default *User Model*. I am thinking of using a CustomBackend class overriding the BrowserIdBackend class for adding customisation *[1]*. Also, I think it would be required to have a *new *User model for these extra fields which can be used by django-browserid for the initial user registration. Initially, these *extra *fields can be set to *empty*. Later on, with the help of an update view users can be asked to update their profiles when they login. This would require the use of database migrations. Other option is to use to create an extra table for these fields and for it the default *User model *would be suffice. In this case, an extra form would do the job. I want to ask whether my approach is correct ? Or it would be more meaningful to take input for these fields during the first time when the user registers by using Persona ? ( I guess it would require some ugly tweaks ) Waiting for your opinion on it ! Thanks, Ankush Sharma IIT-BHU, Varanasi India *github.com/black-perl <http://github.com/black-perl>* [1] : http://django-browserid.readthedocs.org/en/latest/user/customization.html#a…

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers April 2015