[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Page MenuHomePhabricator

Future of the Wikimedia Developer Summit
Closed, ResolvedPublic

Description

We need to agree on the future of the Wikimedia Developer Summit, and reflect it in the Wikimedia Foundation Annual Plan FY2017-18.

  • Goals
  • Scope
  • Ownership
  • Budget
  • Location and dates

See also

Related Objects

StatusSubtypeAssignedTask
ResolvedQgil
ResolvedQgil
ResolvedQgil
Resolved Rfarrand
Resolved Rfarrand
Resolved Rfarrand
Resolved Rfarrand
Resolved Rfarrand
Resolved Rfarrand
Resolved Rfarrand
Resolved Rfarrand
ResolvedQgil
Resolved Rfarrand
Resolved Rfarrand
ResolvedQgil
ResolvedQgil
ResolvedLucie
ResolvedAklapper
ResolvedTgr
DuplicateNone
Duplicate Moushira
ResolvedMarkAHershberger
Resolved chasemp
ResolvedAnomie
Resolvedcscott
OpenNone
DeclinedMarkAHershberger
OpenFeatureNone
OpenNone
DeclinedNone
OpenNone
OpenFeatureNone
OpenNone
OpenNone
ResolvedTpt
ResolvedYaron_Koren
Resolveddaniel
Resolved brooke
Resolveddaniel
Resolveddaniel
DeclinedNone
OpenNone
Resolvedcscott
Resolvedssastry
Declinedssastry
Duplicatecscott
OpenNone
Resolvedcscott
OpenNone
ResolvedTheDJ
DuplicateNone
DuplicateTheDJ
DuplicateYurik
Resolvedcscott
ResolvedHalfak
ResolvedHalfak
ResolvedHalfak
Resolved Fjalapeno
Resolved Capt_Swing
Resolvedcscott
Resolvedgreg
Declineddaniel
ResolvedKrinkle
Resolveddaniel
ResolvedJoe
DeclinedArrbee
ResolvedAklapper
ResolvedJoe
ResolvedJoe
ResolvedNone
ResolvedVolans
ResolvedJoe
ResolvedVolans
Resolved jcrespo
ResolvedLegoktm
Resolvedgreg
Resolved MelodyKramer
Resolvedsrishakatux
Resolved Rfarrand
Resolved Rfarrand
Resolvedsrishakatux
ResolvedQgil
ResolvedQgil
Resolved mmodell
Resolvedsrishakatux
Resolvedsrishakatux
Resolvedsrishakatux
DeclinedQgil
Resolved Rfarrand
Resolved Rfarrand
Resolved Rfarrand
Resolved Rfarrand
ResolvedQgil

Event Timeline

Qgil renamed this task from Decision point: Future of the Developer Summit to Future of the Wikimedia Developer Summit.Oct 27 2016, 1:03 PM
Qgil removed Qgil as the assignee of this task.
Qgil subscribed.

Thanks for the initiative, @Elitre. I think it is definitely worth having a discussion about the future of the Wikimedia Developer Summit at the Summit, but I object on other points (and I took the liberty to edit accordingly):

  • Forcing a decision point during the Summit is probably not a good idea, because that is an explicitly biased environment.
  • The real decision point is provided by the Wikimedia Foundation Annual Plan FY2017-18 process, where the Summit either has owner and budget or it hasn't.
  • Given the kind of event the Summit is today, I personally don't think it is the Technical Collaboration team who should own that decision, but the Technology department -- our role should be to support them, not to drive this event.
  • ... and @Rfarrand as the event manager is the natural facilitator of this session, imho.

I would be happy to run this as an informal unconference session if there is demand for it.
Welcoming any help from co-organizers or people with further suggestions.

What I was thinking today is, just make it a part of the final wrapping session?

A discussion about the future of the Summit as part of a plenary session?

If it's a silly idea, don't do it and just make it a question in the after-event survey?

I don't think it is a silly idea. A BoF type of session during the Unconference with the people really interested has all the chances of being very useful, especially if we start the discussion here (there is no reason not to). Having a, say, 20 minute discussion as part of the wrap up with all the attendees in the room is a different story, that probably won't work.

Asking about the future of the Summit in the survey is a very good idea!

@Elitre Hey! As developer summit is less than four weeks from now, we are working on a plan to incorporate the ‘unconference sessions’ that have been proposed so far and would be generated on the spot. Thus, could you confirm if you plan to facilitate this session at the summit? Also, if your answer is 'YES,' I would like to encourage you to update/ arrange the task description fields to appear in the following format:

Session title
Main topic
Type of activity
Description Move ‘The Problem,' ‘Expected Outcome,' ‘Current status of the discussion’ and ‘Links’ to this section
Proposed by Your name linked to your MediaWiki URL, or profile elsewhere on the internet
Preferred group size
Any supplies that you would need to run the session e.g. post-its
Interested attendees (sign up below)

  1. Add your name here

We will be reaching out to the summit participants next week asking them to express their interest in unconference sessions by signing up.

I have just suggested that this happens. I believe it makes sense for DevRel people to lead it eventually?

To maintain the consistency, please consider referring to the template of the following task description: https://phabricator.wikimedia.org/T149564.

@Elitre my bad! I missed the comments above. thank you for proposing this.

would anyone be interested in facilitating this session?

After thinking further... now I am not convinced about having this session at the Summit. It's a very good Annual Plan discussion that we will surely have, but the Summit might not be the right time and place.

Also, the way the proposal is made above puts a lot of pressure and it might create more tension than needed at the event.

I'd say let's organize and enjoy this Summit. Let's do surveys and let's distill lessons learned. And with all these experiences, let's discuss the plan for the next year starting with the basics: goals, ownership, resources.

This task will be assigned to @Rfarrand or @Qgil and discussed/agreed after the Summit, as part of the WMF Annual Plan FY2017-18 work.

Meeting with Maggie, Victoria, Wes, Quim & Myself schedule for Monday to discuss options. Will update this task afterwards.

Meeting with Maggie, Victoria, Wes, Quim & Myself schedule for Monday to discuss options. Will update this task afterwards.

@Rfarrand: Any updates to share yet? :)

