On Mon, Oct 03, 2016 at 10:53:30AM -0700, John Dickinson wrote: > > > On 27 Sep 2016, at 9:21, Sean McGinnis wrote: > > > I would like to announce my candidacy for a position on the Technical > > Committee. > > > <snip> > > Sean, > > Are there some specific areas of complexity that you would like to change in > OpenStack now? How would you change them? Are there things you see happening > in OpenStack now that need to be stopped because they will produce too much > complexity? > > > --John > >
I wrote a response earlier today, but now I don't see it. Apologies if this is a second response, but rephrasing are restating never hurts to communicate ideas. ;) I think most of us are engineers. It is usually our natural tendency to over-engineer solutions. I've been down this road far too many times, and I hope I can help identify when that's happening and help steer things to a simpler solution. I will state - I am not coming in to this with a big agenda. I don't look to pull down any tents or build any coliseums. I think it's important to have a diverse mix of members on the TC. Varying view points and good arguments, as long as they are technical arguments, are import for something like the TC to be effective in making good long term decisions. As part of these discussions, I also think it's important to keep in mind what our real goals are and make sure we are not going down a certain path just because it's what's considered the "OpenStack way". We also need to make sure all voices are heard. I think we've seen many cases on the mailing list where early agreement to an idea has deterred others from expressing their doubts about it. We need to make sure we're open to other viewpoints and listening to input. We need to help make it easy for new contributors to get involved. If there are 10 steps to go through and two weeks of reading governance documents and (outdated) wiki instructions, then the only new contributors we will get are the ones being assigned to OpenStack by their employers. I'm really just rambling now. I assure you, my earlier response was much more eloquent and concise. :) Sean __________________________________________________________________________ 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