On Thu, Jan 22, 2015 at 12:58 PM, Pranjal Yadav godricg...@gmail.com
wrote:
Hello
I'm a programming enthusiast and recently started working in
python about 6 months back, I have had experience in cryptography and many
machine learning techniques. I started reading about mailman few
Hi,
As per the feedback from Steve, I have made changes to the code in
following areas
- The get_listing method has been moved to the lib/utils and has been
rebuilt in a class
*independent* way, and it works as good as before.
- The connection checking has been moved to the connect
Hi Steve
On Fri, Aug 8, 2014 at 10:04 AM, Stephen J. Turnbull
turnb...@sk.tsukuba.ac.jp wrote:
Rajeev S writes:
...
Sure, but that's not particularly important since actually it will be
the mailman.client directory when you integrate it, and (especially
after Barry's post just now) I'm
Hi Steve,
On Thursday 07 August 2014 12:00 PM, Stephen J. Turnbull wrote:
Rajeev S writes:
I feel that it will make the code cluttered. Since the CLI code
is independent of the rest of mailman client, won't it be
better to maintain the CLI code in a separate folder, as it is now
Hi Steve,
On Wednesday 06 August 2014 12:14 PM, Stephen J. Turnbull wrote:
Tree organization
-
I don't think the CLI should be buried several levels deep in the
source. The mailman.client package is really a collection of
services, and the CLI should be at the same level in
Hi,
As the Summer of Code period comes to an end, I am one more step closer
to completion of the
features mentioned in my proposal.
I have built the initial version of the backup and restore tool, that
currently supports backup
and restore of a sqlite Mailman Instance, by archiving the
On Tuesday 05 August 2014 12:27 AM, Rajeev S wrote:
Hi,
As the Summer of Code period comes to an end, I am one more step
closer to completion of the
features mentioned in my proposal.
I have built the initial version of the backup and restore tool, that
currently supports backup
Hi,
I have pushed r68 that adds the export to CSV feature to the mailman
command line tools.
Usage
./mmclient show user -v --csv path/to/file.csv
./mmclient show list -v --csv path/to/file.csv
./mmclient show domain -v --csv path/to/file.csv
The r68 further adds the support for
Hi,
I have been a bit unhappy about the regular expression approach for command
validation and array processing for command parsing to get the arguments.
So I have decided to switch to the conventional and right method to do it,
using the Lex-YACC duo, using the PLY module.
I have already ported
Hi,
I have pushed two revisions, r65 (19/07/2014) and r66 (20/07/2014).
Here are the changes under r65:
- Changes the command preprocessing workflow
- Command processing invoked by using a decorator.
- Removes redundant code in present in the shell, for example, at the
auto complete
to reduce redundant code at many
functions and betterment of error and exception handling and reporting.
The revision 65 will also include Preferences related actions.
http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision/64
*Regards,Rajeev S*
*http://rajeevs.tk http://rajeevs.tk
Hi,
I have pushed 2 revisions r62 (10/07/2014) and r63 (12/07/2014) that
implement the create object and delete object functionalities.
A snapshot of the new revisions:
1. The support for automatic implicit filtering based on reserved
environment variables like
domain has also been
Hi,
I have pushed the r61 [1], which makes it the first commit on the Command
Line shell. As Steve suggested, I have also modified the CL tools (and
shell) to support both singular and plural instance names using a naive
function, that can be replaced with a prefix matching procedure, if
Hi,
A modification has been suggested for the Command line tools in an IRC
discussion with Abhilash.
It was suggested that, to make commands more intuitive, the commands be
partitioned into singular and plural as per the scale of the action
performed.
For example,
In the current scenario
Hi,
Now the mid term evaluations are done, I would be building the command
line shell, as planned. I would like to present how I would like to
tackle the requirement at hand.
As mentioned in my proposal and the most logical approach, all the
common functionalities between the shell and the
Hi,
As promised, I have completed the preference related commands and pushed
it as revision 60 [1].
The preferences form a new scope, along with user, domains and lists.
There are 2 commands associated
with the `preference` scope.
1.Show Preference
./mmclient show preference [scope]
Hi,
I have pushed r59 (In fact, 2 days before) which adds commands to
perform the following actions
- Add moderators
./mmclient add-moderator list l...@domain.org --user a...@b.com
b...@c.com d...@e.com
- Add owners
./mmclient add-owner list l...@domain.org --user a...@b.com
Hi,
I have completed the describe instance feature and the subscription
features for
the CLI. I have pushed the changes as r58.[1]
The describe feature is implemented as an extension to the `show` command.
This feature adds 3 new usages for the `./mmclient show` action, apart
from the
Hi,
I have completed the `describe instance` feature for the list object. I
herewith attach the sample output of the command.
https://gist.github.com/rajeevs1992/3ca077fd7d1a5a1d5729
The describe feature is triggered when the `show` action is supplied a
object name of the corresponding
This is always possible
subscribe users us...@foo.com us...@bar.com us...@bar.com --list
l...@domain.org
Hi,
I have built to features, subscribe and unsubscribe users, as described
above
*subscribe users us...@foo.com us...@bar.com us...@bar.com --list
l...@domain.org*
and
On Fri, Jun 6, 2014 at 5:19 PM, Abhilash Raj raj.abhila...@gmail.com
wrote:
I think it would be more intuitive to have this command in list scope
rather than user scope. And anyway list scope must have a command to
list all subscribers.
Could it be used somehow to subscribe or unsubscribe
Hi,
The next set of tasks for the coming weeks, before the mid term
evaluation, are mostly subscription and membership related actions for the
CLI.
The various actions that are to be implemented are
1.
Show members of a list
The `list members of a list` feature is currently
On Mon, Jun 2, 2014 at 11:53 AM, Abhilash Raj raj.abhila...@gmail.com
wrote:
Hi Rajeev,
Rajeev S rajeevs1...@gmail.com wrote:
Thanks for considering my suggestion. I think you don't need to create
a sub-module for each scope inside `tests` module. It should be simpler
like `/tests
Hi,
As per Abhilash's comment to follow the TDD, I have covered
the test cases for the `domain` scope.
I know that TDD requires to write tests before implementation.
However, I believe that it's not a good idea to postpone test cases for the
existing units further.
Also, I would like to thank
Hi,
I have made more additions to the CLI, like the `delete` command and the
`user` scope.
Following is the list of changes brought about
1.Introduce User scope
Actions supported by User scope currently are create, show and delete.
show users, like other scopes, supports verbose and no-header
On Friday 30 May 2014 07:09 PM, Abhilash Raj wrote:
On Fri, 30 May 2014 18:12:18 +0530
Rajeev S rajeevs1...@gmail.com wrote:
I agree that an override for the confirmation message is necessary so that
the CLI
commands can be used in scripts and I would like to follow Barry's
suggestion of using
Hi Barry,
Although I haven't had time to go through the code, I'm liking what I'm
seeing
here on the mailing list. Just a quick comment.
[...]
Ideally, because this is a command line tool aimed and users, there should
be
a manpage for mmclient. Fortunately, it's *really* easy to write
On Tuesday 27 May 2014 12:27 PM, Abhilash Raj wrote:
Rajeev S rajeevs1...@gmail.com wrote:
Both of these options looks clean to me as a user. So if I am right you
have completed
* Listing of domains
* Listing of mailing lists(filtered by domain also)
* Creating domains
* Creating mailing
As discussed, I have completed the r54, that does the following
1. The arguments will be specified as positional arguments
wherever necessary and possible. The ideal way to use
positional arguments here is if the argument to the command
is the name of an instance the scope, use positional args
Hi,
I have pushed the revision 53, that has the following changes.
1. Refactoring as mentioned in the comments by Steve
2. Grouping of options and sub commands using subparsers
3. Changed the format of the command from *mmclient scope action*
to *mmclient action scope*
4. Replaced ambiguous
On Tuesday 13 May 2014 07:12 PM, Barry Warsaw wrote:
On May 13, 2014, at 03:27 PM, Rajeev S wrote:
Would --list be implied by seeing a `--listname=l...@example.com`? E.g. would
this be just as useful, and a little shorter:
mmclient show --listname=l...@example.com --domain=example.org
On Monday 12 May 2014 10:15 PM, Stephen J. Turnbull wrote:
Barry Warsaw writes:
Also as a general rule, I think we want just one level of
subcommand, so that `mmclient show --list` would be the template.
(That's open to discussion.)
I wonder about this in the context of argparse and
On Monday 12 May 2014 09:12 PM, Barry Warsaw wrote:
A better name might be `show` since the term list is so overloaded in this
context. Here's it's being used as a verb and a noun to refer to different
concepts, and I think that's confusing.
Yes, its confusing. In fact, I was looking for a
Hi,
I have elaborated the implementation and the motivations behind the
current approach in the following blog post, in case it might help
reviewing the code better.
http://myfossblog.blogspot.in/2014/05/lets-talk-over-cup-of-code.html
___
Hi,
I have added two more methods, *create domain* and *list mailing lists*.
The listing feature is performed using the `tabulate` module, which I have
added to the install_requires.
Also, the usage of the CLI is explained in the cli/docs/using.txt.
*Regards,Rajeev S*
*Government Engineering
Stephen J. Turnbull wrote:
Ah, OK, I see what you're getting at now.
I think this is out of scope for the CLI project, although it's
possible that providing some kind of scriptable interface (even a
simple way to store a sequence of commands acting on the current
list should suffice, where
Hi,
I have added the licensing blocks to the files and pushed the code.
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
On Fri, May 2, 2014 at 7:13 AM, Barry Warsaw ba...@list.org wrote:
On May 02, 2014, at 06:36 AM, Rajeev S wrote:
3
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
Please don't top-post. It's very helpful to readers to keep the
subthreads about particular issues separate, while at the same time
bundling them together for ease of mail-handling.
Why not? The CLI tools will have access to the user database, so in
theory you could authenticate. In
argparse,sorry about that :). And thanks
for the style guide tip.
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
On Sat, Apr 26, 2014 at 10:42 AM, Abhilash Raj raj.abhila...@gmail.comwrote:
On Fri, Apr 25, 2014 at 6:14 PM, Rajeev S rajeevs1
and push it to the mailman.client project.
And forget about the git vs bzr part. I am OK with using bzr :).
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
On Tue, Apr 22, 2014 at 9:01 PM, Stephen J. Turnbull step...@xemacs.orgwrote:
Just
pick up bzr
if necessary.
3.Is it necessary for me to hangout in the IRC?If yes, when?
4.Can I start coding right away?
Thank you once again!
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
On Thu, Mar 20, 2014 at 6:50 PM, Rajeev S rajeevs1
Hi Abhilash,
Thank you for the reply.
I will post a write up describing the implementation details of the
project.All other issues stand resolved.I will be using bzr+launchpad,and I
prefer mail to IRC.
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http
Hi,
Made a minor edit upon Meflin's comment, asking to change project title.
http://myfossblog.blogspot.in/2014/03/yet-another-change.html
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
On Fri, Mar 14, 2014 at 3:50 PM, Rajeev S rajeevs1
to the proposal
and revised the proposal accordingly.
http://myfossblog.blogspot.in/2014/03/gsoc-proposal-to-gnu-mailman.html
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
___
Mailman-Developers mailing list
Hi Bhargav,
You will be asked whether to *add a superuser* during *syncdb*. If you
answered no to that, do *python manage.py createsuperuser * and use that
username and password to login.
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
On Wed
Hi,
You will be asked for the create user prompt only the first time you run
syncdb.That's why you don't see it now.
Once the DB is created, only new tables, specified via django models, get
added to DB during the syncdb.
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http
/mailman-cli/blob/master/client
*Usage:*
To list the registered domains in your server, do
- ./client domain --list
To list the registered mailing lists in your server, do
- ./client list --list
For help with options available, do
- ./client -h
*Regards,Rajeev S*
*Government
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?
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
On Mon, Mar 3, 2014 at 4:35
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 bgo...@g.clemson.edu wrote:
Thanks Barry and Terri for your
Hi,
I have written and deployed an App that generates and decodes anonymous
emails,as I had mentioned.
Find the application here
http://anongen.herokuapp.com/
Source here
https://github.com/rajeevs1992/anongen
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk
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
this
functionality, before building my application.
*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
://docs.google.com/file/d/0B0oFc02F56UzRkU2R0JkeklMbEk/edit?usp=drive_web
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https
Thanks.Did it anyway,I guess I was biased by the github pull request
method, and that did not work with launchpad.
Submitted the patch at
https://code.launchpad.net/~rajeevs1992/postorius/postorius/+merge/207826
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk
the branch cannot be merged.
What am I doing wrong?
*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
-coders/postorius/trunk/parent
branch:
http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/
*Regards,Rajeev S*
*Government Engineering College,Thrissur*
*http://rajeevs.tk http://rajeevs.tk*
On Sun, Feb 23, 2014 at 5:52 AM, Stephen J. Turnbull step...@xemacs.orgwrote:
Rajeev S writes
57 matches
Mail list logo
