Page MenuHomePhabricator
Create Task
Maniphest T153996

Wikimedia Developer Summit 2017: Feedback Survey
Closed, ResolvedPublic
Actions

Description

I will be creating a Wikimedia Developer Summit Feedback Survey.
I will be using last year's survey with a few changes - including: logistic details relevant to this year, giving people the option to opt in to a mailing list for events, and anything else that comes up throughout the event or that is suggested here and makes sense. Suggest away!

Related Objects
Search...

StatusSubtypeAssignedTask
 ResolvedQgilT153007 Technical Collaboration annual plan FY2017-18
 ResolvedQgilT159313 Draft WMF annual plan program about technical events
 ResolvedQgilT149300 Future of the Wikimedia Developer Summit
 Resolved• RfarrandT153996 Wikimedia Developer Summit 2017: Feedback Survey
Resolved• RfarrandT141926 Wikimedia Developer Summit 2017
 Resolved• RfarrandT141928 Contracting for Wikimedia Developer Summit
Resolved• RfarrandT141929 Developer Summit Catering Orders Complete
Resolved• RfarrandT141932 Furniture set-up and order for Wikimedia Developer Summit
Resolved• RfarrandT141939 Contract the Golden Gate Club for the Wikimedia Developer Summit
 Resolved• RfarrandT141933 Shuttle Transportation: Wikimedia Developer Summit
 Resolved• RfarrandT141934 Social Event Plan: Wikimedia Developer Summit
