It might be nice if the SDM were viewed as an organizer package that uses service contracts to connect to:
1. A ticket tracker
2. A download repository
Getting the design right for this might not be easy in the given timeframe, though. The motivation of course would be to make it possible to drop in alternatives. Especially for the ticket tracker which I don't like all that much. Download's a nice package but I think communication via acs service contract makes sense in general. I think having releases live in the download package is nicer than having them live as tarballs in the SDM as is the case today.
I wouldn't worry much about CVS integration right off unless you need it right off - the existing OpenACS 3 SDM has the pieces but they need some work (speaking as someone who's been off-and-on trying to keep tarballs etc alive here at openacs.org).
