uPortal developers,
I'd like to consider widening the set of persons to whom UP JIRA issues
can be "assigned".
Currently that field is constrained down to a role that we also use for
other purposes. For instance, "uPortal developers" can see restricted
security-related JIRA issues. I **am not** suggesting that we widen the
set of folks who can e.g. see those issues, nor am I here suggesting
radically widening the set of committers.
Rather, I'm suggesting a technical, tactical tweak in the way JIRA is
configured for the UP project.
The current situation is goofy in that folks like Josh Helmer can do
lovely work
https://issues.jasig.org/browse/UP-4149
but cannot be the "assignee" of the issue on which they do the lovely
work. This impairs slightly giving credit where credit is due [1] and,
I think much more importantly, it makes it harder to use the issue
tracker to signal intentions. In a better workflow, Josh would take
assignment of this issue when he spiritually takes ownership of
completing it.
Part of the power of Git and distributed version control is that it
decouples ability to take tasks and do valuable work from formal
"committership". Adjusting JIRA configuration would help in taking
advantage of that looser coupling.
Kind regards,
Andrew
[1]: Though I rather think that at this point if you're looking to
assign credit, a view like this
https://github.com/Jasig/uPortal/graphs/contributors?from=2012-01-01&type=c
is more useful than anything JIRA can spit out.
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
