Hi all,
I’m trying to add a feature to Wikimetrics that will allow users to create a cohort with a username and find all accounts across wikis. I want to use the CentralAuth database, because as far as I can tell, it stores the global username and all the local usernames. However, I don’t see where it connects the globalusers to the localusers. Is it just the username?
Does the username have to be the same across local wikis and you query the localuser table with what you think is the global username? If that’s the case, I suppose I don’t need to look at the global table.
Thanks,
Teresa
I just wondered if anyone doing MediaWiki development had any
experience in catching CSS regressions?
We have had a few issues recently in mobile land where we've made big
CSS changes and broken buttons on hidden away special pages -
particularly now we have been involved in the development of mediawiki
ui and moving mobile towards using them.
My vision of how this might work is we have an automated tool that
visits a list of given pages on various browsers, take screenshots of
how they look and then compares the images with the last known state.
The tool checks how similar the images are and complains if they are
not the same - this might be a comment on the Gerrit patch or an
e-mail saying something user friendly like "The Special:Nearby page on
Vector looks different from how it used to. Please check everything is
okay."
This would catch a host of issues and prevent a lot of CSS regression bugs.
Any experience in catching this sort of thing? Any ideas on how we
could make this happen?
On Thursday, March 27, 2014, David Gerard <dgerard(a)gmail.com> wrote:
>
> Making Vector more easily skinnable would help A LOT, fwiw. If we want
> the various WMF sites to maintain distinctness from third-party
> installations, best way would be to make it really easy to do so.
> Heck, some third-party sites get really eyegougingly horrible already
This is my main motivation trying to find mentors for this GSoC proposal:
https://www.mediawiki.org/wiki/User:Protnet/Frontend_for_Vector_skin_CSS_cu…
Sadly, I lack the skills. Volunteers welcome!
PS: sorry for the pitch, in a few days the hunt for GSoC mentors will be
over.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Currently mediawiki constrains image size primarily by width, which doesn't
work so well for images which are taller than they are wide. There is no
way to ask for an image which has a height equal to the "default thumbnail
size" (without explicitly specifying a size in px)!
It would be nice to fix this. VisualEditor/Parsoid would really prefer to
use a simplified model where all bounding boxes are square, including the
default thumbnail size.
Please see
https://www.mediawiki.org/wiki/Requests_for_comment/Square_bounding_boxesfor
two concrete proposals for how this might be achieved, and discuss!
Thanks...
--scott
--
(http://cscott.net)
Hey all,
I wanted to give people an extra notice that we're updating the default
typography across all Wikimedia sites, for users of the Vector skin. This
was also mentioned in the last Tech News edition, and announced by Greg as
part of the deployment roadmap.
This will happen in the following order:
1. Test wikis and mediawiki.org tomorrow. That's Thursday, March 27th.
2. Non-Wikipedia projects on Tuesday, April 11th.
3. All Wikipedias on Thursday April 3rd.
If people have questions, there is a summary of the changes and an
extensive FAQ at https://www.mediawiki.org/wiki/Typography_refresh. There
will also be a post at blog.wikimedia.org tomorrow morning, and we have
other messages to go out on-wiki.
Wikitech-l subscribers: you may remember an extensive recent thread that
mostly debated the use of non-free fonts like Helvetica Neue and Georgia as
the primary fonts in the new font-family settings. We took this feedback to
heart. Thanks to patches/testing led by Ryan Kaldari and Vibha Bamba, we
released a new version a couple weeks ago, which puts a set of fine FOSS
fonts first (say that ten times fast). For the curious, the relevant patch
is gerrit 120978.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
Hi all
I have submitted a proposal on captcha improvements as a GSoC project and i
have come to know that I need to complete some microtasks assigned by a
mentor in order to prove i am capable of handling the project. My problem
is how to get somebody to mentor my project? How can i have the microtasks
i should do?
Thanks
RuchirangaW
Pronunciation samples in Wiktonary, or even tools to ease creating them
are a frequently requested subject on feedback pages [1].
There have been considerations about IPA -> voice solutions but I
believe that audio recording and uploading through crowd sourcing has
several benefits: Dialects can be recorded and the recording user is not
required having knowledge about the IPA. Additionally, a voice-recording
tool may be used for other purposes in future as well, for example
spoken Wikipedia, provided that necessary free audio compression tools
are developed.
Now that UploadWizard[2], which a MediaWiki extension prototype[3]
depends on, needs a lot of refactoring, I proposed developing a gadget
with close community involvement. Future extension development will
benefit from that by means of feedback, metrics collected and
implementation.
The goal is producing something that is actually working, intuitive to
use and easy to deploy for Wiktionary administrators.
Please share your opinion on
https://meta.wikimedia.org/wiki/Grants:IEG/Finish_Pronunciation_Recording#D…
--
Rainer Rillke
https://commons.wikimedia.org/wiki/User:Rillke
[1]
https://meta.wikimedia.org/wiki/Grants:IEG/Finish_Pronunciation_Recording#W…
[2] https://www.mediawiki.org/wiki/Extension:UploadWizard
[3] https://www.mediawiki.org/wiki/Extension:PronunciationRecording
Hello,
Could someone please tell me if there's any way to have an #ask query
return sub-categories? I've tried all the different configuration
options and nothing seems to allow it.
For example if I write the query {{#ask:[[Category:Foo]]}} then all the
normal pages which are categories in Foo will show up in the results,
but none of the sub-categories of Foo.
Thanks,
Aran