On 19/02/11 16:10, Mark A. Hershberger wrote:
In any case, we would like to get these bugs need to be fixed before
we begin putting a 1.17 tarball together. That's an important
milestone for me personally since I want to start working on the 1.18
release sooner rather than later.
I don't
I an not sure if it is the right place to ask this.
I got the source of fss_prep_replace at
http://opensees.berkeley.edu/wiki/extensions/FastStringSearch/fss.c
But are there any Perl or Python implementations?
Thanks.
___
Wikitech-l mailing list
Hey everyone,
for a few weeks now, I have been using a Firefox extension which automatically
redirects me to the secure.wikimedia.org server when visiting a Wikimedia
site. Unfortunately, this does not work for all wikis, e.g. the OTRS wiki is
not included in the redirect rule set. At first, I
Ryan Chan wrote:
I an not sure if it is the right place to ask this.
I got the source of fss_prep_replace at
http://opensees.berkeley.edu/wiki/extensions/FastStringSearch/fss.c
But are there any Perl or Python implementations?
Thanks.
The original source is
On 02/16/2011 04:48 PM, Ryan Lane wrote:
K Who cares about wether or not a bit of whitespace changed ?
My argument exactly.
Every couple weeks I do
$ svn diff -r BASE:HEAD RELEASE-NOTES
and if all looks safe, I then do
$ svn update
You aren't running trunk in production, right? Right?
Hoi,
One of the reasons why trunk is of such high quality is because it is used
on translatewiki.net. Quite regularly you will find one of its developers,
Raymond Nikerabbit and Siebrand to name the most obvious ones reverting
code.
For translatewiki.net there is a compelling reason; we localise
You aren't running trunk in production, right? Right?
And what's wrong with that?
One of the nice things about the MediaWiki development process is that
our trunk generally *is* usable. Sure, every one in a while someone
fails to test their code properly before committing and breaks
On 15 February 2011 22:43, K. Peachey p858sn...@yahoo.com.au wrote:
Release Notes will be corrected and formatted to make it appropriate
for release, nothing is going to change it. The standard is for 80 (or
is it 72) characters wide and it will be corrected if theres errors.
This is just
On Sun, Feb 20, 2011 at 2:01 PM, Thomas Dalton thomas.dal...@gmail.com wrote:
On 15 February 2011 22:43, K. Peachey p858sn...@yahoo.com.au wrote:
Release Notes will be corrected and formatted to make it appropriate
for release, nothing is going to change it. The standard is for 80 (or
is it
- Original Message -
From: Thomas Dalton thomas.dal...@gmail.com
On 15 February 2011 22:43, K. Peachey p858sn...@yahoo.com.au wrote:
Release Notes will be corrected and formatted to make it appropriate
for release, nothing is going to change it. The standard is for 80
(or
is it
On 20 February 2011 19:06, Chad innocentkil...@gmail.com wrote:
On Sun, Feb 20, 2011 at 2:01 PM, Thomas Dalton thomas.dal...@gmail.com
wrote:
On 15 February 2011 22:43, K. Peachey p858sn...@yahoo.com.au wrote:
Release Notes will be corrected and formatted to make it appropriate
for release,
On Sun, Feb 20, 2011 at 2:24 PM, Thomas Dalton thomas.dal...@gmail.com wrote:
Can we please stop this thread already? Starting a thread about
whitespace was stupid, and continuing to discuss it is equally stupid.
It seems to me that making commits to change whitespace that, from
what I can
On 20 February 2011 19:09, Jay Ashworth j...@baylink.com wrote:
Why are we imposing such an outdated rule? CLIs and text editors got
the ability to automatically wrap text several decades ago.
In fact, they *lost* the ability to automatically wrap text.
They thought that was an acceptable
Platonides wrote:
CORS does seem to be the way to go. I have drafted a new proposal below
which attempts to fix several bug in our way of doing central login.
Two questions and a comment about this.
First, would this impede the ability to switch to an AJAX login interface in
the future?
Aryeh Gregor wrote:
On Wed, Feb 16, 2011 at 11:46 PM, MZMcBride z...@mzmcbride.com wrote:
If there's a way to improve the general login workflow (AJAX, CORS,
whatever), I'd like to see that implemented before this checkbox is ripped
out.
Doesn't seem hard. Why don't we set an extra cookie
On 02/20/2011 09:53 PM, MZMcBride wrote:
Platonides wrote:
CORS does seem to be the way to go. I have drafted a new proposal below
which attempts to fix several bug in our way of doing central login.
Two questions and a comment about this.
First, would this impede the ability to switch to
MZMcBride wrote:
Platonides wrote:
CORS does seem to be the way to go. I have drafted a new proposal below
which attempts to fix several bug in our way of doing central login.
Two questions and a comment about this.
First, would this impede the ability to switch to an AJAX login interface
On 02/20/2011 11:52 PM, Platonides wrote:
MZMcBride wrote:
Second, would this impede the ability to remove the you've been logged in
screen? Aryeh mentioned an idea that would allow MediaWiki to remove this
horrible workflow interrupter.[2]
You may have noticed that I included a horrible
Ryan Lane wrote:
I don't think we should encourage people to run trunk in production.
We should encourage people to run release candidates in production,
and possibly betas for those that know the software *really* well. We
should likely encourage people to run trunk on their live testing
This thread at LWN seems like it might have some information which would
be interesting to those people who might be charged, down the road, with
the SSLizing of Wikimedia:
http://lwn.net/Articles/428594/
In particular, it discusses SSL session-caching across a cluster, which I
hadn't realized
- Original Message -
From: Platonides platoni...@gmail.com
Ryan Lane wrote:
I don't think we should encourage people to run trunk in production.
We should encourage people to run release candidates in production,
and possibly betas for those that know the software *really* well.
Jay Ashworth wrote:
should be possible != is a good idea.
Just sayin'
Cheers,
-- jra
Specially when we are not there yet ;)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Original Message -
From: Platonides platoni...@gmail.com
Jay Ashworth wrote:
should be possible != is a good idea.
Just sayin'
Specially when we are not there yet ;)
Best time to take policy decisions with large potential impact, no? :-)
Cheers,
-- jra
On Sun, Feb 20, 2011 at 12:42 PM, Ryan Lane rlan...@gmail.com wrote:
I don't think we should encourage people to run trunk in production.
I think we should encourage people to run trunk in production *if*
they're planning on keeping up with it, will report or fix problems,
and are aware that
On 20/02/11 21:23, Ryan Chan wrote:
I an not sure if it is the right place to ask this.
I got the source of fss_prep_replace at
http://opensees.berkeley.edu/wiki/extensions/FastStringSearch/fss.c
But are there any Perl or Python implementations?
FastStringSearch has an implementation of
25 matches
Mail list logo
