headers
Daniel Friesen | 1 Feb 2011 01:13

Re: NNTP access for Wikimedia mailing lists

On 11-01-31 03:43 PM, River Tarnell wrote:
> In article<4D47370A.5030909 <at> nadir-seen-fire.com>,
> Daniel Friesen<lists <at> nadir-seen-fire.com>  wrote:
>> On 11-01-31 01:47 PM, River Tarnell wrote:
>>> I've set up an NNTP gateway for Wikimedia mailing lists.  The
>>> "wikimedia.*" hierarchy is available via news.tcx.org.uk.  More
>>> information:<http://news.tcx.org.uk/wikimedia.html>.
>> Mmm... I'll be salivating when you get posting working.
> This is a test post.  If you can see it, then posting is now working (at
> least somewhat).
I see it off gmane. However either it hasn't made it to the new nntp, or 
the new nntp is notably slower at picking up messages than gmane T_T.
>> ((I use gmane, but I'm always having an issue posting, so I've become
>> accustomed to changing my From: to the e-mail lists <at>  account from the
>> newsgroups lists <at>  account, changing Newsgroup: ->  To: and then typing at
>> least wikit before letting it autocomplete the full wikitech-l address
>> (think I usually type wikitech fully)))
>> I'll love to be able to post back to the list directly.
> Your From: address still needs to be subscribed to the list if you post
> via NNTP.
>
> 	- river.
It is. Gmane just seams to have been rejecting posts in general at least 
till got tired of opening up my dead sent folder in Local Folders (I 
have separate accounts now, Local Folders is a dead archive of ancient 
pop emails) and opening up my email to re-send it after it doesn't end 
up on-list and stopped posting over gmane.

~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
(Continue reading)

Permalink | Reply | 8 comments |
headers
River Tarnell | 1 Feb 2011 01:18
Picon

Re: NNTP access for Wikimedia mailing lists

In article <4D47502F.1070600 <at> nadir-seen-fire.com>,
Daniel Friesen  <lists <at> nadir-seen-fire.com> wrote:
>On 11-01-31 03:43 PM, River Tarnell wrote:
>> This is a test post.  If you can see it, then posting is now working (at
>> least somewhat).
>I see it off gmane. However either it hasn't made it to the new nntp, or 
>the new nntp is notably slower at picking up messages than gmane T_T.

For some reason articles posted locally (via NNTP) don't seem to be 
appearing in the group.  I have no idea why this should be, but I will 
investigate.

	- river.
Permalink | Reply | 0 comments |
headers
River Tarnell | 1 Feb 2011 01:30
Picon

Re: NNTP access for Wikimedia mailing lists

In article <4D47502F.1070600 <at> nadir-seen-fire.com>,
Daniel Friesen  <lists <at> nadir-seen-fire.com> wrote:
>On 11-01-31 03:43 PM, River Tarnell wrote:
>> This is a test post.  If you can see it, then posting is now working (at
>> least somewhat).
>I see it off gmane. However either it hasn't made it to the new nntp, or 
>the new nntp is notably slower at picking up messages than gmane T_T.

Okay, I think that problem was caused by the gateway script not removing 
the X-Trace header in posts that went news->mail->news; INN rejects 
articles that contain this header, so the article was never posted back 
to the group.

Hopefully this article will appear correctly.

	- river.
Permalink | Reply | 6 comments |
headers
Daniel Friesen | 1 Feb 2011 02:11

Re: NNTP access for Wikimedia mailing lists

On 11-01-31 04:30 PM, River Tarnell wrote:
> In article<4D47502F.1070600 <at> nadir-seen-fire.com>,
> Daniel Friesen<lists <at> nadir-seen-fire.com>  wrote:
>> On 11-01-31 03:43 PM, River Tarnell wrote:
>>> This is a test post.  If you can see it, then posting is now working (at
>>> least somewhat).
>> I see it off gmane. However either it hasn't made it to the new nntp, or
>> the new nntp is notably slower at picking up messages than gmane T_T.
>
> Okay, I think that problem was caused by the gateway script not removing
> the X-Trace header in posts that went news->mail->news; INN rejects
> articles that contain this header, so the article was never posted back
> to the group.
>
> Hopefully this article will appear correctly.
>
> 	- river.
>
>

Yup... this one should too. I may need to tweak some settings myself, it 
also might have felt slow as a result of Thunderbird not checking the 
nntp server as often.
Permalink | Reply | 5 comments |
headers
Rob Lanphier | 1 Feb 2011 03:45
Picon
Gravatar

