antoviaque
March 24, 2022, 11:50am
4
We discussed the three blockers with the most votes during the last Contributors meetup on Tuesday – @jalondonot did an amazing job summing them up in the meeting recap:
1. Async channels seem kinda quiet. Is that because everyone’s humming along just fine?
Conclusions:
This might be related to the workload from each person’s main job.
The discussion around this topic should keep going in Discuss since it seems there is not a clear root cause nor an action point yet.
We agreed to see how it goes, as well as to encourage bringing up any blocker or issue around CC work.
2. Getting feedback/reviews for OSPRs is as always a challenge
Conclusions:
It is difficult to find someone who has enough experience to review that. It could be useful to have a community expert directory to know who is an expert on what to reach out to the correct person: OEP-56: Architectural Advisory Process
Using OEP-55 could be useful.
=> I posted a question related to this in the OEP, about whether maintainers would be required to provide reviews: https://github.com/openedx/open-edx-proposals/pull/290#discussion_r834141344 . And see also https://github.com/openedx/open-edx-proposals/pull/290#discussion_r834091497
People become experts without knowing they became experts. Building confidence is a point to be considered.
If you have done enough to get the community informed about the changes you are trying to implement and even with that, you don’t get enough feedback/reviews, you should trust your gut and go ahead. If it’s broken, someone will raise her hand and put a spotlight on it.
Encouraging people to review even if they are not experts is a great way to start acquiring expertise
Having reasonable deadlines in place for a review could be a good approach to encourage people to do it and also to resolve the blocker in case the lack of reviews and feedback is preventing the PR from being merged. At the end of that deadline, you should feel comfortable getting the PR merged.
Even if you don’t have the ability to provide an improving review it does not mean you can’t give a review
3. I’m difficulty assign something from BTR board to myself or moving issue assigned to me from in progress to Done. How we can improve these how I can perform these tasks myself?
Conclusions:
If you don’t have the right access to the repository where the issue is you cannot self-assign or assign that person. However, if that person comments and says “you can assign this to me”, that person will get the issue assigned.
Also here @sarina took on an action item, to start a discussion (in the forums, or maybe in a new PR?) about how/when to grant the read/write privilege that allows to assign issues. In this case it could make sense to grant that privilege to @Zia_Fazal but there should be a limit to who gets that write privilege, as it means also having write access to the corresponding git repository.
2 Likes