Mailman 3 January 2013 - pydotorg-www

Adding User Group Calendar to home page
by mmueller＠python-academy.de Feb. 7, 2013

Feb. 7, 2013

Hi web team, Since the dates of Python events are split between the events calendar and the user group group calendar it makes sense to add both to the python.org home page. While the events calendar appears in left column, the user group calendar does not. It would be nice to have the user group calendar there, just below and in the same style. This is the link for the iframe "https://www.google.com/calendar/embed?src=3haig2m9msslkpf2tn1h56nn9g%40grou…" Thanks, Mike

3 7

Updating feed on Planet Python
by Malthe Borch Feb. 5, 2013

Feb. 5, 2013

Hello, Might someone update my feed to: http://www.maltheborch.com/rss Thanks, \malthe

2 1

Fwd: URGENT: Removal of Information for FUNERALCALL
by Brian Curtin Jan. 29, 2013

Jan. 29, 2013

Can anyone who deals with the job board take a look at this? Amberly from Funeral Call needs a post removed... ---------- Forwarded message ---------- From: Amberly Odom <amberly(a)funeralcall.com> Date: Tue, Jan 29, 2013 at 8:54 AM Subject: URGENT: Removal of Information for FUNERALCALL To: jnoller(a)python.org, spambayes-dev(a)python.org, brian(a)python.org, guido(a)python.org Hello, I just came across a job opening that you have posted for our company. We have not given anyone information to post a job and need this to be removed immediately.This posting must be removed within 48 hours. http://www.python.org/community/jobs/ -- Amberly Odom Director of Marketing Funeral Call p.770-830-6000 e. amberly(a)funeralcall.com

2 1

Re: [pydotorg-www] Changing default wiki permissions
by Paul Boddie Jan. 25, 2013

Jan. 25, 2013

Aahz wrote: > On Thu, Jan 24, 2013, M.-A. Lemburg wrote: > > We're currently working on setting up the new VM with the Python and > > Jython wikis. > > > > In order to increase security and also to help a bit with avoiding > > spam/vandalism, we'd like to disable editing of wiki pages without > > login. > > > > Any objections ? > > That was in fact the setup previously, and I strongly support reverting > to it. As Barry notes, there are some pages that will need a higher > level of protection, but as long as we've got off-VM backups, we can > handle any mishaps. Indeed. I don't buy into the myth that people perpetuate about Wikis having to allow anonymous access or otherwise be instruments of The Man, or whatever. The Internet is full of people who will happily pollute any editable site with their idiotic spams and scams, and some fairly basic measures will deter the bulk of these people. I recommend... Requiring some kind of login. This actually makes it easier for the editors to see at a glance who has edited a page (Aahz rather than, say, 123-client.456-server.verizon.com) and make a quick judgement about whether the edit needs investigating. We can support OpenID - you can even use your Python Package Index identity! - and so don't even need to make people set and remember distinct passwords. Maintaining the textcha protection for random newcomers. I appreciate that textcha questions can be a pain - on one Wiki I use, the questions required a fair amount of research on my part because I am a mere developer and not part of the target audience - but we can migrate people quickly to a group/list that doesn't get bothered with questions. Textcha can be very effective: on some sites I've seen where they turned the feature on, spam was more or less eliminated. Having some kind of mechanism for managing new user registration. I wouldn't want to impose the approval of new users because it stops the quick-but-good edits of people who are new to the Wiki but want to fix something, but it is the case that there may be a lot of "registration spam", meaning that the Wiki fills up with users who will never succeed in making an edit because they can't answer the textcha questions. Maybe there are already tools that deal with this. If not, I may be encouraged to write something. Beyond this, we could introduce edit approval for random newcomers - I wrote something that puts edits in approval queues - but this is really something for a site where you want the barrier to editing to be very low but the barrier to publishing to be much higher. For the Python Wikis, the barrier to editing should be low but not *very* low, and the barrier to publishing should not be significantly higher. Finally, I would like to thank Marc-André for his forensic and recovery work as well as Thomas and Reimar for their work in attempting to restore the content. Once again, the PSF should be thanked for making resources available for the improvement of MoinMoin in various respects. Ensuring the vitality of widely-used Python projects like MoinMoin is an essential part of ensuring the vitality of Python itself. Paul

