Hi folks,
Hope you are all safe and well. We have just released v3.1.0 of the Commons
app for beta testing last week, containing basic integration for Wiki Loves
Monuments uploads!
You can find more details about our implementation (and the challenges that
we faced) at
https://commons.wikimedia.org/wiki/Commons:Mobile_app/WLM_release , but the
summary is that WLM pins have been added to our Nearby map, for WLM
monuments. From now until 30 September, people can upload photos of
monuments through this map, and if their country is participating in WLM
2021, the relevant template will be added to these uploads.
Please do help us test this beta version if you can - we hope to release to
production early next week so all users can access it. :)
Many thanks!
Best regards,
Josephine
Hi,
package-lock.json is basically impossible to manually review but we
still have to do some form of basic checking on its contents.
I'd like to introduce a small, conservative tool that does *some* of
these checks for of us. package-lock-lint[1] currently checks that:
* package-lock.json is using lockfileVersion 1 or 2 and matches the
basic schema.
* All dependencies resolve to valid URLs (catches [2])
* All dependencies are downloaded over HTTPS/SSH (not insecure)
* Not depending upon the typo but real "-" package
Even if all of these are passing, it does not guarantee that the
modified package-lock.json is good, however any failure in these checks
is a sign something is wrong.
This code has been running as part of LibUp since May and has caught
instances where dependencies were being downloaded over HTTP[3] as well
as bugs in npm that would've caused LibUp to submit buggy patches.
If there are no concerns, I would like to enable running this tool in
all instances where CI installs stuff from npm.
The main Phabricator bug for this is
<https://phabricator.wikimedia.org/T242058>, thanks to James_F for
providing input and advice on the design.
[1] https://gitlab.com/legoktm/package-lock-lint
[2] https://phabricator.wikimedia.org/T278857
[3] https://gerrit.wikimedia.org/r/q/topic:%2522package-lock-https%2522
Thanks,
-- Legoktm
Hello!
This morning I found a tick coastal line on wikimedia maps
screenshot: https://i.imgur.com/tVGhBO6.png
Is this something all countries will get or is it a bug?
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2021-08): 304
Active Maniphest users (any activity) in (2021-08): 1068
Task authors in (2021-08): 544
Users who have closed tasks in (2021-08): 307
Projects which had at least one task moved from one column to another on
their workboard in (2021-08): 304
Tasks created in (2021-08): 2289
Tasks closed in (2021-08): 2091
Open and stalled tasks in total: 48026
* Only open tasks in total: 47125
* Only stalled tasks in total: 901
Median age in days of open tasks by priority:
Unbreak now: 13
Needs Triage: 696
High: 972
Normal: 1491
Low: 2106
Lowest: 2174
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2021-08): 9
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 Wed 01 Sep 2021 12:00:23 AM UTC)
