Architecture committee/2016-03-02
Appearance
Summarized notes
[edit]- Action items
- RobLa - Public summary of this meeting
- Gabriel and RobLa - Discuss how to communicate priorities from ArchCom + real-time note conversations
- RobLa: further define https://office.wikimedia.org/wiki/Engineering/New_core_team
- Last week+this week's RfC office hour
- ArchCom touched on RFC office hours from last week and what is planned for this week.
- Last week: https://phabricator.wikimedia.org/E66/23
- This week: https://phabricator.wikimedia.org/E66/24
- Shepherd assignments
- We skipped shepherd assignments this week, since the RFC meeting would be focused on that
- RfC triage + meeting scheduling
- MediaWiki-RfCs board “Inbox†column
- T115852 - Unclear maintenance responsibilities for some parts of MediaWiki core repository
- https://office.wikimedia.org/wiki/Engineering/New_core_team
- ACTION (RobLa): publish page on to meta.
- ACTION (RobLa): Better define proposal as part of WMF FY16-17 budget discussions
- T128351 RfC: Notifications in core
- Should this move forward? Is this ready for an RFC meeting? How much should we move into core?
- Action Item: assign to Brion as shepherd
- T128352 RfC: Need to merge Notifications and Watchlist or lack thereof
- ArchCom discussed wbether this should be before or after T128351, and agreed it could come after. Â Brion wasn't able to volunteer shepherding this one, so the group agreed to put it in the "Needs Shepherd" Column.
- T66214: Use content hash based image / thumb URLs & define an official thumb API
- Brion said he'd be talking to various multimedia folks about this. Gabriel is eager to move forward on at least defining an API for this, which he believes can be done independently of naming images by hash. Brion said he's happy to keep this one, but suggested he's likely to be involved in proposals and implementation.
- Queue for future RfC office hours:
- Next week https://phabricator.wikimedia.org/E66/25
- Following week
- TBD
- Other business 21:30 (10 minutes)
- Code of Conduct/Moderation group
- ArchCom discussed whether a Moderation group is necessary, and whether the ArchCom should have a role in defining this. RobLa suggested that ArchCom's implicit role in Gerrit +2 access gives it some authority. After the meeting, RobLa updated the Gerrit/+2 page to make the link more explicit.
- RobLa to shepherd, Matt to continue to drive
- ACTION ITEM: Daniel to send mail to ArchCom about this
- Code of Conduct/Moderation group
- Next week's ArchCom agenda 0:40 (10 minutes)
- How can we increase the throughput of ArchCom?
- Should we have Rust-style working groups?
- Detailed notes
Note from RobLa: I'm transitioning to a regime where more of the agenda/notes prep can happen on mediawiki.org. Per Good meetings#Note taking, it can be really difficult for a thorough note taker to redact something that wasn't intended for the public minutes, and the transcript is probably less useful for everyone than the summary. The summary takes a little post-meeting time to prepare.