I agree. I think this is the best solution given the situation. I can change the landing page site (that will be going live soon) to point to 'cloudstack.usp.br'.
I think doing url redirect from br.cloudstackcollab.org is pointless and having a cname type will cause confusion because your site links and description will refer to cloudstack.usp.br. so what we could do is send directly to cloudstack.usp.br from the main collab event link. In this case br.cloudstackcollab.org will not be used.
The domain we choose to use here was cloudstack.usp.br. I think it is pretty OK to set the DNS to it.
I recommend that the Apache CloudStack PMC/Marketing team assign some internal folks with posting/publishing credentials to minimize possible delays.
I'm traveling tomorrow and don't want to cause any slippage in timeframe as a result. I'd love to have a backup here, please.
The same can be used for events, with "Downloads and Documentation" changed to "Event Details" or something along those lines.
Do we have press release template for events has we have for all the release of CloudStack we do?