On 2025-11-10 18:12:54 +0100 (+0100), Artem Goncharov wrote: [...]
Actually I would like to disagree with your conclusions: everybody should deal with "own" responsibilities and during my Keystone work I should not take care of oslo.xxx, branching, requirements, zuul, ... - there should be people dealing with those. Right now I do not have time to work on Keystone exactly because I need to take care about everything else, keeping it just "running". [...]
As others have already suggested far more eloquently than I, maybe what we need isn't people working on Keystone (and Nova, and Cinder, and Neutron, and...), but people working on *OpenStack*. I tend to agree that even if you primarily contribute to one project
On 10/11/2025 21:22, Jeremy Stanley wrote: that should not stop you contributing to other. that does not mean i believe it correct for companies to expect that they can ask you to work on any project withing openstack. that is a marital change in your employment terms if you are primary on project A and they tell you to work on project B but i do think working on other projects is good as it allow you to cross pollinate ideas and approaches form one to another. I often come back to https://governance.openstack.org/tc/reference/principles.html#openstack-firs... as well. """ OpenStack First, Project Team Second, Company Third<https://governance.openstack.org/tc/reference/principles.html#openstack-first-project-team-second-company-third> OpenStack leaders are expected to put the needs of OpenStack first in their decision making, before the needs of any individual project team. They are also expected to put the needs of their project team before the needs of the organization they work for, if any. They can of course represent the needs of their project team or their company, but in case of conflicts of interest, they should be ready to put those needs aside and make the best call for OpenStack as a whole. """ I primarily gravitate around nova/neutron/placement (and now watcher/devstack) but i will happily work on almost any part of the python services when i have time and folks as for help if it help the community and projects i am most engaged with. keystone is one of those project that if it needed help and some of my time i would try and make room to contribute, there are certainly features i would love to implement in it like moving public keys to be associated with keystone users and allowing them to be used to login. The main issue i have is i don't know what support keystone needs form contributor and i don't really want to go bring more work to the keystone team by proposing feature extra if i know they are already over burdened. I know we can collaborate on things like this at the ptg or mailing list but i feel like this is one of the things we kind of lost form the in person events. it was a lot easier to hear about initiatives and gaps in the hallway track or over a drink in the evening then in "formal" sessions or virtual cross projects as you just don't have the time to follow up with folks 1:1 or in small groups when you hear about a problem or interesting idea. But yes +1 to working on openstack if your situation allows you too not just working on a specific project. reagards sean.