Changes between Version 16 and Version 17 of BluePrint/OccupyProjects


Ignore:
Timestamp:
02/09/13 12:48:58 (9 years ago)
Author:
Aaron Williamson
Comment:

Accepted Devin's description of the use cases

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/OccupyProjects

    v16 v17  
    77
    88== Use-Cases ==
    9 
    10 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.
    11 
    12 '''V2 - Devin and Aaron need to agree on an integration'''
    139
    1410A 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.