This is the retro for the sprint March 4-18th - thank you to the core contributors who have submitted their check-in!
The content of the check-ins can be found there:
Here are the points that have been listed for improvement. Pick 1 to 3 options by Tuesday, and we’ll try to address & assign action items on the most voted:
Getting feedback/reviews for OSPRs is as always a challenge (@Felipe)
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? (@Zia_Fazal)
Is Tutor ready for doing development? I tried to review a PR with Tutor instead of devstack, and the documentation wasn’t comparable. In the interests of time, I switched back to devstack. , I can’t get the kudos feature to work in friday.app. Somehow the people I want to thank are never in the drop-down list. (@pdpinch)
Async channels seem kinda quiet. Is that because everyone’s humming along just fine? (@sarina)
I should get right the time for the check-in. Also, I need learn more about the CCs processes (@mgmdi)
Hummm regarding the hours, should I really keep track of my hours? somestuff I report aren’t really assigen to me officially as a core contributor since I am a translator… So should I only report stuff related to my official responsibility or everything ? (@ghassan)
To encourage broader reporting, here are the totals of the hours reported in the last four sprint sheets (Mar 18th, Mar 4th, Feb 18, Jan 21):
Hi core contributors – there is until today to vote & comment on the blockers listed above. I’ll bring up the most voted ones at the contributors meetup tomorrow, which haven’t been resolved async by then.
Is Tutor ready for doing development? I tried to review a PR with Tutor instead of devstack, and the documentation wasn’t comparable. In the interests of time, I switched back to devstack. … (@pdpinch)
Hey Peter, @regis and I are actively working to make Tutor suitable as a drop-in Devstack replacement. You can see our roadmap here; check out the epic titled “Dev Quality-Of-Life”. Happy to hear what pain points & documentation gaps you or anyone else found so that we can make sure they’re on that roadmap!
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.