Robert, So I think we should explicitly leave room for experimentation and > divergence, but also encourage a single common path - don't be > different to be different, be difference because it is important in > this specific case.
First of all feature request are the same process as specs (in other projects) Difference is what we are expecting to get in spec and feature request (and auditory) By the way feature request in Rally were introduced* far far before backlogs in other Keystone and Nova.* It strange from me that those projects are reinventing working mechanism from other project=( and not just use it. Best regards, Boris Pavlovic On Thu, May 14, 2015 at 11:45 PM, Robert Collins <robe...@robertcollins.net> wrote: > On 15 May 2015 at 08:34, Jay Pipes <jaypi...@gmail.com> wrote: > > > > Hi Maish, > > > > I would support this kind of thing for projects that wish to do it, but > at > > the same time, I wouldn't want the TC to mandate all projects use this > > method of collecting feedback. Projects, IMHO, should be free to > > self-organize as they wish, including developing processes that make the > > most sense for the project team. > > I think there is a balance to be struck. Where we tell users and > operators to learn something different for every project, that has > real impact. It makes it harder to engage with us, and it makes it > harder to move between projects for contributors. > > Imagine if we had a spread of gerrit, github PR's, launchpad reviews, > gitlab PRs and bitbucket PR's - say nova, swift, barbican, keystone > and glance. That sounds silly because we all recognise the costs of > switching there: I think we need to recognise the costs for other > people even in things that as developers we don't interact with all > that much. > > So I think we should explicitly leave room for experimentation and > divergence, but also encourage a single common path - don't be > different to be different, be difference because it is important in > this specific case. > > -Rob > > > -- > Robert Collins <rbtcoll...@hp.com> > Distinguished Technologist > HP Converged Cloud > > __________________________________________________________________________ > 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