Planned 1.17 deployment on February 8

Hi everyone,

Just repeating something I just posted to
http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/

The engineering team is busy working on the deployment of the 1.17 branch of
MediaWiki[1].  We plan to roll this out next week to all languages and
projects, Tuesday, February 8, with work starting at 07:00 UTC (which is
11pm on Monday, February 7 for San Francisco).

If all goes well, you should only notice the improvement. If it doesn’t go
well, that’s because there’s something we missed, and that’s where we’d love
your help.  Please help us test this release! We have a test instance of the
software we plan to deploy available at http://prototype.wikimedia.org/.  If
you find issues, please report them in Bugzilla:
http://www.mediawiki.org/wiki/Bugzilla

There are many, many little fixes and improvements that have gone into 1.17
(see the draft release notes[2] for an exhaustive list) .  There isn’t much
that’s visible to users of the site, but one under the hood improvement that
should result in some speed improvements: Resource Loader[3].  Resource
Loader optimizes the use of JavaScript in MediaWiki, speeding up delivery of
JavaScript by compressing it sometimes, and cutting down on the amount of
unused JavaScript that gets delivered to the browser in the first place.
 Much of the work in this development cycle has been centered on ensuring
compatibility with the new system.  Since it makes such a large shift in the
way that JavaScript is delivered to the browser, it’s also an operational
aspect we’ll be keeping a close eye on, as load shifts between servers in
our infrastructure.
(Continue reading)

Permalink | Reply | 18 comments |
headers
MZMcBride | 1 Feb 2011 04:41

Re: Planned 1.17 deployment on February 8

Rob Lanphier wrote:
> Just repeating something I just posted to
> http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/

Thank you for posting here. I'm not sure about others, but I rarely visit
techblog.wikimedia.org. It's great news. :-)

> The engineering team is busy working on the deployment of the 1.17 branch of
> MediaWiki[1].  We plan to roll this out next week to all languages and
> projects, Tuesday, February 8, with work starting at 07:00 UTC (which is
> 11pm on Monday, February 7 for San Francisco).

Can you explain why you're rolling out when it's the middle of the night
where Wikimedia is headquartered? I have a few different theories (site
traffic, time zones of the operations team, etc.), but a clarification here
would be good.

> If all goes well, you should only notice the improvement. If it doesn¹t go
> well, that¹s because there¹s something we missed, and that¹s where we¹d love
> your help.  Please help us test this release! We have a test instance of the
> software we plan to deploy available at http://prototype.wikimedia.org/.

Why is prototype.wikimedia.org being used instead of test.wikipedia.org? I
was under the impression that the purpose of test.wikipedia.org was a
pre-deployment launch pad while prototype.wikimedia.org is used for testing
new extensions/features. Has this changed?

Thanks again for the post. I really do appreciate it.

MZMcBride
(Continue reading)

Permalink | Reply | 15 comments |
headers
bawolff | 1 Feb 2011 06:16
Picon

Re: Planned 1.17 deployment on February 8

Rob said
> --Hi everyone,
>
> Just repeating something I just posted to
> http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/
>
> The engineering team is busy working on the deployment of the 1.17 branch of
> MediaWiki[1].  We plan to roll this out next week to all languages and
> projects, Tuesday, February 8, with work starting at 07:00 UTC (which is
> 11pm on Monday, February 7 for San Francisco).
>
> If all goes well, you should only notice the improvement. If it doesn’t go
> well, that’s because there’s something we missed, and that’s where we’d love
> your help.  Please help us test this release! We have a test instance of the
> software we plan to deploy available at http://prototype.wikimedia.org/.  If
> you find issues, please report them in Bugzilla:
> http://www.mediawiki.org/wiki/Bugzilla
>
> There are many, many little fixes and improvements that have gone into 1.17
> (see the draft release notes[2] for an exhaustive list) .  There isn’t much
> that’s visible to users of the site, but one under the hood improvement that
> should result in some speed improvements: Resource Loader[3].  Resource
> Loader optimizes the use of JavaScript in MediaWiki, speeding up delivery of
> JavaScript by compressing it sometimes, and cutting down on the amount of
> unused JavaScript that gets delivered to the browser in the first place.
> Much of the work in this development cycle has been centered on ensuring
> compatibility with the new system.  Since it makes such a large shift in the
> way that JavaScript is delivered to the browser, it’s also an operational
> aspect we’ll be keeping a close eye on, as load shifts between servers in
> our infrastructure.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rob Lanphier | 1 Feb 2011 07:18
Picon
Favicon
Gravatar

