Todd Millecam wrote: > Actually, it's not too late--the city council hasn't approved the sale > to broadweave--and Mstar is gonna make them an offer. The cut-off date > for the council to close with broadweave is June 30th--if you can raise > objections, and make those known to the council members, then this sale > might not go through at all. > > A lot of people have expressed concern, and at least 3/7 council members > appear to be against it. >
You have just provided a spark of hope! I have been feeling moved to act, but thought it was too late. In fact, last night I was feeling restless and specifically wondered if the City Council was meeting and if I should not go to see where the iProvo sale stood. I am amazed to see this thread this morning! That was one prompting unheeded. I would like to help put together an alternative proposal for the salvation of iProvo as a municipal service. I agree that many mistakes were made and there is a lot that the city can still do to make iProvo work, even thrive. Provo City has a great opportunity for a win-win situation here. I am puzzled as to why few seem to see the simple answers. What would any of you propose? I would like to make a list of suggestions, include names of those willing to be counted or consulted, and try to get more involved in this decision. I think that the biggest problem with iProvo so far is that it has been directed exclusively by politics rather than civics. The community at large has not participated, or been free to get involved in the governance or use of the system. For the record, I use iProvo, via MStar. I've championed iProvo from the beginning, despite a few service issues with the ISPs. The possibilities for a civic network are fantastic and 99% unrealized! I agree with most of the comments aired thus far and I am appalled at how the City has handled everything to date. Thanks for the discussion, everyone! Let's catalog our suggestions and make a difference. -- JeffreyD -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/mailman/listinfo/uug-list
