Hi,
For about as long as they've been around, I've been using the HTTPS
urls for Wikipedia and sister projects. Right now, there is basically
no way I'm leaving the secure site, with one exception: the email
messages I receive when I have a new message or when a watched page
changes. This is annoying, because I'm not signed in on HTTP and I
cannot track those visits.
Is there any way I can "tell" MW I want to receive emails with the
https urls? If not, is there at least a bug for that?
Thanks,
Strainu
Can an extension detect that a given article has been transcluded from a given namespace? Here's why I ask.
On our wiki, we have an extension with a special restriction: it can be used only in a specific namespace, N. So it contains logic like this:
if ($title->getNamespace() == NS_N) {
// render
} else {
// display an error message
}
This works fine, but I would also like to permit articles in namespace N to be transcluded into other namespaces:
{{N:My article}}
This fails the extension's "Namespace = N" test and displays the error message. So I really want the logic to be:
if ($title->getNamespace() == NS_N || $title was transcluded from namespace N) {
// render
} else {
// display an error message
}
Is this doable?
Thanks,
DanB
Hi All,
Ryan Lane and I are migrating gerrit's db to a server in eqiad (where the
gerrit app server is located) on Friday, and have a downtime window of
18:00-19:00 UTC (11am-12pm PDT). Actual downtime should be shorter.
Gerrit makes many mysql queries for some page requests; this will improve
the latency of such pages. Additionally, the new db will have both slow
and sample based query profiling in ishmael which should assist with
further optimizations.
-A
-----END PGP SIGNATURE-----
--
Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas
Infomed: http://www.sld.cu/
Hi,
Given that we are going to use labsconsole wiki (which is later going
to be renamed to wikitech) as a documentation base for various
software and server documentation, we should propose a way how this
new documentation base is going to be organized.
I would prefer to create new namespace Documentation (Help is already
used as a help for labsconsole interface) or Docs (shorter), with
following layout where all items are prefixed with category name:
Documentation:Contents - the index page which contains links to subpages
Documentation:Server/<cluster>/<host> for various documentation
related to each server which needs some, either virtual instances on
labs (cluster would be labs in this case) or real servers as we have
now on wikitech
Documentation:Bots/<botname> for documentation of each bot we run on
wikimedia project
Documentation:Software/<name> for documentation of various software /
libraries such as pywikipediabot etc
In addition we could put each page to a category. I know that we could
put all pages in root (Documentation:<name>) and use only categories
but using category in URL has two advantages: If we prefix each page
with category name we avoid conflicts of names as well as it's clear
which category item belongs to just from URL. For example
Documentation:Bots/Cluebot would clearly be a documentation page for
cluebot we use on english wiki, while
Documentation:Server/labs/cluebot could be a server on labs where
cluebot would be hosted
If you agreed with this idea, I would open a ticket to create this
namespace on labsconsole and started to move some documentation there,
especially for bots project which is lacking docs a lot
I currently have a set of internal users for our wiki that have
Administrator access. I also have a set of external users (our customers)
that can only read pages and create discussion pages.
I would like to remove the permission from our customers that allows them
to access the History tab. I looked into the
Extension:GroupPermissionsManager, but we use PHP 5.3.1 and we plan on
upgrading to Mediawiki 1.19 soon, so that doesn't work.
Is there an alternative you recommend? I have removed the history tab from
our CSS, but users could still access the direct url of the history page if
they wanted. I would like a resolution that denies them access, but still
allows myself and other admins to access it.
Thank you,
--
**
*Meghan Mahar*
Technical Writer
Appian Corporation <http://www.appian.com/> | 1875 Explorer Street, 4th
Floor | Reston, VA 20190
T: 703.442.8844 | C: 703.609.0306 | *meghan.mahar(a)appian.com*
I'm forwarding this (below) on behalf of the Fanlore community, which is
seeking some volunteer help. Fanlore is an important archive for the
speculative fiction community. I'd appreciate it if someone could take
a few hours to help them with their current needs, and I'd be delighted
if you could mentor some of their volunteers so they could fix their own
long-term needs.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Fanlore (fanlore.org) is a wiki about fan culture and history that can
be edited by anyone who registers. The wiki is a volunteer project of
the Organization for Transformative Works (transformativeworks.org).
It's a few years old now, and in need of advice on the technical
front.
We're looking for someone who, basically, knows enough about MediaWiki
and wiki spam protection to know what Fanlore needs. We need a
technical liaison whose role would be to advise us (the OTW's wiki
committee) on what improvements are needed, and which
software/extensions we need to make those improvements. Someone with
knowledge about MediaWiki skins would be ideal. Our current default
skin, WordPress, has an unfortunate bug that prevents image centering,
and the skin is deprecated or soon-to-be deprecated in the most recent
versions of MediaWiki. We'll need to switch skins eventually, but
before we can do that, we need to redesign the infobox templates
because those were originally designed mainly to work with the default
skin. We already have people with knowledge of CSS and HTML, but no
one with advanced knowledge of wiki templates.
In addition to our current needs, long-term maintenance of the wiki
also involves investigating (rare) bug reports from users. The
technical liaison would investigate the bugs and determine whether
they can be fixed, how to fix them, and who can fix them.
We're currently in the testing phase for a MediaWiki upgrade, but it's
been plagued with various technical and personnel availability issues
and isn't going very quickly. The MediaWiki upgrade will theoretically
help our spam problem because better tools are compatible only with
the more recent versions. In the meantime, we're also testing
recaptcha and will use that to prevent spambots from signing up.
However, recaptcha isn't our favorite, and we're hoping we can revisit
our spam solutions once we upgrade MediaWiki.
Anyone who's interested in advising us on how to whip Fanlore's
MediaWiki installation into shape, please mail
wiki(a)transformativeworks.org with any questions and we'll get back to
you as soon as possible.
Looking forward to hearing from you,
The OTW wiki committee
Hi All,
Please join me in welcoming S Page as Software Engineer in WMF’s Editor
Engagement Experiments (E3) engineering team.
Some interesting facts about S - yes his name really is 'S', cf. Ford
designer "J Mays". S has been a ski instructor at Squaw Valley and a road
sweeper for the Royal Borough of Kensington & Chelsea. At Sun Microsystems,
S wrote technical documentation for James Gosling and Bill Joy, programmers
so l33t they wrote their own text editors. S has many enthusiasms but the
most relevant ones are SFMOMA 250m West, pinball at Metreon 500m West, and
the snow 300 km East. S is also a Wikipedian, editor on en.wp since
November 2005 and Semantic Mediawiki contributor.
Ping S online or stop by WMF's 3rd floor to say hello in person. He’s
available as @spage on our irc channels including #mediawiki,
#wikimedia-dev and #wikimedia-e3.
Welcome S! Happy to have you onboard the E3 team.
-Alolita
--
Alolita Sharma
Director of Engineering
Wikimedia Foundation
Hello Everyone,
Please welcome Peter Youngmeister who joins us today (7/9/12) as a
full-time member of the Technical Operations staff. He has been working as
a contractor with the Foundation since last March 2011. Prior to that, he
was with another great non-profit, kiva.org.
Peter lives in Ann Arbor, MI, but is a Bay Area native and is around the
office fairly often. You may have also run into him on IRC as notpeter. He
is excited to be finding a more permanent home in the Wikimedia Ops team,
so that he can continue protecting the data and fighting for the user. His
interests include, metal working, fire sculpture and fire performance art,
fine tea and fine liquors, and vegan cooking.
Thanks,
CT