We are now working on the "Cases" page of the draft Code of conduct.
This will become a separate page (for readability of the final CoC), but
is being drafted on the same page with the rest.
This includes both the intro section, and all the sub-sections, which
means everything that starts with "2." in the ToC. Currently this is
"Handling reports", "Responses and resolutions", and "Appealing a
resolution". However, the sections within "Cases" may change:
* Section:
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_conduct_…
* Talk:
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finishing_the_Cas…
* Alternatively, you can provide anonymous feedback to
conduct-discussion(a)wikimedia.org .
This is the best time to make any necessary changes to this page (and
explain why, in edit summaries and/or talk) and discuss it on the talk page.
Other updates:
* The text of the "Report a problem" section has been frozen. Thanks to
everyone who helped discuss and edit these sections. Participation
(including both named and anonymous) helped us improve the
confidentiality line.
Thanks,
Matt Flaschen
Hi!
A couple of months ago I taught a workshop for learning ClojureScript at a
conference, and for the second part I had the students play with a web app.
I set up a scaffold and api fetching/cleaning the media of the month from
commons so that they could code and test stuff.
I thought I would share, it's pretty stupid but the result is clean and
beautiful to read (because the pictures are beautiful).
http://chimeces.com/photo-of-the-day/ (it's media of the month, excuse the
url :p)
Source is at https://github.com/joakin/photo-of-the-day
If you want to learn the ClojureScript language you can try to follow the
online version of the workshop:
*
http://chimeces.com/cljs-browser-repl/#/notebook/diving-into-clojurescript/…
And play with this repo when you're done!
Cheers,
Joaquin
Hi everyone!
I've got a little question about how to control caching of a RL module. But first, my case:
I've several (four) modules defined that depend on each other. Most of them are defined as a FileModule using $wgResourceModules with 'styles', 'scripts', 'messages', .
One of them is implemented as a class that derives from ResourceLoaderModule (not ResourceLoaderFileModule). I've grouped (using the 'group' entry in $wgResourceModules) them so they all get loaded together in one request (and separately from other modules).
This module group delivers pretty static content, but much of it (approx. 2MB). So it would be ideal to cache it on the client side.
Unfornuately the load.php call always incudes a 'version' parameter with the current timestamp and the 'expires' header of the response is set to "now". So no client caching. I believe it has something to do with my custom ResourceLoaderModule subclass. I've already tried to override methods like "getModifiedHash" or "getModifiedTime" but without success.
What can I do to get rid of the 'version' parameter in the load.php call and the 'expires' header?
--
Robert Vogel
Hi!
I would be participating in the Grace Hopper Celebration - India Chapter
<http://gracehopper.org.in> this year (Dec 2- Dec4, 2015) and wanted to
know if there's anyone else from our community who'd be joining in the
event? Till now, I am aware of only one other community member, Santoshi
Tiwari, who would be there too.
GHCI will have a lot of participants and particularly females. A lot of
students would be attending too. It'd be great to know all the Wikimedians
who would be attending GHCI and thus, plan in advance to make people aware
about Wikimedia and how can they become contributors to the movement.
Similar to the initiative in GHC, here is something for the Grace Hopper
Celebration India. I have created a Slack community
<https://ghci15.slack.com/> for the participants of GHC-India 2015.
To join the Slack group, simply fill in this
<https://docs.google.com/forms/d/1tjzN3u6C6aHDy7zJRrEbezlkwMOYF-Tk6cHmA1k1hj…>
easy form and you'll receive an invite for the Slack community.
After you join the Slack channel, you'll have the access to a Google doc
with
information of arrivals and departures per day to share, rides from and to
airport and a lot of more information which will be build up by the
participants.
Also, please invite other participants you know who might be participating
but are not enrolled on this mailing list. I also invite other ABI members
to join the channel and share useful information with us.
Special thanks to Nithya Pari for the original idea. :)
--
Thanks and Regards,
Ankita Shukla
Computer Science Engineering
B.Tech Final Year (Senior)
Indian Institute of Technology Roorkee
Hello,
I am Bill Morrisson, a 4th year Under graduate Student from Catholic
University Insitute, Buea, Cameroon.
I want to contribute to Wikimedia's opensource projects. I am a newbie in
PHP and MySQL(just started learning the language 8 months ago) and had in
mind in contributing to the organization as soon as I am comfortable in the
languages.
I would like to contribute in PHP and looking forward to learn javascript
on the go with other projects as well. I would love to hear from wikimedia
if there is anything I can do first.
Thank you
Hi all,
here is the weekly look at our most important readership metrics, a bit
belatedly this time.
As laid out earlier
<https://lists.wikimedia.org/pipermail/mobile-l/2015-September/009773.html>,
the main purpose is to raise awareness about how these are developing, call
out the impact of any unusual events in the preceding week, and facilitate
thinking about core metrics in general. We are still iterating on the
presentation and eventually want to create dashboards for those which are
not already available in that form already. Feedback and discussion welcome.
For readers of this report who haven’t already seen it, I’d like to mention
the exciting announcement
<https://lists.wikimedia.org/pipermail/analytics/2015-November/004529.html>
of the new pageview API for per-article readership metrics.
Now to the usual data. (All numbers below are averages for November 9-15,
2015 unless otherwise noted.)
Pageviews
Total: 540 million/day (+0.7% from the previous week)
Context (April 2015-November 2015):
(see also the Vital Signs dashboard
<https://vital-signs.wmflabs.org/#projects=all/metrics=Pageviews>)
Some may remember that back in September, this weekly report called
<https://lists.wikimedia.org/pipermail/mobile-l/2015-September/009794.html>
out
<https://lists.wikimedia.org/pipermail/mobile-l/2015-September/009785.html>
a “conspicuous 4.3% drop” in total pageviews during the week until Sept 20
(followed by another 0.7% decrease the following week). Well, last week the
Analytics team solved that mystery
<https://phabricator.wikimedia.org/T114379#1802927>: An improvement in
detection of web crawlers had caused much more pageviews to be classified
as non-human, from Sept 16 on (e.g. for Commons, estimated human traffic
dropped
<https://vital-signs.wmflabs.org/#projects=commonswiki/metrics=Pageviews>
from about 12 million to about 4 million per day).
Desktop: 57.5% (previous week: 57.5%)
Mobile web: 41.3% (previous week: 41.3%)
Apps: 1.2% (previous week: 1.2%)
Global North ratio: 77.6% of total pageviews (previous week: 77.5%)
Context (April 2015-November 2015):
New app installations
Android: 55.3k/day (-8.8% from the previous week)
Daily installs per device, from Google Play
Context (last month):
As already mentioned in last week’s report, the Android Wikipedia app got
featured in the "New and Updated Apps" section of the Google Play store on
November 5, enabled by the Android team’s recent update work and
facilitated by the Partnerships team. The promotion lasted one week and we
can now see that it was a huge success (with the effect on download numbers
much more clearly discernible than in the case of the “Back to School”
feature we discussed last month
<https://lists.wikimedia.org/pipermail/mobile-l/2015-October/009835.html>).
Predictably, uninstalls went up slightly too, but most of the new users
kept the app on their phone. What is a little concerning though is that
after the promotion, install numbers fell below the previous baseline, with
the install base even shrinking a tiny bit right afterwards. (One
possibility is that we are seeing some sort of depletion effect, due to
people who would have installed the app anyway around this time, but saw it
earlier due to the promotion.) For that reason, we will wait a bit longer
before estimating the overall impact of this promotion.
iOS: 4.59k/day (+4.3% from the previous week)
Download numbers from App Annie
Context (last 12 months):
No big news here - things are back to normal after the App Store feature
last month.
App user retention
Android: 15.2% (previous week: 13.9%)
(Ratio of app installs opened again 7 days after installation, among all
installed during the previous week. 1:100 sample)
Context (last three months):
Recall that this metric lags one week behind, so to speak. I.e. the effects
of the Play Store promotion are not fully visible yet above (spoiler
though, having looked at a few more days of data already: retention for
installs who had come in during the promotion does not appear to have been
lower than usual, which is good news).
In general, this data is quite noisy due to the low (1:100) sample rate.
iOS: N/A
(Ratio of app installs opened again 7 days after installation, among all
installed during the previous week. From iTunes Connect, opt-in only = ca.
20-30% of all users)
Unfortunately I encountered some data quality issues with this metric this
week. Will investigate, and report iOS retention again once this is sorted
out. (The numbers and charts provided in the iTunes Connect App Analytics
appears to have changed quite a bit retroactively.) Unique app users
Android: 1.217 million / day (+2.7% from the previous week)
Context (last three months):
A somewhat noticeable rise that could well be connected with the
aforementioned Play Store promotion, but still needs a closer look once
more data is in.
iOS: 281k / day (+0.2% from the previous week)
Context (last three months):
No news here.
----
For reference, the queries and source links used are listed below (access
is needed for each). Most of the above charts are available on Commons, too
<https://commons.wikimedia.org/w/index.php?title=Special:ListFiles&offset=20…>
.
hive (wmf)> SELECT SUM(view_count)/7000000 AS avg_daily_views_millions FROM
wmf.projectview_hourly WHERE agent_type = 'user' AND
CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-11-09"
AND "2015-11-15";
hive (wmf)> SELECT year, month, day,
CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date,
sum(IF(access_method <> 'desktop', view_count, null)) AS mobileviews,
SUM(view_count) AS allviews FROM wmf.projectview_hourly WHERE year=2015 AND
agent_type = 'user' GROUP BY year, month, day ORDER BY year, month, day
LIMIT 1000;
hive (wmf)> SELECT access_method, SUM(view_count)/7 FROM
wmf.projectview_hourly WHERE agent_type = 'user' AND
CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-11-09"
AND "2015-11-15" GROUP BY access_method;
hive (wmf)> SELECT SUM(IF (FIND_IN_SET(country_code,
'AD,AL,AT,AX,BA,BE,BG,CH,CY,CZ,DE,DK,EE,ES,FI,FO,FR,FX,GB,GG,GI,GL,GR,HR,HU,IE,IL,IM,IS,IT,JE,LI,LU,LV,MC,MD,ME,MK,MT,NL,NO,PL,PT,RO,RS,RU,SE,SI,SJ,SK,SM,TR,VA,AU,CA,HK,MO,NZ,JP,SG,KR,TW,US')
> 0, view_count, 0))/SUM(view_count) FROM wmf.projectview_hourly WHERE
agent_type = 'user' AND
CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-11-09"
AND "2015-11-15";
hive (wmf)> SELECT year, month, day,
CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")), SUM(view_count) AS
all, SUM(IF (FIND_IN_SET(country_code,
'AD,AL,AT,AX,BA,BE,BG,CH,CY,CZ,DE,DK,EE,ES,FI,FO,FR,FX,GB,GG,GI,GL,GR,HR,HU,IE,IL,IM,IS,IT,JE,LI,LU,LV,MC,MD,ME,MK,MT,NL,NO,PL,PT,RO,RS,RU,SE,SI,SJ,SK,SM,TR,VA,AU,CA,HK,MO,NZ,JP,SG,KR,TW,US')
> 0, view_count, 0)) AS Global_North_views FROM wmf.projectview_hourly
WHERE year = 2015 AND agent_type='user' GROUP BY year, month, day ORDER BY
year, month, day LIMIT 1000;
https://console.developers.google.com/storage/browser/pubsite_prod_rev_0281…
(“overview”)
https://www.appannie.com/dashboard/252257/item/324715238/downloads/?breakdo…
(select “Total”)
SELECT LEFT(timestamp, 8) AS date, SUM(IF(event_appInstallAgeDays = 0, 1,
0)) AS day0_active, SUM(IF(event_appInstallAgeDays = 7, 1, 0)) AS
day7_active FROM log.MobileWikiAppDailyStats_12637385 WHERE timestamp LIKE
'201511%' AND userAgent LIKE '%-r-%' AND userAgent NOT LIKE '%Googlebot%'
GROUP BY date ORDER BY DATE;
(with the retention rate calculated as day7_active divided by day0_active
from seven days earlier, of course)
https://analytics.itunes.apple.com/#/retention?app=324715238
hive (wmf)> SELECT SUM(IF(platform = 'Android',unique_count,0))/7 AS
avg_Android_DAU_last_week, SUM(IF(platform = 'iOS',unique_count,0))/7 AS
avg_iOS_DAU_last_week FROM wmf.mobile_apps_uniques_daily WHERE
CONCAT(year,LPAD(month,2,"0"),LPAD(day,2,"0")) BETWEEN 20151109 AND
20151115;
hive (wmf)> SELECT CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0"))
as date, unique_count AS Android_DAU FROM wmf.mobile_apps_uniques_daily
WHERE platform = 'Android';
hive (wmf)> SELECT CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0"))
as date, unique_count AS iOS_DAU FROM wmf.mobile_apps_uniques_daily WHERE
platform = 'iOS';
--
Tilman Bayer
Senior Analyst
Wikimedia Foundation
IRC (Freenode): HaeB
Hi,
I'm working on a project to improve the categorization of pictures in the
Upload to Commons Android app <https://phabricator.wikimedia.org/T115101>
with Nicolas_Raoul and Niedzielski as part of the Outreachy Dec '15
program. I'm very much just starting out, so I'd love any feedback or
suggestions that anyone might have.
We are planning on two major phases/releases for app updates, with Phase 1
enabling category suggestions based on the picture's location, and Phase 2
enabling more flexible category search results. It would be a huge help if
we had some volunteers to test these releases (planned for Jan and Feb
respectively), so it would be great if anyone could download the app <
https://play.google.com/store/apps/details?id=fr.free.nrw.commons> and try
it out. The source code and issues are stored on GitHub <
https://github.com/misaochan/apps-android-commons>.
Many thanks! :)
Josephine
Hi everyone,
I mopped up a bunch of Brion's time and expertise earlier this week,
did some futzing, discussed it a little with ArchCom, and and came up
with a set of working areas that are reflected on Phab[1] and on
mediawiki.org[2]
Here's the list that's posted in Phab:
- Content format [T119022] -
This is about the format of our data, with a primary emphasis on the
future of Wikitext & markup (or possibly, the future of eliminating
it). The central problem in this area: "how do we make manipulating
our data easier and more useful" (both for humans and computers)
- Content access and APIs [T119029]
this is about getting our data in-and-out of the system (e.g.
rest.wikimedia.org). The central problem in this area: "how do we
make accessing and distributing our data easier and more useful?"
- Collaboration [T119030]
this is about how we work together. Central problem: "how do we
scale editing our code up to populations similar to editing our
projects, proportionally increasing our positive impact and
productivity?"
- Software engineering [T119032]
this is about building and delivering high quality code. Central
problem: "how do we build high-quality software that we can
dramatically increase the number of people that can understand it
while increasing the reliability and maintainability of Wikimedia
sites?"
- User interface presentation [T119162]
improving our user interactions. Central problem: "how to we make
our software look and feel joyful to use?"
We have some initial nominees (mostly from ArchCom) to lead up the
selection process, but really, now is the time to demonstrate a
combination of volunteer spirit and leadership if you would like to
influence outcomes for the better. My initial nominations were a
combination of gut feel and nominees not saying "no". :-)
Please head to Phabricator and comment in the specific areas about
your vision about what we should emphasize at WikiDev 16.
Rob
[1] https://phabricator.wikimedia.org/T119018
[2] https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016/Scope#Workin…