Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

I am in the "others" category. And you said in a private message during the competition that I can push when the polls are closed. So I have pushed a major updates to my program since the polls closed. I am aware that if we need to make a new poll this will be very unfair if any of us have pushed updates. I have the competition version deb still on my machine so I am willing to push it to somewhere. But pushing it to extras-devel is not acceptable as all my users would suddenly get a update that would take them back to the stone ages :) I hope removing new account votes works as the second option would be messy for everyone.

I agree here. It's not 100% right way and will get rid of some real N900 users that just stopped by and voted. But at the same time maybe the only smart and doable solution.

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

I think the votes done with account created after June, 20th should be removed from all categories, not only "Other" category.

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

I don't have any reason to believe that the same issue happened on the desktop category where I was competing on, or any other category for this matter, but I would suggest that once we have to endure this pain that we should check all the polls to avoid this issue coming back.

Also in my opinion if we end up having to open the polls again I don't think comparing newer versions would be a big issue.... we all have had the same time and we all hope the development of these applications will continue.... To be fair we may want to give everybody some time before starting the polls again so developers can have a chance to clean up their changes and prepare a stable release.

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

The reason I started this action in the "Other" thread and not any of the others (that's confusing naming) is that, through our own monitoring of voting patterns, accounts logged in on the page, and feedback, we had strong evidence that votes from dummy accounts could have affected final placings. I do not suspect the same in the other threads, which is why i have not brought this issue up in them. I am content that the final places reflected good voting in those.

Now, let's extrapolate this logically from what you are saying andy and .. i think... fcrochik. If you want to put on this restriction of only accounts before July 21st on all these other threads now, and the mods are not able to work with us on this, you will need to rerun the entire competition.

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

Ouh, I'm so sorry. My Application is in the Multimedia section and at the evening after the poll I uploaded a new version with all changes I made during the last week. I thought the feature freeze was only until the respective Vote was closed. :(

Was I to eager? :(

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

Hi,

in my opinion, asking someone to vote
for my app, even if he isn't related to maemo
is cheating. Period. (do we really need an explicit rule?)
Did it happen here?
Come on, the voting result is just rediculous.
No other category with so many votes.
No other category, where two apps collected
so many votes in the last days.
Every time qexercise came near to tweego,
tweego got some more votes. Why that? Why did
your users wait with their votes?

But I am against the two options.
First, we can not change the rules afterwards.
It wasn't forbidden to vote for new users,
so we can not exclude them now.
Second, we can not repeat the voting after
this discussion. If one or both apps loose, they can
always say, it is just because everybody think they
cheated.

As sad as it is we have to take this result.

regards
Nicolai

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

Not at all helex :) Im only replying to a point Ben made earlier, ofcourse you were welcome to update as soon as your voting had finished :) Just kinda spelling it out in "rule speak" for anyone who thought otherwise ;)

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

I think we should check all the threads and I do hope we will find that we don't need to run the polls again. If any reason is found to assume foul play I think it would better to have to poll again than not trusting the results.

If there isn't a way to check than is a different subject all together.... but in that case I would ask the competitors in each categorie if they feel the need or not and the majority will decide

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

fcrochik, when you say "check" can you make clear what exactly you want to check for in the other threads. If it's a check for votes from accounts created after July 21st then Im sure all the threads will have some new voters. We need to be more specific than that.

In the case of the "other" thread, it was not just because of new voters but because what looked like a pattern of voting from new and possibly 'fake' accounts to the extent that it could have affected the final placings.

Re: [ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all!
 

Before we rerun the poll (I think that is not a good idea).

I like this idea:
but also:
but I think rerunning the poll would be wrong.

Please calm down all, it's not the end of the world.
Decisions were made based on feedback we got. If there was no feedback we choose the best way in our opinion (think about the system of donations, no poll were made but everyone is happy).

Now we have to make the best out of it.
It is not easy because someone has decided to get an advantage, without considering the consequences for the other.

Please help us with your (constructive) opinion how to proceed.