User:Bryan Hilderbrand/Meeting Notes (13JAN)

Attendees

• Ad Strack van Schijndel
• Bryan Hilderbrand
• Cindy Cicalese
• Ike Hecht
• Jeroen De Dauw
• Lex Sulzer
• Rich Evans
• Richard Heigl
• Yaron Koren

Meeting notes for MediaWiki "Products" Discussion (Wed Jan 13 16:30-17:30 UTC 2020)

Notes

1. Introductions
2. Ad Misson/Vision/Goals
   • We have a start at this already
3. Rich We something like an "App Store"
   • Ad Sounds like you're saying this is a "Marketplace"
     • We are currently doing that now at Wikibase Solutions, but not as a "package", just knowing what we have internally to fit the need
     • Need a description of all the components
4. Yaron I think Misson/Vision/Goals is defined on the Project Canasta page
   • Rich What are the list of deliverables
     • Yaron Infrastructure & 1st product = 1st deliverable
5. Richard There are many levels to this, so what are all the components & how do they work together
6. Rich I have a File Management package
7. A vote was taken on Etherpad to decide the first package, Document Management won, results below:
   1. CRM
      • Lex
   2. QM/ISO
      • Yaron
   3. BPM
      • Richard Heigl
      • R.Evans
   4. Document Management
      • Ad
      • Ike
      • Bryan
   5. Technical documentation
8. Yaron What are the features/requirements needed
9. Details of both Ike's and Rich's Document Management system below
10. Ad A benefit would be the ability to edit in a browser for files (Word, etc.)
11. Rich Would be nice to have a parser function to "download" a file and strip the unique identifier I need to add to each file
12. Bryan How do we keep the "common" data from each product
    • It seems like "people" are at the heart of most products
13. Cindy There's lots of ideas about perfect "feature sets" but we should deconstruct this into the lowest level:
    1. Sets of pages as a Package
    2. Packages into Modules
    3. Modules into Products
14. Ad Gave an example of how User pages/Modules/Training Pages can give deeper insight into users
    • Paper Ad wrote about An Architectural Model for Component-Basd Application Development
15. Yaron I'm slightly disappointed with the progress of these meetings
    • Please put your infrastructure/ideas/methodology in the Infrastructure solution page for Project Canasta

Document Management Structure

General goal, store file based documents (Word, Excel, PDF, etc.)

Ike's structure

Main idea is an alternative to Google Drive that is more useful in corporate environments as it adds powerful search and tagging.

The system shouldn't care where the document is physically stored, including that Google Docs can be linked to or embedded. In theory, documents can stay in Google Drive and the wiki can just be a wrapper that adds the tagging and other semantic attributes.

A simple example of this type of system was built and presented about by Ike. But the project is not open-source and the copyright is not owned by Ike.

• Presentation about it starts here
• Slides about it (#26-30) are here

Classes

• Document:
  • File name
  • Description
  • Tags
  • Implicit data (size, created by, creation date, last modified by, modification date)

Rich's structure

Multiple signatures are key (engineers, QM, etc.). 2 Main Parts:

1. Unique Identifiers for documents
2. Authorizing signatures

Document Management Classes

• Document
  • ID
  • Title
• Users
• Roles
• Approvals
• ChangeRequests

Chat

• Yaron Koren: https://www.mediawiki.org/wiki/Project_Canasta
• Bryan: https://etherpad.wikimedia.org/p/projectcanasta
• Rich Evans: https://emw-meza.site/emwdev/Files
• Jeroen De Dauw: ill vote your preferred option for 1 bitcoin
• Bryan: ONE Bitcoin? I'll give you 1 satoshi
• Richard Heigl: :-)
• Ike Hecht: With apologies, I figured out why we never released the document management system we built. The client refused to release it as open-source. I can still post some of the features, etc. on the Etherpad.
• Yaron Koren: Yes, please do!
• Bryan: Ike, how does that work for your ability to give "help", "guidance", etc.
• Yaron Koren: Surely you can just list out the set of fields, etc., no? They can't sue you for that...
• Richard Heigl: Rich, can you organisze a presentation, what you already have and what you miss on basis of a productive system?
• Yaron Koren: Oh, I found it - slide 28.
• Ike Hecht: > how does that work for your ability to give "help", "guidance", etc. I think I'm safe :)
• Bryan: Ad, link to your paper?
• Cindy Cicalese: http://users.ece.utexas.edu/~perry/prof/wicsa1/final/goedvolk.pdf maybe?
• Bryan: https://www.semanticscholar.org/paper/Component-based-Application-Development-Strack-Schijndel/c2b819ba864b1e83623cc666490c0b9106d08ee3
• Bryan: Ah, yup. Same thing. You beat me Cindy :)
• Cindy Cicalese: I actually got it from the same link you shared but clicked on the PDF ;-)
• Richard Heigl: I will have to leave in 5 minutes
• Bryan: https://www.mediawiki.org/wiki/Project_Canasta/Infrastructure_solution