Hosted requests

[Mike McGrath]

Generally we've been dropping the ball on hosted requests, some sitting
outstanding for several days before someone even responds.

So what is a solution?

I think we could automate the process even more then we do already, I'm
open to suggestions.

	-Mike

[Keiran Smith]

Mike McGrath wrote:
>  Generally we've been dropping the ball on hosted requests, some
> sitting
>  outstanding for several days before someone even responds.
>
>  So what is a solution?
>
>  I think we could automate the process even more then we do already, I'm
>  open to suggestions.
>
>  	-Mike
>  _______________________________________________
>  infrastructure mailing list
>  infrastructure(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/infrastructure
>
>     
hmm.. How about have it like this.
Request Submitted -> System Checks What users activity is -> Assigns job 
to user with least activity -> E-Mail is sent to the list

I think this will be an efficient way to Complete tasks much quicker.

Regards,
  Keiran Smith (Affix)

[Jorge Gallegos]

Currently there's no way to assign tickets as much as each one going to
the list and cherry-pick the requests we believe we can attend. I'd
really like to have some automated way to do this as well, but I don't
think trac has such facilities, now, I am not a trac expert, but I'll
start looking into solutions.

On Fri, 2010-01-22 at 00:15 +0000, Keiran Smith wrote:
>  Mike McGrath wrote:
>  > Generally we've been dropping the ball on hosted requests, some sitting
>  > outstanding for several days before someone even responds.
>  >
>  > So what is a solution?
>  >
>  > I think we could automate the process even more then we do already, I'm
>  > open to suggestions.
>  >
>  > 	-Mike
>  > _______________________________________________
>  > infrastructure mailing list
>  > infrastructure(a)lists.fedoraproject.org
>  > https://admin.fedoraproject.org/mailman/listinfo/infrastructure
>  >
>  >   
>  hmm.. How about have it like this.
>  Request Submitted -> System Checks What users activity is -> Assigns job 
>  to user with least activity -> E-Mail is sent to the list
>  
>  I think this will be an efficient way to Complete tasks much quicker.
>  
>  Regards,
>    Keiran Smith (Affix)
>  _______________________________________________
>  infrastructure mailing list
>  infrastructure(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/infrastructure

[Mike McGrath]

On Fri, 22 Jan 2010, Keiran Smith wrote:

>  Mike McGrath wrote:
>  > Generally we've been dropping the ball on hosted requests, some sitting
>  > outstanding for several days before someone even responds.
>  >
>  > So what is a solution?
>  >
>  > I think we could automate the process even more then we do already, I'm
>  > open to suggestions.
>  >
>  > 	-Mike
>  > _______________________________________________
>  > infrastructure mailing list
>  > infrastructure(a)lists.fedoraproject.org
>  > https://admin.fedoraproject.org/mailman/listinfo/infrastructure
>  >
>  >
>  hmm.. How about have it like this.
>  Request Submitted -> System Checks What users activity is -> Assigns job
>  to user with least activity -> E-Mail is sent to the list
>  
How do you measure 'activity'.  Some tickets require far more work then
another.  And what happens when a ticket gets assigned to someone who is
busy or away?  I'd hate to think we're causing additional work for them,
or sending tickets to a black hole.

	-Mike

>  I think this will be an efficient way to Complete tasks much
> quicker.
>

[Todd Zullinger]

Mike McGrath wrote:
>  Generally we've been dropping the ball on hosted requests, some
>  sitting outstanding for several days before someone even responds.
>
>  So what is a solution?
>
>  I think we could automate the process even more then we do already,
>  I'm open to suggestions. 
I never seem to have as much time as I'd like for things.  I did do
some work on a gitsetup script in python that can do a bit more of the
setup than the current shell script can.  I need to integrate that
with the mailman list setup script (and push my changes to allow that
script to be run non-interactively).  That might help a little, by
making the process many less steps than the host repo SOP is now, for
git at least.

Ideally, the whole process should be scripted so that all we need is
for folks to check the ticket, verify all the needed info is present,
then run a setup script.  Bonus points if we write the setup scripts
in a way that lets us re-use them to make this a web based process in
some future with flying pigs.

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Health is merely the slowest possible rate at which one can die.