User:Bryan Hilderbrand/Meeting Notes (06JAN): Difference between revisions
Jump to navigation
Jump to search
Bryandamon (talk | contribs) No edit summary |
Bryandamon (talk | contribs) No edit summary |
||
Line 27: | Line 27: | ||
# {{Agenda presenter|Lex}} | # {{Agenda presenter|Lex}} | ||
#* I use both in my setup for my virtual machine | #* I use both in my setup for my virtual machine | ||
#* I use Docker, then wrap everything up in a zip (see 2nd image below) | |||
#** https://github.com/dataspects/dataspectsSystemBuilder | #** https://github.com/dataspects/dataspectsSystemBuilder | ||
#** https://github.com/dataspects/dataspectsSystemBuilder/blob/master/docker-images/php-apache/Dockerfile | #** https://github.com/dataspects/dataspectsSystemBuilder/blob/master/docker-images/php-apache/Dockerfile | ||
Line 33: | Line 34: | ||
#*: | #*: | ||
#*: [[File:Canasta Meeting (06JAN) - 2.png|border|400px]] | #*: [[File:Canasta Meeting (06JAN) - 2.png|border|400px]] | ||
# {{Agenda presenter|Rich}} | |||
#* I thought Docker was a "single file deploy" | |||
#* I think it's better to work on something existing (like [https://www.mediawiki.org/wiki/Meza Meza]) | |||
# {{Agenda presenter|Lex}} | |||
#* Docker can create any "level" at your discretion, the whole kitchen or per appliance | |||
#* I was an early supporter of the Meza project (coined the term "Flock to Meza"), but it's too rigid for my goals | |||
# {{Agenda presenter|Rich}} | |||
#* What you're describing sounds a lot like Meza, just type <code>meza deploy</code> and sit back | |||
# {{Agenda presenter|Lex}} | |||
#* Docker is a process wrapper (see DataAspects System Builder above) | |||
# {{Agenda presenter|Yaron}} | |||
#* Meza doesn't seem to be maintained anymore | |||
# {{Agenda presenter|Rich}} | |||
#* Support for 1.35 is being worked on now | |||
#* https://github.com/enterprisemediawiki/meza/tree/35.x | |||
#* [https://matrix.to/#/#mwstake-MEZA:matrix.org?via=matrix.org Element Meza room] | |||
Revision as of 16:43, 6 January 2021
Attendees
- Bryan Hilderbrand
- Ike Hecht
- Lex Sulzer
- Lexi McGillivray
- Rich Evans
- Yaron Koren
Meeting notes for MediaWiki "Products" (Project Canasta) Discussion (Wed Jan 06 16:00-17:00 UTC 2020)
Notes
- Yaron
- What is the best Day/Time for these meetings? Is this Day (Wednesday) and Time (16:00 UTC / 08:00 PST / 11:00 EST / 17:00 CET) work OK for everyone?
- This time is perfect for me Lex
- Later in the day is better for me if I'm going to attend Ike
- I can support earlier or later Bryan
- What is the best Day/Time for these meetings? Is this Day (Wednesday) and Time (16:00 UTC / 08:00 PST / 11:00 EST / 17:00 CET) work OK for everyone?
- Yaron
- Does anyone have an issue with the name, Project Canasta
- As a reminder, it's just the code name for the project to work on this effort
- No objection recorded
- Yaron
- The goal is to make a downloadable thing that allows you to quickly set-up and get a running wiki
- Contenders seem to be a Docker based approach or an Ansible based approach
- Lex
- I use both in my setup for my virtual machine
- I use Docker, then wrap everything up in a zip (see 2nd image below)
- Rich
- I thought Docker was a "single file deploy"
- I think it's better to work on something existing (like Meza)
- Lex
- Docker can create any "level" at your discretion, the whole kitchen or per appliance
- I was an early supporter of the Meza project (coined the term "Flock to Meza"), but it's too rigid for my goals
- Rich
- What you're describing sounds a lot like Meza, just type
meza deploy
and sit back
- What you're describing sounds a lot like Meza, just type
- Lex
- Docker is a process wrapper (see DataAspects System Builder above)
- Yaron
- Meza doesn't seem to be maintained anymore
- Rich
- Support for 1.35 is being worked on now
- https://github.com/enterprisemediawiki/meza/tree/35.x
- Element Meza room
Areas of focus
- Three main parts to Project Canasta:
- Platform (Meza, Sunflower Distribution, Docker approach, some combination, something entirely new)
- Transfer (PX, Wikibase method, MABS, other)
- Content (Actual Product/Package/Module/etc.)
Next steps
- Next meeting is next week and will focus on a Content Package (CRM, ERP, etc.)
- Next infrastructure meeting is in 2 weeks