I see three ways one could make a decently-scaling selector:
1) Make the select box only pull from those people with CVS on the same project. Pro: very small list. Con: Doesn't make sense for Drupal itself, and requires CVS module.
2) Wrapper so that if a project is also an OG node, offer a select list of all people subscribed to that OG only. Pro: integrates with other modules, very configurable; Con: Useless for drupal.org.
3) Replace the select box with an auto-complete field. Pro: Infinite scaling, useful for Drupal.org, well-established mechanism. Con: Doesn't auto-suggest as well as a select box.
I think #3 is the way to go for Drupal.org itself, possibly combined with a role restriction. For your use case, a site-specific patch for any of the above would probably work. (I likely will need #2 at some point, but #3 would work as well.)
Happy coding. :-)
--Larry Garfield
On Wed, 26 Mar 2008 09:26:12 -0500, "Tony Yarusso" tonyyarusso@gmail.com wrote:
I talked to some people a couple of months ago about this, and wanted to follow up on the status. I'm using the Project and Project Issue modules, and need a way for a user of a particular role to assign those tasks to users other than themself. I know people were debating a bunch of different approaches, and the key problem seemed to be that it still needed to be usable on a large site like drupal.org. While that's a valid concern, I personally only need it functional for a few dozen users for the moment, so if it's only partway there that's okay. Could someone make a recommendation for how I should proceed?
-- Tony Yarusso http://tonyyarusso.com/