compostproject-devel Mailing List for COMPOST

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Howdy,

Here's my vision of the project (at the moment): (I apologize for its 
convoluted nature)

It should support a wide variety of co-operatives -- be it what Ueli and I 
discussed over in CopCor, what you guys have been discussing in your group, 
a traditional co-op, or any other breed which may come along.

How can we do this? I suggest a hierarchy -- you group shares together based 
on the entity (an individual or a group of shares).  Here's an example:

Level 1:
100% - CopCor Trading

Level 2:
150 shares - Peter
100 shares - Cory
50 shares - Engelbert

or

Level 1:
10% - Savings
80% - Dividends to members
10% - Dividends to employees

Level 2a (Savings):
100% - To savings account

Level 2b (Members):
9 shares - Mr. A
8 shares - Mrs. B
6 shares - Mr. O
...

Level 2c (Employees):
23 shares - Engelbert
21 shares - John
...

>Do we want to build in automated systems for things like taxes?

Taxes could be taken care of by adding "taxes" on level 1...

>I have a system that I've discussed out with a couple of people, but it's 
>pretty radically
>different, so I hestiate to bring it forward.  I look forward to seeing 
>what notes you have
>already.

What are your "radical" ideas? I want to make sure they could fit in here 
too!

So when you create the level 1 groups/categories, you define the type of 
system that applies to on level 2, and what operations are allowed on that 
level... that way we can develop different operations for trading, or 
whatever -- but still remain flexible enough to tackle anything (since you 
can always add another system to the list)

>For example, do we want a finite number of shares that get subdivided into 
>smaller shares, or do we just want to be able to add more to a pool?

Allow both!

...and taking a step back, we need a log-in system, and some sort of 
wiki-type recording system for storing all transactions/changes.

We'll also need an accounting system -- to keep track of transactions 
between the co-op and the members -- so if the co-op pays out the monthly 
surplus (in $$, bottle caps, whatever), the members each keep a balance.  
The accounting system should allow trades directly between members too -- so 
they can trade 100 m^3 of H2 for USD$100 if wanted...

----

Here my previous work that just outlined some of the features the trading 
component would need:

Work Entries
- Input hours worked, including both a brief and complete description
- Modify existing work entries
- Delete work entries
- View all work entries
- Search work entries
- request comments/veto work entries

Trades
- Add new trades (suggest a trade)
- Accept an offer of trade
- Reject an offer of trade
- Counter-offer a trade (implemented by automatically rejecting the initial 
offer and creating a new offer)

Summaries
- Generate a summary report of the RCC ownership (weekly, monthly, 
...whatever)

Misc
- Veto power is restricted to users who have traded in "x" months. (however, 
all users can comment)
A veto blocks approvals, and causes the entries in question to not be 
included in the ownership totals.

Overall
- Record every transaction that occurs (just like wiki, we can see what 
other users have done, and correct tampering)

----

And a preliminary database structure (incomplete):

Tables

A prefix should be used for all of our tables; something representative of 
our name...
Flags
notes:
Contains records meant to flag trade and hour submissions
Can be used to veto a trade, request comments, and ask people involved in 
the trade to elaborate (anything else?)
fields:
Flag_ID: Unique Identifier
Flag_Type: The type of flag this refers to (values: V=veto, C=comment, ...)
Flag_RecordType: What type of record is this flagging? (values: T=trade, 
W=work, ...)
Flag_RecordID: The ID of the record being flagged
Flag_Title: Brief title of the flag
Flag_Text: Further explanation and description of the flag
Flag_UID: User ID of the person who created the flag

Trade_Summaries
notes:
records are generated in this table each time the number of shares in the 
RCC is calculated
a single record containing all the totals is generated in this table
fields:
...

Trade_Summaries_Data
notes:
multiple records are generated in this table for each single record 
generated in Trade_Summaries
each record will contain the data on each RCC member (# hours, % ownership)
fields:
...

Trades
notes:
...
fields:
Trade_ID: Unique identifier for this record
Trade_Date: Date the trade was proposed on
Trade_UID1: User ID of the user proposing the trade
Trade_WID1: Work log ID of the first work log entry (block of hours this 
quantity of hours is being deducted from)
Trade_Quantity1: integer or decimal value
Trade_Unit1: ID of the Unit in the Units table (below)
Trade_UID2: User ID of the user being proposed to
Trade_WID2: Work log ID of the second work log entry
Trade_Quantity2: integer or decimal value
Trade_Unit2: ID of the Unit in the Units table (below)
Trade_Approved: true/false, approved if user #2 decides to accept the trade
Trade_Rejected: true/false, rejected if user #2 decides not to accept the 
trade
Trade_Locked: true/false, locked if the trade has been finalized and no 
future changes should occur

Units
notes:
This table is a list of different units which may be used in data entry
fields:
Unit_ID: Unique identifier for this record
Unit_Name: Name of the unit (for example: Hour(s), USD, cubic meter(s) of 
hydrogen, etc)

Users
notes:
Use the existing postnuke users table to identify each user (user ID).
fields: (of interest to us)
full name
user id
email address

Work_Log (need a better name for this table...)
notes:
We could have a single date, or two dates (for start and end date)... any 
thoughts?
fields:
W_ID: Unique identifier for this record
W_Date
W_UID1: User ID
W_Quantity: integer or decimal value
W_Unit: ID of the Unit in the Units table
W_Title: Title of the work
W_Desc: Full Description of the work

Cheers,
Cory.

_________________________________________________________________
Take advantage of powerful junk e-mail filters built on patented Microsoft® 
SmartScreen Technology. 
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines 
  Start enjoying all the benefits of MSN® Premium right now and get the 
first two months FREE*.

compostproject-devel Mailing List for COMPOST

compostproject-devel — Developer's Discussion List