Author Topic: Major feature instead of new up for NANY? (Read 37,089 times)

phitsc · « **on:** January 24, 2011, 08:01 AM »

I'm wondering if it wouldn't be a good idea to extend NANY to allow major feature updates of an existing application instead of it having to be a new one. The reason being that a major feature could require just as much time as a new app but could potentially be more useful to users than if I just come up with something tiny. I'd have no problem to let someone like mouser or Perry judge if a suggested feature qualifies for NANY or not.

Maybe we'd have to find a new definition for NANY though

mouser · « **Reply #1 on:** January 24, 2011, 08:23 AM »

i wonder if the solution to this might be to have a mid-year event celebrating the UPDATING of our apps?

phitsc · « **Reply #2 on:** January 24, 2011, 08:26 AM »

Quote from: mouser on January 24, 2011, 08:23 AM

i wonder if the solution to this might be to have a mid-year event celebrating the UPDATING of our apps?

And if I then want to bring something new mid-year?

mouser · « **Reply #3 on:** January 24, 2011, 08:51 AM »

some people are hard to please!

Renegade · « **Reply #4 on:** January 24, 2011, 11:06 AM »

Hahahaha~!

...Quarterly suits me better...

Stoic Joker · « **Reply #5 on:** January 24, 2011, 12:51 PM »

Quote from: Renegade on January 24, 2011, 11:06 AM

Hahahaha~!

...Quarterly suits me better...

Do you have any idea what a mess that would make out of the NANY (badge) icons debate..?

(hehe)

But seriously, I thought major program updates/rewrites were already allowed for NANY entries ... Yes?

phitsc · « **Reply #6 on:** January 24, 2011, 12:58 PM »

Quote from: Stoic Joker on January 24, 2011, 12:51 PM

Do you have any idea what a mess that would make out of the NANY (badge) icons debate..?

Ha, now we're getting to the point. I was *actually* wondering if I should wait with releasing that cool new FARR plugin I've been working on lately just so that my NANY icon shows a 3 instead of a 2.

skwire · « **Reply #7 on:** January 24, 2011, 05:55 PM »

I think mouser would have a fit if you withheld a FARR plugin for nearly a year.

phitsc · « **Reply #8 on:** January 24, 2011, 10:05 PM »

Quote from: skwire on January 24, 2011, 05:55 PM

I think mouser would have a fit if you withheld a FARR plugin for nearly a year.

And we don't want that, do we

mouser · « **Reply #9 on:** January 24, 2011, 11:14 PM »

Perry Mowbray · « **Reply #10 on:** January 24, 2011, 11:49 PM »

We've actually discussed previously that the New Year Celebration could / should encompass other aspects of DC's year (NANY just being one). There are lots of facets of DC that get "lost" through the year that could be helped by being repackaged at the end of the year.

Coding Snacks is one, and New Releases of existing software is another.

Where as they aren't really a NANY (more just a NA

) maybe the badge could extended to the celebration, which could include things like featured:

coding snacks
major new releases
major reviews

as well as New Apps??

timns · « **Reply #11 on:** January 25, 2011, 12:35 AM »

What is the date of DC's anniversary?

Then we could have "New Apps for Donationcoder's Anniversary" - NADA!

Ah... er... $:-\$

mouser · « **Reply #12 on:** January 25, 2011, 12:43 AM »

yeah one of the serious discussions we've had about NANY is:

Should NANY encompass any NEW apps made during the previous year.

It is somewhat illogical to think that someone who has released 10 coding snacks over the course of the year might not enter NANY just because their programs were released a month earlier as a NANY.

So one proposed change would be to say that NANY celebrates new applications released in the past year, regardless of when.

Perry Mowbray · « **Reply #13 on:** January 25, 2011, 12:45 AM »

Quote from: mouser on January 25, 2011, 12:43 AM

Should NANY encompass any NEW apps made during the previous year.

NAPY???

worstje · « **Reply #14 on:** January 25, 2011, 12:57 AM »

Quote from: mouser on January 25, 2011, 12:43 AM

Should NANY encompass any NEW apps made during the previous year.

It is somewhat illogical to think that someone who has released 10 coding snacks over the course of the year might not enter NANY just because their programs were released a month earlier as a NANY.

So one proposed change would be to say that NANY celebrates new applications released in the past year, regardless of when.

