I am curious as to how the manageIQ community and development team inside Red Hat do Project Mgmt / Requirements gathering for this project.
So far, I have seen some bugs and feature requests start here in the talk forum, and then migrate to github issues and then be handled there until they either go into code or the issue is closed. Also there is a trello board, which I rather like, but I have not had time yet to understand what it holds. So I guess I would say that it appears that ‘requirements’ are held in various places at various times. I know that agile and open source projects often do this different and this is fine.
I guess my real question is: how is product/project mgmt done? like priority, severity, impact, and then deciding what tasks/requirements/bugs/whatever are done by who and when - how is it decided which bugs to work on first and when they are due etc?
Does the manageIQ team have standup or weekly bug meetings of any kind? I know we did that at my last (semi) open source company, Zenoss. Are there formal product managers that interact at the community as well as product level?