On 8/20/19 11:52 AM, Clement Verna wrote: > > > Yes just to make sure there is no misunderstanding I am not trying to blame anyone too and I am also keen on finding a better ways for these work to move smoothly without the need for you to bug someone every day and without having someone bugging us every day :-D. > > I think in that particular case, the problem is that your needs went under our radar, and the work that you needed was not visible, hence not prioritized at our team level. This means that we have been busy with X other initiatives (Rawhide Gating, EPEL-8, Community OpenShift, + usual keeping the lights on work). Unfortunately it is almost impossible for you to see how busy we are and what are our current priorities and work in progress. We hope to improve in that area, so that I believe it would be easier for you to see what the team is busy with. Then it should be easier for you to raise your hand and say that you have something urgent coming in. > In the same time we don't really have visibility to your planning and to your milestones, so it is also difficult for us to make a good call without knowing the expected timeline and what is your critical path. > > All that to say I think the main problem here is lack of communication and lack of sharing information. We are totally in agreement. My request here was trying to short circuit the process since I know what our priorities are and you know what your priorities are we can make sure we sync up on the overall goals (i.e. high level sessions where we discuss what we want to do and how to do it, like the sesions we had with mohan, patrick, kevin before) and then someone from our team executes on those goals. I understood from the beginning that it might not work. Just wanted to have the conversation. Thanks for everything you do cverna! Dusty _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
