Hello,
I have released Quibble 0.0.47 a minute ago:
* Fixes installation under Python 3.5
* Inject MediaWiki related environment variables when running a user script
* Run "composer test-some" for mediawiki/core (which will let us make
"composer test" to run against all files as it is done on all other
repositories).
* Test Parsoid as if it were an extension
And that is about it. The complete changelog is at:
https://doc.wikimedia.org/quibble/changelog.html
The CI jobs will eventually be updated to it over the next hours / days.
cheers,
--
Antoine "hashar" Musso
Hi all,
The 1.37.0-wmf.4[0] train is currently blocked at group0 by the
following issue:
* Special:RecentChanges with userExpLevel=newcomer causes Fatal
exception of type "Wikimedia\Rdbms\DBQueryError": Unknown column
'actor_user'
- https://phabricator.wikimedia.org/T281981
If this issue is resolved before the 19:00 UTC train deployment window,
the train will proceed as normal to group1.
As ever, you can follow train progress on Freenode's
#wikimedia-operations as well as on the blocker task[0].
Regards,
-- Your bedraggled train crew
[0]. <https://phabricator.wikimedia.org/T281145>
[1].
<https://wikitech.wikimedia.org/wiki/Deployments/Holding_the_train#Issues_th…>
Dear Wikimedians,
The Wikimedia Foundation Board of Trustees met last week to decide on a
plan for the 2021 Board elections. The Board Governance Committee created a
proposal based on the report of Call for Feedback about Community Board
Seats
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_Boa…>
[1]. The full proposal
<https://upload.wikimedia.org/wikipedia/foundation/8/83/BGC_Community_Truste…>[2]
is available on Foundation Wiki. The Board wants to thank the more than 800
volunteers that participated in the Call for Feedback in one way or
another. It has been very difficult to decide on every open question
considering the quantity and diversity of opinions received. We hope this
resolution feels sensible to everybody.
The summary of the proposal is as follows:
1. The Board drafts a call for candidates that includes details about
the skills and experience that are currently represented on the Board
(excluding trustees whose terms are expiring) and that the Board would like
the selected trustees to have.
2. The Foundation devotes resources to informing communities of the
trustee selection process and encouraging people from emerging and
underrepresented communities to run as candidates.
3. As part of their self-nomination process, candidates fill out the
trustee evaluation form.
4. The Foundation continues to devote resources to invite communities to
participate in the selection process by engaging candidates during the
campaign period and by voting.
5. Community members vote and their votes are counted using a *proportional
voting system* chosen by the Elections Committee.
6. The Foundation conducts the usual vetting of the selected candidates
(background check and communications review).
7. The Board appoints the selected candidates for whom the vetting
process did not reveal any significant issues.
This proposal does not suggest implementing quotas or hard requirements for
candidate skills or experience for the 2021 round of community trustee
selection. Instead, it relies on the more detailed information from the
Board in the call for feedback, the community outreach efforts, and the
proportional voting system to meet the Board’s needs in terms of skills and
diversity. However, it also contemplates potentially adding or changing
elements to the process for future rounds of trustee selection, based on an
assessment of the effectiveness this first time.
The draft timeline is as follows:
1. April 15: Board meets to consider and approve this proposal
2. April - May: Elections Committee and staff plan the details of the
selection process
3. June 1-2: Board meets and approves the call for candidates
4. June 8 - 29: Call for candidates; candidate outreach
5. June 29 - July 20: Candidates campaign and answer questions;
community outreach
6. July 20 - August 3: Voting; community outreach
7. August 3 - 10: Vote counting and processing
8. August 10 - 24: Foundation vetting of selected candidates
9. August / September: Board appoints selected candidates
*(tentative only, subject to change)*
Please go through the full proposal[2] for further details, and let me know
if you have any questions. In the upcoming days, the Board elections
facilitation team will share their ideas to support candidates and voters.
Best,
Krishna Chaitanya,
Communications Facilitator, Board Governance
[1] Call for Feedback report:
https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_Boa…
[2] Full proposal:
https://upload.wikimedia.org/wikipedia/foundation/8/83/BGC_Community_Truste…
Hello all,
The following breaking changes will be made without deprecation in MediaWiki 1.37 release [1]:
- File::deleteFile - will accept UserIdentity instead of User
- File::getDescription - will accept Authority instead of User
- File::userCan - will accept Authority instead of User
- LocalFile::deleteOldFile - will accept UserIdentity instead of User
The parameter types in method signatures have been widened, so callers of these methods will not be affected.
However, these methods are marked as “@stable to override” per Stable Interface Policy [1] and widening
the parameter type hints will break classes overriding the aforementioned methods. However, according to
codesearch [2] none of these methods are overridden by anything in MediaWiki ecosystem.
Please reach out on Gerrit or on this mailing list if you have concerns about the proposed change.
Best regards, Petr Pchelko
[1] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/677014 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/677014>
[2] https://www.mediawiki.org/wiki/Stable_interface_policy <https://www.mediawiki.org/wiki/Stable_interface_policy>[3] https://codesearch.wmcloud.org/search/ <https://codesearch.wmcloud.org/search/>
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2021-04): 366
Active Maniphest users (any activity) in (2021-04): 1152
Task authors in (2021-04): 603
Users who have closed tasks in (2021-04): 295
Projects which had at least one task moved from one column to another on
their workboard in (2021-04): 303
Tasks created in (2021-04): 2594
Tasks closed in (2021-04): 2266
Open and stalled tasks in total: 47761
* Only open tasks in total: 46879
* Only stalled tasks in total: 882
Median age in days of open tasks by priority:
Unbreak now: 2
Needs Triage: 635
High: 952
Normal: 1393
Low: 2009
Lowest: 2067
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2021-04): 8
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 Sat 01 May 2021 12:00:21 AM UTC)