User:Bryan Hilderbrand/Meeting Notes (03FEB): Difference between revisions

From MWStake
Jump to navigation Jump to search
No edit summary
(→)
 
Line 16: Line 16:
==Notes==
==Notes==
The meeting voice transcription is available on the [[User_talk:{{PAGENAME}}|talk page]].
The meeting voice transcription is available on the [[User_talk:{{PAGENAME}}|talk page]].
# {{Agenda presenter|Yaron}} This
# {{Agenda presenter|Yaron}} My inclination is to move forward with Lex's solution
 
#* Lex has had the time to create a working solution
#* NASA's development team have been slow to participate and seem to be stuck at an older MW version
# {{Agenda presenter|Lex}} I'm not sure I understand, my solution is a way to package & distribute a MW set-up, not create it
#* That's why I call it [https://github.com/dataspects/mediawiki-manager Mediawiki Manager (GitHub link)]
# {{Agenda presenter|Markus}} Described Hallo Welts Docker approach
# {{Agenda presenter|Lex}} Ikea & NASA have similar goals, create anything with minimal tools
#* I incorporated a Extension Diff checker into my [https://github.com/dataspects/mediawiki-manager Mediawiki Manager] that allows different people to design/build different solutions and "compete", then understand what changed
# {{Agenda presenter|Rich}} What NASA needs is a "MediaWiki Easy Administration Tool", not a completely intentional reference to Meza, but that's what we need
# {{Agenda presenter|Markus}} I see difficulties in the extension upgrading procedure and I also think we should only target 1.35 and move forward
# {{Agenda presenter|Markus}} It seems Meza can't handle different extensions?
#* {{Agenda presenter|Rich}} No, there is a [https://github.com/enterprisemediawiki/meza/blob/master/config/core/MezaCoreExtensions.yml configuration file] that handles this
#* {{Agenda presenter|Markus}} Then why is it difficult to jump to 1.35?  Shouldn't this be straightforward?
#* {{Agenda presenter|Rich}} They have a very robust testing/CI process that handles SAML/SSO, WikiFarms, Parsoid, etc., all changes must make sure all components don't break


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

Latest revision as of 21:06, 3 February 2021

Attendees

  • Bryan Hilderbrand
  • Cindy Cicalese
  • Ike Hecht
  • Lex Sulzer
  • Markus Glaser
  • Rich Evans
  • Yaron Koren

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


Notes

The meeting voice transcription is available on the talk page.

  1. Yaron My inclination is to move forward with Lex's solution
    • Lex has had the time to create a working solution
    • NASA's development team have been slow to participate and seem to be stuck at an older MW version
  2. Lex I'm not sure I understand, my solution is a way to package & distribute a MW set-up, not create it
  3. Markus Described Hallo Welts Docker approach
  4. Lex Ikea & NASA have similar goals, create anything with minimal tools
    • I incorporated a Extension Diff checker into my Mediawiki Manager that allows different people to design/build different solutions and "compete", then understand what changed
  5. Rich What NASA needs is a "MediaWiki Easy Administration Tool", not a completely intentional reference to Meza, but that's what we need
  6. Markus I see difficulties in the extension upgrading procedure and I also think we should only target 1.35 and move forward
  7. Markus It seems Meza can't handle different extensions?
    • Rich No, there is a configuration file that handles this
    • Markus Then why is it difficult to jump to 1.35? Shouldn't this be straightforward?
    • Rich They have a very robust testing/CI process that handles SAML/SSO, WikiFarms, Parsoid, etc., all changes must make sure all components don't break

Chat transcript

Content pulled from the chat record of the meeting.

Retrieved from "https://mwstake.org/w/index.php?title=User:Bryan_Hilderbrand/Meeting_Notes_(03FEB)&oldid=2780"