Session Themes and Topics
- Theme: Working together, decision making and responsibilities
- Topic: Collaboration(inter/intra community/WMDE/WMF) and Process
- Birgit Müller
- Greg Grossmeier
- Deb Tankersley
At this session we will look into intersections and requirements between different stakeholders and discuss processes, responsibilities and roles. It’s going to be interactive, challenging and fun :-).
We want to develop a
- joint understanding about requirements, intersections, dependencies and gaps between teams, orgs, individual contributors
- joint understanding about roles and responsibilities in the product development process, both in different scenarios and for different stakeholder groups
- joint understanding about best practices for collaboration, feedback iterations and decision making
We will mainly work with breakout groups, and around the development processes for:
A.) Wikimedia projects
- WMF and WMDE product development
- Volunteer driven projects
B.) 3rd party usage
Questions to answer during this session
- Who owns features, UIs, code and processes? What process determines code ownership and establishing operational responsibility? Who owns the decisions in the development process and at what points?
- How do platform teams serve and schedule the features to serve multiple use cases, organizations and products?
- What does effective collaboration look like between Audiences and Technology? What about product and engineering? Research and Product? What about WMF/WMDE? Who owns which parts of the processes? What feedback loops need to be established?
- Where should the TechCom process fit into the engineering and product planning processes?
Facilitator and Scribe notes
Session Leaders please:
- Add more details to this task description.
- Coordinate any pre-event discussions (here on Phab, IRC, email, hangout, etc).
- Outline the plan for discussing this topic at the event.
- Optionally, include what it will not try to solve.
- Update this task with summaries of any pre-event discussions.
- Include ways for people not attending to be involved in discussions before the event and afterwards.
Post-event Summary/Action items:
Things we need to adress/action items (prioritized via dot voting, 3 dots per person across fields)
WMF/WMDE development for Wikimedia
Open questions/currently not working well:
- How do we plan for maintenance once a product is in production? (21)
- Decision, approval, Technical Committee (10)
- How to decide on impact metrics (8)
- How do we figure out security and privacy implications (2)
- Come up with better ideas to get new ideas into the pipeline and communicate these ideas (3)
Important/good that we have this:
- Documentation, user design, proof of concept (9)
Volunteer driven development for Wikimedia
- How do we ensure volunteer time is not wasted? (12)
Currently not working:
- No process to support volunteers in their contributions (2)
- Dedicated code review team for volunteer contributions (17)
- Socialize and validate” touch point early in the process (“good idea/bad idea”, “this is how you can do that”) (8)
- Cognitive styles/GenderMag (0)
- Contribution styles (0)
Important/good that we have this:
- Events/Hackathons (0)
Development for/of 3rd Party users
Currently not working well:
- Define update mechanism (9)
- Define delivery method (3)
- Choose a Release Manager for 3rd party releases (0)
- Define bundles of extensions (1)
- Governing body, SIG with regular meetings and diverse participation (16)