Then why not provide a 200 dollar RFP, solicit designers that love open source, and pick the best one?
You gotta realize that designing stuff takes time. This means that there's a bunch of designers working hard for a prize that will most likely not be there. This isn't like OSS contributions where patches are integrated, this is direct competition for compensation, in the form of a spec work contest.
I'm pretty sure building http://rubycommitters.org/ takes time as well and I don't believe anyone is paying Aaron to build it. In fact, it sounds like it's costing him his hard earned "love bucks".
Get over your hostility and either do something fun on the internets, or don't.
I don't think I am. I never said Aaron and the potential designers are in the same position. I was merely responding to sudont's notion that a person's time must always be compensated by an up-front, cash contract. In reality, people spend their time on many things for many different reasons.
My understanding is http://www.no-spec.com/ is a reaction to businesses exploiting designers through spec work (if that's wrong, please enlighten me). There is no one exploiting anyone here, just a developer who would like his open source, zero revenue, app to look presentable.
A designer who only opens photoshop for cash probably won't be interested, but a designer who also loves to design in their free time may.
In that way, Aaron and a potential designer may very well be similar. They don't treat their craft as a day job, but more as a lifestyle.
The poster you responded to, was suggesting that a decent designer could be matched to the project before the majority of the work takes place.
This makes sense.
If you have a competition - the amount of effort expended is far greater, and much of that combined effort will have been spent for nothing.
--
There's a commonly held assumption that design takes only a little bit of effort, and that it's so remarkably fun that little or no reward is required by its practitioners.
This assumption is wrong, and even if it wasn't .. what's the point in creating a design that stands a very good chance of not being used?
You're right that a competition isn't the most efficient solution from a total effort / end result perspective.
However, that's not what competitions are designed to provide. This isn't a corporate productivity debate.
Competitions generate excitement, stroke entrant's competitive nature, provide some openness (in cases where the public participates), and promotes more out of the box thinking.
You see it all the time with sports, the increasing number of hackathons (where yes, developers, designers, and others spend X hours building something nonstop for zero guaranteed reward), government initiatives (challenge.gov), etc.
Religiously calling all competitions/contests bad because there are some companies which exploit the characteristics of a challenge is a bit naive.
Note: I recognize that design is time intensive and not always fun. Hell, it's the same thing for developers.
i don't actually understand why this was downvoted. The point is fairly valid.
More to the oss point, if you want to really treat this in an oss sort of way, then fork the project's theme or what have you, make skinning it a sort of project people would actually give their time to rather than dangling a carrot.
I think the majority issue here is that most people don't mind giving up their time for something they care about, but most people don't like being commoditized.
You gotta realize that designing stuff takes time. This means that there's a bunch of designers working hard for a prize that will most likely not be there. This isn't like OSS contributions where patches are integrated, this is direct competition for compensation, in the form of a spec work contest.