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 50: | Line 50: | ||
#* https://github.com/enterprisemediawiki/meza/tree/35.x | #* https://github.com/enterprisemediawiki/meza/tree/35.x | ||
#* [https://matrix.to/#/#mwstake-MEZA:matrix.org?via=matrix.org Element Meza room] | #* [https://matrix.to/#/#mwstake-MEZA:matrix.org?via=matrix.org Element Meza room] | ||
# {{Agenda presenter|Lex}} | |||
#* Hallo Welt!/BlueSpice has an "all-in-one" Docker image for BlueSpice | |||
#** https://hub.docker.com/r/bluespice/bluespice-free | |||
#** https://github.com/hallowelt/docker-bluespice-free | |||
# {{Agenda presenter|Ike}} | |||
#* With any project, I'm worried about the projects maintenance for continued success | |||
# {{Agenda presenter|Bryan}} | |||
#* Does any path lock us into something someone might disagree with (OS, Webserver, etc.) | |||
#** Actually, re-reading that, it would be impossible to make a decision without having someone disagree | |||
# {{Agenda presenter|Rich}} | |||
#* Why not just use VirtualBox? | |||
# {{Agenda presenter|Lex} | |||
#* See my Virtual Box Ubuntu machine DNA | |||
#** https://github.com/dataspects/dataspectsSystemBuilder/blob/master/STEP-0-VBoxManage-create-ubuntu-server.sh | |||
# {{Agenda presenter|Rich}} | |||
#* There doesn't seem to be a proffessional way to push from Virtual Box to Production though | |||
# {{Agenda presenter|Yaron}} | |||
#* Why not just continue to use VirtualBox in Production? | |||
# {{Agenda presenter|Yaron}} | |||
#* Next meeting about infrastructure is in 2 weeks | |||
#** Ideally we can include: | |||
#**# Daren | |||
#**# James | |||
#**# Cindy | |||
#* Next week will be a Package discussion | |||
# {{Agenda presenter|Rich}} | |||
#* I have the EMW-Meza wiki up and going: | |||
#** https://emw-meza.site/emwdev/Main_Page | |||
#* I'll create an EMW-Meza-Canasta wiki | |||
Line 68: | Line 91: | ||
# Next meeting is next week and will focus on a Content Package (CRM, ERP, etc.) | # Next meeting is next week and will focus on a Content Package (CRM, ERP, etc.) | ||
# Next infrastructure meeting is in 2 weeks | # Next infrastructure meeting is in 2 weeks | ||
# Rich will create an EMW-Meza-Canasta wiki |
Revision as of 16:54, 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
- Lex
- Hallo Welt!/BlueSpice has an "all-in-one" Docker image for BlueSpice
- Ike
- With any project, I'm worried about the projects maintenance for continued success
- Bryan
- Does any path lock us into something someone might disagree with (OS, Webserver, etc.)
- Actually, re-reading that, it would be impossible to make a decision without having someone disagree
- Does any path lock us into something someone might disagree with (OS, Webserver, etc.)
- Rich
- Why not just use VirtualBox?
- {{Agenda presenter|Lex}
- See my Virtual Box Ubuntu machine DNA
- Rich
- There doesn't seem to be a proffessional way to push from Virtual Box to Production though
- Yaron
- Why not just continue to use VirtualBox in Production?
- Yaron
- Next meeting about infrastructure is in 2 weeks
- Ideally we can include:
- Daren
- James
- Cindy
- Ideally we can include:
- Next week will be a Package discussion
- Next meeting about infrastructure is in 2 weeks
- Rich
- I have the EMW-Meza wiki up and going:
- I'll create an EMW-Meza-Canasta wiki
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
- Rich will create an EMW-Meza-Canasta wiki