Page MenuHomePhabricator

Wikimedia Technical Conference 2019 Session: Integrating contributions from other teams or volunteers
Open, Needs TriagePublic

Description

Session

  • Track: People and Processes
  • Topic: Integrating contributions from other teams or volunteers

Description

What are current practices to include contributions (code patches, feature requests ...) from other teams or individuals in own team processes and workflows? What worked and what didn’t work in the past, and why? Let’s learn from each other and explore new ideas and improvements for processes, methods and workflows around contributions to own projects.

Questions to answer and discuss

Question:
Significance:

Question:
Significance:

Related Issues

  • ...
  • ...

Pre-reading for all Participants

  • [add links here]

Notes document(s)

[link to notes document (gdoc and / or etherpad)]

Notes and Facilitation guidance

https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/NotesandFacilitation


Session Leader(s)

Session Scribes

  • [name]
  • [name]

Session Facilitator

  • [name]

Session Style / Format

  • [what type of format will this session be?]

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 this session 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:

  • ...

Post-event action items:

  • ...

Event Timeline

debt created this task.Fri, Oct 4, 3:50 PM
TK-999 awarded a token.Sat, Oct 5, 2:55 PM
hashar awarded a token.Mon, Oct 7, 2:46 PM
hashar added a subscriber: hashar.Mon, Oct 7, 2:48 PM

My biggest challenges are:

  • find whom actually maintains the code I touch and how to get them interested in reviewing and accepting my proposal.
  • on the opposite for some of the code I maintain, I have trouble finding co maintainers and for at least one repo, trouble to catch up with all the changes being proposed.

Hey @hashar would you be interested in leading this session? - you could also co-lead it with @WMDE-Fisch, who has some experience in this area too (he might be still out of office, I guess @WMDE-leszek knows more) - I think you would be great as a session-(co-)leader for this :-)

TheDJ added a subscriber: TheDJ.Sat, Oct 12, 3:14 PM

Maybe we can discuss about an incentive system to review code. I feel with the current setup of teams it is very hard to incentivize anyone to review code outside of their own responsibility. It's basically a favor that people are doing to eachother and while nice at the human level (and that will probably always be the primary motivator to use), maybe there is more we can do to encourage people to reach across team/volunteer/3rd party lines..

gamify ? 😂

Tgr added a subscriber: Tgr.Sun, Oct 13, 9:34 PM

Isn't this sort of the same as T234660: Wikimedia Technical Conference 2019 Session: Code Health/Code Review?

I agree with @TheDJ that lack of incentives or responsibilities is one of the main problems here.

I agree with @TheDJ that lack of incentives or responsibilities is one of the main problems here.

I agree.

Also among the large general Gerrit backlog and also the freedoms that an open Gerrit brings I find it quite hard to actually determine what I should review and what people want me to review.
Currently that is easy within a team that has day to day communication, and also across some teams that work with each other day to day, but perhaps this communication could be formalized in a layer on top of just adding reviewers to a patch? Some sort of priority for things to review would be quite nice too.

Hey @hashar would you be interested in leading this session? - you could also co-lead it with @WMDE-Fisch, who has some experience in this area too (he might be still out of office, I guess @WMDE-leszek knows more) - I think you would be great as a session-(co-)leader for this :-)

Yes I am willing to co-lead.

I can definitely present tip and tricks to ease integration of contributions, specially on the code review side/Gerrit. For features/code and how different people synchronize outside of a team scope, I can not tell, the way I work is probably not an example to follow since it is barely formalized and I have lot to improve myself :-D

Maybe we can have the session driven by some examples to raise awareness of what is successfull/bad for various teams/people. Then eventually break out in small groups and come up with a set of good/bad and recommendations.

There is indeed a lot of overlap with T234662: Wikimedia Technical Conference 2019 Session: Integrating contributions from other teams or volunteers as pointed out by @Tgr , though I see that other session to focus on code health automatic feedback. This session could focus on the people behavior and incentives to help folks to work together.

Poking again @WMDE-Fisch lets sync up whenever you are back around :]

Tgr added a comment.Wed, Oct 16, 12:56 PM

Also among the large general Gerrit backlog and also the freedoms that an open Gerrit brings I find it quite hard to actually determine what I should review and what people want me to review.

Yeah, it's hard to differentiate between "this might be interesting for you" and "could you review this please?" (plus some of the change tracking we use involves people being automatically added as reviewers, which makes it impossible to send them a signal by manually adding them). It's probably just a matter of developing new community norms (like adding people to CC instead of reviewers) - as such, definitely a good topic for discussion.

Yes I am willing to co-lead.
Maybe we can have the session driven by some examples to raise awareness of what is successfull/bad for various teams/people. Then eventually break out in small groups and come up with a set of good/bad and recommendations.
I can definitely present tip and tricks to ease integration of contributions, specially on the code review side/Gerrit. For features/code and how different people synchronize outside of a team scope, I can not tell, the way I work is probably not an example to follow since it is barely formalized and I have lot to improve myself :-D
This session could focus on the people behavior and incentives to help folks to work together.

@hashar awesome, thanks :-) - I like that idea. That would provide the room to exchange on what worked/didn't work in the past and come up with a list of recommendations for better/best practices.

In case Fisch is not back in time - would anyone in this round be interested in co-leading this session?

@hashar, looks like Fisch will be back in time, will add both of you as session leaders to the task description. :-)

Bmueller reassigned this task from Bmueller to hashar.Thu, Oct 17, 7:33 PM
Bmueller updated the task description. (Show Details)