y so much complications?

DrV,

Would this be someone with an idea being breadcrumbed thru breaking their idea down into concrete steps, or a 3rd party doing so on behalf of the idea creator?

How is it different (aside from lining up workers with inidividual tasks) with some sort of web based MS Project?

Does this force people into a waterfall style methodology?

What is your revenue model? (No, I don't care about the revenue model, sometime I just ask that for kicks.)

I'm extremely interested in this and have thought about the same problems. I'd love to discuss this with you in more detail. I may even be interested in joining your team on this, and believe me, I do not say that lightly.

Please PM me at your convenience if you're interested in discussing it more. Meanwhile, you're getting my 5 star vote.

I don't think creating less work is enough incentive for developers. That said, I think that there are plenty of entrepreneurial developers who might be interested in making contributions for profit-sharing.

While it's possible to create reusable models/components that are "easier" to assemble, the assembly of these components into logical modules is non-trivial.

--ooper

The idea is not to create incentive through less work. The idea is to create an interface for a community to develop from, and to provide built-in management tools. That is, take the idea, mold it into a workable design, then outsource it to the community to develop. The reimbursement for a developer's contribution is solely at the discretion of the idea owner. However, having a community of this sort would also enable developers to bid for positions, as well as visa versa. This would enable a developer to make offers to join in on the idea, and the idea owner would be able to make counter offers as well. Basically an online platform for project management and development yet with a social twist.

How do you make sure the pieces work together? And the final product works reliably under real life conditions? In my experience each programmer does things differently....

"How do you make sure the pieces work together? And the final product works reliably under real life conditions?"

Firstly, every piece is an object which has 3 requirements: Name, Arguments, Return Value. Basically the properties of a function. Every piece has its respective purpose: to take the given arguments, do some actions, and return the results.

Secondly, every project goes through a proper life-cycle. If it were a piece of software, there would be a design, development, testing, and deployment phase. Generally, a project always goes through proper testing to ensure reliability. Codesorceror is expected to have partners to provide prizes and special offers as promotional tools to beta test new projects to the masses. Codesorceror will also have a beta-tech division that is to create a community of technology enthusiasts that love emerging technologies. By joining this group you will be given exclusive exposure to the latest and greatest, have the chance to earn points to use within the CodeSorceror community, or receive special offers.

Every programmer does things slightly different. Version control has been created because of this. Therefore version control will be built into the CodeSorceror (I was thinking SVN).

And now a brief of the process:

1) Create idea. (either through CambrianHouse, MindMeister, etc.)
2) Pitch the idea to the CodeSorceror (the developer community).
The developer community leaves comments on the idea, as well as possible methods of implementation. The idea creator then selects the "accepted method of implementation" from all the suggestions (kind of the way answers.com works in picking the best answer from within the community questions). This developer then receives a certain number of points of the project. He can then use these points within the community much like Cambros.
3) Project Creation.
Once the "method of implementation" has been chosen, the CodeSorceror creates an empty project and creates categories for you to rearrange your existing idea into (categories depend on technologies chosen for implementation).
4) Project Design and Orgainization.
Once you have a rough outline of your idea, you're going to need professionals to mold it into a solid logic model(UML) so that it can be split into pieces to shop to developers. The CodeSorceror can provide you with professional solutions for a small fee, or you can take the project to the masses once again! By submitting the project to the CodeSorceror community you can either: have people bid on the project (with monetary compensation, equity stake of the company, etc), create a point value for hourly or goal completion contribution (as the design can be completed using an online interface that could keep track of user activity, time spent, etc.)
5) Code Separation and Project Development.
Once the logical model of the project design is complete, the CodeSorceror breaks down the model into pieces (each piece representing a node of the logical model). These pieces are then valued based on complexity and shopped once again to the community for development. Developers can make counter-offers or join the development team.
6) Testing.
Read above about promotional tools and viable options for beta-testing.
7) Deployment.
Once a project is deployed, the points distributed by the idea's creator are turned into stock in the company depending on how the original terms were established by the idea creator for such points.

* I am working on ways of creating an Invest! feature to provide investors an effective solution to invest in new innovative technologies and be able to easily manage and monitor these investments. Any ideas would be of help.

I love this idea...I think it would be a great model to trasition from CH... Again, this is from someone with very little technical knowledge, but an abundance of ideas.

isn't this what open-sourcing - like sourceforge --- is about? you can submit any sw idea and in an open forum get them to participate actively. there is no need to give them inventives; they already have that by their active and productive participation. complex ideas will get refactozied, naturally, into more optimal sizes by virtue of the talents that will gravitate to ideas that they find appealing.

I was going to mention SF - how does your idea differ from this?

since everyone is worried about how to be compensated why don't it just be simple such as this the "Idea owner" goes to a website submits the "need" at the same time he enters a number from 0-100% this is the amount he/she will be taking off the top for his share. and the rest is equally divided among the contributors. That is of course if it becomes profitable. There's a revenue model that is simple and can not be broke. And yes there will be some logistics, but they are worked out through the course of building. Maybe this is an idea in itself.

Mas -
SourceForge is a fantastic website...for opensource developers.
The idea behind CodeSourcing is to bring the users of SourceForge to the users of CambrianHouse for collaboration of profitable software applications (for web, phone, pc, mac, etc). One of the biggest problems with SourceForge is that the developers are mostly looking for opensource solutions to make their jobs easier. It is also not easy to ensure ownership.

threeg5 -
I like it. It will solve a lot of potential problems. I was also thinking of having a portable fund-raiser (in a similar fashion to how ideas for idea warz can be promoted) to collect "donations" for the project. This can be worked into an optional shares distribution system that can allocate a certain number of shares based on the size of the donation and total number of shares.

This is so good it's probably been done. WikiCodeSource. Yeah. But WARNING -- you have to watch out for malware going on both the site and the cusomer's.

It's a neat idea, I've seen a couple variations on this. My big concern from a project management perspective is quality of the code and security.

I've worked with teams that are made up of a lot of coders all doing small separated bits that need to be integrated. If you do not have a framework to allow all these bits to link together, you have kludge code big time. This makes your product horrid to develop in an agile manner, you get unexpected errors and breakage all the time. Tricky to get the quality problems to go away.

Security wise, I'd worry about back doors, exploits, hacks, and the like all getting built into the system if it is all farmed out in modular bits like this.

A tricky problem to figure out, the open source communities have dealt with these issues, I'd look to them for solutions.