Re: [pydotorg-www] let this be a warning to would-be wiki editors
On Jun 27, 2017, at 03:31 PM, Fox wrote: >you wanna put up with this ? Not really. Can we block this guy? -Barry ___ pydotorg-www mailing list pydotorg-www@python.org https://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Help with mailing lists?
CC'ing in postmaster. On Dec 23, 2014, at 05:56 AM, Ned Batchelder wrote: I needed some help with some mail lists at mail.python.org: I need a password reminder, but never got one, and I have some questions about creating a new list. I just tried it with the 'playground' mailing list and it worked just fine. I got the password reminder within minutes. FWIW, the playground list is just that, a dummy list that the postmasters can use to experiment with the live Mailman system on mpo. I'm not sure why you haven't gotten you password reminder. The page at http://mail.python.org says, If you are having trouble using the lists, please contact mail...@python.org mailto:mail...@python.org, so I sent my questions there. That's pretty much a canned listinfo overview page. We could hack that to explicitly name postmas...@python.org. mail...@python.org is the site list, and until just now, only myself and Ralf were members of that list, and my delivery is disabled. I just added postmas...@python.org to that mailing list, so it should forward everything to the postmasters. I got an automated response email that said that no one will answer, and to write to postmas...@python.org. I forwarded my questions there. Yep, that's Mailman's replybot. I got an automated response email in German that said to send requests to postmas...@charite.de. So I forwarded my questions there. Yep, that's probably Ralf's replybot. ;) I got an automated response email (in German and English!) that said, Thank you for your email. We'll work on email issues right away, all other issues will be ignored. I don't know if my questions are considered email issues or not, so I don't know how long to wait before trying something else. What should I do now? Any ideas who I can contact? Things seem broken on a number of levels. postmas...@python.org is the right place ultimately for all things email for python.org. I'm not sure whether the postmasters read pydotorg-www. As MAL points out, it's the typical slow holiday season, so response may be delayed. Cheers, -Barry ___ pydotorg-www mailing list pydotorg-www@python.org https://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Vandalism/spam on wiki.python.org: changes to default permissions
On May 31, 2014, at 10:49 PM, M.-A. Lemburg wrote: I've added a new user group called NewUsersGroup, which does get editing rights, but we'll have to manage this manually and new users who want to receive editing rights will have to write to this mailing list to be added to the group. TBH, we've been doing this on the Mailman wiki for years now. Of course, we don't have as high a contributor rate as the Python wiki, and I wish I didn't have to take that step, but it *has* reduced the spam rate to nearly zero. I'm sure there's been a cost in drive-by contributions, but we do get occasional requests for write permissions and it's trivial to add folks to the editors group. -Barry ___ pydotorg-www mailing list pydotorg-www@python.org https://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] No news appearing on python-announce-list for a month
On May 06, 2013, at 11:49 AM, M.-A. Lemburg wrote: Thanks for checking, so this is not a technical problem, but more a moderator one. I've pinged the moderators off-list. Yep, we're adding new moderators now. Note though, that there *is* a confirmed technical problem with the list. OpenPGP signed email sent to the list disappears into a black hole. I don't remember if it shows up in the moderator queue or not, but it definitely won't show up on the mailing list or gmane. I don't know what the problem is, but I don't think it's in Mailman. 1) More moderators help. 2) Don't sign your announce emails (for now) -Barry ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] No news appearing on python-announce-list for a month
On May 06, 2013, at 05:12 PM, Ralf Hildebrandt wrote: Note though, that there *is* a confirmed technical problem with the list. OpenPGP signed email sent to the list disappears into a black hole. I don't remember if it shows up in the moderator queue or not, but it definitely won't show up on the mailing list or gmane. I don't know what the problem is, but I don't think it's in Mailman. 1) More moderators help. 2) Don't sign your announce emails (for now) I'll send a signed mail there. Gotta get back home first and do some shopping. I suspect our NNTP gateway at XS4ALL. I pinged Thomas about this but never heard back, so he's CC'd again here. I think he's the only one who has inside information about our NNTP gateway. -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Retiring catalog-sig
CC'ing postmaster, who can do the mailing list thingies. On Mar 31, 2013, at 09:14 AM, Richard Jones wrote: Hi all, apologies for the x-post, Could someone please help me retire the catalog-sig? I'm about to notify all current members, telling them to subscribe to the distutils-sig if they wish to. I believe the references to the catalog-sig are on: http://www.python.org/community/sigs/ http://www.python.org/community/sigs/current/ and it needs to be moved to: http://www.python.org/community/sigs/retired/ I will update all PEPs that have Discussions-To set to the catalog-sig. Does deleting the mailing list remove the archives? I wouldn't want that to happen. It *can* but doesn't by default. Here's an official to postmaster to delete the catalog-sig mailing list but keep its archives. Do you want to forward future postings to catalog-sig to forward to distutils-sig, or should we just let them bounce? -Barry ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Retiring catalog-sig
On Apr 01, 2013, at 10:48 AM, Brad Knowles wrote: I've already started this process. Thanks Brad! The old list has not been deleted, but is fully locked down from getting any more posts made to it, and the auto-responder has been turned on to tell everyone that all new posts should be made to the other list. Assuming that folks still want the archives available, and therefore we leave this in place as a Mailman list that does not accept any new incoming messages, I'm not sure how we would set it up to forward all incoming posts to a different list. It's a bit of a hack, but what you do is delete the old list (probably after backing up the lists/catalog-sig directory just in case). Then you need to add Postfix aliases to forward from catalog-sig to distutils-sig. Finally, you need to add catalog-...@python.org as an acceptable alias, and you might want to add an autoresponder text to the posting address to inform people of this, although you can't currently discriminate between postings to catalog-sig and postings to distutils-sig. Boy, this should would make a good Mailman 3 feature! So far as I know, only outstanding action that remains is to decide what to do with the list of subscribers to the old list. My understanding is that most of them are already subscribed to the new list, so the easiest thing to do might be to do a mass unsubscribe, and included in that message would be an invitation to join the new list if the recipient has not already done so. Other possibilities would include doing the equivalent of a sort -u on the combined subscriber list, remove all the recipients who are already on the new list, and then do a mass subscribe of the remainder to the new list. At that point, we could do a mass unsubscribe for everyone from the old list, and not have to worry about inviting people to join the new one. Anyway, I'm still waiting on feedback for that. I want to do whatever we can to support the community in the way they want to be supported, but I'm not sure what type of method that this particular community would want applied to them. Given that both mailing lists are gated on Gmane, I think it's enough to get the word out about the switch, and let people opt-in to distutils sig. They can always catch up on Gmane if they miss something. -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Python Wiki Spam
On Mar 22, 2013, at 12:19 PM, M.-A. Lemburg wrote: Did this have an effect on the number of editors of the wiki ? It probably did, but it's hard to gauge. It's not like we had a ton of non-spam editors previously. We never denied anybody write access if they asked though. The usual complaint when doing this is that you prevent quick edits (e.g. typo corrections) by raising the bar in this way. Yep. Unfortunately, it was taking way too much of our time weeding out the spam, so before the policy, our wiki was arguably less useful. -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Python Wiki Spam
On Mar 20, 2013, at 10:08 AM, M.-A. Lemburg wrote: If we can't get things under control, we will have to start using such a group and disable public editing of pages :-( FWIW, we've long had this policy on the Mailman wiki. It was the only successful way to control spam. Sign up is open (and yes, we occasionally have to delete profile spam), but folks have to email the mailman-cabal to request write/edit access. We don't get a lot of such requests, so the process is quite manageable, and we get almost zero spam now. -Barry ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Migrating python.org to OSL
On Mar 18, 2013, at 03:17 PM, Noah Kantrowitz wrote: As part of the PyCon sprints I would like to move python.org off dinsdale to a VM at OSL. Due to the build system being tied to SVN, I'll also migrate that service on the same VM. Do any SVN repos other than www/ need to remain available? This would require at least some period of not changing the website, probably a few hours, but I don't think that would be a problem. This is mostly a legacy move so I'm not going to clean it up much, we'll have a new site soon enough. Not that I'm aware of. As Benjamin noted, all RMs will need upload access and it would be great to get a CNAME that won't change (anything will do) since we'll need to update PEP 101 and probably the release script. -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Changing default wiki permissions
On Jan 24, 2013, at 04:28 PM, Radomir Dopieralski wrote: On Thu, Jan 24, 2013 at 3:13 PM, M.-A. Lemburg m...@egenix.com 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 ? I don't really have any objections, but it may interest you that the last few spammer attacks on the wiki all registered random accounts automatically and logged in before posting their spam. +1 for the change, although based on my experience with the (Confluence-based) Mailman wiki, it won't help much. We've resorted to adding a special authors group and only allowing folks in that group to edit pages. You have to explicitly ask the Mailman cabal for permission to join the group. Now the only spam we get (and it is *way* less than it ever was) is in the actual wiki-joining account information. Cheers, -Barry ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [python-committers] Deleting code.python.org
On Jul 02, 2012, at 05:57 PM, mar...@v.loewis.de wrote: code.python.org was meant as a VCS-independent hostname for CPython; PEP 385 chose to use hg.python.org instead. I'd like to delete code.python.org. Objections? None from me. Cheers, -Barry ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] make m.p.o/mailman/ redirect to listinfo?
On Jan 26, 2012, at 10:45 AM, Ralf Hildebrandt wrote: * Jeremy Baron jer...@tuxmachine.com: Hi, IMHO, http://mail.python.org/mailman/ should do something useful rather than throw a 403. I suggest 30[12] - listinfo. I fixed it. Please test. wfm, thanks! -Barry ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] python-win32 mailing list: Bug in Mailman version 2.1.12
On Jan 23, 2012, at 11:49 PM, Michael Foord wrote: Thanks I'll try and remember that for next time (although thankfully such problems are rare). Would it be possible to update the error page to point people to the postmaster address instead of the webmaster one? Probably, but I have no idea where that error page comes from. ;) -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] python-win32 mailing list: Bug in Mailman version 2.1.12
On Jan 23, 2012, at 10:06 PM, Michael Foord wrote: I believe this is your domain. I've copied in pydotorg-www as well just in case there is anyone there who can prod the right bits. Thanks Michael. postmas...@python.org works best for stuff like this. I forwarded it (and will take a look if nobody else does before I find some time). -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
[pydotorg-www] Fw: [Archiver-policy] Impact of SOPA?
I really almost hesitate to send this, not because I'm not entirely sympathetic to the cause, but because political discussions are always problematic and perhaps more so because of the PSF's non-profit status. Still, SOPA and the like are evil pieces of legislation that will have seriously dire consequences to Python and python.org. Notwithstanding the recent backtracking on these bills, I wonder if we should blackout as well for solidarity (and self-interest). I'm deliberately sending it here first, although the board would likely have to decide too. The question is, if we wanted to participate, would it be technically feasible given our volunteer resources? -Barry Begin forwarded message: Date: Sun, 15 Jan 2012 17:21:45 -0800 From: Jeff Marshall marsh...@gmail.com To: Hank Leininger hl...@marc.info Cc: archiver-pol...@python.org archiver-pol...@python.org Subject: Re: [Archiver-policy] Impact of SOPA? Hi Hank, great to hear from you. We've been discussing it this weekend and we are leaning strongly towards doing a full blackout for the day on the 18th. We plan on deciding tonight. We haven't gotten any legal opinions on the proposed legislation, but our IANAL interpretation is pretty dire like yours. It would be great if several of us participated in the blackout together resulting in more awareness across the spectrum. Jeff On Jan 15, 2012, at 4:52 PM, Hank Leininger hl...@marc.info wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi folks, MARC admin here. What are your thoughts on the impact of SOPA on public mailing list archives hosted in the United States? IANAL, and I can't keep up with the various modifications to SOPA and Protect-IP that keep coming, but my impression is that it would be a death sentence: we would be obligated to review all messages for copyrighted content prior to posting, make us liable for any violations, and of course, get our sites taken down/blocked based on unsupported claims (i.e. no due process; guilty until proven innocent). I'd expect to have to shut MARC down, or move it out of the US (and no longer touch it myself, any more). So, I am thinking of participating in the SOPA Blackout Day on Wednesday. I'm curious what the Jeffs think, if you've gotten any legal opinions on the matter, considered participating in the blackout, etc. Thanks, Hank -BEGIN PGP SIGNATURE- iQEVAwUBTxN0wEeo0UvhPpxqAQiy7gf/bKap95vBkW9HcMQCC/xFEYHWJaWszXC5 lIOfPW0lC1fbxa6BkRvMEYloiseYS3yCzgPxUqCkDQvn6R5mHOGAHRvIQWBMlj/d bbCjidpnboRtQ+c0xGD5iib7hXvsMyL2dRQem7c6/WbHq2uvbTngsuA+Wzhwq7nW LJxUB8Ucgp05x/UCsSPgUj+DmGrA4bmisVuBB9xypB6b1NQZ/BsKm6nMumzRiPTe NCXSZGxsSpng+WIyvSSgXfckxZxSfEOF9G3BL9Q4hthTUEMwhAPsH/UKRcOcvCh6 wWSKGBLco8ufMYjMrb+8ntIv/E7aTryMbOqbg+XyRM77Rdi/8z/Lqg== =6Mtz -END PGP SIGNATURE- ___ Archiver-policy mailing list archiver-pol...@python.org http://mail.python.org/mailman/listinfo/archiver-policy Hi Hank, great to hear from you.We've been discussing it this weekend and we are leaning strongly towards doing a full blackout for the day on the 18th. We plan on deciding tonight.We haven't gotten any legal opinions on the proposed legislation, but our IANAL interpretation is pretty dire like yours.It would be great if several of us participated in the blackout together resulting in more awareness across the spectrum.JeffOn Jan 15, 2012, at 4:52 PM, Hank Leininger hl...@marc.info wrote:-BEGIN PGP SIGNED MESSAGE-Hash: SHA256Hi folks,MARC admin here.What are your thoughts on the impact of SOPA on public mailing listarchives hosted in the United States?IANAL, and I can't keep up with the various modifications to SOPA andProtect-IP that keep coming, but my impression is that it would be adeath sentence: we would be obligated to review all messages forcopyrighted content prior to posting, make us liable for anyviolations, and of course, get our sites taken down/blocked based onunsupported claims (i.e. no due process; guilty until proveninnocent).I'd expect to have to shut MARC down, or move it out of the US (and nolonger touch it myself, any more). So, I am thinking of participatingin the SOPA Blackout Day on Wednesday.I'm curious what the Jeffs think, if you've gotten any legal opinionson the matter, considered participating in the blackout, etc.Thanks,Hank-BEGIN PGP SIGNATURE-iQEVAwUBTxN0wEeo0UvhPpxqAQiy7gf/bKap95vBkW9HcMQCC/xFEYHWJaWszXC5lIOfPW0lC1fbxa6BkRvMEYloiseYS3yCzgPxUqCkDQvn6R5mHOGAHRvIQWBMlj/dbbCjidpnboRtQ+c0xGD5iib7hXvsMyL2dRQem7c6/WbHq2uvbTngsuA+Wzhwq7nWLJxUB8Ucgp05x/UCsSPgUj+DmGrA4bmisVuBB9xypB6b1NQZ/BsKm6nMumzRiPTeNCXSZGxsSpng+WIyvSSgXfckxZxSfEOF9G3BL9Q4hthTUEMwhAPsH/UKRcOcvCh6wWSKGBLco8ufMYjMrb+8ntIv/E7aTryMbOqbg+XyRM77Rdi/8z/Lqg===6Mtz-END PGP SIGNATURE-___Archiver-policy mailing listarchiver-pol...@python.orghttp://mail.python.org/mailman/listinfo/archiver-policy
Re: [pydotorg-www] Fw: [Archiver-policy] Impact of SOPA?
On Jan 16, 2012, at 03:26 PM, Patrick Ben Koetter wrote: postmaster hat on: Yes, we can blackout mail for that time I think we'd also want to block archiver access to mail.python.org and throw up an informative page. Though if we do it, we should do it with all the python.org web sites. -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Fw: [Python-Dev] svn.python.org certificate expired
On Jan 10, 2012, at 11:28 PM, Martin v. Löwis wrote: Am 10.01.2012 09:46, schrieb Barry Warsaw: We should renew this even though svn is in read-only. Done. Patrick had generated a new one over Christmas, which I had forgotten to install. Thanks guys! -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
[pydotorg-www] Fw: [Python-Dev] svn.python.org certificate expired
We should renew this even though svn is in read-only. -Barry Begin forwarded message: Date: Mon, 9 Jan 2012 23:01:54 +0100 From: Charles-François Natali neolo...@free.fr To: python-dev python-...@python.org Subject: [Python-Dev] svn.python.org certificate expired Hi, All the buildbots are turning red because of test_ssl: == ERROR: test_connect (test.test_ssl.NetworkedTests) -- Traceback (most recent call last): File /var/lib/buildslave/3.x.murray-gentoo-wide/build/Lib/test/test_ssl.py, line 616, in test_connect s.connect((svn.python.org, 443)) File /var/lib/buildslave/3.x.murray-gentoo-wide/build/Lib/ssl.py, line 519, in connect self._real_connect(addr, False) File /var/lib/buildslave/3.x.murray-gentoo-wide/build/Lib/ssl.py, line 509, in _real_connect self.do_handshake() File /var/lib/buildslave/3.x.murray-gentoo-wide/build/Lib/ssl.py, line 489, in do_handshake self._sslobj.do_handshake() ssl.SSLError: [Errno 1] _ssl.c:420: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed It seems that svn.python.org certificate expired today (09/01/2012). Cheers, cf ___ Python-Dev mailing list python-...@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/barry%40python.org signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] PythonLabs website
On Oct 04, 2011, at 07:06 PM, Noah Kantrowitz wrote: Continuing my nightly whats the deal with … spam, does anyone know what the story with pythonlabs.com is? pythonlabs.com is NXDOMAIN, and www.pythonlabs.com is pointed to GAE, but is serving the same content as python.org/pythonlabs. Additionally there is still a vhost for pythonlabs.com and www.pythonlabs.com on dins dale. Does anyone know who controls the domain or should I just not worry about this? Guido will answer definitively (it's his domain), but please do keep this. It's a cute place to forward folks to when they ask about it. As far as where the domain should point (i.e. the content being the same), again, that should be Guido's decision, but I don't see any reason to keep the GAE up just for that. The content could be served from dinsdale just fine. -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Repeated outages of python.org
On Jul 24, 2011, at 11:34 AM, Thomas Wouters wrote: Barry, it seems many people with root access on (at least) dinsdale aren't on roto-rooters. We should probably fix that, and make sure everyone is added to ~psf/.ssh/authorized_keys on xs4all.nl so they can access the remote console/powerswitch as well (unless they have a reason not to want that access, I guess.) I was mostly off-line this weekend, but I just approved Antoine's, Georg's, and Michael's subscriptions to roto-rooters. -B signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Repeated outages of python.org
On Jul 25, 2011, at 09:16 PM, M.-A. Lemburg wrote: A wiki on a separate server would make that information just as easily available, so I don't really buy into that argument of unorganized administrators (which I don't think we have on python.org). You obviously haven't met any of our administrators. :) -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Repeated outages of python.org
On Jul 27, 2011, at 06:17 PM, Carl Karsten wrote: On Mon, Jul 25, 2011 at 2:20 PM, Barry Warsaw ba...@python.org wrote: On Jul 25, 2011, at 09:16 PM, M.-A. Lemburg wrote: A wiki on a separate server would make that information just as easily available, so I don't really buy into that argument of unorganized administrators (which I don't think we have on python.org). You obviously haven't met any of our administrators. :) Has anyone? It might be good if someone could visually confirm they exist and aren't actually a script. I can confirm that. Of course *I* might be a script, so you probably shouldn't take my word for it. -Barry signature.asc Description: PGP signature ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
