Hi,
I have proposed a new research project about the support for correct
diacritics in the readers of the Romanian Wikipedia [1]. The plan I
made is (probably) limited to the desktop site, but Adam suggested
there might be some overlap with the work you are doing around
emerging communities. So, if someone is interested in extending the
study to mobile users or you have any feedback on the project, please
leave a message on the talk page or contact me by email.
Thanks,
Strainu
P.S. Please keep me in the CC for any responses, as I don't get emails
from mobile-l.
[1] https://meta.wikimedia.org/wiki/Research:Usage_of_correct_diacritics_in_rea…
https://code.facebook.com/posts/1365439333482197/how-we-built-facebook-lite…
"To achieve an extremely byte-efficient wire protocol, instead of using
HTTPS, Lite uses a custom message protocol over TLS (directly over TCP).
One of the biggest pain points in a 2G network is that establishing a
connection can be very slow; it can take multiple seconds. As most Lite
traffic flows over a single connection to the backend, this pain point is
mitigated in comparison."
Hey Folks,
Moushira and I are trying to create a low-barrier way for readers,
community members and staff to contribute to a discussion in a structured,
noob-friendly way.
Here is an instance of the 'inputbox' extension that we made:
https://www.mediawiki.org/wiki/User:Jkatz_(WMF)/Sandbox/Community_Consultat…
Unfortunately, none of the pre-loaded values show up in the mobile editor (see
next link
<https://m.mediawiki.org/wiki/User:Jkatz_(WMF)/Sandbox/Community_Consultatio…>).
Is there any way that you know of that we can override whatever setting
does this in order to show the pre-set text? Any help would be appreciated!
Thanks,
J
Cross posting, in case you don't subscribe to wikimedia-l.
---------- Forwarded message ----------
From: James Alexander <jalexander(a)wikimedia.org>
Date: Fri, Mar 4, 2016 at 8:20 PM
Subject: [Wikimedia-l] Wikimedia Foundation Draft Strategy
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Hi all,
The draft Wikimedia Foundation strategy is now posted on Meta
<https://meta.wikimedia.org/wiki/2016_Strategy/Draft_WMF_Strategy> for your
feedback and comments[1]. This stage of feedback will be open between now
and March 18, 2016. Please note that WMF Staff will not be able to start
responding to comments until Monday (March 7th) so know that the lack of
comments over the weekend is not a sign that you're being ignored :). We
welcome and appreciate any translations you are able to give for the draft
as well so that it can be read and understood by as many people as possible.
*Next steps*:
- During March, the Wikimedia Foundation will use this proposed strategy
to finalize its draft 2016-2017 Annual Plan.
- Between March 18th and April 1st we will review and integrate your
feedback from the draft strategy into the draft Annual Plan as
appropriate.
- On April 1st, The Wikimedia Foundation’s draft annual plan will then
be submitted for comment.
1, https://meta.wikimedia.org/wiki/2016_Strategy/Draft_WMF_Strategy
Thank you again for your feedback earlier that led to this draft and for
your comments in this stage,
James Alexander
Manager
Trust & Safety
Wikimedia Foundation
_______________________________________________
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
Hi folks,
I've been working on the Upload to Commons Android app[1] for the past few
months as an Outreachy project (which was recently completed
successfully[2] :)). A few changes were made to the app to make
categorization of pictures easier, via suggestion of nearby categories and
more flexible category search. However, there are lots of improvements
(documented on our GitHub page[3]) that we couldn't fit into the scope of
the Outreachy project. I would love to be able to continue working on the
app to improve it further - hence an IEG proposal.
My IEG proposal for the app involves:
- Fixing long-standing bugs and looking into old crash reports to try and
prevent them from recurring, to provide a smoother user experience
- Making several enhancements to the app to make it more user-friendly and
newbie-friendly, new location-based features (e.g. a list of nearby
articles lacking pictures), and further enhancing categorization.
- Increasing awareness of non-Wikimedians about this app to grow the
contributor base
Several of the proposed features are based on previous suggestions by
users, and I would very much appreciate more feedback and suggestions! If
you are interested, please do take a look at the current proposal[4], feel
free to ask questions and make new suggestions on the Discussion page, and
review it as you see fit. If you would like to be part of the project,
volunteers and additional advisors are always welcome.
Thank you so much!
[1] https://play.google.com/store/apps/details?id=fr.free.nrw.commons
[2] https://phabricator.wikimedia.org/T126848
[3] https://github.com/nicolas-raoul/apps-android-commons/issues
[4]
https://meta.wikimedia.org/wiki/Grants:IEG/Improve_%27Upload_to_Commons%27_…
--
Regards,
Josephine
Cross-posting.
---------- Forwarded message ----------
From: Madhumitha Viswanathan <mviswanathan(a)wikimedia.org>
Date: Wed, Mar 2, 2016 at 12:18 PM
Subject: [Analytics] [Eventlogging] Dropping Client IPs from EventCapsule
To: "A mailing list for the Analytics Team at WMF and everybody who has an
interest in Wikipedia and analytics." <Analytics(a)lists.wikimedia.org>,
Development and Operations Engineers <engineering(a)lists.wikimedia.org>
Hi all,
The analytics team, in an effort to collect sensitive data less, plans to
drop the clientIP field from the EventCapsule(
https://meta.wikimedia.org/wiki/Schema:EventCapsule), which is the wrapper
for all events flowing into Eventlogging (Currently IPs and User Agents get
purged after the 90 days mark). The field was originally meant only for
debugging, but has served some research usecases. Most of these cases have
been wrapped up at this point. It has also been used as a proxy to count
number of devices visiting sites like our blog - and since IP's are not a
good measure of that anyway - we plan to move such cases to use Piwik.
The rollout of the change will happen in stages (Drop clientIPs first on
the EL end, then the EventCapsule in meta, and finally on the VarnishKafka
end). It should be a clean deployment and there's no scheduled downtime -
EL will keep working as is. What does change? ClientIP's will start being
set as NULL in your mysql tables. If you update the Eventlogging schema you
maintain - causing new tables to be created, the new tables will not have
the clientIp field in them. The change is planned to be rolled out the week
of 11th or 18th March '16, pending the completion of data collection for
the ongoing QuickSurveys based research work.
Let us know if you have any questions/concerns on the list or on
#wikimedia-analytics. The related phab ticket is here -
https://phabricator.wikimedia.org/T128407.
Thanks,
Madhu Viswanathan
Software Engineer, Analytics
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
(Cross-posting)
For Wikimedia folks who are interested in possible collaborations with OSM,
now seems like a good time to start thinking about possible presentations.
Staff from the Wikimedia Foundation, and/or Wikimedia volunteers from
around the US outside of the Seattle area, may want to start thinking about
travel plans.
For Wikimedia volunteers outside of Cascadia Wikimedians territory, you
might consider applying for WMF Travel and Participation Support grants [1].
If you're inside of Cascadia Wikimedians territory and would like to attend
the conference, we may have funds in our budget that can support your
attendance. Contact me off-list for details.
Regards,
Pine
[1] https://meta.wikimedia.org/wiki/Grants:TPS
---------- Forwarded message ----------
From: Clifford Snow <clifford(a)snowandsnow.us>
Date: Tue, Mar 1, 2016 at 5:18 PM
Subject: [opensource-107] Seattle to host the 2016 OpenStreetMap State of
the Map US Conference
To: opensource-107-announce(a)meetup.com
I am excited to announce that Seattle was chosen to host the OpenStreetMap
2016 State of the Map US Conference. The conference will take place July
23-25 on SeattleU's campus. We chose SeattleU for their low cost, proximity
to Seattle and access to public transit. The food trucks near by didn't
hurt either.
We are looking for help! Let us know if you want to help. Request for
presentation proposals should be coming fairly soon. Start thinking about
what you want to present or teach.
The formal announcement can be found at:
https://openstreetmap.us/2016/02/sotmus-2016/
Clifford