ResolvedQgilT141938 Prepare a program for Wikimedia Developer Summit 2017 to effectively address current high level movement needs
 Resolved• RfarrandT141937 Wikimedia Developer Summit Scholarships
 Resolved• RfarrandT141927 Open Registration for the Wikimedia Developer Summit
 ResolvedQgilT141935 Wikimedia Developer Summit Wiki up
 ResolvedQgilT147406 Facilitate Wikidev'17 main topic "How to grow our technical community"
 ResolvedLucieT148598 Actions to grow the diversity of our technical community
 ResolvedAklapperT149564 Better recommending of tasks suitable for new technical contributors
 ResolvedTgrT149635 [WikiDev17] Developer Wishlist
 DuplicateNoneT155073 Organize a first Developer Wishlist survey with results by 2017-02-15
 Duplicate• MoushiraT154545 Discuss creating a UI/UX design hub
 ResolvedMarkAHershbergerT149586 #mwstake meeting at the Developers Summit
 Resolved• chasempT147593 Facilitate Wikidev'17 main topic "Building on Wikimedia services: APIs and Developer Resources"
 ResolvedAnomieT148855 Working with the fancy old MediaWiki API
 ResolvedcscottT147602 Facilitate Wikidev'17 main topic "Handling wiki content beyond plaintext"
 OpenNoneT149667 Build an article annotation service
 DeclinedMarkAHershbergerT147896 Annotations in VisualEditor
 OpenFeatureNoneT20231 provide a way to specify what text/statement is supported by a <ref> block.
 OpenNoneT89578 Allow readers to mark a sentence/selection as needing a citation
 OpenNoneT424062 Extend Extension:Translate to support region annotations
 OpenNoneT131516 Reduce or eliminate the need for the user to touch <translate> tags and unit markers
 OpenNoneT143326 Invent automatic segmentation in translation units without <translate> tags
 OpenNoneT143327 Make the Translate extension be based on DOM, not strings
 OpenFeatureNoneT55974 Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension)
 ResolvedArlolraT50891 Parsoid should support <translate> and <tvar> natively as they are not normal parser tags
 DeclinedssastryT105186 Support Translate extension in Parsoid
 ResolvedArlolraT55874 Add a generic extension registration mechanism
 OpenNoneT49344 Internal nodes should eventually be in a separate document ("sub-documents")
 ResolvedihurbainT261181 Make Translate extension compatible with Parsoid
 ResolvedNikerabbitT44239 Translatable pages (pages using Translate extension syntax) can create unusable section edit (editsection) links
 ResolvedihurbainT291855 Adjust meta tags handling for annotations
 ResolvedihurbainT292285 Add messages for the Translate annotation in the Translate extension
 ResolvedihurbainT295170 Move Parsoid's Translate implementation into the Translate extension repo
 ResolvedihurbainT296107 Special treatment for translation unit marker comments in <translate>
 ResolvedihurbainT295837 Analyze newline dirty diffs introduced by Parsoid around <translate> tags for rendering impacts
 ResolvedBUG REPORTihurbainT295233 PHP Notice: Trying to get property 'parentNode' of non-object
 ResolvedssastryT295406 Look at selser failures in rt-testing caused by the Annotations feature
 ResolvedihurbainT295330 WrapAnnotations breaks DSR correctness in some cases
 ResolvedBUG REPORTihurbainT296169 Parsoid sometimes nests the annotation tags when round-tripping wikitext
 DeclinedBUG REPORTihurbainT296485 Annotation nesting detection is not well handled when annotations span over an attribute
 ResolvedBUG REPORTihurbainT296412 Rendering difference between legacy and Parsoid with <translate> tags around a heading
 OpenBUG REPORTNoneT296408 Rendering difference between legacy and Parsoid with newlines after styling and <translate> tags
 ResolvedBUG REPORTihurbainT297770 Extended annotation ranges sometimes duplicate the closing tag when round-tripping with edits
 ResolvedBUG REPORTArlolraT299685 Some headings are missing on the main page on Meta-Wiki in Parsoid rendering
 ResolvedihurbainT295834 Add special handling for annotation tags in template arguments
 ResolvedBUG REPORTihurbainT296392 Old syntax tvar breaks templates
 ResolvedFeatureihurbainT305066 Make extended annotation ranges uneditable
 ResolvedBUG REPORTmatmarexT303298 mw:Placeholder elements are editable in VE
 OpenBUG REPORTNoneT360267 {{TRANSLATIONLANGUAGE}} is not handled in Parsoid parses
 ResolvedNikerabbitT274881 Change translation variable (tvar) syntax
 OpenNoneT171976 Invest in our future by researching a radically better multi-lingual content system (both reading and editing), compatible across all devices
 ResolvedihurbainT270422 Visual diff behaves poorly on pages using Translate extension
 StalledNoneT325939 Consider adding markers in a duplicated page
 DeclinedNoneT149660 Glossaries, pronunciations, and dictionaries
 OpenNoneT114454 [RFC] Visual Templates: Authoring templates with Visual Editor
 OpenFeatureNoneT44495 Subtitle translation with Translate extension
 OpenNoneT44790 Use language code subpages for subtitles to allow Translate extension usage
 OpenNoneT147626 Basic subtitle translation support for Wikimedia Commons
 ResolvedTptT148828 What should we do for ProofreadPage content models
 ResolvedYaron_KorenT149612 Bringing "Enterprise MediaWiki" to the Wikimedia Foundation
 ResolveddanielT149532 Why Multi-Content-Revisions? Use cases and requirements.
 Resolved• brookeT107595 [RFC] Multi-Content Revisions
 ResolveddanielT141877 Update Multi-Content-Revision design document, and move it to mw.org
 ResolveddanielT141878 Build a straw-man DB schema for Multi-Content-Revisions
 DeclinedNoneT149056 Supporting Vertical Writing Mode in MediaWiki
 OpenNoneT148734 Moving associated content out of the wikitext
 ResolvedcscottT151950 Wikitext 2.0 Session at Wikidev'17
 ResolvedssastryT149282 Improved editability, tooling, reasoning, and performance by adopting DOM-based semantics for wikitext
 DeclinedssastryT142803 [RFC] Spec for future wiki content processing model ("wikitext 2.0")
 DuplicatecscottT149658 A new semantics for templates
 OpenNoneT149659 Grunge, or "zoom"
 ResolvedcscottT151952 Media, Visualizations, and Layout at Wikidev'17
 OpenNoneT90914 Provide semantic wiki-configurable styles for media display
 ResolvedTheDJT150461 Story Builder
 DuplicateNoneT147604 Cross-functional support for rich media
 DuplicateTheDJT149554 What's next for Audio and Video ?
 DuplicateYurikT149547 Making articles more interesting with data visualizations
 ResolvedcscottT151958 Annotations at Wikidev'17
 ResolvedHalfakT147708 Facilitate Wikidev'17 main topic "Artificial Intelligence to build and navigate content"
 ResolvedHalfakT147710 What should an AI do you for you? Building an AI Wishlist.
 ResolvedHalfakT147929 Algorithmic dangers and transparency -- Best practices
 Resolved• FjalapenoT148690 Where to surface AI in Wikimedia Projects
 Resolved• Capt_SwingT149373 Evaluating the user experience of AI systems
ResolvedcscottT149666 Next steps for machine translation
 ResolvedgregT147937 Facilitate Wikidev'17 main topic "How to manage our technical debt"
 DeclineddanielT149535 Refactoring the Interwiki Map: status and outlook
 ResolvedKrinkleT149534 Scaling the MediaWiki database schema
 ResolveddanielT149533 Platforms are Products too!
 ResolvedJoeT149408 Asynchronous processing in production: one queue to rule them all
 Declined• ArrbeeT147171 i18n maintenance for MediaWiki and extensions
 ResolvedAklapperT149639 Better code review processes for reviewers
 ResolvedJoeT149617 Integrating MediaWiki (and other services) with dynamic configuration
 ResolvedJoeT155823 Expand conftool to support multiple objects via a schema definition.
 ResolvedNoneT156100 DNS: dynamically generate entries for service discovery
 ResolvedVolansT160994 Create the failoid service as fallback for the DNS discovery
 ResolvedJoeT156924 Allow integration of data from etcd into the MediaWiki configuration
 ResolvedVolansT160178 MediaWiki Datacenter Switchover automation
 ResolvedjcrespoT161007 Decouple Mariadb semi-sync replication from $::mw_primary
 ResolvedLegoktmT162188 Pick/develop a PHP library for etcd to use in MediaWiki
 ResolvedgregT153022 First Tech Debt Bash
 Resolved• MelodyKramerT146615 Promote the Wikimedia developer Summit 2017 beyond the usual circles
 ResolvedsrishakatuxT146613 Improve remote participation at the Wikimedia Developer Summit 2017
 Resolved• RfarrandT141930 A/V and wifi contracted
