Hello,
I’ve been learning how to use Moses decoder [1] for creating machine translation models for the Uzbek language and was wondering if anyone else has any experience with. After talking to Amir, we decided to set Moses up in a Labs instance. Is anyone else interested in this? How was your experience with the decoder?
Thanks,
Baha
[1] https://github.com/moses-smt/mosesdecoder
I invite review of this preliminary proposal for a Google Summer of
Code project:
http://www.mediawiki.org/wiki/Accuracy_review
If you would like to co-mentor this project, please sign up. I've been
a GSoC mentor every year since 2010, and successfully mentored two
students in 2012 resulting in work which has become academically
relevant, including in languages which I can not read, i.e.,
http://talknicer.com/turkish-tablet.pdf .) I am most interested in
co-mentors at the WMF or Wiki Education Foundation involved with
engineering, design, or education.
Synopsis:
Create a Pywikibot to find articles in given categories, category
trees, and lists. For each such article, add in-line templates to
indicate the location of passages with (1) facts and statistics which
are likely to have become out of date and have not been updated in a
given number of years, and (2) phrases which are likely unclear. Use a
customizable set of keywords and the DELPH-IN LOGIN parser
[http://erg.delph-in.net/logon] to find such passages for review.
Prepare a table of each word in article dumps indicating its age.
Convert flagged passages to GIFT questions
[http://microformats.org/wiki/gift] for review and present them to one
or more subscribed reviewers. Update the source template with the
reviewer(s)' answers to the GIFT question, but keep the original text
as part of the template. When reviewers disagree, update the template
to reflect that fact, and present the question to a third reviewer to
break the tie.
Possible stretch goals for Global Learning Xprize Meta-Team systems
[http://www.wiki.xprize.org/Meta-team#Goals] integration TBD.
Best regards,
James Salsman
Please join us for the following tech talk:
*Tech Talk**:* Hack: An Evolution of PHP
*Presenter:* Josh Watzman from Facebook
*Date:* March 4th
*Time:* 1800 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=Hack%3A+An+Evoluti…>
Link to live YouTube stream <http://www.youtube.com/watch?v=jqXqdqUhxy8>
*IRC channel for questions/discussion:* #wikimedia-office
Google+ page
<https://plus.google.com/u/0/b/103470172168784626509/events/ckh4leo7qam35mc5…>,
another
place for questions
*Talk description: *Although PHP has several features that allow engineers
to be extremely productive in it, it also has several rough edges and
pitfalls that cause problems (and often give the language a bad name). This
talk will introduce Hack, Facebook's dialect of PHP. Hack keeps most of the
PHP language -- all of the parts that make engineers so productive -- but
sands down several of the more problematic sharp edges. It also introduces
several new features, such as a simple yet extremely powerful syntax for
asynchronous IO, to make the language even more effective for existing PHP
programmers and newcomers alike.
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)
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
(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.
> However, when I log in and look at the special user rights management
> page for my own userid, I see that I am in no specific group except for
> the implied group of 'autoconfirmed users' and Administrators. There are
> checkboxes for the Administrators, Bureaucrats and 'editor' groups, but
> none of them are ticked. If I tick a checkbox, and then click save, it
> says the setting has been saved but unchecks the checkbox again.
>
It sounds like UserRights can't reasonably handle groups that are both
implied (e.g. by autopromotion) and actually grant-able to specific users
(where the target user already has implied access?). I'm not entirely
surprised - I'm not sure we officially support that configuration?
> Secondly, and more worryingly, is that if I log in using the
> 141.163.4.11 IP address, and look at the special user rights page, it
> shows everyone as being in the 'Administrators' (sysop) group! If I take
> out the autopromote from the LocalSettings file, then no-one (other than
> the original account created during installation) is shown as being in
> the Administrators group. Very strange.
>
Okay, matching APCOND_ISIP (and APCOND_IPINRANGE) is based on checking
$user->getRequest()->getIP().
But take a look at what User::getRequest does:
https://phabricator.wikimedia.org/diffusion/MW/browse/master/includes/User.…
So it'll determine every user's eligibility for autopromotion... Using the
current requester's IP. Depending on who requests a page (or indeed, from
which IP), the wiki will have different admins. That's ridiculous.
There probably can't be much more useful behaviour from User::getRequest -
a user doesn't have an assigned IP address, and could have made different
sorts of actions from different IPs (log in, edit, etc.) - you wouldn't
want to autopromote any user account that's ever logged in from that
Plymouth University IP, for example. All we can do is look at the current
requester's IP.
I wonder why we're not just throwing an exception when code tries to call
User::getRequest for a User other than the one making the request... Maybe
we just shouldn't even have a User::getRequest function at all.
Alex.
Hi!
Anomie, bd808, CSteipp, and myself have been working on updating Tyler's
previous AuthStack RfC:
<https://www.mediawiki.org/wiki/Requests_for_comment/AuthManager>.
Our goal is to build an authentication system that is flexible enough to
support the variety of usecases that MW currently supports and those it
should support in the future, without requiring tons of hooks or ugly hacks.
Please leave comments and feedback on the talk page :)
Thanks!
-- Legoktm
Hi everyone,
I'm pleased to welcome Eric Evans as a new engineer in our Services team.
Eric lives and works in San Antonio, TX
Eric's formative years in his current career were at Rackspace, which at
the time he joined (February 2000) was a small 30 person hosting company in
southern Texas. At the beginning of his tenure, he was responsible for
customer-facing sysadmin work. As he progressed with increasing
responsibilities, he eventually led a small team in the architecture and
implementation of a multi-petabyte storage system that would become
Rackspace's Cloud Files offering. By the time he left Rackspace, he was a
core contributor on the Cassandra storage software project, contributing
CQL (Cassandra Query Language) among other things. He also is given
credit/blame for having coined the term "NoSQL".
Eric left Rackspace in 2011, and has since worked in a couple of
Cassandra-related roles, first at a London-based startup (Acunu) where he
honed his remote collaboration skills, and later at The OpenNMS Group,
where he developed Newts, a Cassandra-backed time series data store used as
part of the larger network management stack.
Eric has deep roots in the free software world, and contributes even when
not strictly necessary for his job. He is a longtime contributor to the
Debian Project, where he met our very own Faidon Liambotis, and hence, a
big reason why he's here. He also created Lumens, which is software for
controlling Chrismas light displays.
Eric's first job here is to help get RESTbase ready for production use.
RESTbase is a Cassandra-backed (see a theme yet?) revision caching/storage
architecture which we're initially using to accelerate VisualEditor load
times. Everyone involved is really excited to get someone with Eric's depth
of experience in this area, and looking forward to seeing big things here.
Eric starts working remotely today, and can be found on the
#wikimedia-services IRC channel, using the nick "urandom". He'll also be
visiting our SF office the week of March 9-13.
Rob