Page MenuHomePhabricator

Prepare Wikimedia Hackathon 2024 session for Community configuration 2.0
Closed, ResolvedPublicApr 21 2024

Description

@Urbanecm_WMF and @Michael are attending Wikimedia Hackathon 2024 in Tallinn as Growth team representatives. I should prepare a session proposal and log it under Wikimedia-Hackathon-2024 reasonably soon, see the guidance at https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2024/Program.

Details

Due Date
Apr 21 2024, 10:00 PM

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Since I'm the one attending, I should work on the session proposal (with the help from other Growth team members, esp. engineers, as the audience will be technical).

Urbanecm_WMF changed the subtype of this task from "Task" to "Deadline".
Urbanecm_WMF set Due Date to Apr 14 2024, 10:00 PM.

Ideas from a brainstorming session with @Sgs:

  1. Where are we at: We presented an informative session during the 2023 Hackathon in Athens, presenting a lot of open questions. Now, about a year has passed, and we should inform the community about what changed and answer "where are we at".
  2. Make your extension community configurable workshop: It is likely the Hackathon in Tallinn will be attended by developers who intend on making extensions/skins they maintain community configurable. To support them, we can have a conversion session, in which we walk the participants through the changes needed.
  3. "Crash me" session: While we QA CommunityConfiguration internally, it is significantly less likely we notice a bug introduced by a legitimate schema that we simply did not test against. Asking participants to find critical bugs in CommunityConfiguration could be a fun way to make our code less buggy.
KStoller-WMF moved this task from Backlog to Up Next on the Growth-Team board.
Urbanecm_WMF changed Due Date from Apr 14 2024, 10:00 PM to Apr 21 2024, 10:00 PM.Apr 15 2024, 6:36 PM

@Michael and me discussed this earlier today. We're currently leaning towards going with option 1 ("where are we at") and option 2 ("make your extension community configurable" workshop). In the workshop, we can highlight errors/unexpected behaviour will be appreciated as part of the session, but it does not make sense to host a crash me session separately.