Mark & All,

On 8/16/2012 4:07 PM, Mark H. Wood wrote:
>
> So, how do we get to a state in which, while many people see a
> successful vote and think, "I could take care of that," it's highly
> likely that one person sees it and thinks, "merging that is my
> responsibility"?  How can we automatically distinguish someone who
> "should" handle the merge?
>
> We can still recognize that no one has done the merge after a day or
> two, and just take care of it, but we need a way to make this case
> unusual.
>
> Github has the concept of a request being assigned to someone.  Can we
> make use of that somehow?  How would requests be assigned?

The more I think about this, the more I wonder why we aren't just using 
JIRA for this.

Again, we're currently working under the model that new submissions 
require a JIRA ticket (whether or not they are a Pull Request).  Whoever 
is assigned that JIRA ticket is taking the "lead" on that submission. 
The Committer who is assigned the JIRA ticket should be the one who is 
committing/merging the changes.

If the JIRA ticket is unassigned, then we need to get a volunteer, 
obviously.

So, by those rules, here's who is expected to merge those pull requests:

#64 - XOAI = DS-1202 -> Assigned to no one (needs volunteer!)
#43 - Advanced Embargo -> Already merged by Mark Diggory
#45 - Discovery Enhancements = DS-1229 -> Assigned to KevinVdV
#41 - Salt Password AuthN = DS-861 -> Assigned to Mark Wood

So, essentially, we just need one volunteer to tackle merging of XOAI.

- Tim

------------------------------------------------------------------------------
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

Reply via email to