Thread: 2012 Coding Competition
View Single Post
kojacker is offline kojacker
2012-09-15 , 11:17
Posts: 1,086 | Thanked: 2,964 times | Joined on Jan 2010
#607
Originally Posted by frafI View Post
To clarify this: "push to the repository" means "extras-devel", "Ovi Store" (and alike) or a source code repository? I pushed some experimental stuff to the source code repository (https://gitorious.org/flatboat). Most of this is android/OS X specific and doesn't bring any new features to maemo. Do I have to setup another non-public source code repo during the competition? If this is the case, I think this rule is rather counterproductive to the aim of the competition (encourage people to develop).
Code repository should be fine, please don't make a new release with it. TBH I don't really want to get into a discussion around this frafl, as I said a page back please don't ask me! My official position is as was in the rules

There will be a feature freeze on entries during the voting stage of the competition. Please limit your code changes to bug fix only for any competition entry release during this period, and this restriction should remain until the end of the vote.
I can feel that everytime I discuss it then it weakens. What happens is that some people just ignore the rule. Which leaves me and others in a difficult situation - do we try to stop the voting to remove the entry? We most likely will not have the time again with X-Fade to re-set up the vote. Do we disqualify it after voting has been set up? A lot of people might have votes wasted, and there's a lot of people giving up their own time to try and get these things set up and running - it just messes everyone about and makes us all look amateurish. So often I'm trying to find ways to keep people in. I don't really understand why people do it - if someone has a problem with the rules then why did they enter? It's only a week or two to not to push another release so we can get the voting over and done with.

Ohh i can feel myself tumbling into the downward spiral of competition depression...

Another thing that I'm interested in, is a voting guideline: Is there anything everybody should test with every application? Should I install every application I can, or is it OK, not to test an application that does not seem to be interesting (judged by its description)? If I need a long time to figure out, how an application works, shall I regard this as a "minus point"?
It's purely up to yourself how to vote. No-one expects you to have the time to install and compare every application, if in doubt just stick to what interests you.

Finally, I'd suggest that the next coding competition (if there is one) is less restrictive towards existing applications (e.g. let them be part of their respective category). Maemo has a lot of different applications in certain categories (e.g. media players). A simple improvement to one of them could be of greater benefit, than a shiny new one and editing old code (or even foreign old code) can be a bigger challange than starting fresh with a clean concept.
Thank you for your suggestion. In previous competitions we kept upgrades within the respective categories. If you look back in this thread you'll see where we discussed this for this competition, and the initial feedback was that upgrades would not be included at all. It was then agreed to give them their own separate category. So this year's competition was changed due to feedback requesting the change. Hopefully you can bring your suggestions in the setting up phase of the next competition, if it has support then it's what the competition will do
__________________
Follow me on my neglected twitter @kojacker

Cybot950 - Control a robot with your N9/N950
SMSPetFeeder - Build a Bluetooth/SMS dog feeder with Qt, N950, and arduino
Nerf950 - Use your N9/N950 to fire a Nerf gun
 

The Following User Says Thank You to kojacker For This Useful Post: