Hi,
Long time ago I purchased domain cswp.cz in order to use it in same
way as enwp.org for czech wikipedia (cswp.org was taken by something).
I think that it would be probably better if it was owned and
maintained by WMF rather than me, but I don't really know where to
ask, neither if ops are actually interested in maintaining it, the
script which redirects the page is pretty simple:
<?php
$uri = $_SERVER['PHP_SELF'];
$target = "http://cs.wikipedia.org/wiki";
header ("Location: $target"."$uri");
exit();
I can't really provide any data on usage of this domain, because I
never collected any, but if there isn't any long-term plan for global
wiki shorteners I think this domain could be used.
Thank you
Hi Community Metrics team,
this is your automatic monthly Phabricator statistics mail.
Number of accounts created in (2015-01): 305
Number of active users (any activity) in (2015-01): 669
Number of task authors in (2015-01): 401
Number of users who have closed tasks in (2015-01): 199
Number of tasks created in (2015-01): 2584
Number of tasks closed in (2015-01): 1775
Number of tasks in the shell project closed as resolved,fixed in (2015-01): 22
Number of open and stalled tasks in total: 19008
Median age in days of open tasks by priority:
Unbreak now: 50
Needs Triage: 132
High: 133
Normal: 417
Low: 691
Needs Volunteer: 531
TODO: Numbers which refer to closed tasks might not be correct, as described in T1003.
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on iridium at Sun Feb 1 00:00:05 UTC 2015)
Hello!
I am pleased to announce that Wikimedia has been selected as a mentoring
organization for the upcoming Google Summer of Code (out of only 137
organizations selected for this round) and Outreachy rounds.
Congratulations!
We have a phabricator board for possible projects[1] students can work on.
Currently, only 7 projects are in the "Featured" column with well-defined
project scope and mentors assigned.
A lot more are sitting in the "Needs Discussion" and "Missing Mentors"
columns, looking forward to your input.
Enlisting some of the more discussed projects here:
- Gadget Usage Statistics [2]
- Out-of-date fact and statistics identification and review [3]
- Cross-wiki watchlists [4]
- Newsletter Mediawiki Extension [5]
Your comments would be greatly appreciated in shaping these ideas into
featured projects for the students.
If you know of other projects which could be a good fit for a 3 month
GSoC/Outreachy round, please feel free to add them to the board.
If you think you can mentor one of these projects, please do comment on the
ticket indicating so.
[1] https://phabricator.wikimedia.org/tag/possible-tech-projects/
[2] https://phabricator.wikimedia.org/T21288
[3] https://phabricator.wikimedia.org/T89416
[4] https://phabricator.wikimedia.org/T5525
[5] https://phabricator.wikimedia.org/T76199
Thank you!
Niharika.
PS: I am a co-organizer for the upcoming GSoC & Outreachy rounds for
Wikimedia, along with Quim. Nice to meet you!
I recently started setting up a server with Varnish and realized that
our instructions for configuring Varnish look terrible. Specifically our
recommendations for Varnish 4.0.
https://www.mediawiki.org/wiki/Manual:Varnish_caching#Configuring_Varnish_4…
That said, while I know things look wrong, I'm not enough of a Varnish
expert to be confident changing the guide.
## Purging
The purge instructions look all wrong.
ban() is not equivalent to ban_url() so the invocations look broken.
Also the Varnish 4 instructions do purging with a `return (purge);` and
omit the vcl_hit and vcl_miss.
See:
https://www.varnish-cache.org/docs/trunk/users-guide/purging.html
## Gzip
The instructions still include Accept-Encoding handling. Varnish now
handles gzip natively.
>From what I understand without this code Varnish will natively prefer
requesting gzipped responses from the server and will handle gunzipping
things for clients that don't support it.
I believe normalizing "gzip, deflate" -> "gzip,deflate" or just "gzip,
deflate" -> "gzip" is also redundant now:
https://github.com/varnish/Varnish-Cache/blob/336f2eb8fe1c8f46dbf32a9bad387…
## XFF
The instructions include the setting of an X-Forwarded-For header to
client.ip as well.
This is redundant. Varnish implements XFF natively. And it does it
correctly, which is to append to XFF when already present. The guide
will end up stripping out information which CheckUser makes use of.
## Redundant and harmful vcl_recv overriding
Varnish's default vcl already does stuff like CONNECT piping,
Authorization and Cookie passing (and now it also handles the absence of
SPDY support).
https://github.com/varnish/Varnish-Cache/blob/master/bin/varnishd/builtin.v…
However the guide duplicates these things and ends with a
`return(hash);` making it so the default vcl is never run.
## If-None-Match
Someone is going to have to explain this block to me, because doing it
does not make sense to me:
if (req.http.If-None-Match)
{return(pass);}
--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
You're welcome. I wonder how APCOND_ISIP and APCOND_IPINRANGE were expected
to work, and if we should deprecate/remove them.
On 28 February 2015 at 23:17, John Horne <john.horne(a)plymouth.ac.uk> wrote:
> On Sat, 2015-02-28 at 03:27 +0000, Alex Monk wrote:
> > (CCing wikitech-l)
> > On 28 February 2015 at 01:04, John Horne <john.horne(a)plymouth.ac.uk>
> wrote:
> > >
> > > $wgAutopromote['sysop'] = array(APCOND_ISIP, '141.163.4.11');
> > >
> > Wait, what? MediaWiki supports that?! You should not do that.
> >
> Yes, MW allowed me to do this, but reading your reply I can see why it
> is not something we want to do. It also explains why the 'user list'
> page seemed to allocate everyone to the administrators group.
>
> We have now changed things a bit in that the 'editor' permissions have
> been pushed into the 'user' group (most were there anyway).
>
> We also removed any other 'autopromote' settings. By logging in using
> the default login mechanism, and with the initially created account, I
> could then set my own account to be administrator and bureaucrat. After
> that everything looked fine.
>
> However, we are intending to use the Shibboleth extension (as forked on
> github) as the main login mechanism. When we reapplied this, my groups
> were gone again! It seems the extension has a bug in that it removes a
> users groups, but never adds them back again. I have corrected this, and
> submitted a patch upstream.
>
> So now we are happy. We have Shibboleth login working fine, and the
> users groups are as they should be and remain so upon login/logout. We
> are now not using autopromote at all.
>
>
>
> Many thanks for your reply,
>
> John.
>
> --
> ----------------------------------------------------
> John Horne Tel: +44 (0)1752 587287
> Plymouth University, UK
>
>
> _______________________________________________
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
Please join us for the following tech talk:
*Tech Talk**:* What's New with MediaWiki-Vagrant?: Simple Use Cases and
Beyond
*Presenter:* Bryan Davis & Dan Duvall
*Date:* November 25th
*Time:* 1830 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=What%27s+New+with+…>
Link to live YouTube stream <http://www.youtube.com/watch?v=I66xR-fq2O8>
*IRC channel for questions/discussion:* #wikimedia-office
Google+ page <http://www.youtube.com/watch?v=I66xR-fq2O8>, another place
for questions
*Talk description:*We'll start off by giving a brief refresher on how
MW-Vagrant works and how it differs from stock Vagrant. Next, we'll
showcase some of the newest and most useful features of MWV such as
multi-wiki support, SSH/HTTP sharing, Labs integration, advanced
customization using Hiera and local roles. Finally, we'd like to show how
MWV can be useful in test-driven development by demonstrating how to run
unit and browser tests. The last 15 minutes will be reserved for Q/A.
== Outline (WIP) ==
* (10 minutes) What is Vagrant, MediaWiki-Vagrant, Puppet (dan + bryan)
* (15 minutes) Local customizations (bryan)
* (15 minutes) Running unit tests and browser tests under MW-V (dan)
* (5 minutes) Vagrant sharing (it's awesomesauce!!!) (bryan)
* (15 minutes) Q & A
Hi Community Metrics team,
this is your automatic monthly Phabricator statistics mail.
Number of accounts created in (2015-02): 317
Number of active users (any activity) in (2015-02): 733
Number of task authors in (2015-02): 422
Number of users who have closed tasks in (2015-02): 216
Number of tasks created in (2015-02): 2952
Number of tasks closed in (2015-02): 2092
Number of tasks in the shell project closed as resolved,fixed in (2015-02): 10
Number of open and stalled tasks in total: 19967
Median age in days of open tasks by priority:
Unbreak now: 17
Needs Triage: 122
High: 104
Normal: 394
Low: 675
Needs Volunteer: 522
TODO: Numbers which refer to closed tasks might not be correct, as described in T1003.
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on iridium at Sun Mar 1 00:00:04 UTC 2015)