We can totally set things up that way, but I'm not sure I follow the reasoning..?  The assumption I was operating under is that people running the script are looking to contribute code back to Dreamwidth, and so they need to have their own forks of the DW repositories.  If this is true, I'd rather have the script splutter and die if the user doesn't have forks of dw-*, rather than check out Dreamwidth's copies and keel over before it finishes configuring the needed remotes.

Again, I'm following the steps from the wiki:

http://wiki.dwscoalition.org/wiki/index.php/Dreamwidth_Scratch_Installation#Get_the_Dreamwidth_code

but if those can change, we can change the wiki and the script in parallel. =)