Hello!
Thanks to everyone who took the time to provide their valuable feedback on
the Toolhub taxonomy[0]!
After a round of community feedback and input, we made the following
decisions about which categories and values to implement in the first
productionized version of the taxonomy.
=== Summary of Changes ===
1.
Exclude the proposed Programming language attribute.
2.
Exclude the proposed Platform attribute
3.
Revise the Tasks attribute values:
1.
Remove "Creating or uploading content"
2.
Add "Creating new content"
3.
Rename "Generating and recommending content" to "Recommending content"
4.
Revise the Content types attribute values:
1.
Add additional level of hierarchy to group content types and enable
both broad or specific values to be applied.
2.
Remove "Files".
3.
Split "Maps" and "Geographic Data"
Find more details of additional changes on the decision record log page[0]
=== Next Steps ===
The team will continue to observe and improve the taxonomy as the community
continues to use Toolhub.
We will monitor tags and community created lists to determine if certain
attributes would be useful or feasible in the future.
[0]: https://meta.wikimedia.org/wiki/Toolhub/Data_model#Taxonomy_v2 [1]:
https://meta.wikimedia.org/wiki/Toolhub/Decision_record#Taxonomy_v2
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
Hi,
it looks like there is nobody who can work on a bug or production error
like this: https://phabricator.wikimedia.org/T316858
I don't think, that this is a production error but really a bug. If it's
not possible to open a page (
https://de.wikipedia.org/wiki/Benutzer:Doc_Taxon/Test4 ) because of running
into timeout, the time should be increased to open the page to get the
content of this page.
Is there really nobody from WMF or a volunteer who can help me with this
issue? If you know somebody feel free to name him/her for contacting
him/her.
Thank you very much
Martin (aka Doc Taxon) ...
I just got the attached email. Is this just fishing, or is this actually some wikimedia thing for real?
I host spi-tools in github. I have no plans to move it to gitlab. Why has somebody created it on gitlab for me and invited me to be an owner?
> Begin forwarded message:
>
> From: Gitlab <gitlab(a)gitlab.wikimedia.org>
> Subject: StrikerBot invited you to join GitLab
> Date: September 7, 2022 at 6:22:56 PM EDT
> To: roy(a)panix.com
> Reply-To: Gitlab <gitlab(a)gitlab.wikimedia.org>
>
>
>
> StrikerBot <https://gitlab.wikimedia.org/striker> invited you to join the toolforge-repos / spi-tools
> project as a owner
>
> Join now <https://gitlab.wikimedia.org/-/invites/HJBAaZxkTZ-YspzANUqe?invite_type=ini…>
> Project details
> 1 member
> 0 issues
> 0 opened merge requests
> What's it about?
> Projects are used to host and collaborate on code, track issues, and continuously build, test, and deploy your app with built-in GitLab CI/CD.
>
>
> GitLab is a complete DevOps platform, delivered as a single application, fundamentally changing the way
> Development, Security, and Ops teams collaborate
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds an
open meeting on the first Wednesday of each month. Come talk to us about
anything related to Wikimedia search, Wikidata Query Service (WDQS),
Wikimedia Commons Query Service (WCQS), etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, September 7th, 2022
Time: 15:00-16:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CEST / 19:00 GST
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vgj-bbeb-uyi
Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927
Hope to talk to you next week!
—Trey
Trey Jones
Staff Computational Linguist, Search Platform
Wikimedia Foundation
UTC–4 / EDT
Hey all,
This is a quick note to highlight that in six weeks' time, the REL1_39
branch will be created for MediaWiki core and each of the extensions and
skins in Wikimedia git, with some (the 'tarball') included as sub-modules
of MediaWiki itself[0]. This is the first step in the release process for
MediaWiki 1.39, which should be out in November 2022, approximately
six months after MediaWiki 1.38.
The branches will reflect the code as of the last 'alpha' branch for the
release, 1.39.0-wmf.28, which will be deployed to Wikimedia wikis in the
week beginning 12 September 2022 for MediaWiki itself and those extensions
and skins available there.
After that point, patches that land in the main development branch of
MediaWiki and its bundled extensions and skins will be slated for the
MediaWiki 1.40 release unless specifically backported[1].
If you are working on a new feature that you wish to land for the release,
you now have a few days to finish your work and land it in the development
branch; feature changes should not be backported except in an urgent case.
If your work might not be complete in time, and yet should block release
for everyone else, please file a task against the `mw-1.39-release` project
on Phabricator.[2]
If you have tickets that are already tagged for `mw-1.39-release`, please
finish them, untag them, or reach out to get them resolved in the next few
weeks.
We hope to issue the first release candidate, 1.39.0-rc.0, two weeks after
the branch point, and if all goes well, to release MediaWiki 1.39.0 a few
weeks after that.
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://www.mediawiki.org/wiki/Bundled_extensions_and_skins>
[1]: <https://www.mediawiki.org/wiki/Backporting_fixes>
[2]: <https://phabricator.wikimedia.org/project/board/5694/>
The performance team are progressively deploying the MediaWiki
multi-DC project. This project allows us to make use of servers in the
Dallas data center which were previously idle. When the project is
fully deployed, most MediaWiki backend GET requests will be routed to
whichever data center is nearest to the CDN node at which the request
is received.
Deployment plan:
* Stage 1: test.wikipedia.org and test2.wikipedia.org. Already done.
* Stage 2: mediawiki.org. Planned for deployment on August 15.
* Stage 3: traffic percentage. A small percentage of all requests
will be sent to the nearest DC. Date undecided, but could be as
early as August 22.
* Stage 4: full deployment. Date TBA. But it will be soon. If you
need to update your tools, please start updating.
For more details, see T279664 <https://phabricator.wikimedia.org/T279664>.
I'm not aware of any blockers. As far as I know, we could fully deploy
it now and it would more or less work. If you think otherwise, please
let us know.
-- Tim Starling
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2022-08): 261
Active Maniphest users (any activity) in (2022-08): 1064
Task authors in (2022-08): 567
Users who have closed tasks in (2022-08): 317
Projects which had at least one task moved from one column to another on
their workboard in (2022-08): 322
Tasks created in (2022-08): 2575
Tasks closed in (2022-08): 2356
Open and stalled tasks in total: 50574
* Only open tasks in total: 49687
* Only stalled tasks in total: 887
Median age in days of open tasks by priority:
Unbreak now: 11
Needs Triage: 806
High: 1183
Normal: 1715
Low: 2389
Lowest: 2519
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2022-08): 6
To see the names of the most active task authors:
* Go to https://wikimedia.biterg.io/
* Choose "Phabricator > Overview" from the top bar
* Adjust the time frame in the upper right corner to your needs
* See the author names in the "Submitters" panel
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on phab1001 at Thu 01 Sep 2022 12:00:24 AM UTC)