Event:102: Difference between revisions

From MWStake
Jump to navigation Jump to search
(: Outline.)
(: More notes.)
Line 25: Line 25:
#* (Richard) Still coming, no ETA yet.
#* (Richard) Still coming, no ETA yet.
# '''User survey'''
# '''User survey'''
#* (Mark)  
#* (Mark) The survey was created by Jeroen for:
#*# Users and decision makers
#*# People who don't use MediaWiki yet
#* (Richard) We can advertise the survey through our channels, just need to know when the survey is finished
#* (Richard) #2 seems like the hardest to identify.  One way might be to send tweets with hashtags for Confluence, SharePoint, etc.
# '''Thoughts on the remote EMWCon'''
# '''Thoughts on the remote EMWCon'''
#* (Ike) This was the best we could do given the circumstances and was possibly the most informative conference I've attended.  That being said, there is a lot lost by not being in person
#* (Ike) Suggest that there should be guidance for who should watch developers vs. users
#* (Mark) Lex had a schema for that
#* (Cindy) How it usually happens:
#*# Send out a call for papers
#*# Wait for emails
#*# Guilt people into talking
#*# Collect what you can and group them thematically
#*# I've never had the luxury of a volume of talks to separate tracks
#* (Ike) We need conference attendees to be new users (vs. the same group that attends every year)
#* (Mark) People with these ideas should commit to helping organize in the future so Cindy isn't the only one
#* (Bryan) Given the success of the remote conference for attracting speakers and attendees who would not otherwise be able to attend, we should try to have a concurrent remote conference with every in-person conference
#** (Bryan) Possible downside might be the sentiment from NASA management.  If remote is a possibility, why should we send anyone in-person
#* (Bernhard) Maybe different costs base on in-person vs. remote attendance?
#* (Cindy) The remote portion functionally doesn't have a cost and we don't want to deter possible attendees
#* (Yeroen) Prefer if online is free.  It's a form of marketing.
# '''Discussion about blogs / blogging platforms'''
# '''Discussion about blogs / blogging platforms'''
#* Links
#* (Bernhard) Blogs should be SMW powered.
# '''Composer RFC'''
# '''Composer RFC'''
#* Link
#* (Cindy) There is a need for a best practices page (e.g. Never use Composer to enable an extension, extension.JSON should load them)


==Action board==
==Action board==

Revision as of 16:13, 6 April 2020

Blank.png Date (UTC): 3 April 2020 15:30:00 - 3 April 2020 16:30:00
Blank.png URL: https://meet.google.com/mdd-ufhn-ksb
Blank.png Etherpad: https://etherpad.wikimedia.org/p/mwstake-2020-04

Person.png Attendees: Bernhard Krabina, Bryan Hildebrand, Charlot Cobben, Cindy Cicalese, Daren Welsh, Ike Hecht, James Montalvo, Jared Olson, Jeroen De Dauw, Lex Sulzer, Mark Hershberger, Megan Cutrofello, Peter Meyer, Richard Heigl, Tom Harriman

Click for time zone conversion

{{#copywatchers: Template:Event}}

Meeting agenda

  1. Wait for attendees & chat 5 min
  2. Wiki Quickie 5 min TBD
  3. User survey 20 min Mark
  4. Composer RFC discussion 15 min Mark
  5. Wiki Watercooler remaining Open Mic

Notes

  1. Discussion with WMF CTO
    • (Richard) I had a meeting with Grant Ingersoll, CTO of WMF, regarding MediaWiki usage.
    • (Richard) We discussed the 2030 strategy process.
    • (Richard) He was very interested in what users/developers/consultants think (PHP vs. other languages, microservices, ACL, skinning, etc.).
  2. Update on the MediaWiki Blog
    • (Richard) Still coming, no ETA yet.
  3. User survey
    • (Mark) The survey was created by Jeroen for:
      1. Users and decision makers
      2. People who don't use MediaWiki yet
    • (Richard) We can advertise the survey through our channels, just need to know when the survey is finished
    • (Richard) #2 seems like the hardest to identify. One way might be to send tweets with hashtags for Confluence, SharePoint, etc.
  4. Thoughts on the remote EMWCon
    • (Ike) This was the best we could do given the circumstances and was possibly the most informative conference I've attended. That being said, there is a lot lost by not being in person
    • (Ike) Suggest that there should be guidance for who should watch developers vs. users
    • (Mark) Lex had a schema for that
    • (Cindy) How it usually happens:
      1. Send out a call for papers
      2. Wait for emails
      3. Guilt people into talking
      4. Collect what you can and group them thematically
      5. I've never had the luxury of a volume of talks to separate tracks
    • (Ike) We need conference attendees to be new users (vs. the same group that attends every year)
    • (Mark) People with these ideas should commit to helping organize in the future so Cindy isn't the only one
    • (Bryan) Given the success of the remote conference for attracting speakers and attendees who would not otherwise be able to attend, we should try to have a concurrent remote conference with every in-person conference
      • (Bryan) Possible downside might be the sentiment from NASA management. If remote is a possibility, why should we send anyone in-person
    • (Bernhard) Maybe different costs base on in-person vs. remote attendance?
    • (Cindy) The remote portion functionally doesn't have a cost and we don't want to deter possible attendees
    • (Yeroen) Prefer if online is free. It's a form of marketing.
  5. Discussion about blogs / blogging platforms
    • Links
    • (Bernhard) Blogs should be SMW powered.
  6. Composer RFC
    • Link
    • (Cindy) There is a need for a best practices page (e.g. Never use Composer to enable an extension, extension.JSON should load them)

Action board

Search actions Add an action See this page for more information

Open
None of these labels
+ Extension
+ Conference