Mailman-Developers March 2014

mailman-developers@python.org

27 participants
69 discussions

Re: [Mailman-Developers] [GSoC 2014] Command line Client
by Florian Fuchs 04 Mar '14

04 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/03/2014 03:11 PM, Rajeev S wrote: > Hi Florian, > > I had discussed about the full anonymization project with Stephen > and I had found that I had quite misunderstood the use case of that > project. > > So I have decided to go forward with applying for the mailman > command line client project. > > The deliverables of the project would be, at the least, > > * Command line tools to perform tasks in the mailman client docs * > Any Extra useful functionalities that can be identified, such as > export, backup * Other Useful tools like backup and restore. * Man > Page entries for the new commands Sounds good! But make sure to mark steps 2 to 4 as optional. > Also, I did not quite get the "/coming up with a //great layout /" > part. Do you mean to build a custom shell for mailman? If yes, what > extra functionality should it provide than the standard command > line tools? I don't know if I would call it a shell, but something like that, yes. I talked about it with Patrick Koetter a while ago (who is also a possible mentor for this project), and we had something *a little* similar to the mysql/sqlite3 client in mind. Similar meaning: You start the client (possibly providing some context option, like the database used) and then perform operations on a given context/object (in our case: lists, users, addresses, preferences) using predefined commands. Ideally, the application makes all operations pretty easy, by using auto-completion, a good help function etc. This is just a rough idea though, maybe you can come up with a better one... ;-) Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTFYUaAAoJEEceGbPdavl7jEEIAKJa5XMXRXp9HxJsQgyurZi+ YHqbJlGGNPG0eXOkHS2gdkNXp36cwSLgtKZM/1Xj9pvgnj5+MKlMg8528iGUNqDU WUdQlIcWLsVovy0m3ANI77k8I5TBFCl8vX4X0NuR05H6RmqwjtlWs9ZnFXlPnrtd atMCXm7JkEwubTcI+m6I5utLDNzmNLzPwRekFX9umcMR1DXmIDm5v8cE16+DWLmj ZO5Fj83OH8pA6sUvucfR6YddbDlgRsVfC6K88j2yHFl+0GUeYwIoKPHFXu49/zj+ ThcnNkhx4nMiJlKh41urxA27ysvCavbhgjGvehwWp6eDHBQT29lJtBPEWKRRryM= =AY/u -----END PGP SIGNATURE-----

1 0

Re: [Mailman-Developers] [GSoC 2014] Cordova/Android App for GNU Mailman Admin Interface
by Rajeev S 03 Mar '14

03 Mar '14

Hi Bhargav, Just do *mailman start*, without the bin. I have edited the wiki. *Regards,Rajeev S* *Government Engineering College,Thrissur* *http://rajeevs.tk <http://rajeevs.tk>* On Mon, Mar 3, 2014 at 10:37 PM, Bhargav Golla <bgolla(a)g.clemson.edu> wrote: > Thanks Barry and Terri for your feedback. > I was trying to install Postorius locally and analyze what all would be > required in a mobile app for Admin. Doing the same, I have hit a roadblock. > I am using the wiki provided here[1]. I tried to install mailman using "set > up sources" part of the wiki. Though python setup.py install executes > without any errors, I am unable to see the folder bin/ in the same > directory. So, even though I proceed with further setup, I am getting a > "Mailman REST API not available. Please start mailman core" on my > localhost:8000 webpage. Could anyone help me here? > > [1] > > http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… > > Thanks > > > On Sun, Mar 2, 2014 at 1:18 AM, Terri Oda <terri(a)toybox.ca> wrote: > > > > > On 2014-02-28, 7:36 AM, Bhargav Golla wrote: > > > >> I have a few questions regarding this idea. > >> 1. I intend to develop it on Cordova since it will help in porting the > app > >> easily to multiple platforms. Were there any ideas in this directions > >> regarding going native or hybrid? > >> > > > > Personally, I'd prefer if we went hybrid and had an html5 webapp that > > could be used straight over the web for mobile users who don't want to > > install an app, with Cordova used to build the individual platform apps. > I > > may not be the mentor on this one, though, so I'm happy to defer to > whoever > > the final mentor is on this front. > > > > Incidentally, I've been using Intel's XDK for building Cordova apps > lately > > and highly recommend it for quick testing on various platforms and screen > > sizes. I've found it a very useful tool, and not just because I work for > > Intel now! > > > > 2. Can I assume that all mailing lists built by Mailman support the REST > >> interface? Also, I have tried to see if I can get JSON responses and I > am > >> unable to by adding a HTTP Accept Header to take "application/json". Am > I > >> doing anything wrong or is JSON not implemented? > >> > > > > I don't know the answer to this off the top of my head: Barry? > > > > > > 3. As a starter, could I ignore internationalization for GSoC, but > >> implement interface in such a way as to be able to internationalize it > >> easily? > >> > > > > We don't expect you to actually translate anything, don't worry. :) But > > you should definitely build as much as possible so that > > internationalization will be easy: make sure there's a quick way to get a > > list of strings that need translation, at least. Some of the strings may > > be already translated in other components of Mailman, so you may be able > to > > get some translations to use to test if you have time at the end of the > > summer for internationalization. > > > > Terri > > > > > > > -- > Bhargav Golla > M.S Computer Science > Github <http://www.github.com/bhargavgolla> | > LinkedIN<http://www.linkedin.com/in/bhargavgolla> > | Website <http://www.bhargavgolla.com/> > _______________________________________________ > 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/rajeevs1992%40gm… > > Security Policy: http://wiki.list.org/x/QIA9 >

