P2paid.org
From Katrina Help Info
| Table of contents |
MEMO FOR P2P AID NETWORK
4th November 2005
Hi All
There is a lot of frustration everywhere because NGOs and relief orgs seem to have constraints and pressures, and not to communicate effectively. We are all 'go getters' around here, used to real time communication, and working with relief that does not seem effective is driving us crazy, and making us depressed
What to do? Well, I d like to be able to send a blanket, a box of tinned soup and a tent, whre they are needed, now
Without having to wait for someone to sort out their bureocracy.
So when thinking along these lines, Angelo and I have started a project - gosh, another one!
Some ideas below, please feel free to join us and make a contribution, there are a lot of things that need to be set up/created.
Purpose
To set up a p2p aid network using available online technologies, where possible free and open source that would enable person to person transactions on the following basis need for aid is collected on the ground by relief camps needs are packetised to small chunks/units to facilitate fulfilment, and published to a website, built around oscommerce, mambo and sugar crm platforms
recipient creates account and logs a need
donors fulfil the need
recipient of relief supply issues receipt and follow up reports
We have already secured server space and a domain name, p2paid.org, we are now thinking of how the architecture should be built trying to come up with the simples, most effecive rapid prototype ever
There is a lot ot be done in the following areas
Concept developement and propagation Draw up a minimal policy statement emphasising the neutrality of the project (person to person, no polics nor religion) GUI/template design Marketing/communication (logo, outreach) Community developement (sustainable long term)
Group Mailing List
Project admins/contributors please sign up here
http://groups.google.com/group/p2paid
Current Schedule
Project Management (tools currently being set up)
- make a list of individuals/groups who should be invited to collaborate to the project (relevant contacts, peers)
seaeat team@risepak.com katrinahelp shelterfinder is
- set up wiki page, project management tool
- set up tasks and allocate them
Project admins/contributors please sign up here http://groups.google.com/group/p2paid
Unstructured notes exchanged so far
infrastructure
- implement rapid prototype (see separate spec) - write a blurb and diffuse it
Server: , org name, brief mou? policy statement?
Architecture/Model
The system should be able to create logins for end users User1 - The entity with need (individual, camp, hospital, other) username: entity administrator must be able to create/update/suspend a 'product request', with description, when request is fulfilled, should be able to issue receipt/follow up reports
User2- entity who wishes to fulfil need, must be able to receive receipt/follow up reports
Object: Need/Request class: primary (food, water, clothing, shelter) medical (medicine,counselling, tools,people), safety (hygenic products etc) Other classes attribute: unit description (example: box with food/blankets
Logistix
Method of fulfilment: direct (send box) intermediated (send payment to supplier, make list of third party?)?? other?
Dispatching route
User 2 should be able to choose from list the carrier, public mail service, courier, other to agreed collection point, where relief networks picks up and dispatches maybe one bit of workflow could require a tick when dispatch is complete carrier should give the system contact/email for tracking receipt issue should be scheduled within 48 hours of receipt of supply perishable and special handling goods should have priority codes,
Functional reqs
users must be able to create account have private information share public/group information user 1 should be able to create 'goods' description dispatching should be trackable
all transactions should be recorded for auditing purposes other
Marketing
Once the system has been tested within our team, we can publish it for everybody to use/promote it will be open to the public but she should initially rely on our communities of online volunteers (there must be hundreds of us out there now waiting to help others directly)
Make logo?
Communication
Improve on a standard GUI
Successful case studies could be published to promote the initiative
Funding
we would open a donation box on the site for people to give a penny or two to support the project
other?
TEMPORARY TEMPLATES
basic choice for templates, please express a choice! all templates design are indicative only of color scheme and fonts, actualy layout and details will be tweaked
1) http://demo.joomlahacks.com/index.php?jos_change_template=ab_deviant I LIKE THE ABOVE, BUT ITS TOO DARK, WOULD KEEP THE BLUE TO THE EXTERNAL FRAME AND THE CENTRAL PART WOULD MAKE IT LIGHT GRAY
2)http://demo.joomlahacks.com/index.php?jos_change_template=maxm0006 I LIKE THIS LAYOUT, COMPACT AND SIMPLE, MAYBE WOULD CHANGE THE COLORS TO BLUE/GRAY OR PINK/GRAY OR BLUE/PINK/GRAY
3)http://demo.joomlahacks.com/index.php?jos_change_template=wds_design
I LIKE THIS COLOR SCHEME, PINK/BLUE
4) http://demo.joomlahacks.com/index.php?jos_change_template=animal_01 RADICAL, IMPACTFUL, NOT WHAT I HAD IN MIND, BUT I LIKE IT
5)http://demo.joomlahacks.com/index.php?jos_change_template=ddj002 LIKE THIS BUT NOT WHITE BACKGROUND, LIGHT GRAY
6)http://demo.joomlahacks.com/index.php?jos_change_template=greenbiz
LIKE GREENBIZ, BUT NOT WHITE BACKGROUND, LIGHT GRAY
INTERACTION DESIGN
Mambo provides interface to os commerce module sugar crm module
user logs into mambo, mambo creates accounts - DECIDE: ONE ACCOUNT VALID FOR BOTH? OR TWO
ACCOUNTS? I THINK IF SYS NEEDS TO BE INTEGRATED, THEN IT SHOULD BE ONE ACCOUNT VALID FOR
BOTH
ACCOUNT ON OS COMMERCE - CREATE DESCRIPTION OF DEMAND ENTER 'RECIPIENT DETAILS' GENERATES EMAIL ACCOUNT (WEB BASED) ISSUES NOTIFICATION UPON FULFILMENT ALLOWS STATUS UPDATES
ACCOUNT ON SUGAR ALLOWS REPORTING,
TRACKING
OTHER FUNCTIONALITY?
THERE ARE 2 TYPES OF ACCOUNTS, RECIPIENT AND DONOR
IT IS IMPORTANT AT THIS STAGE OF SYSTEM DESIGN THAT WE MAP THE INTERACTIONS BETWEEN THESE TWO ACCOUNTS
THE DONOR ACCOUNT INTERACTS WITH THE RECIPIENT ACCOUNT AS FOLLOWS - WHEN IT BROWSES RECIPIENTS REQUESTS - WHEN IT REQUIRES MORE INFO/COMMUNICATION - WHN IT FULFILS REQUESTS -WHEN IT RECEIVES NOTIFICATION/FOLLOW UP REPORTS
ACCOUNT MANAGER OS COMMERCE
DONOR RECEIVE THE REQUEST