3 2

Changing default wiki permissions
by M.-A. Lemburg Jan. 25, 2013

Jan. 25, 2013

We're currently working on setting up the new VM with the Python and Jython wikis. In order to increase security and also to help a bit with avoiding spam/vandalism, we'd like to disable editing of wiki pages without login. Any objections ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jan 24 2013) >>> Python Projects, Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/

7 11

Re: [pydotorg-www] [PSF-Members] [Infrastructure] Wiki news?
by Paul Boddie Jan. 19, 2013

Jan. 19, 2013

M.-A. Lemburg wrote: > On 18.01.2013 19:59, Neil Schemenauer wrote: > > [PSF list removed] > > > > On 2013-01-18, M.-A. Lemburg wrote: > >> In other words, the backdoor will likely have been open for > >> several months. > > > > My thanks to all the work put in by volunteers. Has there been any > > consideration given to using different wiki software? It's my > > impression that MoinMoin has a quite poor record with regard to > > security: > > > > http://moinmo.in/SecurityFixes > > > > The abundance of past holes doesn't predict future ones but in > > general there seems to be a correlation. > > I think that's a misinterpretation. MoinMoin is used in a *lot* > of places and so finding vulnerabilities becomes more attractive > than for other similar software. Agreed. Just because the MoinMoin project has openly published advisories (and fixed vulnerabilities) doesn't mean that it has a "poor record", or at least a record that is poorer than other software. I happen to be subscribed to notifications for MediaWiki, for example, and advisories are regularly published exhorting users to upgrade in order to fix various issues. We could spend substantial effort migrating to something else without any guarantee of improved security and with substantial inconvenience incurred. As I noted on a rather tiresome thread on the PSF list, throwing everything out in order to do things some other, supposedly "better" way is an unfortunate Python community tendency that we shouldn't indulge. I also think that using people's software and then abandoning it (and them) when we find something we don't like about it, instead of offering to improve it, is counterproductive if not a betrayal of those people. > I agree, though, that a security audit would probably not > hurt :-) Perhaps they should have one of their GSoC students > run such an audit this summer. > > > Whatever software we use, > > keeping the wiki separated (e.g. in its own VM) is definitely a good > > idea. Anytime you allow remote users to create content the risks > > are high. > > True. I don't want to speculate on what should be done or should have been done because I think the MoinMoin developers do a lot of thankless work supporting their software so that others may freely benefit from it, but there are certainly measures that might be taken to reduce the risk of running this and other Web applications. > Let's not overreact :-) Without the incident we would still be under > the assumption that we have backups for everything... > > It also shows that we have to make a few enhancement to the way > we do logging; but that's going to be a new thread. I think the way forward is to be constructive and to consider how the Wiki can enhance what the complete python.org site offers and how we can be sure that it operates in a way that can be considered acceptable. If that involves spending time and effort on improving the software, then we should encourage that to happen through whatever reasonable means we have at our disposal. Paul

2 2

Wiki news?
by Frank Wierzbicki Jan. 18, 2013

Jan. 18, 2013

Just checking to see what is known about the Python and Jython wiki. I know about the breach and I know that everything was deleted. Is the content recoverable? Does anyone know when there will be some update on when/whether the wikis will reappear? I really do appreciate all of the hard work that goes into supporting the infrastructure, so I hope no one reads this as impatience. I just want to be able to pass on any info to the Jython folks that had content on the wiki. There's always the wayback machine to get some of it back if things are as bad as they could be... -Frank

9 17

Re: [pydotorg-www] [Infrastructure] FWD: Site rebuild: 2013
by Aahz Jan. 17, 2013

Jan. 17, 2013

