Change Details

We need to define our budget request for FY2016-17 developer events, as part of {T124420}. In the current fiscal year our big items are the #Wikimedia-Developer-Summit-2016 and the #Wikimedia-Hackathon-2016, and they comprise organization logistics plus travel sponsorship. Wikimania's hackathon is not included here because its organization and budget are part of Wikimania itself. While the Wikimedia Hackathon looks like well aligned with T124420, the significantly more expensive Summit is not very consistent with the goal of Boosting developer contributions. We have several logical options: * Re-focus the Summit in order to have an event that contributes directly to the Technical Collaboration team goals. * Stop organizing the Summit (or organize it with a different budget) and use the budget for other hackathons or developer events with a focus on outreach and community contributions. * Re-focus the Technical Collaboration team goals.

We need to define our budget request for FY2016-17 developer events, as part of {T124420}. In the current fiscal year our big items are the #Wikimedia-Developer-Summit-2016 and the #Wikimedia-Hackathon-2016, and they comprise organization logistics plus travel sponsorship. Wikimania's hackathon is not included here because its organization and budget are part of Wikimania itself. While the Wikimedia Hackathon looks like well aligned with T124420, as of today the significantly more expensive Summit is not very consistent with the goal of Boosting developer contributions. We have several logical options: * Re-focus the Summit in order to have an event that contributes directly to the Technical Collaboration team goals. * Stop organizing the Summit (or organize it with a different budget) and use the budget for other hackathons or developer events with a focus on outreach and community contributions. * Re-focus the Technical Collaboration team goals. * Assume that the main goal of the Summit and the Technical Collaboration team are different, but still valid in both cases. No matter what, we need a clear plan for an ask of $120k USD ($100 for logistics, $20 for travel sponsorship) + extra accommodation costs of WMF employees (very rough and conservative assumption: 60 travelers x 3 extra nights x $200 night = $36,000 ). In previous editions we had hesitations between internal discussion vs outreach.

We need to define our budget request for FY2016-17 developer events, as part of {T124420}. In the current fiscal year our big items are the #Wikimedia-Developer-Summit-2016 and the #Wikimedia-Hackathon-2016, and they comprise organization logistics plus travel sponsorship. Wikimania's hackathon is not included here because its organization and budget are part of Wikimania itself. While the Wikimedia Hackathon looks like well aligned with T124420, as of today the significantly more expensive Summit is not very consistent with the goal of Boosting developer contributions. We have several logical options: * Re-focus the Summit in order to have an event that contributes directly to the Technical Collaboration team goals. * Stop organizing the Summit (or organize it with a different budget) and use the budget for other hackathons or developer events with a focus on outreach and community contributions. * Re-focus the Technical Collaboration team goals. * Assume that the main goal of the Summit and the Technical Collaboration team are different, but still valid in both cases. No matter what, we need a clear plan for an ask of $120k USD ($100 for logistics, $20 for travel sponsorship) + extra accommodation costs of WMF employees (very rough and conservative assumption: 60 travelers x 3 extra nights x $200 night = $36,000 ). In previous editions we had hesitations between internal discussion vs outreach.