Resolved• RfarrandT132400 Developer Summit 2017: Work with TPG and RelEng on solution to event documenting
ResolvedsrishakatuxT150150 Create a schedule table for sessions in a grid format for the developer summit
ResolvedQgilT146369 Open the Wikimedia Developer Summit 2017 call for participation
 ResolvedQgilT146362 Define main topics of the Wikimedia Developer Summit 2016
 Resolved• mmodellT146377 Phabricator form to submit Wikimedia developer Summit 2017 proposals
 ResolvedsrishakatuxT147955 Organize unconference at the Wikimedia Developer Summit 2017
ResolvedsrishakatuxT147057 Document the Wikimedia Developer Summit Unconference
 ResolvedsrishakatuxT151190 Attend Aspiration Tech to learn new facilitation methods
 DeclinedQgilT146749 Consider using Phabricator Calendar events to schedule Wikimedia Developer Summit sessions
 Resolved• RfarrandT151490 Wikimedia Developer Summit 2017 Opening
 Resolved• RfarrandT151492 Wikimedia Developer Summit 2017 Closing
 Resolved• RfarrandT154339 Wikimedia Developer Summit Signage
 Resolved• RfarrandT155597 Wikimedia Developer Summit 2017 Debrief(s)
 ResolvedQgilT157134 Wikimedia Developer Summit 2017 Program committee debrief

Event Timeline

• Rfarrand created this task.Dec 23 2016, 2:35 AM
Qgil edited projects, added: Developer-Advocacy (Jan-Mar-2017); removed: Developer-Advocacy (Oct-Dec-2016).Dec 23 2016, 8:58 AM
Qgil moved this task from Backlog to Organization on the Wikimedia-Developer-Summit board.
Qgil moved this task from Backlog to Ready to Go on the Developer-Advocacy (Jan-Mar-2017) board.
Qgil added a parent task: T149300: Future of the Wikimedia Developer Summit.
Qgil removed a parent task: T141926: Wikimedia Developer Summit 2017.Dec 23 2016, 9:06 AM
Qgil added a subtask: T141926: Wikimedia Developer Summit 2017.Dec 23 2016, 9:09 AM

We need to gather feedback helping us planning T149300: Future of the Wikimedia Developer Summit.

• Rfarrand added a comment.Jan 10 2017, 11:41 PM

Add question about preferred session length to feedback survey

Qgil added a comment.Jan 11 2017, 12:33 PM

Is it possible to check the survey from last year in order to make suggestions?

• Rfarrand added a subscriber: • MelodyKramer.Jan 11 2017, 7:54 PM

Thanks Rachel! Pairing down this list a bit. I'd love to know:

  1. What can we do to improve the experience for remote participants?
  1. What was the best part of the conference for you?
  1. What would you improve for next year?
  1. Who should be at the next Dev Summit who wasn't at this one?
  1. Are there different ways we should do outreach before or during the conference next year?

(all from @MelodyKramer)

Qgil moved this task from Ready to Go to January on the Developer-Advocacy (Jan-Mar-2017) board.Jan 15 2017, 5:42 PM
• Rfarrand added a comment.Jan 17 2017, 11:10 PM

This was sent out on Wednesday evening after the event. I will send 1 follow up email with a deadline and then close the request for feedback.

Nemo_bis subscribed.Jan 20 2017, 1:24 PM
• Rfarrand mentioned this in T150658: Technical Collaboration quarterly check in for January – March 2017.Jan 26 2017, 12:40 AM
• Rfarrand added a comment.Feb 8 2017, 1:13 AM

The form is now closed, we had 60 responses.
Will update again with a link when I have summarized the information.

• Rfarrand closed this task as Resolved.Feb 15 2017, 2:15 AM

Phew - feedback sprint complete and my head is spinning. As usual, there is some great feedback.

Link the summary of feedback:
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2017/Lessons_Learned

I am closing this task as there is nothing further I need to do with the feedback from the survey itself until the next event. I sent "Thank You" emails to people who ran sessions that got a lot of positive feedback.

The Lessons Learned link above is not quite complete. I need to incorporate both of the following into it before I remove the work in progress tag.
https://phabricator.wikimedia.org/T155597
https://phabricator.wikimedia.org/T154925
(both are currently open tasks with high priority.)

Qgil awarded a token.Feb 20 2017, 2:17 PM
• Rfarrand closed subtask T141926: Wikimedia Developer Summit 2017 as Resolved.Mar 16 2017, 9:53 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits