Re: [Mailman-Developers] GSOC 2014: CI tool for the Mailman suite and postorius improvements

2014-05-01 Thread Tanstaafl

On 4/30/2014 10:11 AM, Barry Warsaw ba...@list.org wrote:

Thanks for giving me opportunity to work with mailman community this
summer. I'm an undergraduate student from Manipal Institute Of Technology,
India and i'll be working on project CI tool for the Mailman suite and
postorius improvements.
I would love to get feedback and suggestions from the community regarding
my project which involves:
1. CI tool for Mailman Suite (mailman core, postorius, hyperkitty)
2. The UI Testing Framework for Postorius
I am in process of discussing the best possible implementation for this
project with my mentors and advice from the community for the same will be
very helpful.



One of the things I think is critical for the core, is testing it against
supported the two supported db backends, SQLite and PostgreSQL.


? Not fully supporting the most popular (mysql/mariadb)?
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9


Re: [Mailman-Developers] GSOC 2014: CI tool for the Mailman suite and postorius improvements

2014-05-01 Thread Barry Warsaw
On May 01, 2014, at 06:25 AM, Tanstaafl wrote:

? Not fully supporting the most popular (mysql/mariadb)?

Contributions welcome!

the-obvious-response-ly y'rs,
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9


[Mailman-Developers] [GSoC 2014] Mailman CLI Project

2014-05-01 Thread Rajeev S
Hi,

I will be using the following branch for the Mailman CLI project

*https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli
https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli*

I have created and committed the basic structure of the project in the
branch.Also, as the first step I have implemented the create list
functionality for the command line tools.

A few snapshots:

1.As discussed in stage of proposal review, the command mmclient (currently
script) triggers the shell if no argument is specified and performs the
action when an argument is supplied.

2.The argparse module has been used for parsing arguments. Shell is built
using Cmd module, currently no functionality.

3.The code has been verified with pep8 *and* flake8 tools. It also passes
most of the guidelines mentioned in Barry's styleguide. Some of the
guidelines are yet to be met, like the licensing block
and stuff like __all__. Also the ^L at major sections are also not
added.(Is it still necessary?)

4.The code rests in mailman.client/src/mailmanclient/cli


I guess it would be easier to discuss the design and architecture based on
this.

*Regards,*
*Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9


Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project

2014-05-01 Thread Barry Warsaw
On May 02, 2014, at 06:36 AM, Rajeev S wrote:

3.The code has been verified with pep8 *and* flake8 tools. It also passes
most of the guidelines mentioned in Barry's styleguide. Some of the
guidelines are yet to be met, like the licensing block
and stuff like __all__. Also the ^L at major sections are also not
added.(Is it still necessary?)

Files should definitely all have licensing blocks.  ^Ls are not required.  I
find them useful for Emacs navigation, but I understand they may be
distracting for other folks in other editors.  I really need to update the
style guide for Python 3 and not-quite-Python-3-yet.

-Barry
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9