Hi all,
Join the Research Team at the Wikimedia Foundation [1] for their monthly
Office hours on Tuesday, 2020-11-03 at 17:00-18:00 PM UTC (9am PT/6pm CET).
To participate, join the video-call via this Wikimedia-meet link [2]. There
is no set agenda - feel free to add your item to the list of topics in the
etherpad [3] (You can do this after you join the meeting, too.), otherwise
you are welcome to also just hang out. More detailed information (e.g.
about how to attend) can be found here [4].
Through these office hours, we aim to make ourselves more available to
answer some of the research related questions that you as Wikimedia
volunteer editors, organizers, affiliates, staff, and researchers face in
your projects and initiatives. Some example cases we hope to be able to
support you in:
-
You have a specific research related question that you suspect you
should be able to answer with the publicly available data and you don’t
know how to find an answer for it, or you just need some more help with it.
For example, how can I compute the ratio of anonymous to registered editors
in my wiki?
-
You run into repetitive or very manual work as part of your Wikimedia
contributions and you wish to find out if there are ways to use machines to
improve your workflows. These types of conversations can sometimes be
harder to find an answer for during an office hour, however, discussing
them can help us understand your challenges better and we may find ways to
work with each other to support you in addressing it in the future.
-
You want to learn what the Research team at the Wikimedia Foundation
does and how we can potentially support you. Specifically for affiliates:
if you are interested in building relationships with the academic
institutions in your country, we would love to talk with you and learn
more. We have a series of programs that aim to expand the network of
Wikimedia researchers globally and we would love to collaborate with those
of you interested more closely in this space.
-
You want to talk with us about one of our existing programs [5].
Hope to see many of you,
Martin (WMF Research Team)
[1] https://research.wikimedia.org/team.html
[2] https://meet.wmcloud.org/ResearchOfficeHours
[3] https://etherpad.wikimedia.org/p/Research-Analytics-Office-hours
[4] https://www.mediawiki.org/wiki/Wikimedia_Research/Office_hours
[5] https://research.wikimedia.org/projects.html
--
Martin Gerlach
Research Scientist
Wikimedia Foundation
Hi!
> This Friday, 2020-10-30, I will be doing some maintenance on stat1005 in the
> EU/CET morning. During this, there will be disruption of everything there and
> there will be multiple reboots. Afterwards, the machine will be running a newer
> kernel (5.8) and updated GPU drivers/rocm library (3.8). Should the update
> fail, or the subsequent tests show that workloads break, we will roll back to
> 4.19 and rocm33.
stat1005 is now running kernel 5.8.0 and rocm38. Note that you will have to
update tf-rocm to the latest version (2.3.1) to work on this machine.
If you have any questions or concerns, let us know.
Best,
Tobias
--
Tobias Klausmann, SRE, Wikimedia Foundation
Hi!
This Friday, 2020-10-30, I will be doing some maintenance on stat1005 in the
EU/CET morning. During this, there will be disruption of everything there and
there will be multiple reboots. Afterwards, the machine will be running a newer
kernel (5.8) and updated GPU drivers/rocm library (3.8). Should the update
fail, or the subsequent tests show that workloads break, we will roll back to
4.19 and rocm33.
If you have any questions or concerns, let us know.
Best,
Tobias
--
Tobias Klausmann, SRE, Wikimedia Foundation
Hi!
In our quest to make teh GPU-equipped machines in analytics ever more useful,
we are going to update the rocm software suite and driver on stat1005 and
stat1008 to the latest version, 3.8.0.
Since this will necessitate a reboot, this is the early warning that on
2020-11-23 (Friday), I will update stat1005. Disruption will likely be less
than an hour. In case the update breaks stuff, we will roll back to v3.3.0.
The update of stat1008 will happen next week, on 2020-11-27 Tuesday, and there
will be a separate reminder for that on Monday.
I will send an all-clear message to these lists once the update is done. For
more details on the process, see https://phabricator.wikimedia.org/T264408
As always, if there is anything out of order, don't hesitate to contact us.
Best,
Tobias
--
Tobias Klausmann, SRE, Wikimedia Foundation
Meedan, a global non-profit I work with, is hiring a software engineer. The
posting says frontend, but full-stack developers are also super welcome.
It's a distributed organization with a great mission and culture. I'm very
happy to answer questions if anyone's interested and very much appreciate
your help spreading the word.
Meedan builds Check <https://github.com/meedan/check>, a web platform for
collaborative media annotation and fact-checking. The frontends include a
React web app, a cross-browser Web Extension and a sophisticated Slack bot,
all accessing our backend services via GraphQL and REST APIs.
https://meedan.com/jobs/software-engineer-frontend/
Best wishes,
Scott
--
Dr Scott A. Hale
http://scott.hale.us
computermacgyver(a)gmail.com
Hi all,
Join the Research Team at the Wikimedia Foundation [1] for their monthly
Office hours on 2020-10-13 at 16:00-17:00 PM UTC.
To participate, join the video-call via this Wikimedia-meet link [2]. There
is no set agenda - feel free to add your item to the list of topics in the
etherpad [3] (You can do this after you join the meeting, too.), otherwise
you are welcome to also just hang out. More detailed information (e.g.
about how to attend) can be found here [4].
Through these office hours, we aim to make ourselves more available to
answer some of the research related questions that you as Wikimedia
volunteer editors, organizers, affiliates, staff, and researchers face in
your projects and initiatives. Some example cases we hope to be able to
support you in:
-
You have a specific research related question that you suspect you
should be able to answer with the publicly available data and you don’t
know how to find an answer for it, or you just need some more help with it.
For example, how can I compute the ratio of anonymous to registered editors
in my wiki?
-
You run into repetitive or very manual work as part of your Wikimedia
contributions and you wish to find out if there are ways to use machines to
improve your workflows. These types of conversations can sometimes be
harder to find an answer for during an office hour, however, discussing
them can help us understand your challenges better and we may find ways to
work with each other to support you in addressing it in the future.
-
You want to learn what the Research team at the Wikimedia Foundation
does and how we can potentially support you. Specifically for affiliates:
if you are interested in building relationships with the academic
institutions in your country, we would love to talk with you and learn
more. We have a series of programs that aim to expand the network of
Wikimedia researchers globally and we would love to collaborate with those
of you interested more closely in this space.
-
You want to talk with us about one of our existing programs [5].
Hope to see many of you,
Martin (WMF Research Team)
[1] https://research.wikimedia.org/team.html
[2] https://meet.wmcloud.org/ResearchOfficeHours
[3] https://etherpad.wikimedia.org/p/Research-Analytics-Office-hours
[4] https://www.mediawiki.org/wiki/Wikimedia_Research/Office_hours
[5] https://research.wikimedia.org/projects.html
--
Martin Gerlach
Research Scientist
Wikimedia Foundation
Dear users of stat100{4,6,7},
we are planning on upgrading stat1004 to Debian Buster this Thursday
(2020-09-17) after 12:00 CEST (10:00 UTC). We will reinstall the machine,
preserving user data (home directories, /srv), but to be on the safe side,
we will backup that data. After the reinstall and a few tests, we will send
an all-clear to this list.
A few things of note:
- It would be greatly appreciated if you cleaned out unneeded data before
the
backup time mentioned above, thus speeding up backup (and restore if we
need
it).
- Any changes made to the file system contents after the time mentioned
above
may be lost.
- Around the time of the backup, both cron and systemd timers will be
disabled, and still-running process may be ungracefully terminated.
If this process works well, the remaining stat100x machines in need of
update
(6, 7) will be processed in a similar manner.
As always, if there are questions, do not hesitate to contact us.
Best,
Tobias
--
Tobias Klausmann, SRE, Wikimedia Foundation
Hello all!
> *Bottom Line *Please review the Event Schema Audit
> <https://docs.google.com/spreadsheets/d/1WXbGPyuu2S6TYvrb-DvWWmrEx_K7TJ5rYPk…>[1]
> and request changes via comment by October 16*.
**Any and all schemas that are not designated for migration will be
deprecated. Datasets who rely on deprecated schemas will no longer receive
data*
*Background:*
- The Modern Event Platform (MEP)
<https://www.mediawiki.org/wiki/Wikimedia_Technology/Annual_Plans/FY2019/TEC…>
will
be the new infrastructure for building services that produce and consume
event data for analytics and production. In order to take advantage of the
new platform data, schemas need to be migrated from the old format
(EventLogging) on meta to the new MEP specification. Given all teams have
schemas, instrumentation and process surrounding the previous way of
generating event data, teams will be required to shift in how they
instrument and produce these events moving forward on the new MEP.
- To do this, we must
- Make a copy of the original Event Logging schema into the new system
and
- Change the name of the original schema to legacy_<name>
- Any instrumentation using the original schema will automatically use
the updated schema. There is no change in application code. Events will
flow to the same database table. There should be no interruption in data,
and there is a QA process in place during this transition.
- Consequences for you and your team:
- Any future modifications to the schema will need to be made in the new
system
- A few additional fields will appear in your database table
- Switching the schema in this way will not make the features of the
Modern Event Platform project available immediately. To get these features,
we need to author a fresh schema and update the instrumentation code. This
is the final step of the migration and will be done in concert with Data
Scientists and Product Teams at a later date.
- You can find out more about our Migration Plan & Timeline
<https://docs.google.com/document/d/1LZ3ZijXePGqur3LAkH9LWSmkTBuTZuGJPlgHeiI…>[3]
and reach out to me if you have any further questions
[1]
https://docs.google.com/spreadsheets/d/1WXbGPyuu2S6TYvrb-DvWWmrEx_K7TJ5rYPk…
[2]
https://www.mediawiki.org/wiki/Wikimedia_Technology/Annual_Plans/FY2019/TEC…
[3]
https://docs.google.com/document/d/1LZ3ZijXePGqur3LAkH9LWSmkTBuTZuGJPlgHeiI…
Best,
--
Seve Kim *(he/him)*
Sr. Technical Product Manager
<https://wikimediafoundation.org/>
*"Imagine a world in which every single human being can freely share in the
sum of all knowledge. That's our commitment."*