No, that would invalidate any votes already made (although I aruge they are no valid results anyway). It would need to be a different poll, not one that is revised.


>I propose that the current poll regarding renaming VFP be revised as soon as possible along the following lines:
>
>Q: Are you in favor of officially naming VFP 8.0, "Visual FoxPro for .NET"?
>
>+2: Yes, strongly favor naming VFP 8 "Visual FoxPro for .NET"
>+1: Favorably inclined, no serious objection to change
> 0: Neutral, indifferent, or undecided - don't care
>-1: Somewhat opposed but not adamant
>-2: No, strongly opposed to the proposed new name
>
>The introductory text of the current poll could stand essentially as-is. Of course the mere fact of raising such a question is inherently "biased", because it suggests the possibility of changing something.
>
>While I'm not the least bit averse to "VFP.NET", it's pretty clear from today's discussion that there is some strong opposition to that choice. However, I've heard nothing to suggest there would be such vehement distaste for "VFP for .NET", so let's cut to the chase and focus on that.
>
>Also, I think the way I've presented the possible responses deals with previous objections. This covers it, and it gives us a way to compute a meaningful overall score for the poll results.
>
>I'm in favor of changing the current poll without delay, because time is very limited. It's clear that in its present form the results could never be decisive or unambiguously interpreted. Let's make this poll worthy of running for at least a week or two, and calling people's attention to it, so we get a serious sampling of the community's feelings.
>
>For those who already expressed disapproval, please take the time to understand what is being asked, and ponder your decision. We're not talking about changing VFP, only trying to establish its relationship to .NET. Of course we can't force Microsoft to do anything, but we can reason with them, and they are reasonable. Do you seriously think the existence of "VFP for .NET" will in the slightest way tarnish .NET? Doesn't VFP have plenty to say about the ways it can work in harmony with .NET? Does the mere mention of .NET in such close association VFP make you gag? Fight that impulse - it's worth it! Think about it, folks, this is something that makes sense for both Microsoft and for the FoxPro community. This opportunity shouldn't be wasted.