1 0

Re: [Mailman-Developers] Gsoc idea discussions : Continuous integration tool
by Florian Fuchs 03 Mar '14

03 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/22/2014 07:54 AM, Varun Sharma wrote: > Hi all, I am interested in continuous integration tool as my gsoc > project and would like to discuss further it's possible > implementations. I think one possible implementation for gatekeeper > is : > > Making another django project mm_gatekeeper which every developer > must run in order to commit to trunk. We can host its repo of on > launchpad. It will act as a proxy to bzr and will perform bzr > commit only after all the unit and doc tests succeeds. > > > bzr pull can be implemented as > > $ mm_gatekeeper PROJECT_NAME pull > > or to pull all projects > > $ mm_gatekeeper pull > > > Instead of using bzr commit in postorius we can use > > $ mm_gatekeepar PROJECT_NAME COMMAND > > $ mm_gatekeeper postorius commit -m"commit message" > I like the idea of having a command line tool to run integration tests! It could be used both by the devs working on the different packages as well as on a central ci server that runs those tests regularly. But I'm not sure it should be tied that closely into the commit/merge process: When a developer works on a new feature in a branch separate from the main line, it's probably very common to commit small changes that would break the whole system, but are commit-worthy anyway because they sum up a small series of changes in a chain of more commits that eventually lead to a mergeable state. So when I (as a developer) *think* my stuff is ready to be merged into trunk, *that's* when I would like to check if everything's fine and run the integration testing tool. Another thought: What versions of the various Mailman packages should the ci tool test against? Should that be configurable for different test scenarios? Like: - - Use the branch I'm currently working on, but get all other packages from their respective main lines (the perspective of a developer working on a new feature before merging). - - Use the current main line of one package, but everything else from pypi (the perspective of a developer when preparing the release of one package) - - ...? Why would you use Django to build the tool as opposed to "just" a python package? Cheers, Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTFEvWAAoJEEceGbPdavl7UPMH/A5cd7PWdw+qMaOFRfxfTVuV lvwdwTOb/Z7oeeE5bol/czvuG7ejaBi5fVxerSb2Ffo4N8aESP1gmxt4U+Qp1SFr 0oIORix0L35Kz19MurbODaZzphjZB5Hf/F/Fu0OgbS4KmDf1nnMvVvXusB6vOxM4 lvg/AOb1GyGuYd78Cj4GA2CY6oCfh2pAjmzUKI4ULvzHjGFHYtjanmYgaB+cjdwB mNaZbJtQKcjBTvl6iXAON0MU2SzmMG9psA/LcR2hRQMZncBxe0Lbh3fEAA7IHuKe rzqT2lyX3cBZtvsH06TlLwYmxyJp8Z3HTv6Txj7y+YvvrL4Sj5c6fYTts7OtE1M= =fci5 -----END PGP SIGNATURE-----

2 1

Re: [Mailman-Developers] [GSoC 2014] Cordova/Android App for GNU Mailman Admin Interface
by Terri Oda 03 Mar '14

03 Mar '14

On 2014-02-28, 7:36 AM, Bhargav Golla wrote: > I have a few questions regarding this idea. > 1. I intend to develop it on Cordova since it will help in porting the app > easily to multiple platforms. Were there any ideas in this directions > regarding going native or hybrid? Personally, I'd prefer if we went hybrid and had an html5 webapp that could be used straight over the web for mobile users who don't want to install an app, with Cordova used to build the individual platform apps. I may not be the mentor on this one, though, so I'm happy to defer to whoever the final mentor is on this front. Incidentally, I've been using Intel's XDK for building Cordova apps lately and highly recommend it for quick testing on various platforms and screen sizes. I've found it a very useful tool, and not just because I work for Intel now! > 2. Can I assume that all mailing lists built by Mailman support the REST > interface? Also, I have tried to see if I can get JSON responses and I am > unable to by adding a HTTP Accept Header to take "application/json". Am I > doing anything wrong or is JSON not implemented? I don't know the answer to this off the top of my head: Barry? > 3. As a starter, could I ignore internationalization for GSoC, but > implement interface in such a way as to be able to internationalize it > easily? We don't expect you to actually translate anything, don't worry. :) But you should definitely build as much as possible so that internationalization will be easy: make sure there's a quick way to get a list of strings that need translation, at least. Some of the strings may be already translated in other components of Mailman, so you may be able to get some translations to use to test if you have time at the end of the summer for internationalization. Terri

