On Feb 20, 2013 at 3:54 pm, Tim Starling wrote:
The idea of storing a database in a large string literal could
be made to be fairly efficient and user-friendly if a helper
module was written to do parsing and a binary search.
I have implemented the above suggestion with some promising results.
Wonderful!
So, now that we have a release manager for MediaWiki, is the release
manager the person who writes/approves the policy for what sort of
things are worth a 1.x.y release and how they're tracked on bugzilla,
and will Chris be able to make and push tarballs for those even if
they're
On 22 February 2013 12:03, Federico Leva (Nemo) nemow...@gmail.com wrote:
Another thing that would be nice to have on
https://www.mediawiki.org/wiki/Version_lifecycle or elsewhere is what are
reasonable expectations about the stable releases. For instance, we know
that 1.x.0 releases
On Fri, Feb 22, 2013 at 4:41 AM, Johnuniq wp.johnu...@gmail.com wrote:
On Feb 20, 2013 at 3:54 pm, Tim Starling wrote:
The idea of storing a database in a large string literal could
be made to be fairly efficient and user-friendly if a helper
module was written to do parsing and a binary
Two separate users on Commons complained that interproject links from Wikimedia
Commons to Wikidata, like [[d:Q7186]] produce hyperlinks in form
http://wikidata.org/wiki/Q35548; or http://en.wikidata.org/wiki/Q35548;
which do not allow editing of wikidata. Only external link to
On Fri, Feb 22, 2013 at 3:43 PM, Tuszynski, Jaroslaw W.
jaroslaw.w.tuszyn...@saic.com wrote:
Two separate users on Commons complained that interproject links from
Wikimedia Commons to Wikidata, like [[d:Q7186]] produce hyperlinks in form
http://wikidata.org/wiki/Q35548; or
On Fri, Feb 22, 2013 at 10:46 AM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
On Fri, Feb 22, 2013 at 3:43 PM, Tuszynski, Jaroslaw W.
jaroslaw.w.tuszyn...@saic.com wrote:
Two separate users on Commons complained that interproject links from
Wikimedia Commons to Wikidata, like
On 02/22/2013 03:42 AM, Thorsten Glaser wrote:
I am a bit unhappy that instead
of a database, MySQL is used/preferred, but (after the last
few bugfixes), PostgreSQL works, so I’m set.
Please do not hesitate to file any bugs for things that don't work for
you in PG. And if they aren't getting
On 02/22/2013 07:03 AM, Federico Leva (Nemo) wrote:
will Chris be able to make and push tarballs for those even if
they're not (only) security-related?
I can make and push tarballs without involving Chris.
But yes, we need to discuss policy, and start setting expectations, etc.
Can we build
We held our second bug day Tuesday Feb. 19th.
*How it Went*
We looked at open bugs in the Wikimedia's Git/Gerrit component. We
focused on upstream issues that may have been fixed with the recent upgrade
and issues that need status updates. Andre, ^demon, MatmaRex and I triaged
bugs and had
Hello all,
Background and longer/more detailed discussion on this issue is in bug
44570:
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Summary:
As we delete old -wmfX branches there appears to be cached pages that
reference old branch URLs, eg:
On Fri, Feb 22, 2013 at 8:24 AM, Mark A. Hershberger m...@everybody.org wrote:
On 02/22/2013 07:03 AM, Federico Leva (Nemo) wrote:
will Chris be able to make and push tarballs for those even if
they're not (only) security-related?
I can make and push tarballs without involving Chris.
And
On 2013-02-22 2:37 PM, Chris Steipp cste...@wikimedia.org wrote:
On Fri, Feb 22, 2013 at 8:24 AM, Mark A. Hershberger m...@everybody.org
wrote:
On 02/22/2013 07:03 AM, Federico Leva (Nemo) wrote:
will Chris be able to make and push tarballs for those even if
they're not (only)
This is your weekly preview of higher-risk or general you should be
aware of items for the slew of deployments coming in the near term.
During the week of March 11th:
* Scibuntu (Lua) to all wikis
* upgrades to DNS software/config for better reliability
See the full Deployments page for
I believe the OpenID extension is matured to the point where it's usable on
the Wikimedia projects, acting as an OpenID provider. The extension still
needs review and such, but I think it's a good time to discuss how we'd
like to implement this on the projects.
My preference for this would be to
Is this up for discussion, or are we at the point of planning
deployment? It isn't apparent to me why any WMF site would be an OpenID
provider.
maiki
On 02/22/2013 11:33 AM, Ryan Lane wrote:
I believe the OpenID extension is matured to the point where it's usable on
the Wikimedia projects,
I run a bigger bleeding-edge-software MediaWiki via SSL on a Raspberry Pi.
And that's not too slow because I use APC.
My quick tip of the day
# add APC (Alternative PHP Cache)
# seehttps://www.mediawiki.org/wiki/Extension:APC
# stop your web server
service apache2 stop
# Install APC
apt-get
Tested in Firefox and Chromium:
wikitech.wikimedia.org uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
(Error code: sec_error_untrusted_issuer)
FYI, nameless person who fixes that. ^_^
maiki
___
quote name=maiki date=2013-02-22 time=12:17:25 -0800
Is this up for discussion, or are we at the point of planning
deployment? It isn't apparent to me why any WMF site would be an OpenID
provider.
To phrase this differently:
Do you more prefer that WMF sites consume OpenIDs instead of (or in
On 02/22/2013 03:17 PM, maiki wrote:
Is this up for discussion, or are we at the point of planning
deployment?
The latter. I can elucidate a number of scenarios where that is
beneficial, but the primary one from my perspective is that of
authenticating for external tools (like bots and
On 2013-02-22 3:34 PM, Ryan Lane rlan...@gmail.com wrote:
I believe the OpenID extension is matured to the point where it's usable
on
the Wikimedia projects, acting as an OpenID provider. The extension still
needs review and such, but I think it's a good time to discuss how we'd
like to
On 02/22/2013 03:44 PM, Brian Wolff wrote:
I would certainly prefer to use
something that already exists.
Meta would seem to be the natural, if ill-named, target.
-- Marc
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
RE: https://www.mediawiki.org/wiki/Extension:OpenID (manual page)
Just my few meta points:
if you should find bugs so, please file them here
https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensionscomponent=OpenID
Open bugs are
On 2013-02-22 4:43 PM, Marc A.
. Each of them currently need their own mechanism, have to implement
baroque processes to associate a Wiki[mp]edia account, and increase
exposure of credentials for the users.
Actually theres been a centralized method of doing that for a while now
(TUSC), so each
On 02/22/2013 03:50 PM, Brian Wolff wrote:
Actually theres been a centralized method of doing that for a while now
(TUSC), so each tool is not reinventing the wheel, but open id sounds much
less hacky.
Oh, cool. I did not know that.
Of course, a /great/ transitional mechanism them presents
Do you intend to cover both SUL and legacy accounts?
I suspect that meta might not work due to the fact that there might be some
accounts that were created on meta, but never merged. So either the URL
would have to be different from the regular [[User:Xxx]] @ meta, like
On 22 February 2013 12:54, Yuri Astrakhan yuriastrak...@gmail.com wrote:
Do you intend to cover both SUL and legacy accounts?
I don't think it's worth anyone's time working out a way of supporting
non-global accounts, given the on-going work to fix these as part of SUL
finalisation which
On Feb 22, 2013, at 6:33 PM, Greg Grossmeier g...@wikimedia.org wrote:
Hello all,
Background and longer/more detailed discussion on this issue is in bug
44570:
https://bugzilla.wikimedia.org/show_bug.cgi?id=44570
Summary:
As w
e delete old -wmfX branches there appears to be cached
On Fri, Feb 22, 2013 at 12:35 PM, maiki ma...@interi.org wrote:
Tested in Firefox and Chromium:
wikitech.wikimedia.org uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
(Error code: sec_error_untrusted_issuer)
FYI, nameless person who
On Fri, Feb 22, 2013 at 12:40 PM, Greg Grossmeier g...@wikimedia.orgwrote:
quote name=maiki date=2013-02-22 time=12:17:25 -0800
Is this up for discussion, or are we at the point of planning
deployment? It isn't apparent to me why any WMF site would be an OpenID
provider.
To phrase this
quote name=Krinkle date=2013-02-22 time=22:29:00 +0100
Well, the obvious thing to do and imho what we should do, like, *right now*
is extend the lifetime of the old branch to the timeout of the cache.
Simply not deleting a directory is very, very easy.
That is definitely a good stop-gap
- Original Message -
From: Ryan Lane rlan...@gmail.com
I believe the OpenID extension is matured to the point where it's usable on
the Wikimedia projects, acting as an OpenID provider. The extension still
needs review and such, but I think it's a good time to discuss how we'd
like to
On Fri, Feb 22, 2013 at 1:03 PM, James Forrester
jforres...@wikimedia.orgwrote:
On 22 February 2013 12:54, Yuri Astrakhan yuriastrak...@gmail.com wrote:
Do you intend to cover both SUL and legacy accounts?
I don't think it's worth anyone's time working out a way of supporting
non-global
quote name=Ryan Lane date=2013-02-22 time=14:00:49 -0800
This isn't really a matter of having one or the other. As Marc has
mentioned, we need some non-hacky form of authentication for bots, tools,
out-of-cluster applications, and non-mediawiki applications.
Right, figured not, just trying to
On Fri, Feb 22, 2013 at 2:03 PM, Jay Ashworth j...@baylink.com wrote:
- Original Message -
From: Ryan Lane rlan...@gmail.com
I believe the OpenID extension is matured to the point where it's usable
on
the Wikimedia projects, acting as an OpenID provider. The extension still
On 02/22/2013 05:03 PM, Jay Ashworth wrote:
or allowing
external non-WMF sites to authenticate against our user database.
Actually, that's the objective -- allow external tools to have their
users be able to prove I am Wikimedia user Coren without having to
hack around with
Ryan wrote:
Any OpenID consumer, whether WMF or not, would be able to use us as an
authentication provider.
There is currently no option, but an option (to restrict serving OpenIDs
to certain
consumer domains eg. only to our domain) could be implemented.
Tom
On Fri, Feb 22, 2013 at 2:30 PM, Thomas Gries m...@tgries.de wrote:
Ryan wrote:
Any OpenID consumer, whether WMF or not, would be able to use us as an
authentication provider.
There is currently no option, but an option (to restrict serving OpenIDs
to certain
consumer domains eg. only
Thanks a lot Quim Gil :-) I want to fix bugs and looking for what can I do.
I will check links and I am going to start fix bug.
22 Şub 2013 14:01 tarihinde wikitech-l-requ...@lists.wikimedia.org yazdı:
___
Wikitech-l mailing list
To be absolutely clear, this does *not* solve the problem of bots/tools
authenticating on behalf of a user. All it does is solve the problem of
where a bot/tool authenticates under its own user account and, out of pure
courtesy for the community, asks users to prove their identity before
allowing
On 2013-02-22 7:20 PM, Tyler Romeo tylerro...@gmail.com wrote:
To be absolutely clear, this does *not* solve the problem of bots/tools
authenticating on behalf of a user. All it does is solve the problem of
where a bot/tool authenticates under its own user account and, out of pure
courtesy
This would also be useful for test wikis people set up on labs. You could
just authenticate via openid instead of creating a new account.
You can already test this here :
http://openid-wiki2.instance-proxy.wmflabs.org/wiki
___
Wikitech-l mailing
On Fri, Feb 22, 2013 at 3:19 PM, Tyler Romeo tylerro...@gmail.com wrote:
To be absolutely clear, this does *not* solve the problem of bots/tools
authenticating on behalf of a user. All it does is solve the problem of
where a bot/tool authenticates under its own user account and, out of pure
In cases where a tool is keeping an authentication database, and is not
acting on behalf of a user, then OpenID would let the tool eliminate its
username/password store.
This is exactly what I'm saying. It doesn't do this. If a tool has a
username/password store, i.e., it uses the username
On Fri, Feb 22, 2013 at 4:07 PM, Tyler Romeo tylerro...@gmail.com wrote:
In cases where a tool is keeping an authentication database, and is not
acting on behalf of a user, then OpenID would let the tool eliminate its
username/password store.
This is exactly what I'm saying. It doesn't
On Thu, Feb 21, 2013 at 2:01 PM, Tyler Romeo tylerro...@gmail.com wrote:
- Where is QA? I mean, I know somewhere somebody is probably doing some
sort of testing, but having worked as a QA engineer I haven't seen
anything
in MW that would resemble proper and traditional testing
On Fri, Feb 22, 2013 at 9:32 PM, Željko Filipin zfili...@wikimedia.org wrote:
Feel free to add features/scenarios to the backlog[2] in the meantime. Let
me know if you need help with that. (Test results for our browser
automation project are available[3] to everybody, by the way).
[snip]
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed around quite a bit recently, and I'm curious:
is there any plan to start integrating this jenkins and our other jenkins?
More importantly: is there any chance to get the results of these sorts of
tests in Gerrit? I think it's
- Original Message -
From: Ryan Lane rlan...@gmail.com
Any OpenID consumer, whether WMF or not, would be able to use us as an
authentication provider.
So, then, all OpenID guarantees is this provider says it's the same person
it was last time?
Cheers,
-- jra
--
Jay R. Ashworth
On 02/22/2013 03:43 PM, Marc A. Pelletier wrote:
On 02/22/2013 03:17 PM, maiki wrote:
Is this up for discussion, or are we at the point of planning
deployment?
The latter. I can elucidate a number of scenarios where that is
beneficial, but the primary one from my perspective is that of
- Original Message -
From: Ryan Lane rlan...@gmail.com
I see no reason in doing so. If third parties want to allow Wikimedia
as a provider, I don't see why we'd object.
There is no potential liability there?
Cheers,
-- jra
--
Jay R. Ashworth Baylink
On 02/22/2013 06:33 PM, Brian Wolff wrote:
Which coincides to several bots/tools and would generally be quite useful.
Quite honestly having bots make edits directly on someones behalf using
their account sounds scary.
For autonomous bots, yes (they should keep using their own accounts).
But
On 02/22/2013 10:44 PM, Jay Ashworth wrote:
There is no potential liability there?
IANAL, but I can't think of a scenario where allowing a user to prove I
am user X on Wikimedia projects can create liability; if the client is
pleased with the (proven) assertion for their purposes, they can
- Original Message -
From: Marc A. Pelletier m...@uberbox.org
On 02/22/2013 10:44 PM, Jay Ashworth wrote:
There is no potential liability there?
IANAL, but I can't think of a scenario where allowing a user to prove I
am user X on Wikimedia projects can create liability; if the
On 02/22/2013 10:43 PM, Jay Ashworth wrote:
So, then, all OpenID guarantees is this provider says it's the same person
it was last time?
The exact semantics is, IIRC, that person has presented credential to
us we accept as identifying them as our user $IDENTIFIER. Whether the
client trusts
Original Message -
From: Marc A. Pelletier m...@uberbox.org
On 02/22/2013 10:43 PM, Jay Ashworth wrote:
So, then, all OpenID guarantees is this provider says it's the same
person it was last time?
The exact semantics is, IIRC, that person has presented credential to
us we
Matthew Flaschen wrote:
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed around quite a bit recently, and I'm
curious: is there any plan to start integrating this jenkins and our
other jenkins? More importantly: is there any chance to get the results
of these sorts of tests in
On 2013-02-23 12:18 AM, Jay Ashworth j...@baylink.com wrote:
Original Message -
From: Marc A. Pelletier m...@uberbox.org
On 02/22/2013 10:43 PM, Jay Ashworth wrote:
So, then, all OpenID guarantees is this provider says it's the same
person it was last time?
The exact
On 02/22/2013 11:32 PM, Brian Wolff wrote:
What ive always wondered is what happens if your oid provider goes
under/otherwise dissapears. I imagine that means you lose your user account
all across the internet, which is a scary thought
Some sites, like Stack Overflow, allow you to add
On 2013-02-23 12:37 AM, Matthew Flaschen mflasc...@wikimedia.org wrote:
On 02/22/2013 11:32 PM, Brian Wolff wrote:
What ive always wondered is what happens if your oid provider goes
under/otherwise dissapears. I imagine that means you lose your user
account
all across the internet, which
On 22 February 2013 20:30, MZMcBride z...@mzmcbride.com wrote:
Matthew Flaschen wrote:
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed around quite a bit recently, and I'm
curious: is there any plan to start integrating this jenkins and our
other jenkins? More importantly:
So I definitely see the use case for OpenID as a provider (and as long as
everybody is aware that OpenID is not OAuth, I'm fine with that), but I'm
not a bot/tool developers. I am, however, a frequent user of the Internet,
and I find it extraordinarily surprising that Wikipedia is one of the few
On Fri, Feb 22, 2013 at 11:30 PM, MZMcBride z...@mzmcbride.com wrote:
Matthew Flaschen wrote:
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed around quite a bit recently, and I'm
curious: is there any plan to start integrating this jenkins and our
other jenkins? More
On 2013-02-23 1:15 AM, Chad innocentkil...@gmail.com wrote:
On Fri, Feb 22, 2013 at 11:30 PM, MZMcBride z...@mzmcbride.com wrote:
Matthew Flaschen wrote:
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed around quite a bit recently, and I'm
curious: is there any plan to
On Sat, Feb 23, 2013 at 12:19 AM, Brian Wolff bawo...@gmail.com wrote:
On 2013-02-23 1:15 AM, Chad innocentkil...@gmail.com wrote:
On Fri, Feb 22, 2013 at 11:30 PM, MZMcBride z...@mzmcbride.com wrote:
Matthew Flaschen wrote:
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed
On 2013-02-23 1:24 AM, Chad innocentkil...@gmail.com wrote:
On Sat, Feb 23, 2013 at 12:19 AM, Brian Wolff bawo...@gmail.com wrote:
On 2013-02-23 1:15 AM, Chad innocentkil...@gmail.com wrote:
On Fri, Feb 22, 2013 at 11:30 PM, MZMcBride z...@mzmcbride.com wrote:
Matthew Flaschen wrote:
On Sat, Feb 23, 2013 at 12:27 AM, Brian Wolff bawo...@gmail.com wrote:
On 2013-02-23 1:24 AM, Chad innocentkil...@gmail.com wrote:
On Sat, Feb 23, 2013 at 12:19 AM, Brian Wolff bawo...@gmail.com wrote:
On 2013-02-23 1:15 AM, Chad innocentkil...@gmail.com wrote:
On Fri, Feb 22, 2013 at
see also https://bugzilla.wikimedia.org/show_bug.cgi?id=9604 (2007)
Support OpenID extension on all wikimedia projects
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Am 23.02.2013 05:40, schrieb Brian Wolff:
Some sites, like Stack Overflow, allow you to add alternate OpenIDs,
which helps for temporary or permanent downtime.
Presumably you would have to do that before the downtime though as you
wouldn't be able to login once downtime starts. So one could
Am 23.02.2013 00:48, schrieb Ryan Lane:
On Fri, Feb 22, 2013 at 3:19 PM, Tyler Romeo tylerro...@gmail.com wrote:
To be absolutely clear, this does *not* solve the problem of bots/tools
authenticating on behalf of a user. All it does is solve the problem of
where a bot/tool authenticates under
70 matches
Mail list logo
