User:Bryan Hilderbrand/Meeting Notes (27JAN): Difference between revisions

From MWStake
Jump to navigation Jump to search
()
()
Line 34: Line 34:
#* {{Agenda presenter|Gokhan}} It's stored on GitHub and we try to keep it as small as possible
#* {{Agenda presenter|Gokhan}} It's stored on GitHub and we try to keep it as small as possible
#* {{Agenda presenter|Gokhan}} We use Continuous Integration testing
#* {{Agenda presenter|Gokhan}} We use Continuous Integration testing
# {{Agenda presenter|Markus}} Showed the [https://github.com/hallowelt Hallo Welt GiHub repo]
#* {{Agenda presenter|Markus}} We have the same Docker environment for [https://github.com/hallowelt/docker-bluespice-free BlueSpice Free] & Pro
#* {{Agenda presenter|Markus}} We have to think about how to make the system flexible
#* {{Agenda presenter|Markus}} The method is platform independent
# {{Agenda presenter|Cindy}} How do you provide containers to people?
#* {{Agenda presenter|Cindy}} Do you give them the Docker image?  Any need for orchestration?
# {{Agenda presenter|Gokhan}} We are using [https://goharbor.io/ Harbor] as a private registry.  Docker Hub.  Building is the same
# {{Agenda presenter|Lex}} My solution is not an alternative to Meza, it's a post process
#* {{Agenda presenter|Lex}} Something should create a MW root structure, my solution acts on this
#* {{Agenda presenter|Yaron}} Your solution seems to have 2 steps:
#*# Set up MW
#*# Package it
#*#* {{Agenda presenter|Lex}} Yes


==Chat transcript==
==Chat transcript==

Revision as of 21:33, 30 January 2021

Attendees

  • Ad Strack van Schijndel
  • Bryan Hilderbrand
  • Cindy Cicalese
  • Gökhan Geyik
  • James Montalvo
  • Lex Sulzer
  • Markus Glaser
  • Rich Evans
  • Richard Heigl
  • Yaron Koren

Meeting notes for MediaWiki "Infrastructure" (Project Canasta) Discussion (Wed Jan 27 16:30-17:30 UTC 2020)

Notes

The meeting voice transcription is available on the talk page.

  1. Rich Asked Yaron to describe what Canasta is.
    • Yaron Pointed to the Project Canasta page on MediaWiki.org and went over the four main components listed.
  2. Rich Asked Yaron to describe the current needs.
    • Yaron We've heard from Lex, Cindy, Wikibase Solutions, and Bluespice, but haven't heard about Meza yet. I'd like to hear from James more about Meza.
  3. James Provided links to Meza on MediaWiki and GitHub
    • James Meza is actively maintained
    • James We're currently on MW 1.31, but have a branch for 1.35
    • James Working on packages for maintenance
  4. Markus Hallo Welt!/BlueSpice built a MW distribution based on Docker
    • Markus Just need to run Composer install to draw in all extensions, etc.
    • Markus We have many composer files for BlueSpice free, BlueSpice Pro, PDF feature, etc.
    • Markus We start with one composer file and add more for additional needs (extensions, etc.)
  5. Gokhan I work on BlueSpice with Markus at Hallo Welt!
    • Gokhan Composer is handled by the Dev team
    • Gokhan It's stored on GitHub and we try to keep it as small as possible
    • Gokhan We use Continuous Integration testing
  6. Markus Showed the Hallo Welt GiHub repo
    • Markus We have the same Docker environment for BlueSpice Free & Pro
    • Markus We have to think about how to make the system flexible
    • Markus The method is platform independent
  7. Cindy How do you provide containers to people?
    • Cindy Do you give them the Docker image? Any need for orchestration?
  8. Gokhan We are using Harbor as a private registry. Docker Hub. Building is the same
  9. Lex My solution is not an alternative to Meza, it's a post process
    • Lex Something should create a MW root structure, my solution acts on this
    • Yaron Your solution seems to have 2 steps:
      1. Set up MW
      2. Package it
        • Lex Yes

Chat transcript

Content pulled from the chat record of the meeting.