.
This poll is to complicated and questions much to much stuff, especially with regards to lists. The only question here is whether to use hyphens or asterisk...
What's next? We can't question everything. There are certain things that can be changed, but the Hyphen List Markup Proposal never questioned the indention, it only questioned the character. I know that allot of people wrote their opinions about it, but we will never get a result if we conduct polls like this.
There has to be a simple question: Accept Hyphen List Markup Proposal as defined in the current form: YES or NO. If someone would like to add a reasoning why he rather would like to keep the old style, or how the proposal could be changed so that he would say yes, then he can use this talk page. But please make it short.
Same for all the other points...
The problem is that a consensus is impossible to reach that way.
Do you want votes? Can everybody veto a decision? or only those who participated to WMS Workshop?
I'll say again NO to Hyphen List Markup Proposal and NO to the current EscapeCharacterProposal. I've already explained what I'd like (simple escape etc.) and what I won't implement in my engine (fuzzy markup).
-- YvesPiguet, 2007-Apr-10
I agree with Yves, I'd say NO to both proposals too. It's not about which character to use, mind you -- the Hyphen List Markup Proposal make quite a few assumptions, including a particular implementation of the escape character. Besides, simply changing the character to be used doesn't really solve anything. OTOH, voting "no to hyphens" seems to imply that I'm against using hyphens for lists at all -- which is simply not true.
Then again, the poll seems to be a little complicated. Maybe we should prepare a Yet Another List Markup Proposal and vote? :) Or just choose between them:
- Creole 0.5
- Require Space After Bullet Proposal
- Hyphen List Markup Proposal + Escape Character Proposal
By the way, nobody made an Indented Nested Lists Proposal, so I guess we are safe to skip them...
-- Radomir Dopieralski, 2007-Apr-10
This poll seems way too complicated. If wiki developers can't submit their votes, something is wrong. Could you simplify this poll, so we could get a better feeling of opinions about 0.6?
-- Chuck Smith, 2007-Apr-10
If it's too simple, the result will be no. I don't know whether you object to the openness or to the use of tables. Please do whatever you want to this poll (removing columns, lines, or the page itself).
-- YvesPiguet, 2007-Apr-10
What do you mean by the result being "no". I don't object to the openness, but I object to the complexity of the poll. It's so confusing that even if we get answers, I think they will be impossible to analyze.
-- Chuck Smith, 2007-Apr-10
If we want a consensus, since I've rejected both the hyphen list and the escape character proposal (and so has Radomir), we won't get it. The only solution is to continue the discussions, but we don't know very well where we're going and when we should stop, as the withdrawal of 0.6 has shown.
The poll could have permitted us to discard proposals with strong disagreements, to accept proposals with only agreements/don't care, and to discuss the remaining ones, paying attention to arguments of people who disagreed.
-- YvesPiguet, 2007-Apr-11
I think the poll is a really great idea and nicely executed, as well! But I also feel the pain of people who want things to settle down. I would finish the poll regardless of what the consequences will be, because it will give an overview of where everyone stands. After that, there can be a discussion about what (if anything) to do about the poll results.