I will use some forum names in here, this does not mean that they agree to this or are even aware of this prior to this post. I have not spoken to any of them regarding this, I use their names for example sake and if it offends anyone who has been mentioned, please PM me I will edit and remove your names.
This is brief, not definitive. It is posted to see if there is interest. Detail can be worked out later.
The objectives are several:
A: More PB exposure.
B: Author/contributor exposure.
C: Earning a pittance.
D: Assisting PB users.
THE PLAYERS
These are the main players in the game.
* Player one manages the project - Creates and distributes the CD. There is only one player one. Someone like Andre of PureArea, for example, who has already organised the code archive.
* Player two (who is different from player one) provides the E-Commerce ability. There can be several player twos. For example, Karbon, with a proven e-retail record
=== Note: Player 1 and player(s) two should be seperate people so that there is some accountability.
* Player three is the contributor group. See below.
* Player four is the purchasers. Their role is to buy the CD.
CONTENTS OF CD
The CD should contain quality stuff. (There is quality stuff in the code archive, but not all of it would qualify here and most of it should remain as code-archive snippets.)
The content can be anything that is going to improve life for an end user and/or that will help get PB "out there".
Therefore documentation, code, tools, etc.
Where possible code, released stuff must be complete, and useful. Some suggested guidelines:
1: Only code items that create something usable "as-is" go on the CD.
. Examples:
.. Games such as Paul's LadyBird.
.. Utilities such as El_Choni's TailBite.
.. DLL's and User Libs that provide functionality, such as FloHimself's Lua
.. Tools such as GPI's jaPBe
2: Code items must include both the full source and the "binary" (exe, dll, library).
3: Sources in languages other than PB should be considered carefully before inclusion. If the item is such that inclusion is very desirable, then source must still be released, and notes on the needed compiler and method of making the binary must be provided.
4: All items nust be version-compatible, eg, if the CD is for PB 4 all code must compile under version 4, and all docs must be Version 4, and all tools work with version 4.
5: There should be a small but useful section containing code that works with the demo (no api calls, etc).
6: Docs in HTML format. Other formats such as .chm, .pdf, .doc, etc, as useful and additional to the original.
The CD should contain the demo version of PB and VisualDesigner. These count as 1 contribution, but they are mainly there so that PB gets some exposure (people buy CD for the snippets, give the disk to a friend who then buys PB, people buy the cheap CD to see and then hopefully buy PB).
The CD can contain evaluation versions of acceptable saleable tools, but only where there is space after all other contributions are there. And the contributors of evaluation versions should pay for the exposure. See below.
COSTINGS AND REWARDS
The CD is sold.
The cost of the CD must cover the e-commerce provider costs and the distributor/manager costs, plus have a buffer for error and profit.
The minimal cost of the CD will therefore be the cost of a (decent) CD, plus the cost of the most expensive postage/delivery from source to destination (anywhere in the reachable world) plus a buffer.
The buffer covers things like a percentage of bad-burns, returned CDS, etc. This should be factored in for voth Manager/distributor and for eCommerce "shops".
The Price of the CD is higher than the cost, and includes a margin for rewards. Rewards are split between Manager/Distributor (main), eCommerce "shops" (secondary), and Contributors.
Price and cost are fixed, so regardless of which "shop" has the CD as a product, the price is X.ZZ whatevers.
Rewards are suggested. This is to keep contributors/authors on side and motivated to keep their contributions up to date with PB releases.
All contributors get 1 share of the rewards per acceptable contribution (regardless of size of the contribution).
A contribution is considered to be something that stands alone, in or of it's own right. For example, a small app, a DLL, a document, a tool. Dependencies do not count.
All contributors must agree that if they cannot upgrade the code for the next version release of PB/CD then someone else can do it, and that someone gets the associated rewards.
When contributor share points reach a certain level, they are paid.
Contributors who do not want payment can nominate that it goes to PB or the distributor/manager, or can take it and give it to their favourite charity. But to avoid unpleasantness, there should be a payment made.
Evaluation software - contributors providing evaluation items with a view to making a sale later should make a payment equal to 1 or more CDs (to be decided) and these payments are considered CD sales for purposes of distribution of funds. Also evaluation software should be pertinent. An editor/designer for PB is, an MP player usable anywhere is not.
Finally
My bias here is Windows and English, but obviously as this would be a team effort my bias don't count.
My contribution would probably be to buy a CD, and if I ever release any code that qualifies, it would go on the CD. Don't hold your breath on this, the man is willing but the brain is weak.
I say the above as I would dearly love to see something like this happen, but for and by the community and not for and by someone who intends to make it a personal gain (although that would ensure someone who was dedicated to making it work!). Where there is gain for effort (eg management/distribution) I think it should go to people who made the effort in the past, eg the sites that hosted code, etc.
