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

That is bad.

I did not add new features for scout, because I thougth only
bugfixes are allowed.
And I don't have free time in the next days to work on it :-(

nicolai

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

I agree, this is bad for those affected by it nicolai. I can only apologise to you.

The other situation is that I begin disqualifying perhaps 20 or more projects from the competition but, with no real legal grounds of doing so, that won't work :( The bug fix only restriction was only really discussed in this thread, for it to be workable it needed to have been in the wiki from before voting began. If we go the other way and push the ban on enhancements now then we have the problem of policing that (if it is not declared it could take a side by side look at the code to find it..) and everyone else who played by this rule wouldnt have a chance to update their projects. We cant force anyone who has updated to go back a version now, thats also unworkable.

I'm sorry you have been left in this sticky situation :(

On the positive side, it enables the competition to continue, most of the votes have been cast by now, and there is really only limited time left now for small updates anyway.

On the negative side, there will be those like nicolai who through no fault of his own will find himself disadvantaged. Please feel free to discuss forthcoming updates with those who ask questions in your threads if you feel that will help you gather support.

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

Yes! I support this option. ;-)

But seriously, I stick to the
"we all have won with those great applications".
So, no Problem!

regards nicolai

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

@Nicolai,
I am right with you on this one... Didn't release anything because of the rules and now can't even if I want....

Scout is great regardless!

For my application would not make much of a difference: Queen Beecon is just too far ahead and, I have to say, all my competitors are all just too good!

Congratulations to all for this competition! It is just amazing how much was produced in two months of spare time...

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

Seriously, you really are much too nice! :p:)

I have a lot of sympathy for the disqualification option ;) but that's a lot of arguing and a fight we can't win.. by opening it up, we make it even again. Unfortunately it hasn't worked out in your case and probably a few others too... but for the majority I think it's the cleanest way forward. :rolleyes:

And apologies to you too, fcrochik, and anyone else affected by the change.

If it makes you feel any better, from whats been reported back to me, most of the updated projects are kinda smaller and maybe more beginner projects. For example, projects that have been helped to move up a repository but at the same time they've re-arranged a couple of options or changed a menu due to ffeedback.. so I don't think there's anything major thats been done at all. I guess after 2 months of work, 5 days during voting isnt going to get a huge lot more done. But a change is a change.. :rolleyes:

Echo'd! There's definitely a superb and talented development community on here :) *thunderous applause to all*

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

I wrote "a change is a change.." in my last post, but perhaps I'm wrong on this. Is it possible to have a list of allowed changes to entered projects?

For example:
*Bug fixes
*Versioning changes to the project to facilitate moving up through repositories.
*UI improvements such as text size/positioning, color
*Optification fixes
*Your input.....
*
*


Not allowed:
*No new functionality/features basically..

And what i can do is I'll add the new rule to the wiki after I get your feedback, I'll PM everyone in the comp to let them know the restriction will be in place from immediate, and we'll carry on from there?

So let me know.. open up the restriction or create a new rule to lock this down for the rest of the comp?

Edit: First draft of possible PM to send out to members, please advise.. awaiting feedback on what to do next :)

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

I don't mind if a new set of rules are officially announced to every participator. So that everybody know something that should not be done. However, I want to clarify something:

1) That is restricted to software release , or also restricted to source repository? Can I add new feature to project , but not release it?

2) If (1) is yes , can I talk / promote in Maemo.org about it?

(I am not intended to do so , just want to clarify it)

3) Can I fork a project?

I am preparing to release a sub-project of PenPen. It is called as libpenpen (LGPL or BSD , not decided yet). I have done a lot of code refactor to move the vector drawing engine used in PenPen to a library. So that other developer may embed the vector drawing engine in their application. It could save their time and may develop more maemo application.

3.1) Do it count it as a new feature? But in fact , it have no any new feature to PenPen is added.

Personally speaking , I don't want to stop the development when I have the mood. But if it is restricted , I can suspend it and work on other stuff first.

3.2) Can I talk / announce it?

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

Ben thank you, this is the kind of stuff I don't know about that I need help with. So Im throwing this out to the other developers to tell me what you think. I want make this fair for you, so tell me what you need for that to happen.. we'll rescue the situation yet! :) I need something that is short enough to add to the wiki rules, that covers everything, and is easy for newbs to understand..

Personally I dont want you to stop any development, but at the same time there is a strong feeling that it should not be counted in competition entries until after the voting ends. Is there an easy way to wrap up and answer all your questions into a sentence or two.. or is that asking too much? :)

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

I think that any restrictions are pretty pointless. Given that the original rules did not specify any restrictions, and how hard they are to judge, it will be easier for all to allow the devs to update anything they wish. It's only a few days after all.

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

The voting phase of the competition is a feature freeze.
You may respond to feedback and fixup bugs but principle remember voters are basing their assumptions on your work within the development phase.

You are welcome to create branches and discuss ongoing active development and hope all the apps are expanded based on the intensive brainstorming and discussion occurring throughout the competition but hold pushing these branches to -testing repository just until the end of the period if they expand on the competition experience.