8 January 2021 MWstake Meeting
|Date (UTC):||8 January 2021 16:30:00 - 8 January 2021 17:30:00|
|Attendees:||, , , , , , , , ,|
- Wait for attendees & chat
- Wiki Quickie
- MediaWiki News
- Creating MediaWiki-based "products"
- Update & invitation to interested people
- Original email description
- Wiki Watercooler
The meeting voice transcription is available on the talk page.
- MediaWiki-based "products" (Project Canasta)
- Info on Project Canasta:
- I want to hear Richard's approach to Content Distribution
- Sunflower MediaWiki" (previous discussion)
We had some efforts/ideas, "
- 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
Project Canasta has 3 parts:
- Platform (Meza, Sunflower Distribution, Docker approach, some combination, something entirely new)
- Transfer (PX, Wikibase method, MABS, other)
- Content (Actual Product/Package/Module/etc.)
- The Platform part has a few contenders (Meza & Docker)
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 Hallow 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
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?
As a note, we have a schedule for 2 different meetings, each held bi-weekly:
- 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
- I recommend starting with code. Do something & iterate. Avoid brainstorming and see what actually works. Show people what you've been working on (GitHub)
- We need to define/document the requirements
- There are several different levels of requirements. Requirements are needed before we start to talk about specific technologies
- Use Case side & Technical is needed
- A WikiFarm "standard approach" would be good. The software should support a standard method
- 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?
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?
- 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
- Hybrid Extension Management
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.)
- 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
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.
- There was an idea about Hybrid Extension Management
this page for more informationSee