Changes between Version 2 and Version 3 of BluePrint/OccupyProjects

Timestamp:

02/08/13 20:49:28 (12 years ago)

Author:

devin

Comment:

I added a "second version" of these blueprints to the wiki, incorporating what was published in this conversation ref: ​https://groups.google.com/d/msg/sahana-eden/-gVIf4R8IcA/wSVrBcYsdaUJ Aaron and I should get together to discuss integration.

BluePrint/OccupyProjects

@@ -9 +9 @@
 
 A project team member would create a new project and associated activities. They would create tasks for services they need, assigned to the people who lead those services (tech, volunteers, funding, etc.). Activity/project info would be publicly accessible to people interested in volunteering on specific activities. Project team members could view information about all ongoing and planned projects.
+
+'''V2 - Devin and Aaron need to agree on an integration'''
+
+A project team member would register for the Sahana site as a "Project User" role, which would allow them to register their project in the system.  Once registered, Project Admin users can approve or reject them. Approved projects have their basic details publicly accessible via table and map views, but the rest of their information would only be accessible to project owners and project admins.  An additional tab on project profiles only viewable to project owners and admins would be a threaded comments section where those two groups could publish notes and communicate with each other.
+
+Project users have the ability to make requests for supplies, people (skils) and services from the network. Project Admins maintain a directory of "services" (new request type: services) that can be requested by projects.  Services consist of a Title, Description and General Contact Email and can be associated with a Person Entity: individual, group/team, organization.  When a project requests a service, the general contact is sent an email notification (via saved search and notification functionality).  These requests would be viewable by filtering services for type: services.
+
 
 == Requirements ==