[evilDagmar]

Except that, as what happened in Nashville showed, the incumbents will take up all the available space on those poles, requiring any newcomers to wait for them to move their wires up or down a bit in order to make them ready for the newcomers to hang their wires. When these moves happen is apparently left entirely up to the incumbents discretion, as 18 months into Google Fiber attempting to deploy here about 33 poles had been touched. That's a brisk pace of two each month. So, with AT&T and Comcast left to themselves, some of Nashville will actually be ready for a new player at about the same time as we're ready to formally declare 32-bit time() functions unsafe to use.

[rayiner]

Some sort of make-ready work is unavoidable when you have shared poles. But it's not left up to the incumbents' discretion. Under current rules, existing attachers have 60 days (105 days for orders involving large numbers of poles) to move their lines. The FCC is currently considering shortening those periods, or adopting a "one-touch make ready" process that would permit the new attacher to move other companies' lines.

I don't know what's causing the hold up in Nashville. The lawsuits don't stop Google from deploying, only from relying on the city's "one-touch make ready" ordinance which would allow bypassing the FCC process. But Google deployed in Kansas City, etc. without the expedited process, so that doesn't explain the delay. And Google Fiber's deployment in newer Fiber cities like Atlanta has been slow even though they face no litigation there. I suspect it all has to do with the fact that Google Fiber only has like 1,500 employees and recently cut 10% of its workforce.