How to "stage" input from a broad community?

I manage a significant, private, closed-source software project that is
considering moving to a completely open-source forum and introducing the
software and development publicly to an open audience on the internet/web.

However, if and when source-code input starts coming from external
developers, I would like to be able to "stage" the input for review, to see
what things we want to but in the code repository (which is Subversion
based), and which things we do not.

How might my website, repo, process, and/or some other mechanisms manage
this? I assume this is a common problem that is addressed in many
open-source communities, including Subversion.

Could we exclusively accept patches?

Does Subversion and/or any other tools help automate this "staging" process?

-Matt

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 8 17:11:01 2006