8 January 2021 MWstake Meeting

From MWStake
Revision as of 19:15, 28 January 2021 by Bryandamon (talk | contribs) ()
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Blank.png Date (UTC): 8 January 2021 16:30:00 - 8 January 2021 17:30:00
Blank.png URL: https://meet.google.com/mdd-ufhn-ksb
Blank.png Etherpad: https://etherpad.wikimedia.org/p/mwstake-2021-01

Person.png Attendees: Cindy Cicalese, Frank Taylor, Greg Rundlett, Ike Hecht, Jeroen De Dauw, Lex Sulzer, Lexi McGillivray, Mark Hershberger, Richard Heigl, Yaron Koren

Click for time zone conversion

{{#copywatchers: Template:Event}}

Meeting agenda

  1. Wait for attendees & chat 5 min
  2. Wiki Quickie 5 min TBD
  3. MediaWiki News 20 min Mark
  4. Creating MediaWiki-based "products" 5 min Bryan
  5. TBD 20 min TBD
  6. Wiki Watercooler remaining Open Mic


The meeting voice transcription is available on the talk page.

  1. MediaWiki-based "products" (Project Canasta)
    • Info on Project Canasta:
    • Mark I want to hear Richard's approach to Content Distribution
    • Richard We had some efforts/ideas, "Sunflower MediaWiki" (previous discussion)
      • We are happy to collaborate
      • We need collaboration & methodology to pay developers for creation/maintenance
      • It's crazy that many of us are recreating the same things
    • Yaron Project Canasta has 3 parts:
      1. Platform (Meza, Sunflower Distribution, Docker approach, some combination, something entirely new)
      2. Transfer (PX, Wikibase method, MABS, other)
      3. Content (Actual Product/Package/Module/etc.)
    • Yaron The Platform part has a few contenders (Meza & Docker)
    • Cindy Having a containerized infrastructure is an important goal
      • WMF is using Docker organized by Kubernetes
      • WMF is creating standardized images, they aren't targeting 3rd party uses, but I'm pushing to not preclude that
      • Work that Hallo Welt! and Wikibase have been collaborating on that includes page based access control sounds like a good approach
      • I'm very happy that multiple users/companies/etc. are combining/collaborating to work on this
    • Richard We need more that just a technological solution, but also a need for defined use cases
      • An example use case: What can a Document Management System be and look like?
    • Bryan As a note, we have a schedule for 2 different meetings, each held bi-weekly:
      1. Infrastructure
      2. Package/Content/Module/etc.
    • Greg One way to get a lot of momentum/productivity is just schedule a meeting to have everyone collaborate & write down ideas on a wiki page
    • Lex I recommend starting with code. Do something & iterate. Avoid brainstorming and see what actually works. Show people what you've been working on (GitHub)
    • Cindy & Greg We need to define/document the requirements
    • Cindy There are several different levels of requirements. Requirements are needed before we start to talk about specific technologies
    • Richard Use Case side & Technical is needed
    • Cindy A WikiFarm "standard approach" would be good. The software should support a standard method
    • Frank Can such "minimum standards" help establish a "safe harbor" for the adoption of MediaWiki by sectors (such as law or government) in which the users have heightened obligations for confidentiality and privacy?
    • Richard Regarding WikiFarms, Confluence makes it easy to create another "Space", but I find that problematic for knowledge sharing.
      • I'd like to hear from others about "why" you create farms? What is the use case?
      • Bryan It might be a "feature, not a bug" that it is harder to create a separate "silo" of knowledge using MediaWiki. I've found it's much better to try and keep a companies knowledge in on "silo". That being said, I do appreciate the need to have different levels of access for some knowledge
  2. Hybrid Extension Management
    • Richard There was an idea about Hybrid Extension Management
      • Can we agree on a standard (use Composer?)
      • We must talk about users & use cases
      • For use cases (well defined) we need expertise (customers, users, etc.)
    • Cindy For some RFC Information, there was an RFC that was rejected. That has been used as an excuse about why composer shouldn't be used for extensions
    • Greg Update from me. I'm not sure about the future of QualityBox, but I'm a full-time developer for Pega Systems now & work closely with Wikibase Solutions.
      • I'll have more time moving forward & now represent a different aspect of a Stakeholder.

Action board

Search actions Add an action See this page for more information

None of these labels
+ MWStake