Qgil raised the priority of this task from Low to High.
Qgil moved this task from January to February on the Developer-Advocacy (Jan-Mar-2017) board.

I'm taking this task because it is tightly related to the annual plan work. I will update it soon.

Before getting into details about the Summit, we are getting a common picture about the different events organized by the Foundation involving Technology, Product, and Technical Collaboration. The goal is to make these events fit together, with clear and complementary purposes for each.

one suggestion is to have the summit partially or entirely overlap a weekend. This would make it easier for volunteers and people with other obligations during the week (e.g. school) to attend, though I understand this might not be ideal for staff developers, etc.

the european hackathon and wikimania are very good, in this respect.

The current idea is to have all technical events promoted by the Wikimedia Foundation under the same program in the Annual Plan 2017-18. This includes the Summit, the Wikimedia Hackathon, the Hackathon in Wikimania, and any other hackathons or meetings we aim to organize. This program would be lead by Technology (meaning that Victoria Coleman as CTO would be the ultimate owner) and it would be shared with Product and Community Engagement (specifically the Technical Collaboration team). TC would keep organizing these events, no changes there. The change is that all the events will be under the same program, driven by common goals and owners, and organized around a common budget umbrella.

I took the action of drafting that program. It is expected to go through a basic internal review first to clarify the responsibilities of Technology, Product, CE and set basic expectations. I will publish the details as soon as we have a sensible proposal.

Qgil lowered the priority of this task from High to Low.Apr 8 2017, 10:24 PM
Qgil added a subscriber: bd808.

The proposed future of the Wikimedia Developer Summit is described at https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Technology#Program_4:_Technical_community_building

Pasted here for convenience:

  • Outcome 5: Organize Wikimedia Developer Summit as a three day meeting of ~50 senior technical contributors focusing on one strategic theme announced before the call for participation and scholarship requests start.
    • Objective 1: Developer Summit web page published four months before the event includes dates and location (at least nearest airport), main theme, call for participation, call for scholarship requests, and calendar with deadlines. A good representation of non-WMF stakeholders related to the main theme are invited and participate at the event (preferred) or online.
    • Objective 2: A process allows prospect participants to submit statements and proposals about the main theme, and allows the Program Committee to review them and notify their decisions. Discussions start before the event with the involvement of all the relevant stakeholders, in order to identify the points that need to be addressed at the event.
    • Objective 3: Activities during the Summit are well documented, especially outcomes and actions, which will be compiled in a systematic way for better evaluation and followup.

I am going to send an email to wikitech-l highlighting this change and the plans for the Hackathons, which are described at https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Community_Engagement#Program_12:_Onboarding_new_developers (no major) changes are to be expected for the Wikimedia Hackathon and the Hackathon in Wikimania).

Lowering priority of this task, which will remain open until the WMF Annual Plan is officially approved.

Lowering priority of this task, which will remain open until the WMF Annual Plan is officially approved.

@Qgil: https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Technology#Program_4:_Technical_community_building is available now and says

Outcome 5: Organize Wikimedia Developer Summit as a three day meeting of ~50 senior technical contributors focusing on one strategic theme announced before the call for participation and scholarship requests start.

Should this task get resolved, or is something missing?

Not quite resolved! Hopefully by the end of the month!

Lowering priority of this task, which will remain open until the WMF Annual Plan is officially approved.

Andre is right, now the plan is officially approved. News and work related to the next Summit can be organized around new tasks. Time to close this one.