Hi Tim,
sorry to intrude again. When any new feature (pull) comes in place, i see
myself assuming two positions:
1 - Developer (Does it work? Does it fulfill the DSpace
programming/contributions guidelines?)
2 - DSpace Instance Administrator (How interesting the feature is? Must be
included on the next release or not? Enabled by default or not?)
As so, there is a possible interest to have a larger community voting (2nd
point), have you ever considered it? Something like 2 rounds, 1st devel
team votes, then a larger community, or switched order. Keeping in mind
that only new features (not bug fixes/enhancements) requires an
Administrator vote.
On 15 August 2012 20:46, Tim Donohue <[email protected]> wrote:
> MarkW,
>
> You definitely make good points here. A few other ideas/brainstorms
> inline...
>
> On 8/15/2012 12:40 PM, Mark H. Wood wrote:
> > Well, see, I worry that the "any committer can do this" rules are what
> > has led to the current bottleneck. If anybody can do it, then it
> > easily becomes Somebody Else's Problem. Surely someone having greater
> > knowledge of <subject of the changes> than I will have something to
> say....
> >
> > My point here is that anyone may be able to do X, but we still need
> > for some specific someone to choose to do it.
>
> Yep, very good point.
>
> >
> > Just a little more structure might help. We need a way to bump along
> > requests which elicit no strong opinions. If a pull request has sat
> > without substantial objection for a week or two, I think it should be
> > explicitly accepted for the requestor to hop onto dspace-devel and
> > call for a vote. I doubt that anyone would have objected if this had
> > happened in the past, but it hasn't become part of The Way It's Done.
> > As in: "if you feel that your request is languishing without being
> > blocked by any specific issues, *please* call for a vote."
>
> +1. I think we should all be encouraged to call votes on Pull Requests /
> JIRA tickets (whether yours or someone elses) that we think are
> languishing or just need a few more eyes.
>
> I definitely agree we should encourage *anyone* to call a vote if they
> feel their work is languishing in a pull request / JIRA ticket.
>
> > Could we stand one more periodic report, on aging pull requests?
> > Would it help? Or perhaps the week's IRC moderator could open the
> > meeting with a *brief* notice: five pull requests inactive for the last
> > week, up two from last week. Github probably has some way to support
> > the data gathering.
>
> One question that keeps popping into my head is: isn't an "aging pull
> request" also an "aging JIRA ticket"? (Since we require a JIRA ticket to
> track pull requests)
>
> In other words, can we "collapse" these two queues into one queue, or
> use JIRA in ways that help us manage this better (as JIRA honestly has
> better built in reporting/tagging/filtering tools than GitHub).
>
> Some really rough ideas:
>
> * helix84 has already started tagging/labeling JIRA tickets as
> "has-pull-request" if they have a corresponding Pull Request [1]. We
> could all keep this initiative going & make this a
> requirement/recommendation.
>
> * JIRA has voting built in. We could start actually using it (even on a
> trial basis) and ask the Community to also use it. (As in: "Is a
> specific feature/bug fix important to you? Add your vote in JIRA & the
> Committers will do our best to prioritize the highest vote-getters") It
> could provide a way for popular tickets (and perhaps corresponding Pull
> Requests) to become known [2]. We could even use this as a way to
> 'fast-track' particular tickets / Pull Requests (e.g. things that bubble
> up get higher priority in IRC mtgs)
>
> * I say all this realizing we also have a JIRA queue problem which we do
> need to tackle (just a lot of tickets that still need
> review/volunteers). But, encouraging the broader Community to help us
> *rank* these tickets by voting could help us to prioritize.
>
> Again, the ideas are rough. Just wanted to write up what is bouncing
> around in my head. Feedback or alternatives are more than welcome!
>
> I think we are all in agreement that we want to find ways to
> discuss/approve/reject Pull Requests & JIRA tickets more rapidly. We may
> just want to try a few options and see what seems to work.
>
> - Tim
>
>
> [1] JIRA tickets tagged 'has-pull-request':
>
> https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%3DDSpace+AND+labels%3Dhas-pull-request
>
> [2] All Unresolved tickets sorted by # of votes :
>
> https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project%3DDSpace+AND+resolution%3DUnresolved+ORDER+BY+votes
>
>
>
>
>
> >
> > For my part, I need to be less timid about diving into places in
> > DSpace where I have a lot to learn, in the hope of being able to give
> > a useful review of something outside my usual areas of interest.
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >
> >
> >
> > _______________________________________________
> > Dspace-commit mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/dspace-commit
> >
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Dspace-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>
--
Thanks,
DSpace Department
*Lyncode*: Official
website<http://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2F&sa=D&sntz=1&usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ>
[image: Follow us on
Facebook]<http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q>
<http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
