Maybe not exactly on the topic but I’d like to express some more thoughts on OpenStack development rhythm being too harsh for newcomers and part time developers.
Although I partially agree with the initial Thierry’s point I think the key thing here itself is that they are part time developers. Too part time.. Based on my observations, it’s very very difficult to weave a new developer with normal average skills (there geniuses, of course, but they are exceptions) into the project development if he/she randomly spends several days a month to contribute upstream. If we adjust the speed of development to make these people happy then we’ll be moving forward like turtles. I would rather work on encouraging companies to allocate full time developers explaining them all the benefits of such approach. I know, I know, it’s not easy but it seems to me that everyone is suffering from the situation when devs only work on their priorities w/o taking responsibility for the overall project quality, and then suddenly realize that the project is almost dead just because it’s not interesting to anyone else who want to use it for slightly different use cases but can’t because it’s not mature enough (and hold on with contributing for the same reason). I strongly believe this is a serious issue. It feels to me that it used to be different years ago, people weren’t afraid to be more responsible for their projects. So I agree that this is a problem but I’m not sure that making development cycles longer will solve it. Despite all I said, I’m still for 1 year cycles. The main reason for me is that it seems like we spend much time for inter cycle activities, including preparation to PTGs and summits, releasing, taking care of FFEs and emergency back ports etc. I as a developer get distracted seriously from solving technically challenging tasks. And then it’s often hard to tune back to a needed wave. But many tasks require focus during a significant period of time to be solved. Sounds a little bit fuzzy probably but it’s an issue personally for me. Maybe because I’m also trying to combine development with PTLship, but still.. Thanks Renat Akhmerov @Nokia On 14 Dec 2017, 12:02 +0700, Ed Leafe <e...@leafe.com>, wrote: > On Dec 13, 2017, at 5:44 PM, Clint Byrum <cl...@fewbar.com> wrote: > > > One thing I've always admired about Swift was how immune to the cadence > > Swift > > appears to be. > > As I've pointed out before [0], Swift is a whole 'nother thing. > > It does not have API interdependencies with anything else in OpenStack. It is > free to do things its own way on its own schedule. > > The rest of OpenStack is what Nova originally was. It was split into many > different project because of the sheer complexity of the tasks it had to > perform. But splitting it up required that we occasionally have to make sure > that we're all still working together well. > > [0] https://blog.leafe.com/on_swift/ > > > -- Ed Leafe > > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