Re: Planned 1.17 deployment on February 8

On Mon, Jan 31, 2011 at 7:41 PM, MZMcBride <z <at> mzmcbride.com> wrote:

> Rob Lanphier wrote:
> > Just repeating something I just posted to
> > http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/
>
> Thank you for posting here. I'm not sure about others, but I rarely visit
> techblog.wikimedia.org. It's great news. :-)

No problem!   One thing I forgot to mention (this goes for everyone)  Please
spread the word!  There are no doubt going to be people who are caught off
guard by this no matter where we post this, (possibly) short of
CentralNotice.

> > The engineering team is busy working on the deployment of the 1.17 branch
> of
> > MediaWiki[1].  We plan to roll this out next week to all languages and
> > projects, Tuesday, February 8, with work starting at 07:00 UTC (which is
> > 11pm on Monday, February 7 for San Francisco).
>
> Can you explain why you're rolling out when it's the middle of the night
> where Wikimedia is headquartered? I have a few different theories (site
> traffic, time zones of the operations team, etc.), but a clarification here
> would be good.

We lost the game of rock/paper/scissors.  :)  We decided to do this very
late U.S. west coast time so that our European and Australian contingents
would be well rested in case there are problems.  Given that we have key
personnel pretty much all over the globe, there wasn't going to be a great
time for this, and this has the added advantage of being a relatively low
(Continue reading)

Permalink | Reply | 14 comments |
headers
Roan Kattouw | 1 Feb 2011 10:14
Picon

Re: Planned 1.17 deployment on February 8

2011/2/1 Rob Lanphier <robla <at> robla.net>:
>> Can you explain why you're rolling out when it's the middle of the night
>> where Wikimedia is headquartered? I have a few different theories (site
>> traffic, time zones of the operations team, etc.), but a clarification here
>> would be good.
>
>
> We lost the game of rock/paper/scissors.  :)  We decided to do this very
> late U.S. west coast time so that our European and Australian contingents
> would be well rested in case there are problems.  Given that we have key
> personnel pretty much all over the globe, there wasn't going to be a great
> time for this, and this has the added advantage of being a relatively low
> traffic time for us.
>
Look at http://torrus.wikimedia.org/torrus/CDN?path=%2FTotals%2F and
you'll see that, for the past two days, the time of lowest traffic was
between 06:00 and 07:00 UTC. This has been a quite reliable pattern
for quite some time now (except that it shifts by an hour in Northern
Hemisphere summer, due to DST), and we've also used this time for the
first few Vector deployments.

It'll be an annoying time for all of us. Europe-based people will have
to get up relatively early ("engineer early", in RobLa's words), it'll
be 1am and 2am respectively for our US-based operations people
(despite WMF being headquartered in SF, we currently have no ops
engineers there, although of course other SF people will be involved
and they'll also be working in the middle of the night), and Tim will
most likely be eating dinner at his desk while possibly keeping the
site up.
(Continue reading)

Permalink | Reply | 11 comments |
headers
Krinkle | 1 Feb 2011 16:13
Picon
Gravatar

Re: Planned 1.17 deployment on February 8

Rob Lanphier wrote:

> MZMcBride wrote:
>
>> Rob Lanphier wrote:
>>> If all goes well, you should only notice the improvement. If it  
>>> doesn¹t go
>>> well, that¹s because there¹s something we missed, and that¹s where  
>>> we¹d love
>>> your help.  Please help us test this release! We have a test  
>>> instance of the
>>> software we plan to deploy available at http://prototype.wikimedia.org/ 
>>> .
>>
>> Why is prototype.wikimedia.org being used instead of  
>> test.wikipedia.org? I
>> was under the impression that the purpose of test.wikipedia.org was a
>> pre-deployment launch pad while prototype.wikimedia.org is used for
>> testing
>> new extensions/features. Has this changed?
>>
>
> Yeah it has.  I don't recall the exact history of how we got to this  
> point.
> I imagine that the two should become one in the future.
>

Another difference I'd like to point out is that prototype isn't 1  
wiki, it's a group of
wikis. If I recall correctly there will be a prototype for each of the
(Continue reading)

Permalink | Reply | 0 comments |

Gmane