Event:126: Difference between revisions
Jump to navigation
Jump to search
Bryandamon (talk | contribs) (→) |
Bryandamon (talk | contribs) (→) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 27: | Line 27: | ||
#** [[User:Bryan_Hilderbrand#Project_Canasta|Notes]] (MWStake) | #** [[User:Bryan_Hilderbrand#Project_Canasta|Notes]] (MWStake) | ||
#* {{Agenda presenter|Mark}} I want to hear Richard's approach to Content Distribution | #* {{Agenda presenter|Mark}} I want to hear Richard's approach to Content Distribution | ||
#* {{Agenda presenter|Richard}} We had some efforts/ideas, "[http://mwstake.org/mwstake/wiki/Event:93#:~:text=standard%20distribution%20of%20MediaWiki%2B | #* {{Agenda presenter|Richard}} We had some efforts/ideas, "[[Sunflower MediaWiki]]" ([http://mwstake.org/mwstake/wiki/Event:93#:~:text=standard%20distribution%20of%20MediaWiki%2B previous discussion]) | ||
#** We are happy to collaborate | #** We are happy to collaborate | ||
#** We need collaboration & methodology to pay developers for creation/maintenance | #** We need collaboration & methodology to pay developers for creation/maintenance | ||
| Line 39: | Line 39: | ||
#** WMF is using Docker organized by Kubernetes | #** 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 | #** WMF is creating standardized images, they aren't targeting 3rd party uses, but I'm pushing to not preclude that | ||
#** Work 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 | #** I'm very happy that multiple users/companies/etc. are combining/collaborating to work on this | ||
#* {{Agenda presenter|Richard}} We need more that just a technological solution, but also a need for defined use cases | #* {{Agenda presenter|Richard}} We need more that just a technological solution, but also a need for defined use cases | ||
| Line 50: | Line 50: | ||
#* {{Agenda presenter|Cindy & Greg}} We need to define/document the requirements | #* {{Agenda presenter|Cindy & Greg}} We need to define/document the requirements | ||
#* {{Agenda presenter|Cindy}} There are several different levels of requirements. Requirements are needed before we start to talk about specific technologies | #* {{Agenda presenter|Cindy}} There are several different levels of requirements. Requirements are needed before we start to talk about specific technologies | ||
#* {{Agenda presenter|Richard}} Use Case side & Technical is needed | |||
#* {{Agenda presenter|Cindy}} A WikiFarm "standard approach" would be good. The software should support a standard method | |||
#* {{Agenda presenter|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? | |||
#* {{Agenda presenter|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? | |||
#** {{Agenda presenter|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 | |||
# '''[https://phabricator.wikimedia.org/T250406 Hybrid Extension Management]''' | # '''[https://phabricator.wikimedia.org/T250406 Hybrid Extension Management]''' | ||
#* {{Agenda presenter|Richard}} There was an idea about Hybrid Extension Management | #* {{Agenda presenter|Richard}} There was an idea about Hybrid Extension Management | ||
| Line 56: | Line 62: | ||
#** For use cases (well defined) we need expertise (customers, users, etc.) | #** For use cases (well defined) we need expertise (customers, users, etc.) | ||
#* {{Agenda presenter|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 | #* {{Agenda presenter|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 | ||
#* {{Agenda presenter|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== | ==Action board== | ||
Latest revision as of 18:15, 28 January 2021
 Date (UTC):
|
8 January 2021 16:30:00 - 8 January 2021 17:30:00 |
|---|---|
| URL:
|
https://meet.google.com/mdd-ufhn-ksb |
| Etherpad:
|
https://etherpad.wikimedia.org/p/mwstake-2021-01
|
 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
Meeting agenda
- Wait for attendees & chat 5 min
- Wiki Quickie 5 min TBD
- MediaWiki News 20 min Mark
- Creating MediaWiki-based "products" 5 min Bryan
- Update & invitation to interested people
- Original email description
- TBD 20 min TBD
- Wiki Watercooler remaining Open Mic
Notes
The meeting voice transcription is available on the talk page.
- MediaWiki-based "products" (Project Canasta)
- Info on Project Canasta:
- Project Canasta (Mediawiki.org)
- Notes (MWStake)
- 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:
- Platform (Meza, Sunflower Distribution, Docker approach, some combination, something entirely new)
- Transfer (PX, Wikibase method, MABS, other)
- 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:
- Infrastructure
- 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
- Info on Project Canasta:
- 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.
- Richard There was an idea about Hybrid Extension Management
Action board
See this page for more information
| Open | |||
|---|---|---|---|
| |||