I'm pleased to see folks have started to use our Jira to report real issues. This is a good way to work: it meets the basic Apache criteria of being open and inclusive. If much (even most) of Milagro ends up happening in or through Jira, that's OK. At a simple level, I've been wondering if we should introduce additional components in Jira for non-repo-specific topics such as "protocol", "docs" and "tests", but I figure that kind of thing can be done any time on-demand.
I've also had some off-list communications about Jira, from which I infer project members are interested in using advanced features for purposes perhaps deeper than simple issue management. Today I've been looking at Atlassian's docs and at Apache's Jira administration pages. Before giving further consideration to this, can I put it to the list: what would folks like to see from Jira over and above managing the workflow from reporting to resolving an issue? Are there Jira capabilities available elsewhere that people are missing at Apache? Also, is there any appetite for assigning primary responsibility for particular components to individual team members? This can sometimes help avoid issues languishing unattended, but only works if willing component maintainers step up. -- Nick Kew
