User:Bryan Hilderbrand/Meeting Notes (18DEC): Difference between revisions

From MWStake
Jump to navigation Jump to search
No edit summary
No edit summary
Line 46: Line 46:
#** Customers' Developers
#** Customers' Developers
#**: [[File:Concept vs Technical.png|border|400px]]
#**: [[File:Concept vs Technical.png|border|400px]]
# {{Agenda presenter|Rich}}
#* We have a solution for MW+, Meza!
#* Software Version Description
#** Known set of software that plays well together
#** Use git
#* Different approach from Software <--> Templates/Forms/etc.
#** Doesn't use git
#** Need to bring wiki content under version control (like git)
#*** Totally agree {{Agenda presenter|Ad}}
#*** Could store it on git {{Agenda presenter|Yaron}}
#* {{Agenda presenter|Eric-Jan}}
#** Draw up a list of standard products Ad & Yaron agree on
# {{Agenda presenter|Rich}}
#* Document Management is a good package idea
#* I've been working on a solution and have it deployed on my wikis
# {{Agenda presenter|Richard}}
#* Need to define a list of requirements
#** Requirements are at the core of my world {{Agenda presenter|Rich}}
#** Good requirements just mean, "I provide this"
# {{Agenda presenter|Yaron}}
#* ISO seems like a good "product"

Revision as of 22:35, 31 December 2020

Meeting notes for MediaWiki "Products" Discussion (Fri Dec 18 16:00-17:00 UTC 2020)

Attendees
  • Ad Strack van Schijndel
  • Bryan Hilderbrand
  • Eric-Jan van Kakerken
  • Greg Rundlett
  • Ike Hecht
  • Lex Sulzer
  • Lexi McGillivray
  • Markus Glaser
  • Rich Evans
  • Richard Heigl
  • Yaron Koren
  1. Introductions
  2. Yaron
    • 30s Elevator Pitch
  3. Rich
    • Does this represent a way to pay for things? (buy a fix for an issue, etc.)
    • What is the governance model?
  4. Markus
    • Like a common core? Or a collection of Use Cases (Templates + Use Cases)?
      • Each product would be MW + Extensions + Templates/Forms Yaron
    • MWStake already exists, should this be under their umbrella?
  5. Ad
    • This is similar to the talk I gave at SMWCon2020 called "MediaWiki based open source content services platform" (YouTube link)
    • We need a "common foundation" (MW + Extensions + Search + etc.)
    • Internally we have a tool to "sync" via git
    • We have CRM & Workflow modules
    • Could have a menu with a dropdown so people can add other "Products"/"Components"/"Modules"
      • I think it's better to sell each thing as a stand-alone Product without overselling it as something that "does everything". Better to undersell & then grow Yaron
  6. Richard
    • We need a distribution of MW+
    • Something like the "Sunflower Distribution" (discussed during an MWStake meeting on 04OCT19 link)
  7. Eric-Jan
    • "Content Services Suite"
  8. Ad
    • I think we should focus on the platform with one approach
      • We can do that in parallel Yaron
  9. Lex
    • Should we start with concept vs. technical first?
      • End Users
      • Admins
      • Customers' Developers
        Concept vs Technical.png
  10. Rich
    • We have a solution for MW+, Meza!
    • Software Version Description
      • Known set of software that plays well together
      • Use git
    • Different approach from Software <--> Templates/Forms/etc.
      • Doesn't use git
      • Need to bring wiki content under version control (like git)
        • Totally agree Ad
        • Could store it on git Yaron
    • Eric-Jan
      • Draw up a list of standard products Ad & Yaron agree on
  11. Rich
    • Document Management is a good package idea
    • I've been working on a solution and have it deployed on my wikis
  12. Richard
    • Need to define a list of requirements
      • Requirements are at the core of my world Rich
      • Good requirements just mean, "I provide this"
  13. Yaron
    • ISO seems like a good "product"