devsatisfaction
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
Comment only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAIAJAKALAMANAOAPAQARASATAU
1
What is the most important thing we should do to improve the OpenStack software over the next year?What is one change that would make you happier as an OpenStack Upstream developer? 
positive
negative
vote for change
vote for same
Containers
Contributors experiencing real clouds
Corporate involvementCross-projectDeveloper quantityDeveloper retentionDocsFoundation EventsGeneral Architecture
Technical Leadership
Infra/CI needs
Inter community communication
Intra community communication
Onboarding
Labor issues
Packaging/Deployment
Product refinementProduct simplifyProduct stability
Product upgradability
Pro-FeaturesPro-Fixes
Project profusion bad
Project inclusion/fewer cliques
QA simplicity
QA more like real world (not devstack)
QA more complete
Review velocityUser focusinfratcreleasecindernovaswiftinteroprefstackqadevstackhorizon
2
Open-Ended ResponseOpen-Ended Response
3
Continue to push connecting developers with operators.Less distractions from downstream work.11111111
4
Stability, stability and stability. (With the community shrinking, one of the side effects seems to be gaining more of that as there is less orgs/people insisting their cornercase new feature being on the next release.)Getting rid of these "One size fits all" artificial community goals. We had fairly tight cycle so the community goal discussion kind of slipped from us. The approach and the reasoning to move the policies to the code is pretty horrific, causes security concerns and we can't do it consistently anyways. But I guess someone had to be able to justify their position in the employing organization.22111
5
Keep focusing on good documentation.??111
6
get more developer.translator.1111
7
Loaded question! There will always be lots of things worth doing. But I suppose one pain point folks are having is in attracting folks with sufficient talent/commitment. It's easy for companies in particular to not regard open source contribution/review capability as a full-time job. Perhaps more educational/evangelical outreach around all of this?If we keep doing that singalong at the PTG, I think we'll all be just fine. :) 111111
8
Ease of skip upgradeMore structured information on what is going on/needs contribution211111
9
Go back to focusing on the developers as rockstars that actually get the stuff done that will keep openstack moving. Stop choosing stupid sessions for the Summit and focus on what is actually being done.Stop treating us like free labor to execute the things that the Telcos and Users want without context or funding for actual work.2211
10
NANA
11
Continue to iterate as has been the way for awhile now. Incremental improvements are the best way forwardMore reviews!? :-) The community is great and responsive, but it would be great to have more involvement.2111
12
Improve work / feedback loops with other communities More love for the infra team and all they do :)1111
13
Fixing bugs and removing sharp edges.Simpler setup of CI infrastructure (this might be completely impossible)21111
14
More stabilization, lowering the entry barriers -> attracting more clients, keeping up the hype -> will make the 7) more easy for me ;-) Like the simplification website mockups by Mike Perez!Getting more time for upstream work from my very own company ;-)1211111
15
Try to prevent laying off the coresI don't know111111
16
I don't know. I think you're doing great. I'm pretty happy. 21
17
Prioritize HardeningDunno1111
18
Groom more Dev and reviewers.1111
19
Actually policy in code is a pretty awesome goal already.Don't glorify the TC/Infra/Release people.11111111
20
Ask me next time - just getting acclimated to the Openstack Cinder teamI plan to help with documentation. Again I'll have a more informed opinion in March 181
21
Keep it going. :)Maybe extend the schedule to allow for better cross team meeting. 11
22
Try to make bug list looks smallPTG, it has been very helpful for discussing our plans, finalizing it and if something went wrong then we can revisit the same during summit. 111
23
ContainersMiss the summits! :)211
24
improve upgrades testingmake it working outside of devstack :-)12111
25
Get the basics right. Improve performance.This is my first PTG and I hope my company will continue funding my attending future events.1211111
26
Be responsive to bugs and operator feedbackI preferred the old model of the design summit and letting projects have a midcycle on their own. It was easier and less expensive for me121111
27
Improve and expand the user documentation.Having reviewers relax a bit and submit follow-up patches for minor issues with patches from more casual contributors. Not to lower standards, but to allow people who aren't 100% upstream to be more effective.21
28
Stay positiveBrief reports from project teams111
29
Stabilise.Nothing comes to mind.11
30
Securing more cloud resources for the CI : when its slow, this slows down our workflow.Zuul v3. A gerrit bot that would apply basic heuristics to propose people to add as reviewers of a change, e.g. based on the people that have touched the same files in the past.112111
31
Increase scalabilityOverall community gathering 111
32
Focus more on stability and less on features.More complete CI testing to reduce regressions.21111
33
No responseTwo comments about PTG&Summit co-location: 1. Back-to-back events in the same city may not be most people's first choice, but it *might* be most people's second choice and a good compromise between the old co-location and the new PTG. I don't remember if the surveys included ranked preferences, but if not, it may be useful. For people who attend only one of two events, there would be little downside, with only the upside of greater opportunity for the two audiences to interact at the overlap events. For the people who attend both (myself included), it may be a grueling and undesirable situation, but we are the minority, and at least we do save ourselves from an extra plane trip. 2. In terms of cost, it may be possible to do the PTG portion at a cheaper suburb of the summit city. It'll definitely add burden on the organizer, but it's a thought.11
34
continue forward momentum More piano bar karaoke ;) 11
35
Continuing to improve the operator experience through better deployment orchestration.N/A1111
36
A sense of discipline could be brought to how technology pieces of OpenStack evolve, overall.More, methodical training. Perhaps an online crash-course. I could then easily bring more of my team along into the upstream developer fold.21111
37
Make it simpler or at least more intuitive to deploy and use. With great power comes great complexity and we should ideally keep the power but simplify the bootstrapping and reduce the operational costs..11111
38
put it right after summit eventput ptg right after summit11
39
make it friendly to the usersfreedom121
40
On boarding more contributors and coresPTG at a fun place12111
41
ease of use, container integrationCI setup2111111
42
Improve ops toolingBan eventlet :-)121
43
Stability and performanceUnsure111
44
Containers make it prioirtyMore recognition12111
45
Keep key teams that enable development and that are losing participation going (infra/interop/refstack/QA). No idea.1111111111
46
Be open to new ideas.LOCI!112111
47
More stability, better testing, better QAIt takes to dang long to report/fix simple bugs. that's more of an issue with the OSIC disruption but it's still a major pain point.1211
48
I'm still too new to have a strong opinionSame -- still new. Haven't quite figured out what's growing pains for me and what are long term issues that I want to complain about :-)
49
N/aN/a
50
Better guidelines for updating... its very common to talk to clients using three cycles behind versionsNothing special1
51
Evolution in baremetal support.Not upstream developer.1
52
OpenStack's ContainerizationHaving more operators feedback2111
53
Get folks to focus on ease of deployment and integration with stuff outside of openstack.more defined and centralized agendas for the projects. perhaps publishing them centrally instead of having separate etherpads.121111
54
Fix RBACexpanding gerrit review comments causes the browser (at least Firefox and Chrome on Mac) to jump elsewhere on the page and then you have to scroll back to see it. Very annoying, especially if there are a lot of comments.12
55
better team organizationtimely review1211
56
continue to focus on maturity-related things like upgrades, docs, stability, gating.addition of more realistic reference deployments in gates.21111111
57
Get people to continue community wide strategic contributions, rather than focus only on company specific small contributions.Getting friends who left the community back into the community.221111
58
Improving our interaction and interoperability with container solutions.Being able to make it to more of the OpenStack Days events/help with more of the Upstream Institute training. That isn't really something you guys can fix though. ;-)21111
59
N/AN/A
60
Make it easily consumable. Stop adding new services now and drop useless services that have no reason to be in openstack.More contributors.221111111
61
Quality & robustness not sure111
62
Stablization. Easier upgradesMore dev hardware21111
63
eliminating complexityStop relying on devstack in the gate for most projects121111111
64
Focus.Simplicity.1211
65
StabilizationMore contributors2111
66
network accessibility. hotel network accesibilitypower supply
67
ease of use. more clear integration points between projects. 21111
68
Streamline projects to have one solution per technology.More events like PTG which gives developers more face to face time.12111111
69
I think Openstack should focus on stability and performance.I can discuss and contribute to Openstack software with engineer over the word.1111
70
OpenStack should elaborate container, BM, VM interoperability.A little improvement is gate infrastructure is more stable and easier to debug.21
71
deprioritize the use of devstack for more realistic customer like deploymentsseeing more of the projects check jobs with a wider variety of deployment tooks like openstack-ansible, tripleo etc.12121
72
Continue hardening the software and make sure there is plenty of consideration in the container spaceI am pretty happy111
73
Cleaning up dead projects, polishing up documentation, making sure "major" projects have enough cores.A better feedback mechanism for project developers.121111
74
Consistency across projectsConsistency121
75
Get the community closer together. SIGs and WGs need to increase and require a liason from each project. A lot of different projects are doing the same things differently and becoming inconsistent.Go back with Design Summits in the Summit and Midcycles. There will be less money spent on Travel Support for key people that have to travel 4 times a year.121111
76
......
77
Less politics.Less politics.221
78
Network connectivity :DN/A
79
More focus on the end-user experience; encouraging companies sponsoring contributors to focus more on polishing the user experience and on bug fixing, and less on new featuresLess travel to the US12111111
80
make sure projects stay healthy...111
81
Have sessions shared amongst all upstream devs to review feature proposals at the start of each cycle (to get interested people involved into it)More/Faster CI infra211
82
Have a better interproject direction.Perhaps more cores for the projects, as they are overloaded.22111
83
Clarify the packaging situation.Foundation support for remote conferencing.21
84
DebugabilityMove CI to a more stable foundation (rather than devstack and grenade)11111
85
I think all goes mh good but main challenge will be to keep the same pace in OpenStack Development. Really need to thing about keeping more contributors in OpenStack.Keeping and maintaining the same pace and same motivation. 11
86
Simplify it :)I'm happy!11111
87
Maintain stable group of developersMaybe condense to 4 days, as days 1 and 2 were light11
88
Unable to keep track of all the new projects that are spinning off at a rapid rate. Not sure I can offer a solution here yet, but how can this mushrooming be more organized or tamed?!Maybe each group can start off their sessions with a level set with a short summary of what was accomplished during the previous release. 11
89
Continue to stabilize and reduce complexity.More inclusiveness. Some projects have cliques that are hard to break into.1111111111
90
Figure out how to fit better into the evolving infrastructure choicesGet to a point where we have a stable set of people, expectations and plans.121
91
Simplify and tighter integration with K8sSlack IRC gateway for #openstack- channels21111
92
Sharper focus on the fundamental aspects of cloud operation.Moving to Zuul v3!11111
93
Stability, deployablity, and health monitoring to ensure that your cloud is running and performing well. All projects include a logger which emits performance metrics2111
94
Location isn't great. Hotel renovations and train are distracting. The overall meeting has been good. Just a bad venue. 11
95
It's more around staying relevant. Everyone's so excited about Kubernetes, but they're often forgetting that deploying it without some kind of IaaS is a really frustrating experience.So far so good! Infrastructure works well and people are helpful.111
96
Upgrades! We can't possibly handle skip upgrades until we can do lockstep upgradesFewer developers replying to with "not my project not my problem". We're all *OpenStack* developers.1211
97
We need companies to send more developers to join PTG(it's hard I know:))better equipment for video conferences:)111
98
We need to keep all the different vendors we have, and try to get more, as losing a company means losing core reviewers.Having jenkins jobs be able to finish quicker.11111
99
Have *one* strategic upstream supported deployment tool which can handle upgrades. There are many different possibilities AFAIK, which creates uncertainties to where to bet on. The missing tooling is IMO the major inhibitor to adopting OpenStack at all and keeping up with the releases once you deployed it (see the amount of releases which are still in production but have reached upstream EOL).I can only talk about Nova here. The bottleneck there is the amount of reviewers capable of reviewing and merging the changes. I sometimes have to wait for weeks until a review gets done. I have no solution to that bottleneck TBH, but it would make me happier if we could find a solution for that. This topic usually comes up at every Summit/PTG and there is no solution at the horizon.22111111111
100
Greater support for componentised deployments (subsets of services for non-compute-cloud needs).Weaker identity for specific project teams: more cross-team code contribution.211111
Loading...
Main menu