Hi,
I recently suggested some scheme for dynamically creating clean wikis for
Selenium tests, which can be found here:
http://www.mediawiki.org/wiki/SeleniumFramework#Testing_with_a_clean_database_and_file_state
After some discussion in the Testing group, I would like to elaborate a bit
Thanks for the help folks. If anyone is curious, here's a little
python script I wrote that prints out the (parsed) edit stream:
http://gist.github.com/628199
//Ed
On Thu, Oct 14, 2010 at 6:31 PM, Platonides platoni...@gmail.com wrote:
Ed Summers wrote:
A question from an IRC/wikipedia
Hello everybody!
I have worked all the summer on interwiki transclusion in branch
iwtransclusion. It is nearly finished now: only small improvements
have to be made before this is merged to trunk.
However, my university work makes me very busy at this time and I
think I will have no time to
Since the discussion about staff collaboration with volunteers started
a few weeks ago, actions and statements by staff members have
undergone an increasing amount of scrutiny and criticism. That in
itself is not a bad thing necessarily: staff members need to be kept
on their toes and not be
On Fri, Oct 15, 2010 at 2:40 PM, Roan Kattouw roan.katt...@gmail.com wrote:
Since the discussion about staff collaboration with volunteers started
a few weeks ago, actions and statements by staff members have
undergone an increasing amount of scrutiny and criticism. That in
itself is not a bad
On 15 October 2010 20:17, Aryeh Gregor simetrical+wikil...@gmail.com wrote:
The bottom line is that you're not going to have a happy volunteer
community unless you consistently pay attention when it complains. I
think the response to the thread I started about this a while ago was
a pretty
2010/10/15 Aryeh Gregor simetrical+wikil...@gmail.com:
The problem is not about attitudes, it's systemic.
You're generalizing in ways that are invalid. Your behavior on this
list, MZMcBride's behavior on this list, Trevor's behavior on this
list, my behavior on this list -- all those things are
So that Aryeh doesn't feel like a lone voice, as he did last time.
Are you really saying here that agreement constitutes an operational problem?
Roan has posited that volunteers complaining constitutes a problem. I
suggest that *why* they're complaining constitutes the problem.
- d.
On 15
Hi David,
Roan has posited that volunteers complaining constitutes a problem. I
suggest that *why* they're complaining constitutes the problem.
I'm suggesting that working together constructively requires everyone
involved to make a serious effort at doing so. The us vs. them dynamic
is
What is this?
I have never read something like this before ...(since 28-2-2002)
Maybe some people need to take a phone and talk with other people.
There are some things that can't be conducted by emails.
--
--
ℱin del ℳensaje.
___
Wikitech-l
2010/10/15 Aryeh Gregor simetrical+wikil...@gmail.com:
But instead of seeing volunteers' frustration as something that needs
to be addressed by staff if you expect to keep a healthy community
going, you see it as a problem in its own right which is the fault of
the volunteers. This
Hey,
I'd like to introduce everyone to an extension called Validator [0] that I
wrote over the past few months and aims to facilitate parameter handling for
other extensions. I developed it for usage in the Maps and Semantic Maps
extensions, as I thought it would be nice to have a less messy way
2010/10/15 Erik Moeller e...@wikimedia.org:
There's no inevitability of outcomes, we're shaping these outcomes
together now. That's, as far as I understand it, the essence of Roan's
point. We can all work together to create a constructive and healthy
atmosphere, all the time. And if we take
2010/10/15 Aryeh Gregor simetrical+wikil...@gmail.com:
The number one thing that
volunteers are unhappy about is non-deployment of volunteer code.
Why? Because the only reason for their participation is so that their
code should be deployed. When their code is neglected while other
people's
On Fri, Oct 15, 2010 at 5:07 PM, Roan Kattouw roan.katt...@gmail.com wrote:
To repeat the subject line of this thread: it's a two-way street. I
acknowledge that the current tensions are a byproduct of certain
crises, and by no means meant to imply that staff members are
practically innocent
2010/10/15 Aryeh Gregor simetrical+wikil...@gmail.com:
I respectfully disagree. Attitude is not important compared to
concrete things that are upsetting people.
I think that we agree more than we disagree here. Obviously a huge
code review and deployment backlog is bad for everyone. Volunteers
On 10/15/10 2:44 PM, Aryeh Gregor wrote:
It's not a two-way street. It would be most accurate to say that the
decision lies in the hands of just a few people.
If the problem is truly being caused by a few people's choice of action,
then volunteers should be sympathetic to staff developers,
On 10/15/10 3:07 PM, Trevor Parscal wrote:
There is no crisis here, there's only a bunch of passionate people
working to make things better - and I personally am thankful that we all
care enough to talk about this. If the community was really dieing, this
thread would have been one post
Roan Kattouw wrote:
[The volunteers'] role, IMO, is to keep the collaborative environment
positive. This means being welcoming to new staff, embracing them,
pat them on the shoulder when they to things right and correct them
when they do things wrong, while keeping their patience.
I feel
On 10/15/10 3:19 PM, Steve Summit wrote:
Please pardon an outside comment which may be misinformed, or too
blunt; I haven't been part of this discussion or followed all of
it, and I'm not well-informed on the tensions which motivated it.
But:
well read this:
2010/10/15 Aryeh Gregor simetrical+wikil...@gmail.com:
But, to reiterate, I think most of the problem will disappear when we
have regular code deployment again. At this point, it's best to focus
solely on that and forget about all other complaints. If problems
linger for long after
2010/10/15 Steve Summit s...@eskimo.com:
It seems to me that if we're talking about backpats, it's the
volunteers who are more likely to need them, not the paid staff.
Since you hire the paid staff, you can presumably pick people who
are professional enough to understand their job requirements
Roan Kattouw wrote:
This'll probably take months, so I know I'm asking for quite a bit of
patience here. But I believe Aryeh is right that regular code
deployments will cure most of the problems we've been discussing, and
I'm willing to bet on that by putting my disagreements with other
On 10/15/2010 9:37 PM, MZMcBride wrote:
The issues surrounding code deployment, branches, and special exemptions for
staff-written code are well documented at this point. And the solutions are
all fairly readily apparent. It isn't time to say we need to come up a
plan, it's time to
* Jeroen De Dauw jeroended...@gmail.com [Fri, 15 Oct 2010 23:08:21
+0200]:
Hey,
I'd like to introduce everyone to an extension called Validator [0]
that
I
wrote over the past few months and aims to facilitate parameter
handling
for
other extensions. I developed it for usage in the Maps
On 10/15/10 8:25 PM, Alex wrote:
That discussion was more
than a month ago. What progress has been made since then?
* Several new people were added to the code reviewers list.
* Brion Vibber was contracted to provide code review office hours.
That looks like action
26 matches
Mail list logo
