From follybeachris at gmail.com Fri Mar 1 19:43:29 2013 From: follybeachris at gmail.com (Chris Cargile) Date: Fri, 1 Mar 2013 13:43:29 -0500 Subject: [Mailman-Developers] Mailman-Developers Digest, Vol 286, Issue 10 In-Reply-To: References: Message-ID: On the matter of communications, I might hope to take yet a moment to address my goals, motivations, and expectations for contributing to the quite-worthy, well-thought-out and respectable mailman3 *team* effort and re-establish what might be already seemingly clear to some...I am a new-comer to the software development field but am not clueless as to the notion that everybody's style doesn't always immediately mesh up automatically but rest assured that I'll try to get to speed and make sure I don't re-address anything beyond reason (my goal for restatement is an attempt at allowing for the opportunity to address any misconceived notions I have so I can get confirmation that I understood correctly and move on quickly). As a contributor in an environment where everybody's diverse experiences are valuable to the group effort, the environment for me will present a much-welcomed chance to draw on such experiences where I am hoping to give as much as I could draw and hope your advice and direction will be shared often to help achieve this! To summarize my background and experience for all with an interested, I began school to be in business, finishing there in 2006 with a BS in Business to become a federally-serving private sector employee working in IT, but realized after just a few short years in that role that the heart of our service - computers - was not only my area of passion but also something I could see myself doing for the longer-term of a career perhaps. In my first position as a 'business person' I built a website (as a separate contract-pay assignment), put my web development experience to work growing in a non-profit for my career sector, and started my own sites and building web applications, to lead me to my current position as a continuing student (in CS,software) where I supposed I am being convinced of my grad school/research ideals but am retaining the goal of philanthropic contribution. I did have the chance to participate in some local STEM initiatives which was pretty cool (involving python programming with middle- and high-school children, locally). I have had the opportunity of working of course with people whose styles meshed easily and some where it was more difficult, but I would like to assert that I'm very enthusiastic about being on-board here with all of you and would like to attend any meetings for general discussion or encourage reaching out if you see me poking around the #mailman chat, you want to set up a google hangout to discuss mailman, etc (by default, email is perfectly adequate, if you prefer that only). The more quickly I can come to fitting in and sharing the heavy-lifting, the better for all (and the outcome for mailman, I hope) Please friend me, follow me, ask about my experiences, or ask to see more if you don't find what out you'd like to know about me through at my site pages: chriscargile.com, chriscargile.com/portfolio When we know whether the networking supports it, I would find it great to meet for a video chat or streamcast from the pysprint, if you're interested? I am working on the virtual-machine idea, in the meantime, if anyone wants a status update on it, sometime soon R/Chris On Thu, Feb 28, 2013 at 6:00 AM, wrote: > Send Mailman-Developers mailing list submissions to > mailman-developers at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/mailman-developers > or, via email, send a message with subject or body 'help' to > mailman-developers-request at python.org > > You can reach the person managing the list at > mailman-developers-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mailman-Developers digest..." > > > Today's Topics: > > 1. background on maintaining the documentation (was RE: > Mailman-Developers Digest, Vol 286, Issue 9) (Chris Cargile) > 2. Re: background on maintaining the documentation (was RE: > Mailman-Developers Digest, Vol 286, Issue 9) (Terri Oda) > 3. Re: background on maintaining the documentation (was RE: > Mailman-Developers Digest, Vol 286, Issue 9) (Barry Warsaw) > 4. Re: Mailman-Developers Digest, Vol 286, Issue 7 (Barry Warsaw) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 27 Feb 2013 14:33:48 -0500 > From: Chris Cargile > To: mailman-developers at python.org > Subject: [Mailman-Developers] background on maintaining the > documentation (was RE: Mailman-Developers Digest, Vol 286, Issue 9) > Message-ID: > gZMV_hdRTdTz+RHMW_iCqRHYF+g2A+G3_mj5Q at mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > thanks guys - that helps me get going with things..like documentation > probably should, huh? :) > > >If there is any functionality that you are wondering about, by all means > >provide a link to an example of its usage and I'll try and give an opinion > on > >whether it will be easily supported or not. Generally, the border between > >Wiki and CMS territory is vague (a Wiki is a form of CMS, after all) and > it > >can be quite straightforward to add functionality regarded as CMS-specific > to > >Moin. > >Paul > > the Moin system will get us away from the Atlassian licensing hassle AND > would tie in great for enabling a new website for the MM3 release, - it > would be cool, IMO, if we got to explore the RSS feature's ( > http://moinmo.in/MoinMoinSyndication) working since we could generate > recent changes outputting onto a feed, and from there, either give the RSS > page some nice CSS or display the feed on the new site main-page if it was > being served up separately from the moin system. I also checked using the > w3c validator and moin outputs its pages in valid-xhtml mark-up so that's > good for accessibility, which seems like a good goal for Mailman too, > seeing as its role is a communications medium > > so +++1 for the moin cms transfer (/RSS?) - I don't have much familiarity > with moin blogspaces, but it'll work fine I bet > > >>So I interpret your question as being whether the documentation on the > Wiki is > >>just a snapshot of some documentation maintained elsewhere or whether the > >>work is being done on the Wiki itself. > > The documentation is maintained to some level in Atlassian, > pythonhosted.org, > and the bzr repos (, other places?) per package, so Terri explained that > Atlassian is the main location for how-to's, admin guides, and GSOC stuff. > Otherwise, for simplicity, the packages have docs and doctests, in the > individual package themselves > > > on Tue, 26 Feb 2013 10:38 Terri Oda wrote: > > At minimum, I think it is important to get confirmation whether the > > confluence snapshot (wiki.list.org) is just a snapshot and we can direct > > our efforts at updating the documentation there? also, on that note, what > > would be the sphinx documentation role in all this and/or how necessary > is > > it to understand that system? > > >>You can, in the case of errors, also submit > >>merge requests to fix the documentation in the source tree. At some > >>point, I imagine Paul will tell us the migration is ready to go and > >>we'll freeze the wiki, but for now go ahead and edit there. > > Would the merges accepted propogate document changes to the package repos > or are we referring to a merge against a documents-repo that is somewhere I > don't know of. I'm still confused on where the sphinx documentation plays > into it (is that maybe like building javadocs only, instead it does so for > python, maybe) > > r/Chris > > > ------------------------------ > > Message: 2 > Date: Wed, 27 Feb 2013 17:18:49 -0700 > From: Terri Oda > To: Chris Cargile , > mailman-developers at python.org > Subject: Re: [Mailman-Developers] background on maintaining the > documentation (was RE: Mailman-Developers Digest, Vol 286, Issue 9) > Message-ID: <512EA269.6020802 at zone12.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > On 13-02-27 12:33 PM, Chris Cargile wrote: > > the Moin system will get us away from the Atlassian licensing hassle > > AND would tie in great for enabling a new website for the MM3 release, > Um... Chris, you do realize that we're experience software developers > working on a project under the banner of the free software foundation? > We're reasonably familiar with licensing issues and how they relate to > mailman! The message you sent (which I've mostly snipped) is not only > un-timely at this point so long after the decision about switching was > made but also seems a little patronizing in context. > > > Would the merges accepted propogate document changes to the package > > repos or are we referring to a merge against a documents-repo that is > > somewhere I don't know of. I'm still confused on where the sphinx > > documentation plays into it (is that maybe like building javadocs > > only, instead it does so for python, maybe) > > There is a docs directory in each project. There is no separate docs repo. > > Mailman's is here: > > https://bazaar.launchpad.net/~mailman-coders/mailman/3.0/files/head:/src/mailman/docs/ > > Postorius' is here: > > https://bazaar.launchpad.net/~mailman-coders/postorius/trunk/files/head:/src/postorius/doc/ > > and I don't have a link for Hyperkitty's handy but I'm sure you can find > it yourself. > > And now my turn to border on patronizing: My recommendation is that as > a new contributor, you should really stick to editing the wiki until you > have a sense of what you're doing and let the devs maintain the > documentation for their own packages. > > Terri > > > > > ------------------------------ > > Message: 3 > Date: Wed, 27 Feb 2013 22:59:40 -0500 > From: Barry Warsaw > To: mailman-developers at python.org > Subject: Re: [Mailman-Developers] background on maintaining the > documentation (was RE: Mailman-Developers Digest, Vol 286, Issue 9) > Message-ID: <20130227225940.65ce4d94 at anarchist.wooz.org> > Content-Type: text/plain; charset=US-ASCII > > On Feb 27, 2013, at 02:33 PM, Chris Cargile wrote: > > >the Moin system will get us away from the Atlassian licensing hassle AND > >would tie in great for enabling a new website for the MM3 release, > > I'm really hoping we can get onto Moin soon, not only for the above good > reasons, but also because of the free software issue, and because -- while > generous -- it's still a big hassle to deal with our Confluence hosting > provider when problems come up. I'm very confident we can find a > Moin-based > wiki a good home. > > >The documentation is maintained to some level in Atlassian, > pythonhosted.org, > >and the bzr repos (, other places?) per package, so Terri explained that > >Atlassian is the main location for how-to's, admin guides, and GSOC stuff. > >Otherwise, for simplicity, the packages have docs and doctests, in the > >individual package themselves > > I'm a big fan of having as much documentation in the source repository as > possible. I love a good wiki, but everything needs gardening and > documentation seems better suited for version control systems. Not all > documentation need be testable, but that which can be works great being > part > of the source tree. (The current doctest suite is I think of mixed > quality; > some of the older doctests conflated too much bad-path testing which makes > it > more difficult to read as documentation. I've been migrating much of that > to > unittests, in order to improve the readability and good-path flow of the > documentation.) > > It's also much easier to review and merge documentation changes via our > dvcs > tools. > > One thing that's missing is better overview documentation. That's long > been > on my list of things to improve. > > >Would the merges accepted propogate document changes to the package repos > or > >are we referring to a merge against a documents-repo that is somewhere I > >don't know of. I'm still confused on where the sphinx documentation plays > >into it (is that maybe like building javadocs only, instead it does so for > >python, maybe) > > The pythonhosted.org (formerly packages.python.org) documentation is > generated > from the source tree via `python setup.py build_sphinx`. You can build it > and > view it locally the same way. `python setup.py upload_docs` is what gets > the > new documentation uploaded, but I've just created a project on > readthedocs.org > so I think we should migrate there as our primary online documentation > source. The nice thing is that gets automatically updated when we push > updates to lp:mailman (i.e. trunk). > > Cheers, > -Barry > > > ------------------------------ > > Message: 4 > Date: Wed, 27 Feb 2013 23:12:07 -0500 > From: Barry Warsaw > To: mailman-developers at python.org > Subject: Re: [Mailman-Developers] Mailman-Developers Digest, Vol 286, > Issue 7 > Message-ID: <20130227231207.1e281f5f at anarchist.wooz.org> > Content-Type: text/plain; charset=US-ASCII > > (I really should catch up on all the threads before I start responding. > Sigh, > it's been a long day. ;) > > On Feb 26, 2013, at 10:38 AM, Terri Oda wrote: > > >Barry just uses the blog functionality as a news area; I'm guessing a > "recent > >news" page would probably suffice for this. I expect we'll keep the > >Confluence wiki around for a little while after the migration, but since > it's > >a minor hassle to get our license renewed, I expect it will lapse > eventually. > > I mostly stopped blogging on Confluence, even for new releases, since it's > actually kind of a pain. I should blog more Mailman stuff on my own blog > (www.wefearchange.org) and will definitely do so after Pycon. > > >I still have a todo list item reminding me that we'd like a new website > for > >Mailman 3.0's release (including cleaning up the myriad different docs > >available for previous versions) so maybe at that point we'll go back to > >using the front page for news updates. > > Of course, I'm +1 on a new website for MM3, and I'd *dearly* love to get > rid > of the ht2html based web site on www.list.org. I bet Sphinx can give us > something awesome, and beautifully themed to our new logo and color scheme. > > Cheers, > -Barry > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > http://mail.python.org/mailman/listinfo/mailman-developers > > > ------------------------------ > > End of Mailman-Developers Digest, Vol 286, Issue 10 > *************************************************** > From fehwalker at gmail.com Sat Mar 2 00:02:48 2013 From: fehwalker at gmail.com (Bryan Fullerton) Date: Fri, 01 Mar 2013 18:02:48 -0500 Subject: [Mailman-Developers] Background, was Re: Mailman-Developers Digest, Vol 286, Issue 10 In-Reply-To: References: Message-ID: <51313398.1090309@gmail.com> On 13-03-01 01:43 PM, Chris Cargile wrote: > On the matter of communications, I might hope to take yet a moment to > address my goals, motivations, and expectations for contributing to the > quite-worthy, well-thought-out and respectable mailman3 *team* effort and > re-establish what might be already seemingly clear to some... Well, that was... energetic. Anyway, this seems an auspicious time to say I'm also paying attention to this list again, having finally excavated my gmail archive. Although I'm no longer hosting mailing lists for fun and a notable lack of profit I will likely muck about with the software, point out broken things from time to time, and possibly even try my hand at fixing them. Thanks, Bryan From tom.browder at gmail.com Sat Mar 2 17:38:12 2013 From: tom.browder at gmail.com (Tom Browder) Date: Sat, 2 Mar 2013 10:38:12 -0600 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) Message-ID: Earlier I was pointed to the REST API for programatically generating a new list--looks good. However, the docs mention a default set of attributes for a new list and I wonder if there are yet any other choices. I guess the real question for me is: is there a templating system in MM 3 so that different list types can be defined? My search through the code so far hasn't found such except for language templates. Having just agonizingly set up a true (IMHO) read-only list under Mailman 2, I think such a template to choose (at least to start from) would be very helpful in Mailman 3. (I don't doubt there is an easier way under Mailman 2, but I find the various inputs in the web interface too scattered around for my tastes.) Best regards, -Tom From barry at list.org Tue Mar 5 21:23:39 2013 From: barry at list.org (Barry Warsaw) Date: Tue, 5 Mar 2013 15:23:39 -0500 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) In-Reply-To: References: Message-ID: <20130305152339.7a5b221d@anarchist.wooz.org> On Mar 02, 2013, at 10:38 AM, Tom Browder wrote: >Earlier I was pointed to the REST API for programatically generating a new >list--looks good. However, the docs mention a default set of attributes for >a new list and I wonder if there are yet any other choices. > >I guess the real question for me is: is there a templating system in MM 3 so >that different list types can be defined? My search through the code so far >hasn't found such except for language templates. Yes, these are called "list styles". See the IStyle interface in src/mailman/interfaces/styles.py for the API and src/mailman/styles/default.py for the two built-in styles, both essentially legacy styles. Note that styles are only applied when a list is created, so it is better to think of them as the default set of attributes for a list. IOW, if you changed a style after a list is created, the list attributes do not change. In fact, the mailing list doesn't record what styles were applied to it. The mailman.cfg file has a [styles] section, with a `paths` variable and a `default` variable. The `paths` variable names Python dotted-module paths which are searched for IStyle implementations. Thus, if you arranged for your MM3 installation to include on sys.path, the package mylocal.mailman.styles, you could put your own styles in there and Mailman should find them automatically. At that point, you can use one of your named styles as the default (via the `[styles]default` variable), or you can specify the style to use when creating a new list through the REST API. See src/mailman/rest/docs/list.rst for details. >Having just agonizingly set up a true (IMHO) read-only list under Mailman 2, >I think such a template to choose (at least to start from) would be very >helpful in Mailman 3. (I don't doubt there is an easier way under Mailman 2, >but I find the various inputs in the web interface too scattered around for >my tastes.) Hopefully the above makes sense, and provides enough information to play with the feature in MM3. I'm absolutely open to ideas for making list styles easier to add, customize, and use. Cheers, -Barry From tom.browder at gmail.com Wed Mar 6 02:51:45 2013 From: tom.browder at gmail.com (Tom Browder) Date: Tue, 5 Mar 2013 19:51:45 -0600 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) In-Reply-To: <20130305152339.7a5b221d@anarchist.wooz.org> References: <20130305152339.7a5b221d@anarchist.wooz.org> Message-ID: On Tue, Mar 5, 2013 at 2:23 PM, Barry Warsaw wrote: > On Mar 02, 2013, at 10:38 AM, Tom Browder wrote: ... >>I guess the real question for me is: is there a templating system in MM 3 so >>that different list types can be defined? ... > Yes, these are called "list styles". See the IStyle interface in > src/mailman/interfaces/styles.py for the API and src/mailman/styles/default.py > for the two built-in styles, both essentially legacy styles. Ah, that's where it is! (And I assume ALL "attributes" are defined there.) But to my non-Python eyes I see only one actually defined. But there is where we could add some other mailman-defined styles, correct? > Note that styles are only applied when a list is created, so it is better to > think of them as the default set of attributes for a list. IOW, if you > changed a style after a list is created, the list attributes do not change. > In fact, the mailing list doesn't record what styles were applied to it. That makes sense to me. > The mailman.cfg file has a [styles] section, with a `paths` variable and a > `default` variable. The `paths` variable names Python dotted-module paths > which are searched for IStyle implementations. Thus, if you arranged for your > MM3 installation to include on sys.path, the package mylocal.mailman.styles, > you could put your own styles in there and Mailman should find them > automatically. Great! > At that point, you can use one of your named styles as the default (via the > `[styles]default` variable), or you can specify the style to use when creating > a new list through the REST API. See src/mailman/rest/docs/list.rst for > details. Thanks, Barry! Best regards, -Tom From turnbull at sk.tsukuba.ac.jp Wed Mar 6 04:28:43 2013 From: turnbull at sk.tsukuba.ac.jp (Stephen J. Turnbull) Date: Wed, 06 Mar 2013 12:28:43 +0900 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) In-Reply-To: <20130305152339.7a5b221d@anarchist.wooz.org> References: <20130305152339.7a5b221d@anarchist.wooz.org> Message-ID: <874ngpjjf8.fsf@uwakimon.sk.tsukuba.ac.jp> Barry Warsaw writes: > Note that styles are only applied when a list is created, so it is > better to think of them as the default set of attributes for a > list. I'm unhappy with the name, then. "Style defaults" would be pedantically correct. > IOW, if you changed a style after a list is created, the list > attributes do not change. In fact, the mailing list doesn't record > what styles were applied to it. OTOH, would it really be that burdensome to keep styles in the database and allow styles to be updated with appropriate effects on the lists? A style *change* that could be applied domain-wide (and DRY-ly!) without affecting other domains on that host would be a killer feature. Or is there another way to accomplish that? From terri at zone12.com Wed Mar 6 08:46:43 2013 From: terri at zone12.com (Terri Oda) Date: Wed, 06 Mar 2013 00:46:43 -0700 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) In-Reply-To: <874ngpjjf8.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20130305152339.7a5b221d@anarchist.wooz.org> <874ngpjjf8.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <5136F463.7010800@zone12.com> On 13-03-05 8:28 PM, Stephen J. Turnbull wrote: > OTOH, would it really be that burdensome to keep styles in the > database and allow styles to be updated with appropriate effects on > the lists? A style *change* that could be applied domain-wide (and > DRY-ly!) without affecting other domains on that host would be a > killer feature. Or is there another way to accomplish that? > Would this maybe be viable as a GSoC project? Terri From stephen at xemacs.org Wed Mar 6 14:11:37 2013 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 06 Mar 2013 22:11:37 +0900 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) In-Reply-To: <5136F463.7010800@zone12.com> References: <20130305152339.7a5b221d@anarchist.wooz.org> <874ngpjjf8.fsf@uwakimon.sk.tsukuba.ac.jp> <5136F463.7010800@zone12.com> Message-ID: <87wqtkisfq.fsf@uwakimon.sk.tsukuba.ac.jp> Terri Oda writes: > > On 13-03-05 8:28 PM, Stephen J. Turnbull wrote: > > OTOH, would it really be that burdensome to keep styles in the > > database and allow styles to be updated with appropriate effects on > > the lists? A style *change* that could be applied domain-wide (and > > DRY-ly!) without affecting other domains on that host would be a > > killer feature. Or is there another way to accomplish that? > > > Would this maybe be viable as a GSoC project? I'm not sure it's big enough by itself. (Let's put it this way: I have too much respect for the FLUFL's design skills to believe it's big enough!) But I'll take Barry's word for it. Maybe combining it with some of the "by popular request" styles? ("True anonymous", "true read-only", etc.) From terri at zone12.com Wed Mar 6 17:58:44 2013 From: terri at zone12.com (Terri Oda) Date: Wed, 06 Mar 2013 09:58:44 -0700 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) In-Reply-To: <87wqtkisfq.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20130305152339.7a5b221d@anarchist.wooz.org> <874ngpjjf8.fsf@uwakimon.sk.tsukuba.ac.jp> <5136F463.7010800@zone12.com> <87wqtkisfq.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <513775C4.5050101@zone12.com> On 13-03-06 6:11 AM, Stephen J. Turnbull wrote: > Terri Oda writes: > > > > On 13-03-05 8:28 PM, Stephen J. Turnbull wrote: > > > OTOH, would it really be that burdensome to keep styles in the > > > database and allow styles to be updated with appropriate effects on > > > the lists? A style *change* that could be applied domain-wide (and > > > DRY-ly!) without affecting other domains on that host would be a > > > killer feature. Or is there another way to accomplish that? > > > > > Would this maybe be viable as a GSoC project? > > I'm not sure it's big enough by itself. (Let's put it this way: I > have too much respect for the FLUFL's design skills to believe it's > big enough!) But I'll take Barry's word for it. > > Maybe combining it with some of the "by popular request" styles? > ("True anonymous", "true read-only", etc.) That was what I was thinking. Or equally, combining it with the necessary interface changes (which also shouldn't be hard, but would necessitate learning postorius so that's probably enough extra). If anyone's got time to write up something and put it on the wiki, that would be awesome. I'm sadly stuck doing other paperwork the next few nights so I'm pretty sure one of you can get to writing up a description faster than I will. Terri From follybeachris at gmail.com Wed Mar 6 20:44:48 2013 From: follybeachris at gmail.com (Chris Cargile) Date: Wed, 6 Mar 2013 14:44:48 -0500 Subject: [Mailman-Developers] buildout instructions Message-ID: I am getting stuck during my buildout due to a mix-up b/w what versions zc.buildout and/or eggs are expected and am assuming this is an ongoing issue from zope, per a 9/6/12 developers-list message , I could not surpass the buildout step as the system complained about the ScriptBase module not being found and was hoping someone might kindly guide me past this fwiw, working through zc-buildout/recipe issues w/ python >=2.7 has been done, case these issues are related. Here is the my buildout-stacktrace in case someone can advise thanks! Chris From barry at list.org Wed Mar 6 21:34:28 2013 From: barry at list.org (Barry Warsaw) Date: Wed, 6 Mar 2013 15:34:28 -0500 Subject: [Mailman-Developers] buildout instructions In-Reply-To: References: Message-ID: <20130306153428.56f7a6c9@limelight.wooz.org> On Mar 06, 2013, at 02:44 PM, Chris Cargile wrote: >python >=2.7 has been done, case these issues are related. Here is the my >buildout-stacktrace in case >someone can advise That looks like a network issue actually. buildout can't seem to talk to server providing restish. I just tried to buildout a fresh checkout of the v3 branch and while I got errors trying to talk to http://ish.io, it did manage to grab 0.12.1 from PyPI afaict. Cheers, -Barry From barry at list.org Wed Mar 6 21:44:27 2013 From: barry at list.org (Barry Warsaw) Date: Wed, 6 Mar 2013 15:44:27 -0500 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) In-Reply-To: References: <20130305152339.7a5b221d@anarchist.wooz.org> Message-ID: <20130306154427.47e633a4@limelight.wooz.org> On Mar 05, 2013, at 07:51 PM, Tom Browder wrote: >> Yes, these are called "list styles". See the IStyle interface in >> src/mailman/interfaces/styles.py for the API and >> src/mailman/styles/default.py for the two built-in styles, both essentially >> legacy styles. > >Ah, that's where it is! (And I assume ALL "attributes" are defined >there.) But to my non-Python eyes I see only one actually defined. There are two classes in default.py, LegacyDefaultStyle and LegacyAnnounceOnly, both of which have @implementer(IStyle) decorators. This is the way you declare that a class implements a particular interface, and it's how Mailman auto-discovers available styles. >But there is where we could add some other mailman-defined styles, correct? Probably not. However, if we wanted to package some new "out-of-the-box" styles, we'd probably create a new module in that directory and add new classes there that declare they implement the IStyle. But MM3 is designed to be extensible, so your own styles don't need to be in this package directory. As long as they are on Python's sys.path, and defined in your own mailman.cfg file, Mailman should be able to find them and allow them to be used. Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From barry at list.org Wed Mar 6 21:54:55 2013 From: barry at list.org (Barry Warsaw) Date: Wed, 6 Mar 2013 15:54:55 -0500 Subject: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?) In-Reply-To: <874ngpjjf8.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20130305152339.7a5b221d@anarchist.wooz.org> <874ngpjjf8.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <20130306155455.6ecdccfb@limelight.wooz.org> On Mar 06, 2013, at 12:28 PM, Stephen J. Turnbull wrote: > > IOW, if you changed a style after a list is created, the list > > attributes do not change. In fact, the mailing list doesn't record > > what styles were applied to it. > >OTOH, would it really be that burdensome to keep styles in the >database and allow styles to be updated with appropriate effects on >the lists? A style *change* that could be applied domain-wide (and >DRY-ly!) without affecting other domains on that host would be a >killer feature. Or is there another way to accomplish that? Ideally, I'd like things to work this way, but it's a lot of work to get from here to there. Some of the issues that will have to be worked out include: - Do those attributes still live in the `mailinglist` table or do they get split up into separate tables? - Do you handle individual attribute overrides, and if so how? (e.g. I want an announce list, except with a higher max size because i'm using it to send audio files). - Do you handle one style or multiple styles per list, and if the latter, how do you handle application order and conflicts? - What happens when a style goes away, or new styles get added? how do you change styles that are associated with a particular list? - How do you plumb style choices through to the command line and REST UIs, and how do you present these options on the admin web ui? I think this could be an interesting GSoC project, but it might actually be *too* big for summer students. OTOH, if we work out a spec that answers some of the questions above and defines the semantics, the actual implementation work would probably be pretty interesting. Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From follybeachris at gmail.com Wed Mar 6 23:20:36 2013 From: follybeachris at gmail.com (Chris Cargile) Date: Wed, 6 Mar 2013 17:20:36 -0500 Subject: [Mailman-Developers] buildout instructions In-Reply-To: <20130306153428.56f7a6c9@limelight.wooz.org> References: <20130306153428.56f7a6c9@limelight.wooz.org> Message-ID: I was able to pip install restish and then built with success but am looking into the "./bin/test -vv" output shown, before I do 'mailman start': " ..Ran 334 tests with 1 failures and 1 errors Running mailman.testing.layers.LMTPLayer tests:: src/mailman/testing/helpers.py", line 258, in get_lmtp_client raise RuntimeError('Connection refused')" I should be understanding the how's and why's better after reading up about LMTP (is this b/c I need a package again?), as it looks like there's a good documentation describing this - i'll be diving into that real soon (I'm off for free pizza/tech-talk) Thanks Barry On Wed, Mar 6, 2013 at 3:34 PM, Barry Warsaw wrote: > On Mar 06, 2013, at 02:44 PM, Chris Cargile wrote: > > >python >=2.7 has been done, case these issues are related. Here is the my > >buildout-stacktrace in case > >someone can advise > > That looks like a network issue actually. buildout can't seem to talk to > server providing restish. > > I just tried to buildout a fresh checkout of the v3 branch and while I got > errors trying to talk to http://ish.io, it did manage to grab 0.12.1 from > PyPI > afaict. > > Cheers, > -Barry > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > http://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: > http://mail.python.org/mailman/options/mailman-developers/follybeachris%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > From paul at boddie.org.uk Thu Mar 7 22:58:04 2013 From: paul at boddie.org.uk (Paul Boddie) Date: Thu, 7 Mar 2013 22:58:04 +0100 Subject: [Mailman-Developers] Wiki Migration Update In-Reply-To: <201302252152.37714.paul@boddie.org.uk> References: <201302250001.18261.paul@boddie.org.uk> <512BAF20.6090700@zone12.com> <201302252152.37714.paul@boddie.org.uk> Message-ID: <201303072258.04648.paul@boddie.org.uk> On Monday 25 February 2013 21:52:37 Paul Boddie wrote: > > Well, I'll let you know what progress I make, and I guess Barry and I will > try and work on the hosting aspect as the process nears completion. So, to follow up on this, I have updated the snapshot of migrated data: http://mmwiki.boddie.org.uk/ Certain things have been improved since the last update: * Tables are now supported, although it is likely that some tables will not appear entirely correctly, and I have yet to support cell attributes. See http://mmwiki.boddie.org.uk/DEV/LogoSubmissions for a fairly complicated example. * Attachments are also supported, as illustrated in the above example. To support tables, I'm using a table parser that I developed to handle the general need for a more flexible table representation, and this does seem to be required to handle various actual tables in the Mailman Wiki (such as the list in one of the logo submissions in the above example). It's documented here: http://moinmo.in/ParserMarket/ImprovedTableParser Obviously, lots of issues remain, including... * Some links in the most recent XHTML-based revisions won't work because I have to set the link target properly for that particular style of links. * In the Confluence markup, combinations of formatting markers can cause problems, and the conversion to XHTML format actually produced ill-formed XML. See http://mmwiki.boddie.org.uk/COM/donate_to_the_GNU_Mailman_project for an example. * The issue accessing page names with question marks remains as I'm still using mod_rewrite in my deployment of this site, but it isn't a real problem for a "proper" deployment of Moin. * Macro support still needs to be completed, although I don't think that macro usage is particularly diverse on the Mailman Wiki, meaning that only a few different ones are used. Some issues, like the handling of anchor tags on http://mmwiki.boddie.org.uk/COM/Organizations_that_use_Mailman need to be reviewed and fixed. I aim to continue the process of developing the converter over the coming weeks, and I hope to bring it to a state of completion in that time. Paul From terri at zone12.com Thu Mar 7 23:45:22 2013 From: terri at zone12.com (Terri Oda) Date: Thu, 07 Mar 2013 15:45:22 -0700 Subject: [Mailman-Developers] Wiki Migration Update In-Reply-To: <201303072258.04648.paul@boddie.org.uk> References: <201302250001.18261.paul@boddie.org.uk> <512BAF20.6090700@zone12.com> <201302252152.37714.paul@boddie.org.uk> <201303072258.04648.paul@boddie.org.uk> Message-ID: <51391882.2090303@zone12.com> On 03/07/2013 02:58 PM, Paul Boddie wrote: > So, to follow up on this, I have updated the snapshot of migrated data: > > http://mmwiki.boddie.org.uk/ Looking great, Paul! One possible item of concern is the way code snippets look here: http://mmwiki.boddie.org.uk/DEV/A%205%20Minute%20Guide%20to%20Get%20the%20Mailman%20Web%20UI%20Running%20%28only%20for%20development%29 But I can see elsewhere that preformatted stuff is fine: http://mmwiki.boddie.org.uk/DOC/How%20can%20I%20Mass%20Subscribe%20a%20list%20with%20real%20names So it's possible that we'll need to just hand-fix that one page. Also, in browsing the FAQ for that second example, I noticed it's telling me that a page doesn't exist and yet giving me links to more pages that it claims don't exist. I assume this is still related the problem you were having earlier with question marks, I think it was? But it may need more checking if you thought that was fully fixed. Is there a plugin or something to have moin generate short links? As you can tell from above, we're not exactly email-friendly (or readable) by default. Terri From paul at boddie.org.uk Fri Mar 8 00:27:31 2013 From: paul at boddie.org.uk (Paul Boddie) Date: Fri, 8 Mar 2013 00:27:31 +0100 Subject: [Mailman-Developers] Wiki Migration Update In-Reply-To: <51391882.2090303@zone12.com> References: <201302250001.18261.paul@boddie.org.uk> <201303072258.04648.paul@boddie.org.uk> <51391882.2090303@zone12.com> Message-ID: <201303080027.31932.paul@boddie.org.uk> On Thursday 07 March 2013 23:45:22 Terri Oda wrote: > On 03/07/2013 02:58 PM, Paul Boddie wrote: > > So, to follow up on this, I have updated the snapshot of migrated data: > > > > http://mmwiki.boddie.org.uk/ > > Looking great, Paul! Thanks! > One possible item of concern is the way code snippets look here: > http://mmwiki.boddie.org.uk/DEV/A%205%20Minute%20Guide%20to%20Get%20the%20M >ailman%20Web%20UI%20Running%20%28only%20for%20development%29 > > But I can see elsewhere that preformatted stuff is fine: > http://mmwiki.boddie.org.uk/DOC/How%20can%20I%20Mass%20Subscribe%20a%20list >%20with%20real%20names > > So it's possible that we'll need to just hand-fix that one page. I think Moin has a problem with the generated syntax, and I'll try and figure out what that problem is because I think I've seen it elsewhere. > Also, in browsing the FAQ for that second example, I noticed it's > telling me that a page doesn't exist and yet giving me links to more > pages that it claims don't exist. I assume this is still related the > problem you were having earlier with question marks, I think it was? > But it may need more checking if you thought that was fully fixed. Yes, pages with question marks won't be served because of the mod_rewrite bug, but I can assure you they are still there. I'll try and get my hosting provider to suggest an alternative, but the preferred way of serving the pages wouldn't suffer from this. > Is there a plugin or something to have moin generate short links? As > you can tell from above, we're not exactly email-friendly (or readable) > by default. The %-encoding for spaces can be avoided by using underscores instead, which Moin recognises as being equivalent and which helps quite a bit. Short links could be done with redirect pages, and there may be some things that help with this, but I don't recall seeing anything specific. Paul From follybeachris at gmail.com Fri Mar 8 22:50:24 2013 From: follybeachris at gmail.com (Chris Cargile) Date: Fri, 8 Mar 2013 16:50:24 -0500 Subject: [Mailman-Developers] unable to tear down.. [errno 98] Message-ID: Is the smtp port setting declared in a configuration file used to bind a mailman instance to a particular process (such as the MTA) on a particular port? I tried looking through the configuration files to identify the location to which I thought the stmpd was trying to bind but did not figure out how it worked I am hoping to learn how this works (and to hack my configuration, if needed) to get past the SMTP/RestLayer teardowns, and am stuck getting: [Errno 98] Address already in use (log file ) From follybeachris at gmail.com Mon Mar 11 14:47:09 2013 From: follybeachris at gmail.com (Chris Cargile) Date: Mon, 11 Mar 2013 09:47:09 -0400 Subject: [Mailman-Developers] unable to tear down.. [errno 98] In-Reply-To: References: Message-ID: I am not getting no failures but got around the 'address in use' error message (..and in its place have discovered a world of possible other error messages, but that's good!) I hope to offer suggestions on ways to make developing easier for newcomers after succeeding in getting a test score of 100% and to provide a URL from which an image file (.vmdk format) can be wget'ed to a more permanent home for a shareable development-ready machine image - the second goal will be a quicker part of the effort I'm hoping since I am learning all this remotely via AWS (which does not cost anything) On Fri, Mar 8, 2013 at 4:50 PM, Chris Cargile wrote: > Is the smtp port setting declared in a configuration file used to bind a > mailman instance to a particular process (such as the MTA) on a particular > port? > > I tried looking through the configuration files to identify the location > to which I thought the stmpd was trying to bind but did not figure out how > it worked > > I am hoping to learn how this works (and to hack my configuration, if > needed) to get past the SMTP/RestLayer teardowns, and am stuck getting: > > [Errno 98] Address already in use (log file > ) > From barry at list.org Mon Mar 11 20:43:33 2013 From: barry at list.org (Barry Warsaw) Date: Mon, 11 Mar 2013 15:43:33 -0400 Subject: [Mailman-Developers] unable to tear down.. [errno 98] In-Reply-To: References: Message-ID: <20130311154333.4e994eb1@anarchist.wooz.org> Sorry, I'm just plain slammed trying to get ready for Pycon. On Mar 08, 2013, at 04:50 PM, Chris Cargile wrote: >Is the smtp port setting declared in a configuration file used to bind a >mailman instance to a particular process (such as the MTA) on a particular >port? Yes. The base configuration values are in src/mailman/config/schema.cfg. These get overridden/specialized by src/mailman/config/mailman.cfg by default, and whatever mailman.cfg file you might have installed when you run MM3 in production. In a testing environment, src/mailman/testing/testing.cfg is the top configuration file. Look in the [mta] section and you'll see that by default, Mailman connects to localhost:25. This changes to localhost:9025 when running the test suite. >I tried looking through the configuration files to identify the location to >which I thought the stmpd was trying to bind but did not figure out how it >worked MM3 uses the lazr.config system. http://pythonhosted.org/lazr.config/ >I am hoping to learn how this works (and to hack my configuration, if >needed) to get past the SMTP/RestLayer teardowns, and am stuck getting: > >[Errno 98] Address already in use (log >file >) If you're getting this during the tests, it almost always means that the Python subprocess binding to that address didn't exit. The test suite (and MM3 in general) is pretty careful about shutting down its subprocesses, but sometimes this fails. Use killall or friends to actually stop the process. We use lazr.smtptest to start up the SMTPd for testing, and this should properly set the reuse flag on the socket. Cheers, -Barry From barry at list.org Mon Mar 11 20:44:59 2013 From: barry at list.org (Barry Warsaw) Date: Mon, 11 Mar 2013 15:44:59 -0400 Subject: [Mailman-Developers] unable to tear down.. [errno 98] In-Reply-To: References: Message-ID: <20130311154459.03efaab3@anarchist.wooz.org> On Mar 11, 2013, at 09:47 AM, Chris Cargile wrote: >I hope to offer suggestions on ways to make developing easier for newcomers >after succeeding in getting a test score of 100% and to provide a URL from >which an image file (.vmdk format) can be wget'ed to a more permanent home >for a shareable development-ready machine image - the second goal will be a >quicker part of the effort I'm hoping since I am learning all this remotely >via AWS (which does not cost anything) We look forward to your suggestions! If you have specific documentation fixes, please do a merge proposal. If you have questions about how to contribute patches to Mailman, don't hesitate to ask. :) -Barry From terri at zone12.com Mon Mar 11 20:59:13 2013 From: terri at zone12.com (Terri Oda) Date: Mon, 11 Mar 2013 13:59:13 -0600 Subject: [Mailman-Developers] GSoC 2013 ideas page updates Message-ID: <513E3791.5020506@zone12.com> Just FYI: I've linked Mailman from the PSF GSoC 2013 page here: http://wiki.python.org/moin/SummerOfCode/2013 I don't know that it'll result in us attracting more students just yet (again, org applications don't open 'till March 18th) but if it seems like there's a small surge after this weekend, you can blame me. GSoC's running on a much later schedule this year than last, so we've got a lot of anxious students worrying about deadlines even though it's pretty early by the schedule. I've also updated our GSoC page with a few more ideas from my mental Postorius queue: http://wiki.list.org/display/DEV/Google+Summer+of+Code+2013 I'd particularly like to see some more hyperkitty ideas up -- Aurelien, are you able to mentor a student this summer? Anyone else working on hyperkitty who'd like to chime in? Pipermail has been a weakness for a while so I expect there'll be students who are really interested in improving it if we give them some starting points. Those of you coming to the sprints can expect me to harass you for ideas/refinement at PyCon next week, of course. But if you, like me, are going through bug queues right now trying to prepare for pycon and figure out what to work on at the sprints... now's a great time to make a list of "I don't think we'll get to this" features to put up as potential GSoC projects! Terri From stephen at xemacs.org Tue Mar 12 03:35:29 2013 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 12 Mar 2013 11:35:29 +0900 Subject: [Mailman-Developers] GSoC 2013 ideas page updates In-Reply-To: <513E3791.5020506@zone12.com> References: <513E3791.5020506@zone12.com> Message-ID: <87li9tfiq6.fsf@uwakimon.sk.tsukuba.ac.jp> Terri Oda writes: > I don't know that it'll result in us attracting more students just yet > (again, org applications don't open 'till March 18th) but if it seems > like there's a small surge after this weekend, you can blame me. s/blame/thank/ Speaking-for-myself-wink-wink-nudge-ly y'rs, From mahendra007.s at gmail.com Thu Mar 14 18:41:50 2013 From: mahendra007.s at gmail.com (mahendra singh meena) Date: Thu, 14 Mar 2013 23:11:50 +0530 Subject: [Mailman-Developers] Error in Archive unpack while setting up mailman client 1.0.0 Message-ID: This is my first time I am setting up mailman.Using step-by-step procedure from http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI+running when i am doing :- $ cd mailman.client $ python setup.py develop I am gettin following error :- ... Processing mocker-1.1.1.tar.bz2 error: Not a recognized archive type: /tmp/easy_install-kM8hYI/mocker-1.1.1.tar.bz2 Any clue how to solve this ? I asked the same on irc but i feel its quite inactive might be due to the time-zone difference with other developers. One more thing that I noticed during the same step is when it downloads mocker and other requirements using script python2.7/site-packages/distribute-0.6.10-py2.7.egg/setuptools/package_index.py It takes proxy not into account when opening url in open_with_auth(url).So, I think we shall modify it to take proxy option also. Please guide me if I have skipped any point or taken a wrong step. Regards Mahendra From flo.fuchs at gmail.com Thu Mar 14 20:23:03 2013 From: flo.fuchs at gmail.com (Florian Fuchs) Date: Thu, 14 Mar 2013 12:23:03 -0700 Subject: [Mailman-Developers] Error in Archive unpack while setting up mailman client 1.0.0 In-Reply-To: References: Message-ID: Hi Mahendra, this seems to be caused by the "mocker" library being distributed as a bzip2 archive. A while ago another developer ran into the same problem and solved it by installing bzip2 separately and then switching to python 2.6 (IIRC). Obviously being stuck with py2.6 is a less then ideal solution, but if you can wait a little: I am currently doing some work on mailman.client to prepare for the Pycon development sprints starting on monday. Part of that work is replacing the "mocker" library with another one called "mock", which is distributed as a less exotic gzipped tarball. This is no solution for your general problem installing bzipped python packages, but at least it will most probably solve this particular issue... I'll post a message here when I'm done... Cheers Florian 2013/3/14 mahendra singh meena > This is my first time I am setting up mailman.Using step-by-step > procedure from > http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI+running > > when i am doing :- > $ cd mailman.client > $ python setup.py develop > > I am gettin following error :- > ... > Processing mocker-1.1.1.tar.bz2 > error: Not a recognized archive type: > /tmp/easy_install-kM8hYI/mocker-1.1.1.tar.bz2 > > Any clue how to solve this ? > I asked the same on irc but i feel its quite inactive might be due to > the time-zone difference with other developers. > > One more thing that I noticed during the same step is when it > downloads mocker and other requirements using script > > python2.7/site-packages/distribute-0.6.10-py2.7.egg/setuptools/package_index.py > It takes proxy not into account when opening url in > open_with_auth(url).So, I think we shall modify it to take proxy > option also. > > Please guide me if I have skipped any point or taken a wrong step. > > Regards > Mahendra > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > http://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: > http://mail.python.org/mailman/options/mailman-developers/flo.fuchs%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > From mahendra007.s at gmail.com Sat Mar 16 19:16:35 2013 From: mahendra007.s at gmail.com (mahendra singh meena) Date: Sat, 16 Mar 2013 23:46:35 +0530 Subject: [Mailman-Developers] Error in Archive unpack while setting up mailman client 1.0.0 In-Reply-To: References: Message-ID: Thanks a lot Florian, As you suggested I bypassed above issue by replacing "mocker" library with "mock". Its really good to see the development server running on my system. One more thing, I know basic Python and few basics of Django but willing to take part in the upcoming mailman PyCon sprint ( http://wiki.list.org/display/DEV/PyCon+Sprint+2013 ), so that I can get involved and gather more knowledge from you guys about Mailman development. So can I really take part in the sprint remotely ? Regards On Fri, Mar 15, 2013 at 12:53 AM, Florian Fuchs wrote: > Hi Mahendra, > > this seems to be caused by the "mocker" library being distributed as a bzip2 > archive. A while ago another developer ran into the same problem and solved > it by installing bzip2 separately and then switching to python 2.6 (IIRC). > Obviously being stuck with py2.6 is a less then ideal solution, but if you > can wait a little: I am currently doing some work on mailman.client to > prepare for the Pycon development sprints starting on monday. Part of that > work is replacing the "mocker" library with another one called "mock", which > is distributed as a less exotic gzipped tarball. This is no solution for > your general problem installing bzipped python packages, but at least it > will most probably solve this particular issue... > > I'll post a message here when I'm done... > > Cheers > Florian > > > > > 2013/3/14 mahendra singh meena >> >> This is my first time I am setting up mailman.Using step-by-step >> procedure from >> http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI+running >> >> when i am doing :- >> $ cd mailman.client >> $ python setup.py develop >> >> I am gettin following error :- >> ... >> Processing mocker-1.1.1.tar.bz2 >> error: Not a recognized archive type: >> /tmp/easy_install-kM8hYI/mocker-1.1.1.tar.bz2 >> >> Any clue how to solve this ? >> I asked the same on irc but i feel its quite inactive might be due to >> the time-zone difference with other developers. >> >> One more thing that I noticed during the same step is when it >> downloads mocker and other requirements using script >> >> python2.7/site-packages/distribute-0.6.10-py2.7.egg/setuptools/package_index.py >> It takes proxy not into account when opening url in >> open_with_auth(url).So, I think we shall modify it to take proxy >> option also. >> >> Please guide me if I have skipped any point or taken a wrong step. >> >> Regards >> Mahendra >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers at python.org >> http://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: >> http://mail.python.org/mailman/options/mailman-developers/flo.fuchs%40gmail.com >> >> Security Policy: http://wiki.list.org/x/QIA9 > > -- 4th Year Dual Degree | Dept. of CSE | IIT Kharagpur, India From mgill25 at outlook.com Wed Mar 20 13:36:05 2013 From: mgill25 at outlook.com (Manish Gill) Date: Wed, 20 Mar 2013 18:06:05 +0530 Subject: [Mailman-Developers] Interested in GSoC 2013 Message-ID: Hello. I'm interested in Participating in Google Summer of Code 2013 and have been searching for good projects in Python. Thought I'd drop by and introduce myself. :) I'm a 22 years old CS student, and have worked been working in Python for the past year or so, primarily web stuff in Flask/Django. 2 projects in particular caught my eye and I hope to work on either one of them with Mailman this summer. :) - The first is the Alternative authentication possibilities - as I've worked on OAuth integration with Facebook/Twitter in a few Flask applications. - The second is the Anti-spam/anti-abuse in Mailman - I admit I don't know much about how anti-spam techniques work, but that's preciously why I'm interested in working on this one, so I can learn new things. :) I've set up a basic virtualenv with Mailman and will be going through the code in the next few days (lots of code!). Thanks! From terri at zone12.com Wed Mar 20 22:24:35 2013 From: terri at zone12.com (Terri Oda) Date: Wed, 20 Mar 2013 14:24:35 -0700 Subject: [Mailman-Developers] Interested in GSoC 2013 In-Reply-To: References: Message-ID: <514A2913.1030904@zone12.com> If you're looking for suggestions, I'd suggest you focus on the anti-spam stuff. We've all gotten pretty hooked on Mozilla Persona for authentication, to the point where we may not bother with other authentication methods in the early releases, so the spam stuff is much more likely to be useful soon! Also, we're still sprinting at PyCon today and tomorrow, so if you're already set up, now's a great time to hang out in IRC while all the devs are focusing on writing code. Terri On 13-03-20 5:36 AM, Manish Gill wrote: > Hello. > > I'm interested in Participating in Google Summer of Code 2013 and have > been searching for good projects in Python. Thought I'd drop by and > introduce myself. :) > > I'm a 22 years old CS student, and have worked been working in Python > for the past year or so, primarily web stuff in Flask/Django. > > 2 projects in particular caught my eye and I hope to work on either one > of them with Mailman this summer. :) > > - The first is the Alternative authentication possibilities - as I've > worked on OAuth integration with Facebook/Twitter in a few Flask > applications. > > - The second is the Anti-spam/anti-abuse in Mailman - I admit I don't > know much about how anti-spam techniques work, but that's preciously why > I'm interested in working on this one, so I can learn new things. :) > > I've set up a basic virtualenv with Mailman and will be going through > the code in the next few days (lots of code!). > > Thanks! > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > http://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: http://mail.python.org/mailman/options/mailman-developers/terri%40zone12.com > > Security Policy: http://wiki.list.org/x/QIA9 > From mark at msapiro.net Tue Mar 26 02:42:11 2013 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 Mar 2013 18:42:11 -0700 Subject: [Mailman-Developers] Mailman log access on cPanel Message-ID: <5150FCF3.8030109@msapiro.net> Many cPanel Mailman users have issues that are difficult to resolve because they don't have access to Mailman's logs. I spoke with a cPanel developer about this at PyCon, and he has created a feature request at . If you are interested in this, go to the above URL and vote for it. Voting requires registration on the site and that requires providing your name and email address and then waiting for a password to be mailed, but apparently anyone can do it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rahul.nbg at gmail.com Thu Mar 28 22:02:11 2013 From: rahul.nbg at gmail.com (Rahul Gaur) Date: Fri, 29 Mar 2013 02:32:11 +0530 Subject: [Mailman-Developers] GSOC 2013 : Authenticated REST-API in Postorius/Django Message-ID: Hello, I have been searching for Python/Django projects for a while and I stumbled upon the Mailman ideas page today. I am very much interested in discussing more about the *Authenticated REST-API in Postorius/Django *and I hope to work on it over the summer *, *but let me first introduce my self. I am into third year of my engineering (Computer Science) and I have been using Python since my first year and for the past couple of months I have been using Django for experimental projects at college and for a interest based social networking site(initially started from pinax). I have already cloned the Mailman code base and it's up and running , I will go through the source code in next couple of days. I haven't implemented RESTful API's before , but I have started learning more about REST and HTTP protocols already and I hope that I would be in a better state by the time GSOC starts. At the moment I am experimenting with the Django Tastypie and I have been wondering if the developers community here have been considering it or anything similar to it ? I would like to get more involved with this project , if this is something community is seeking currently . Please advice, how can I proceed. Thanks and Regards ! ---------------------------------------------------------------------------------------------------------------------- *Rahul Gaur* *irc : iamaregee2* *web: *http://www.rahulgaur.info* * *blogs : *aregee.wordpress.com *fb:* http://facebook.com/iamaregee *github: *https://github.com/aregee From richard at NFSNet.org Fri Mar 29 02:10:58 2013 From: richard at NFSNet.org (Richard Wackerbarth) Date: Thu, 28 Mar 2013 20:10:58 -0500 Subject: [Mailman-Developers] GSOC 2013 : Authenticated REST-API in Postorius/Django In-Reply-To: References: Message-ID: <05BC1D67-31B0-41AA-82C2-8A47AB7AF7BD@NFSNet.org> Welcome to our community, I'm happy to see that you are interested in the REST interfaces. In addition to TastyPie, I suggest that you also look at django-rest-framework. Please compare the two and let us know what you see as the advantages and disadvantages of each. Richard On Mar 28, 2013, at 4:02 PM, Rahul Gaur wrote: > Hello, > > I have been searching for Python/Django projects for a while and I > stumbled upon the Mailman ideas page today. > I am very much interested in discussing more about the *Authenticated > REST-API in Postorius/Django *and I hope to work on it over the summer *, *but > let me first introduce my self. > > I am into third year of my engineering (Computer Science) and I have been > using Python since my first year and for the past couple of months I have > been using Django for experimental projects at college and for a interest > based social networking site(initially started from pinax). > > I have already cloned the Mailman code base and it's up and running , I > will go through the source code in next couple of days. > > I haven't implemented RESTful API's before , but I have started learning > more about REST and HTTP protocols already and I hope that I would be in a > better state by the time GSOC starts. > > At the moment I am experimenting with the Django Tastypie and I have been > wondering if the developers community here have been considering it or > anything similar to it ? > > I would like to get more involved with this project , if this is something > community is seeking currently . > > Please advice, how can I proceed. From barry at python.org Fri Mar 29 15:39:13 2013 From: barry at python.org (Barry Warsaw) Date: Fri, 29 Mar 2013 10:39:13 -0400 Subject: [Mailman-Developers] GSOC 2013 : Authenticated REST-API in Postorius/Django In-Reply-To: References: Message-ID: <20130329103913.0f221fdf@anarchist> Hi Rahul, welcome to mailman-developers! On Mar 29, 2013, at 02:32 AM, Rahul Gaur wrote: >I haven't implemented RESTful API's before , but I have started learning >more about REST and HTTP protocols already and I hope that I would be in a >better state by the time GSOC starts. I highly recommend Leonard Richardson's and Sam Ruby's O'Reilly book on RESTful Web Services: http://shop.oreilly.com/product/9780596529260.do Although the book's been out for many years now, I still think it holds up well, and will give you a great understanding of the basic concepts and design principles behind REST. It also gives lots of great tips for organizing your resources, etc. Of course, it makes the most sense for the authenticated REST API to as closely mimic the core admin API as possible. Where there are conflicts, we should discuss on this mailing list. Cheers, -Barry