2 1

Re: [Mailman-Developers] [GSoC 2014] Command line Client
by Florian Fuchs 03 Mar '14

03 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/25/2014 03:17 AM, Rajeev S wrote: > Hi, > > I am Rajeev S , A CSE Undergrad from India. I would like to work > with the Command Line client project listed in the GSoC ideas > page. > > I have been working on the Postorious package lately and have > managed to make some tweaks in it, like the add users by file > upload and an improved email validator. > > As a part of the project, I would like to build,at the minimum, > the functionalities listed at the > mailmain.client/src/mailmanclient/docs/using.txt > > Can the mentor of this project elaborate upon the requirements of > the project? I think the functionalities listed in the mailman.client docs are a good orientation point, because those represent almost everything the core REST API currently exposes. It also makes sense to use mailman.client instead of writing new code that handles the HTTP stuff and object binding. I guess the most difficult part of this project is coming up with a great "layout", possibly borrowing stuff from other well-known command line clients (mutt, mysql/sqlite3, the ipython shell, lynx etc.). Of course there are bonus points for all kinds of stuff, like exporting data to files/stdout, making the tool extensible etc. But I really think designing the right interface and implementing most or all of what mailman.client can do will take a good amount time. > Also I have thought of an approach for the full anonymization > project.Is it possible that I can work on both of these as a single > project?(I have a feeling that the CLI is a small project, am I > right?) You should definitely pick one project and come up with good ideas for that. Cheers Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTFGH3AAoJEEceGbPdavl7ZYIH+gJVB27H6G5LXd+0+vytx1gC sZiQCy/vYEr8jtCbe8BdoLvk+jyBNRaUzaxDuL/9Pb3g8HCwuJQ+HzEQm25ewZ0X vlvWZ7dW07sEYr5q7cRatkqO/GQc2n6B6IgGd3oTkihQUO4iZQTu/ddytMghvCP0 MYtuQyuecjZm8JBlCn6AU0KQWxNx/Kt7CsuPfk6FcCOmA15ZEnZ4kxZFY0khVY5a NLetoDDY7fQAf5fFlea8SfIN8PFB1i4qv5DdjDaX17Yg/S+X5S0nZx18uvqX7Up8 RlGLTCSA8s3qsYItaI9NWpXRdo/Z1p8MN/hQOOot85e3SVernKn9oq1TSI/7lww= =pozr -----END PGP SIGNATURE-----

2 1

Gsoc 2014 : Mailman SNMP support
by Nitin Agarwal 03 Mar '14

03 Mar '14

Hi, Here its Nitin Agarwal, an open source Software developer and enthusiast. I am looking forward to contribute to Mailman in the upcoming Google Summer of Code 2014 through the Mailman SNMP Support Project idea. I have an experience with the open source software development and tools used. I have an indepth knowledge of SNMP protocol and an understanding of the concepts specified in the SNMP RFC 1157. I would like to discuss the project idea with the concerned mentor for this Project idea. I would like to start off working and contributing to Mailman through this project idea. Could the mentors Please help me in the starting off with the initial steps and key ideas involved in this project. Thanks *Nitin Agarwal* [1] Github : https://github.com/NitinAgarwal [2] IRC : nitinagarwal3006

1 0

Re: [Mailman-Developers] Installation of mailman on local machine
by Barry Warsaw 02 Mar '14

02 Mar '14

On Feb 28, 2014, at 02:38 AM, Tejas Shah wrote: >However, starting the mailman server using "mailman start", when i try to >test using "nose2 -v" , it gives me o/p: As Mark says, you should not start the mailman server before running the tests. 'mailman start' is there to start the server for production. Any processes the test suite needs it will automatically start and stop itself. -Barry

1 0

GNU Mailman sprinting at Pycon 2014
by Barry Warsaw 02 Mar '14

02 Mar '14

Hello sprinters! Once again, the GNU Mailman project will be sprinting at Pycon, this time the 2014 conference in Montreal. I've created a placeholder page for adding ideas about what you would like to work on, as well as our priorities. We'll be filling out details over the next few weeks, but feel free to start discussing ideas here. http://wiki.list.org/display/DEV/PyCon+2014+Sprint Cheers, -Barry

2 2

Re: [Mailman-Developers] [GSoC 2014] Cordova/Android App for GNU Mailman Admin Interface
by Barry Warsaw 02 Mar '14

02 Mar '14

On Feb 28, 2014, at 10:36 AM, Bhargav Golla wrote: >2. Can I assume that all mailing lists built by Mailman support the REST >interface? Also, I have tried to see if I can get JSON responses and I am >unable to by adding a HTTP Accept Header to take "application/json". Am I >doing anything wrong or is JSON not implemented? I'm not sure this question makes sense. ;) Mailman 3 does expose a REST API, but in the core, it's a protected (e.g. localhost only by default) admin interface. It's not per-mailing list, although there are mailing list specific resources. JSON is the only response format currently supported. See http://tinyurl.com/kzmcwf5 for details. Cheers, -Barry

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 March 2014