we're working on a marketplace where developers can sell/give stuff away.
Some thoughts for your consideration ...
There will be a shopping cart, you will be able to put stuff from many different folk in your cart, and purchase with just one credit card transaction. As a developer, you will get a balance in an account here on the c5 site. You can cash that out via paypal (helps with international issues), or you can use that balance to buy other stuff (themes, merch, block you might want, etc) without putting more money in. Every transaction you make on our site, we're going to take a 25% fee from. 5% of that fee is going to go to a charity you can choose in your profile. You'll be able to see from your profile how much money you've donated to your favorite cause. We aknowledge that 25% is a big number, but- art galleries typically take 50%. I can't understand dotNetNuke's T&C very well, but it reads like they're taking on average 25%. More to the point, we need to make some money eventually and we see this passive revenue angle as much better for both us and you than if we were to take advantage of all the consulting gigs we're being offered. If we can generate enough revenue to pay our bills through runnign the marketplace, then it makes sense for us to spend all our time improving the marketplace, the c5 core, and answering forum questions and the like. If we have to continue to sell our time, y'all are gonna get less and less of it. ;) If the numbers above don't sit right with you, I encourage you to post here and get the debate going now. Transparancy is good.
Oh, paypal's fees are coming out of your payout as well, so it makes sense to wait until you have a balance you'd really like to use - and leave the money in the site if you plan on buying stuff..
Now that that ugliness is out of the way...
We want to keep the license structure around the end sites people get as simple as possible. Even today when you put c5 into
http://fossology.org/ you get a suprising number of sub-licenses around some of the plugins we're using like TinyMCE. We like the simplicty of the MIT license, if you're going to make something free, just make it free, but making it easy for everyone to sell stuff but also easy for clients to buy stuff is a head scratcher.
We're thinking a block, app, or even theme on c5 should be offered under 3 potential license structures.
o... FREE. Using either the MIT or creative Commons 3 license (the cc3 flavor where you have to leave a link in it)
o... Per Install. "domain" is probably the wrong word as many sites have pointers and some people use one c5 install to run multiple sites. we think people should be able to buy a block for their "instance" or "install".
o... Per developer. If you build forums for new clients every week, you're going to get frustrated with Per Install license. This is a bulk license type deal for the specific developer/business purchasing. Buy once, use many.
As someone posting something to sell on our site, you would have to choose 1, but could chose many of these. Each would get it's own downloadable file, so you could have a free version of your theme with a link to your portfolio in it, and a non-branded one for a fee.
We need to choose licenses for the Per Install and Per Developer. I'd like to pick something that has already been written both to save money and also to make it easier for everyone to know what they're getting into at a glance..
We're also going to spend some real time around flags/badges for these things. This will probably emerge over time as the library grows, but is paramount in our mind. Does this block with with that block? Is this theme ie6 friendly? You'll be able to search by this stuff, and we'll be able to group things into friendly sets easily...
Does this all make sense?
Any questions/concerns?
There's obviously a lot more under the hood we're talking about here that I didn't fit into this post, but the stuff above is happening next week so now's the time for feedback.
Either way is fine, but I think the per server deployment is the way to go, $55 for a site or $55 for a deployment that may be hosting 10 sites, or a $55 + 15 honor system per separately deployed install on a different server.