Place order for a/v and contact wifi bump for Developer Summit
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Qgil | T153007 Technical Collaboration annual plan FY2017-18 | |||
Resolved | Qgil | T159313 Draft WMF annual plan program about technical events | |||
Resolved | Qgil | T149300 Future of the Wikimedia Developer Summit | |||
Resolved | • Rfarrand | T153996 Wikimedia Developer Summit 2017: Feedback Survey | |||
Resolved | • Rfarrand | T141926 Wikimedia Developer Summit 2017 | |||
Resolved | • Rfarrand | T141928 Contracting for Wikimedia Developer Summit | |||
Resolved | • MelodyKramer | T146615 Promote the Wikimedia developer Summit 2017 beyond the usual circles | |||
Resolved | srishakatux | T146613 Improve remote participation at the Wikimedia Developer Summit 2017 | |||
Resolved | • Rfarrand | T141930 A/V and wifi contracted |
Event Timeline
@Rfarrand: Detail: Could you ask the folks who provide audio+video recordings of WikiDevSummit sessions to encode the videos in WebM/vpx8 (preferably; vpx9 is the 2nd best option) instead of MPEG4/H264 (like in Jan 2016)?
That would allow skipping one step (re-encoding) before uploading to Wikimedia Commons but no issue if that's not possible. Thanks for considering / trying!
We should consider contracting the whole video recording, editing & publishing, in order to assure that those videos are out in Commons and YouTube few hours / days after those sessions end.
It's a type of work that in theory we can do ourselves (volunteers included). In practice, we are not there yet.
Jein... Whoever performs the "Upload to Commons" part needs
- to have access to the video files quickly™ after the recording,
- the video files to be in a file format accepted on Commons (to avoid re-encoding),
- the video files to have an acceptable file size (influenced by resolution, encoding, length), not triggering "File too large to upload directly",
- use a consistent template (less relevant but nice-to-have).
Those items are relevant no matter if a volunteer or contractor performs the upload.
Yes, we should consider contracting. And a contractor might run into similar obstacles like me last time. Just sayin'.
These are now separate things, we are contracting wifi with one company and a/v through another.
Wifi is final, a/v is almost final.
Will update with details on event wiki and close the task once that has been done and a/v contract is final.
Received the first draft of the invoice, pricing is within expected range, sent it back with a few revisions and I will submit the final to finance and legal when I get it next.
A/v contract returned to vendor a second time for final revisions. My deadline to submit to finance is Sunday evening.
final contract with WMF - nothing more to do on my end, both contracts being processed by accountspayable. I am closing this task! Woo!