In a time span of less than 24 hours, 3 different versions of the same map—which is not finished by the mapper in CS:S—have been posted here. I think we’re gonna have different definitions of ‘qualitatively’ and ‘do it normally’. Besides, Syoudous already detailed a ton of feedback in his post—and that probably doesn’t cover it all.
As a mapper, I have already told you that the sanest advice would be:
- Instead of porting maps, create new things.
- If you’re going to port maps, make sure they won’t get updated any time soon (or at all).
- For maps that won’t get updated any time soon, contact the mapper (if available) and ask them if it’s OK to port the map to CS:GO.
- When porting, strive to make ports that look better than their CS:S counterpart, are the same size or less and won’t cause mid-to-long-term problems. Never modify what the mapper intended any more than to ensure the map is playable on CS:GO.
- Carefully check your ports to avoid releasing 3 different versions (each of them incurring in a 74MB download if compressed) in less than 24 hours. This implies running through the map several times, both locally and on a test server, before releasing anything.
- Probably just do 1., skip steps 2 to 5.
Finally, a reminder: most remaining CS:S mappers are capable enough to port their maps themselves. If they don’t want to do it, or don’t want to do it yet, they might have some reason.