As much as I understand the logic, I say no. I have found that NANY brings DoCo together in a way that regular coding snacks do not seem to do. The IRC channel got busier (or well, at least I became a frequent visitor), people offer to help one another out, we test eachothers stuff, and so forth. In comparison coding snacks are usually a bit of a one-on-one operation with a requester who tests and the one obliging and serving the snack.

skwire · « **Reply #15 on:** January 25, 2011, 02:59 AM »

Quote from: worstje on January 25, 2011, 12:57 AM

As much as I understand the logic, I say no.

Agreed. Leave NANY as it is.

mouser · « **Reply #16 on:** January 25, 2011, 03:19 AM »

Would it really change any of the end-of-the-year NANY stuff? People would still participate in the final push for NANY apps, etc.

wraith808 · « **Reply #17 on:** January 25, 2011, 03:20 AM »

Quote from: mouser on January 25, 2011, 03:19 AM

Would it really change any of the end-of-the-year NANY stuff? People would still participate in the final push for NANY apps, etc.

I think it would. I think that NANY should be left alone, and maybe something else created- DoCo's anniversary seems like a good one, IMO.

Perry Mowbray · « **Reply #18 on:** January 25, 2011, 03:33 AM »

Quote from: mouser on January 25, 2011, 03:19 AM

Would it really change any of the end-of-the-year NANY stuff? People would still participate in the final push for NANY apps, etc.

This was sort of done this year as we opened the event mid year... and looking at the release dates:

people were releasing teasers as early as June, and about 30% had teased by end November
people were releasing final releases as early as November

We had similar worries for this year, but I think what happened was that each entrant used NANY the best way they could... those that like the end of year rush do that and those that prefer the slow build up do that (and everywhere in between). So it may not have an effect...

But personally I'd keep NANY as New Year and do something else for the Celebration / Anniversary (was it March??)

mouser · « **Reply #19 on:** January 25, 2011, 03:36 AM »

March is our anniversary month, and this year we DO need to have a new fundraiser (last one was 2 years ago); doing this yearly would also make sense.

But it doesnt make sense to have a programming event then i don't think.. Though i guess encouraging UPDATES to existing apps for march could make some sense.

Perry Mowbray · « **Reply #20 on:** January 25, 2011, 03:39 AM »

Quote from: mouser on January 25, 2011, 03:36 AM

But it doesnt make sense to have a programming event then i don't think.. Though i guess encouraging UPDATES to existing apps for march could make some sense.

You don't think that doing a wrap up of the previous year's achievements wouldn't work? for which badges could also be given??

Seems to me that reminding people of the great benefits of DC have given over the past 12 months could have lots of nice follow ons...

Edit: Agreed -- another competition wont work so close...

Deozaan · « **Reply #21 on:** January 25, 2011, 03:48 AM »

As for the original topic, I'd say that updates to existing programs don't count for NANY. All you have to do is expand NANY to New Apps for the New Year to see why.

If we started including apps made all year round or updates to existing apps, we'd definitely have to do something in addition to or instead of NANY.

Perhaps NYCE: New Year Coding Extravaganza.

Or MY DC: Mid-Year DonationCoder Challenge.

Quote from: Perry Mowbray on January 25, 2011, 03:39 AM

You don't think that doing a wrap up of the previous year's achievements wouldn't work? for which badges could also be given??

Seems to me that reminding people of the great benefits of DC have given over the past 12 months could have lots of nice follow ons...

Perhaps an annual CODY award ceremony: Coder(s) Of Da Year

mouser · « **Reply #22 on:** January 25, 2011, 04:02 AM »

rules for nany have always allowed complete REWRITES, and perhaps major new version which are more than 50% new code, as allowable nany, but not simple updates.

phitsc · « **Reply #23 on:** January 25, 2011, 06:33 AM »

Don't worry mouser. I'll release the plugin when it's done, be it NANY or not. I must learn to put personal recognition in the form of nice colourful badges aside and try to strive for inner peace instead (or something like that

).

phitsc · « **Reply #24 on:** January 25, 2011, 06:43 AM »

Quote from: Perry Mowbray on January 25, 2011, 03:39 AM

You don't think that doing a wrap up of the previous year's achievements wouldn't work? for which badges could also be given??

Seems to me that reminding people of the great benefits of DC have given over the past 12 months could have lots of nice follow ons...

Sounds like a very nice idea to me!