Of course using a project 'machine_name' as a namespace will help. What I figure out first is which of the modules, install profiles, themes (and makefiles) I will release to the public (github, drupal.org, etc). The ones I will release get generic names, while the other ones get PROJECTNAME_short_description as a name. 

For a hacker community project I am developing, the generic zen sub-theme I developed is called 'Conway', while the actual theme (using Conway as a base theme) is called 'hacker_theme'. Same goes for hacker_event_feature, hacker_install_profile, hacker_distro (a kit-compliant distribution specific feature, equivalent to the projectname_tweaks module I see everywhere).

Best practice for avoiding module / theme / profile name clashes?
I have sp application where there are 15 subsite.I need to redirect each subsite to the respective logout page when i click logout.How do i achieve this &amp; properly logout each respective subsite? 
