@ronaldofs obviously you have much more experience working with CSS than I, so I accept that you don't feel comfortable with others organizations. At the moment, this organization is what feels the most comfortable to me for the reasons gabriel has already mentioned earlier, among others. Nonetheless, I don't find your arguments strong enough to make me keep using alphabetical order. For instance, the "natural language" upside you talk about doesn't feel so natural in the context of CSS. I mean, I like to see that a group of properties, which are near each other, have a similar effect on the rendered component.

About one thing you said:
"Properties are obviously related, but in practice that doesn't mean you have many of them in single selectors making that kind of organisation stand out. And why group in that order? why color after position? and inside each group how do you order the properties?"
* What's the relation/problem with single selectors and the organization proposed?
* The grouping order is not one that I made up by myself, it's the result of reading various proposals from people who have some saying about this matter. That's not a valid argument by itself, but, I actually feel that this is more natural and makes sense.
* The last question doesn't make sense, since I've put inside each group an explicit order for the most used properties in that group.

Me and Gabriel agree with this organization (mostly). Miguel is willing to try it as well as Zamith, who also has a preference for alphabetical order.
I'm not saying that this is the perfect way, I'm just proposing something I feel makes sense and that might work for a better development environment. We just need to try it out :)