4 October 2019 MWstake Meeting
|Date (UTC):||4 October 2019 15:30:00 - 4 October 2019 16:30:00|
|Attendees:||, , , , , , , , , , , ,|
- Wait for attendees & chat
Wiki Quickie- No topic
- Consider MWStake role/support for SMWCon Fall 2020
- Sunflower distribution
- MediaWiki news channel
Shared notes: https://etherpad.wikimedia.org/p/mwstake-2019-10
- Process & Safety Management (PSM) with MW + SMW
- I developed a Hazard & Risk analysis for PSM to meet ISO & OSHA requirements using MediaWiki + Semantic MediaWiki
- next mwstake meeting. should plan a presentation of this for the
- Announcing SMWCon 2020
- During SMWCon2019, Matteo Busanelli announced his desire to chair SMWCon 2020
- MWStake should support the conference
- 3rd party MW Maintainers "hang out" at SMWCons
- MWStake should definitely support SMWCon & EMWCon, but what does "support" mean? So far, we haven't been able to support financially, we might be able to in the future, but unsure now.
- OSDA There is potential for financial support by
- As a note, OSDA wasn't able to support SMWCon 2019
- Announcing EMWCon 2020
- I have full support of my management
- Would like to determine an organizing committee. Who is in-charge of the process?
- We should define the process (it doesn't currently exist), but we would like to help where we can
- Noted, I just don't want to do anything out of normal practices
Gave some background on NASA with regards to the conference and a possible tour
- NASA is spread into 10 field centers
- NASA Glen in Cleveland Ohio is lesser known. Most others are "mission" oriented, further north facilities are "tech/research" divisions
- NASA Plum Brook Station is located in rural Ohio, "we are a torture chamber for equipment that is launched". Others design equipment, we reproduce flight/operation conditions
- We could do a tour including the world's largest space vacuum chamber
- We can offer conference facilities at no cost
- Are Foreign Nationals OK?
- Kalahari conference center (literally across the street) which would not need any prior notice. What are we trying to prioritize? 1) Cost or 2) Non-US attendance? Great question. We can either host within NASA, but would need prior notice for admitting foreign nationals or host at the
- We have the budget from when we hosted in Virginia @ MITRE and we had foreign nationals which came with some restrictions, but we were able to accommodate
- If the location requires early foreign national registration, it should be advertised early & clearly
- We would need to know the Min/Max attendees to contact Kalahari, do we know that?
- Min/Max is probably around 30-80, but it probably won't exceed 50
- If you advertise the tour of NASA, we could get 100+ attendees, some of which have never used MW :)
- We should try to optimize "Maximum Pull", try to get the most people able to come. In Paris, 2 people added in the last 24 hours
- Europeans will likely need to plan in advance anyway to just make the flight, usually 4 weeks
- As a Canadian, we book at least 4 weeks due to cost. Also, Early access to program content is always a good idea
- News channel for MW
- As a group we need a place where news about MW, SMW, extensions, skins, etc. can be published
- Hallo Welt!, but under the umbrella of MWStake Technically it's planned to be supported by
- We'd like to start within the year
- Any ideas for content?
- Trying to address the needs not met by existing mailing lists, chat room, etc.
- Sunflower distribution
- Pitched the idea for a "standard distribution of MediaWiki+ that all in the community could support and use
- How would this distribution be used? I've been using Meza. Once VE or Elastic Search is included, it gets difficult
- Good point, we may have too many "brands" (MediaWiki, Semantic MediaWiki, BlueSpice, Meza, QualityBox, etc.)
- Ideally we can define a "common core" that can be maintained by many people
This sounds like we are trying to find a consensus between different groups and users, how will we achieve this consensus?
- Discourse Forum or a wiki We could use my
- I propose a governing document to clearly define what is included in the sunflower distribution, but others can imliment/orchestrate via Docker/Ansible/Kubernetes/etc. on CentOS/Debian/Ubuntu/etc. as they see fit. The document just defines the components.
this page for more informationSee