This regular bi-weekly pattern of reported page views
http://stats.grok.se/sv.s/latest90/Wikisource:Projekt_Bibel%C3%B6vers%C3%A4…
is created by a bot job. Note that this is a WikiProject page.
Are the reported number of page views inflated by bots?
Is there no way to filter out bot visits?
In other news, this page has a weekly pattern of real,
human visitors, since it is a radio quiz where lots of
listeners are known to use google searches,
http://stats.grok.se/sv/latest90/Melodikrysset
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se
Assuming wikitech-l also has some people interested in this.
---------- Forwarded message ----------
From: Yuvi Panda <yuvipanda(a)gmail.com>
Date: Mon, Aug 20, 2012 at 11:38 PM
Subject: Announcing Signpost for Android app 1.0 RC1!
To: mobile-l <mobile-l(a)lists.wikimedia.org>
Me and a friend ([[User:Notnarayan]])) have been working on a Signpost
app in our spare time for a while. This lets you access Wikipedia
Signpost from a mobile device in a nice and (hopefully) beautiful way.
More information at https://www.mediawiki.org/wiki/Signpost_Mobile_App
Today, I'm putting out RC1 of the version 1 of this app. You can
download it at https://github.com/yuvipanda/WPSignpost/WPSignpost-1.0RC1.apk/qr_code
and file issues at
https://github.com/yuvipanda/WPSignpost/issues?state=open.
You can find screenshots of the current version of the app at
https://commons.wikimedia.org/wiki/Category:Wikipedia_Signpost_Android_App_…
For this version, features so far are:
1. Load current issue of the Signpost
2. Browse through and load any previous issue of the Signpost
3. Beautiful Image based display of each signpost issue
4. Articles are formatted easily for viewing on your mobile device
5. Sharing of articles from the app
All of them have been implemented, and provided no major new issues
are found, I'll push this version to the Google Play store in a week.
Please do test it out on your device, and report issues either at the
github url specified above or by replying to this email.
--
Yuvi Panda T
http://yuvi.in/blog
Greetings WLM testers,
Below you'll find a new beta of our android app that's very close to being
feature complete.
As before, make sure to have "Unknown sources" in Settings => Applications
turned on.
Uploads will go to test wiki so feel free to upload whatever you like.
Download:
http://dumps.wikimedia.org/android/WLM-v1.1beta2.apk
Feedback:
http://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application/Feedb…
Please try the following:
* Browse by campaign and drill down to the desired region's monuments
* Sort the list by name and address
* Search with a search term
* Open a monument, click on "Get directions"
* Click on add a photo
* Login or create a Commons account
* Choose from gallery or take a photo
* Choose "Save for Later" on the Confirm Upload screen
* Go back to the opening screen
* Click on "Use my current location"
* Move around the map, open a cluster (a group of monuments close together)
* Click on a pin, open the monument
* Add a photo (login should be retained)
* Choose "Save for Later" on the Confirm Upload screen
* Click OK and choose or take another photo
* Go to Uploads and see the uploads saved for later
Let us know what you think!
Known issues:
* Browse by country shows coded region names in some places
* Incomplete/Completed Uploads tab is buggy
* Upload of incomplete uploads not yet functional
* Some back behavior is inconsistent
* Sort by distance appears when browsing by country
* List view should have a "more" link when lists exceed 100 monuments
Please forward this email as appropriate.
--
Phil Inje Chang
Product Manager, Mobile
Wikimedia Foundation
415-812-0854 m
415-882-7982 x 6810
--
Phil Inje Chang
Product Manager, Mobile
Wikimedia Foundation
415-812-0854 m
415-882-7982 x 6810
Have you wondered how GiGeGat [1] works for volunteer developers if
even paid developers have difficulties with it? We have already seen
cases where it works, but we don't know much about the cases where
volunteers decide to give up.
Here, however, is one example [2] of the latter which I want to
highlight. The developer finds it too slow and complicated and wants
to move to GitHub and as consequence we cannot provide translation
services for his extensions at translatewiki.net.
Anyone willing to dig deeper what problems there are and try to resolve them?
-Niklas
[1] My favorite abbreviation for Git, Gerrit and Gated trunk
[2] http://translatewiki.net/wiki/Thread:Support/Add_MediaWiki_Extensions_from_…
--
Niklas Laxström
The SignupAPI I developed indeed takes care of everything required and was
truly developed to cater to such requirements. It would not be a good idea
to rework the same. A lot of brainstorming and architectural discussions
were already done while developing this project & it received input on
several different aspects from the community. I really think that instead
of developing something new, Extension:SignupAPI should be given a chance
for deployment because it solves several requirements including the
tracking of what events are most effective in creating accounts and then
having the ability to suggest suitable exit activities. Also, the UI was
totally revamped to make it visually appealing. Client side validations for
user input have also been implemented including the ability to alert user
if his desired username has already been taken while he enters it on the
signup form. The extension also does a lot of refactoring of the existing
SpecialLoginPage by taking out the account creation logic from it and then
putting it in its own API. The extension has also received extensive
testing by several developers including Santhosh who tested it out with
internationalized usernames & suggested relevant bugs which I fixed.
Some things came up and I didn't get back to working on SignupAPI, but I'm
really keen on helping now & wish to work towards deploying the extension.
I need a mentor to help me through the process because it seems that many
parts of the development process have significantly changed.
Thanks & Regards
Akshay Agarwal
Software Developer
Directi
Makes sense. IMHO most of the stuff I mentioned is just minor qualms. The
overall syntax is pretty nice, and I think it'd be a great idea to have
something like this.
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com | tylerromeo(a)gmail.com
On Sun, Aug 19, 2012 at 7:12 AM, Daniel Friesen
<daniel(a)nadir-seen-fire.com>wrote:
> On 12-08-18 10:37 PM, Tyler Romeo wrote:
>
> I think this is an awesome idea and I'd be willing to help on this.
>
> I have a few questions about the page linked above though:
>
> - Why don't we use foreign keys in MySQL?
>
> We don't use them now so I didn't use them in the abstract table schema
> types. PostreSQL and iirc Oracle use them so I added reference(), it also
> acts as a documentation hint. We could regenerate the table schema
> documentation based on this. This time around directly extracting what
> column refers to another out of the code.
> For MySQL, FKeys actually lower performance, but in any case if you think
> we should use foreign keys we should have a wikitech-l discussion over it.
>
>
>
> - The word "hack" is used three times. That's probably an issue. ;)
>
> Heh. Yeah. Though how else do we handle the few spots where a part of
> our database schema goes and does something complete out of line from the
> rest of the schema?
> eg: cl_timestamp uses timestamp instead of our binary(14).
>
>
>
> - Is there a reason we're changing the default from NULL to NOT NULL?
> Wouldn't it be better to just use a "required" keyword?
>
> 95% of our column definitions are NOT NULL. In fact not allowing null is
> practically a default, you don't really allow null unless you make an
> explicit decision that you want null values.
> So I made NOT NULL the default and made allowing null an explicit nullable
> flag.
> NOT NULL only prevents you from setting a field as null. It doesn't make
> it required because most other fields will still default to something like
> 0, '', or some other default that's specified. So "required" doesn't really
> fit the meaning
>
>
>
> - We should probably support MySQL's -- comment syntax, just in case.
>
> Yeah I planned to from the start. Just include opening #, --, and //
> comments inside the parser.
> Although, when it came to table alters I started contemplating the --
> comment vs. -column; parsing and rethought that.
> Though thinking about it again, the parsing will probably work fine.
>
>
>
> - What's the [ignore] on the insert call do? (It becomes a little
> confusing since there is also the [tablename] syntax on global indexes.)
>
> That was for INSERT IGNORE. After I noticed that some of our
> archive/*.sql files use INSERT IGNORE. I dropped the idea of `insert ignore
> tablename ...` because it would be ambiguous for a table named "ignore".
> So yeah, it would be nice to find a better syntax for insert ignore.
> I'm also contemplating if I should find a syntax for INSERT..SELECT since
> we seem to use it in a small number of migrations.
>
>
>
> - The Alter Table syntax looks really weird (with tildas and whatnot).
>
> I started wanting to keep the alter table syntax as close as possible to
> the table definition/creation syntax.
> So I started with prefixing with - and + which work beautifully as DROP
> and ADD column/etc... commands.
> Then when I thought of MODIFY/CHANGE I didn't want to make that unprefixed
> and ~ seemed to work best for that.
>
> But yeah, here and there it could use some ideas for alternative ways to
> do the syntax.
>
>
> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
>
> *--*
> *Tyler Romeo*
> Stevens Institute of Technology, Class of 2015
> Major in Computer Science
> www.whizkidztech.com | tylerromeo(a)gmail.com
>
>
>
> On Sat, Aug 18, 2012 at 2:20 PM, Daniel Friesen <lists(a)nadir-seen-fire.com
> > wrote:
>
>> I see the branch, but I don't see the code:
>>
>> https://svn.wikimedia.org/viewvc/mediawiki/branches/abstract-schema/phase3/
>> It looks like someone just copied phase3 and then never actually changed
>> any code. I don't even see a syntax idea there.
>>
>> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
>>
>> On 12-08-18 11:10 AM, Chad wrote:
>> >
>> > We tried this before, and I'd love to see it happen. Take a look at
>> > the abstract-schema branch in SVN for what we did.
>> >
>> > -Chad
>> >
>> > On Aug 18, 2012 1:53 PM, "Daniel Friesen" <lists(a)nadir-seen-fire.com
>> > <mailto:lists@nadir-seen-fire.com>> wrote:
>> >
>> > We've got a nice abstract query system but our table creation and
>> > migrations are horrible. We re-write them for multiple database
>> > engines. And as a result extensions need to do the same and often
>> > don't. Leading to things being a mess for databases other than
>> MySQL.
>> >
>> > While I was doing the sites stuff a syntax for defining tables
>> > came to mind and I wrote out an RfC for a method of defining our
>> > database abstractly.
>> >
>> >
>> https://www.mediawiki.org/wiki/Requests_for_comment/Abstract_table_definiti…
>> >
>> > --
>> > ~Daniel Friesen (Dantman, Nadir-Seen-Fire)
>> > [http://daniel.friesen.name]
>>
>
Hi,
I´m developing a extension and I need to add an article to a category.
I only get the title of the article, so I try this:
$articleToAdd = new Article($title);
$context = $articleToAdd->getContext();
$resArticle = MediaWiki::articleFromTitle($title, $context);
$linksupdate = new LinksUpdate($resArticle->getTitle(),
$resArticle->getParserOutput(), $f);
$ps = $linksupdate->getParserOutput();
$categoriesLinks = $ps->getCategoryLinks();
..so I get all the categories for the article, but I need to add and remove
a category. How can I do that ?
Thanks!
Maurice.-
We've got a nice abstract query system but our table creation and
migrations are horrible. We re-write them for multiple database engines.
And as a result extensions need to do the same and often don't. Leading to
things being a mess for databases other than MySQL.
While I was doing the sites stuff a syntax for defining tables came to
mind and I wrote out an RfC for a method of defining our database
abstractly.
https://www.mediawiki.org/wiki/Requests_for_comment/Abstract_table_definiti…
--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
Hello,
We didn't have a bug triage since May. I suggest organizing one in a few
weeks (say 2?)
I agree to take care of this if it is widely supported.
How about focusing on patch triage?
I mean reviewing bugs with patches attached but not in gerrit.
Any other subject would be good as well.
opinions?
Matanya