[ANNOUNCE] The First N900 Coding Competition! 21st May-21st July. Open to all! - Page 50 - maemo.org

Active Topics

The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 5 hrs, 9 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 17 hrs ago
more...

Page 50 of 66

Thread Tools

	nicolai	2010-07-26 , 14:17
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#491

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

Quote & Reply |

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

kojacker	2010-07-26 , 14:23
Posts: 1,086 \| Thanked: 2,964 times \| Joined on Jan 2010	#492

Originally Posted by nicolai

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

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.

__________________
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

Last edited by kojacker; 2010-07-26 at 14:33.

Quote & Reply |

	nicolai	2010-07-26 , 14:35
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#493

Originally Posted by kojacker

... disqualifying perhaps 20 or more projects from the competition ....

Yes! I support this option. ;-)

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

regards nicolai

Quote & Reply |

The Following 5 Users Say Thank You to nicolai For This Useful Post:
casper27, Helmuth, kojacker, OVK, TomJ

	fcrochik	2010-07-26 , 14:38
	Posts: 722 \| Thanked: 1,223 times \| Joined on Apr 2010 @ USA	#494

Originally Posted by nicolai

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

@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...

__________________

My maemo work:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For Harmattan:
GeePS - native UI around google maps - GApp - access to optimized mobile "google apps".
Shutdown - shutdown and reboot with one click - QuickCall - one click call, skypeout and google voice integration using dial tones.
WakeOnLan - wake computers on your local network.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For Maemo/N900:
GApp - access to optimized mobile "google apps". - MobWebMail: browser optimized to access multiple gmail accounts
MyContacts: 75 Contacts on your desktop, ring tones per group and more - GeePS: native front-end for google maps
Macuco2 : web browser to access web sites optimized for the iphone - WakeOnLan: wake up computers on your local network
dbBrowser: Simple application to browse sqlite databases

Quote & Reply |

The Following 3 Users Say Thank You to fcrochik For This Useful Post:
Helmuth, kojacker, Maj3stic

kojacker	2010-07-26 , 14:39
Posts: 1,086 \| Thanked: 2,964 times \| Joined on Jan 2010	#495

Originally Posted by nicolai

Yes! I support this option. ;-)

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

regards nicolai

Seriously, you really are much too nice!

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.

Originally Posted by fcrochik

@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!

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..

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

Echo'd! There's definitely a superb and talented development community on here

*thunderous applause to all*

Last edited by kojacker; 2010-07-26 at 14:52.

Quote & Reply |

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

kojacker	2010-07-26 , 15:09
Posts: 1,086 \| Thanked: 2,964 times \| Joined on Jan 2010	#496

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

Hi all,

I hope you are enjoying the competition so far I wanted to send a quick note in regards to creating feature enhancements during the voting period.

I have received a few complaints that developer's have been making changes and developing new functionality to their projects. As discussed on the competition thread, the spirit of the competition was that only bug fixes would be permitted during this period of the competition. I understand that this was not made clear in the rules, and I apologise for that.

As a compromise, going forward I would like to ask that no further feature requests are implemented in your projects. There are some changes that are permitted, for example:

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

Effective immediately new features and core functionaly is prohibited. This has now been entered into the rules on the competiton wiki (*link to go here*)

I hope this information has been clear. If there are any questions, please feel free to get in contact or discuss it on the competition discussion thread.

Thanks for your understanding, and best wishes in the competition

Last edited by kojacker; 2010-07-26 at 15:30.

Quote & Reply |

	benlau	2010-07-26 , 15:34
	Posts: 135 \| Thanked: 375 times \| Joined on Mar 2010 @ Hong Kong	#497

Originally Posted by kojacker

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?

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?

__________________
Qt Ambassador | Nokia Certified Qt Specialist
PenPen SketchBook |
FrontView - 0.2 is released! | DQuest
Status: Now working on GTD software

Quote & Reply |

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

kojacker	2010-07-26 , 15:38
Posts: 1,086 \| Thanked: 2,964 times \| Joined on Jan 2010	#498

Originally Posted by benlau

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?

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?

Last edited by kojacker; 2010-07-26 at 15:43.

Quote & Reply |

hqh	2010-07-26 , 15:46
Posts: 388 \| Thanked: 842 times \| Joined on Sep 2009 @ Finland	#499

Originally Posted by kojacker

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

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.

Quote & Reply |

The Following 2 Users Say Thank You to hqh For This Useful Post:
Cue, kojacker

	lcuk	2010-07-26 , 15:51
	Posts: 1,635 \| Thanked: 1,816 times \| Joined on Apr 2008 @ Manchester, England	#500

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.

__________________
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk