Hey folks, I'm helping Rebecca Maung (rmaung(a)wikimedia.org) distribute this
request. Her words below:
The Wikimedia Foundation is asking for your feedback in the annual
Community Insights survey. We want to know how well we are supporting your
work on- and off-wiki, and how we can change or improve things in the
future. The opinions you share will directly affect the current and future
work of the Wikimedia Foundation.
If you are a volunteer developer, and have contributed code to any pieces
of MediaWiki, gadgets, or tools, please complete the survey. It is
available in various languages and will take between 15 and 25 minutes to
complete.
Follow this link to the survey:
https://wikimedia.qualtrics.com/jfe/form/SV_0pSrrkJAKVRXPpj?Target=dev
If you have seen a similar message elsewhere and have already taken the
Community Insights survey, please do not take it twice.
You can find more information about this survey on the project page and see
how your feedback helps the Wikimedia Foundation support contributors like
you. This survey is hosted by a third-party service and governed by this
privacy statement. Please visit our frequently asked questions page to find
more information about this survey.
If you need additional help, send an email to surveys(a)wikimedia.org.
Thank you!
//Johan Jönsson
--
(Note: This is only an early heads-up, to be prepared. Google Code-in
has NOT been announced yet, but last year, GCI mentors asked for more
time in advance to identify tasks to mentor. Here you are. :)
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Google Code-in (GCI) is an annual contest for 13-17 year old students.
GCI 2019 has not yet been announced but usually takes place from late
October to December. It is not only about coding: We also need tasks
about design, docs, outreach/research, QA.
Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors , add
your name to the mentors table, and start tagging tasks in Wikimedia
Phabricator by adding the #gci-2019 project tag.
We will need MANY mentors and MANY tasks, otherwise we cannot make it.
Last year, 199 students successfully worked on 765 tasks supported by
39 mentors. For some achievements from the last round, see
https://wikimediafoundation.org/news/2019/02/20/partnerships-make-it-possib…
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and replace 2 uses of
Linker::link() from the list in T223010" style).
We also have more than 400 unassigned open #good-first-bug tasks:
https://phabricator.wikimedia.org/maniphest/query/3YnDUWYJfXSo/#R
Can and would you mentor some of these tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2019#List_of_Wikimedia_mentors
Thanks (as we will not be able to run this without your help),
andre
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
Hello everyone,
I'm excited to announce that we've released OOUI v0.34.0 today.
Key highlights of this release are (summarizing since v0.33.0):
- Update to OOjs v3.0.0, up from v2.2.2
- Update to jQuery v3.4.1, up from v3.3.1
Both updates above are considered breaking changes. Please carefully
test if they affect your code.
- Element: Implement `#setScrollLeft` and use where needed. Improves
scrolling-related operations in RTL languages
- Frameless buttons are now featuring hover and active state as
standard, improving user navigational experience
- ProcessDialog: Improve secondary action appearance to let users
better focus on content
- WindowManager: Prevent iOS Safari from scrolling the page behind the dialog
You can find details on additional new features, code-level and accessibility
changes, styling and interaction design amendments, and all
improvements since v0.33.0 in the full changelog[1].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[0] and library documentation is available
on mediawiki.org[2], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[3].
OOUI version: 0.34.0
MediaWiki version: 1.34.0-wmf.22
Date of deployment to production: Regular train, starting Tuesday 10 September
[0] - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[1] - https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
[2] - https://www.mediawiki.org/wiki/OOUI
[3] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
--
Senior UX Engineer
Wikimedia Foundation
volker.e(a)wikimedia.org | @Volker_E