On Wed, Jan 16, 2013, David Goodger wrote: > > (tl;dr) site rebuild done, 2013 copyright notice is there. Yay! -- Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/ Weinberg's Second Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.

1 0

FWD: wiki down notice moved
by Aahz Jan. 16, 2013

Jan. 16, 2013

Marc-Andre, I have no objection to a news item, but I think the wiki being down is important enough that it should also stay at the top of the page, webmaster is getting constant pings about it. Is there some reason you removed it from the top? Thanks, Aahz ----- Forwarded message from "marc-andre.lemburg" <pydotorg-checkins(a)python.org> ----- > Date: Wed, 16 Jan 2013 16:32:04 +0100 (CET) > From: "marc-andre.lemburg" <pydotorg-checkins(a)python.org> > To: pydotorg-checkins(a)python.org > Subject: [Pydotorg-checkins] r14559 - trunk/beta.python.org/build/data > Reply-To: pydotorg(a)python.org > > Author: marc-andre.lemburg > Date: Wed Jan 16 16:32:04 2013 > New Revision: 14559 > > Modified: > trunk/beta.python.org/build/data/content.ht > trunk/beta.python.org/build/data/newsindex.yml > Log: > Turn the wiki down notice into a news item. > > > > Modified: trunk/beta.python.org/build/data/content.ht > ============================================================================== > --- trunk/beta.python.org/build/data/content.ht (original) > +++ trunk/beta.python.org/build/data/content.ht Wed Jan 16 16:32:04 2013 > @@ -62,9 +62,6 @@ > PyKyra http://www.alobbs.com/pykyra > 3D Rendering http://www.vrplumber.com/py3d.py > > -Note: the Python wiki is currently down as of 2013-01-05 > -(`<http://wiki.python.org/moin/>`__), we will post more details later. > - > **Python is a programming language that lets you work more quickly and > integrate your systems more effectively. You can learn to use Python > and see almost immediate gains in productivity and lower maintenance > > Modified: trunk/beta.python.org/build/data/newsindex.yml > ============================================================================== > --- trunk/beta.python.org/build/data/newsindex.yml (original) > +++ trunk/beta.python.org/build/data/newsindex.yml Wed Jan 16 16:32:04 2013 > @@ -6,6 +6,10 @@ > global: > news: > - > + pubDate: Mon, 7 January 2013, 20:00 +0200 > + title: "http://wiki.python.org taken down for recovery" > + description: !rest "The Python wiki has been taken offline for recovery operations. Please see the `PSF blog <http://pyfound.blogspot.com/>`__ for details and updates." > + - > pubDate: Sat, 29 September 2012, 18:00 +0200 > title: "Python 3.3.0 released" > description: !rest "`Python 3.3.0 </download/releases/3.3.0/>`__ has been released." > _______________________________________________ > Pydotorg-checkins mailing list > Pydotorg-checkins(a)python.org > http://mail.python.org/mailman/listinfo/pydotorg-checkins ----- End forwarded message ----- -- Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/ Weinberg's Second Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.

4 8

Fwd: python.org page descriptions
by Michael Foord Jan. 10, 2013

Jan. 10, 2013

Begin forwarded message: > From: Lance E Sloan <lsloan(a)umich.edu> > Subject: python.org page descriptions > Date: 21 December 2012 14:49:54 GMT > To: webmaster(a)python.org > > Today I wanted to +1 this page on Google+: > > http://www.python.org/getit/mac/ > > When I clicked the +1 button (using a Google+ extension for Chrome on > Mac OS X), it said the description of the page was: > > None > > Looking at the source of the page, I see: > > <meta name="description" content="None" /> > > You should either put descriptions on the Python website pages or > remove these meta tags altogether, because this makes posts about > python.org on Google+ (and probably other services) look silly. > > -- > Lance E Sloan, Application Developer > Univ. of Michigan, Info. and Tech. Services, AIS AMP > http://www.its.umich.edu/ > ** Get free online disk space from Dropbox: > ** https://www.dropbox.com/spacerace?r=NTQ3OTQ2Njk5 > -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html

2 2