Maybe i am doing something wrong so let see it. I have a vocabulary, this vocabulary have a term 'drupal', this term have a sub term 'modulos', and 'modulos' have a many sub terms. Each of the terms have one or more nodes in it.
I'm looking at producing a site for the US / UK / NZ and Aust but the data in the very simple posts will be very local down to cities and suburbs zipcodes etc. Whats a good way to separate the posts so that people see the information for the Country / City they are in (i know I can do it with views). I was hoping to use MYSITE.com/nz/ or MYSITE.com/aust/ etc for domains rather that on sub-domains. Planning on getting 10-15k users over the next 2 years across all 4 sites. I'm familiar with openlayers etc just not sure what direction to take.
I think everybody at one time or another has had to maintain hacked versions of modules (especially themes). When using SVN, the formal way of doing this is through vendor-branching. That is, you maintain a personal SVN repository, manually download each new official release and put it in your repository, and merge the changes between releases with your own hacked/patched version of the module. I was getting fairly comfortable with this process when the Great Git Migration happened :) Of course, I could continue vendor branching like nothing ever changed, but I've read so much about how Git is supposed to magically do this all semi-automatically- which sounds good to me in theory, but in practice I'm a little lost!
I understand rebasing for the most part, which seems like how one is supposed to accomplish "vendor branching" in Git. So I think I could clone the official repo to sites/all/modules/[modulename], create and checkout a "hacked" branch based on the dev branch, and then fetch and rebase the hacked branch on the dev branch whenever there are commits to the official dev branch. A couple of questions I have about this though: