| Latest revision |
Your text |
| Line 1: |
Line 1: |
| :Move out to [https://docs.google.com/document/d/1lUsVOfUNmRLyzJs1N1tGd5D9gJMQ3a9N5KrLsrNe2I4/edit# Google doc] when a section is ready
| | -- |
| | |
| ==Units==
| |
| Newly created Units have a status 'Under review' and the site admin review them. The status then changes to 'Approved' if approved. If not approved, the status changes to 'Not approved'.
| |
| | |
| ==Tasks==
| |
| ;Bid Selection and Task completion evaluation
| |
| These two actions can be done by the Admin or users with the 'Task Management' right which can be applied for once they have a minimum number of activity points and account age. To help them choose, the system highlights the best bids according to skills matched and experience/ previously earned ratings in those skills. Users of the site can also vote for the best bids and those votes can be used as an assist to help the Admins and Task admins choose the best bid (note that users cant select a bid by themselves using the votes)
| |
| | |
| ===Old Status===
| |
| * Editable (1)
| |
| * Waiting for Approval (2)
| |
| * Open for Bidding (3)
| |
| * Bid Selection (4)
| |
| * Assigned (5)
| |
| * In Progress (6)
| |
| * Work Evaluation (7)
| |
| * Completed (8)
| |
| * Cancelled (9)
| |
| | |
| | |
| ===New Status===
| |
| * Draft (deliverables, milestones)
| |
| * Waiting for Approval (from users with 'Task Management' right)
| |
| * Open for Bidding (users bid on it; When there's 1 bid on it, a timer of 10 days starts)
| |
| * Biding Closed (system auto-closes it). Task Management is now reviewing the bids and they select the winning bidder.
| |
| * Assigned (now the bidder has to accept the task; If not accepted, Task management can set it back to Bidding closed or Open for Bidding, depending on what they think is appropriate)
| |
| * In Progress (if the bidder accepted the task; and now they're working on it)
| |
| * 'Completed (Under Evaluation)' - this status is set by the bidder - Task Management will come and review it
| |
| * 'Completed' - Status set is the work is accepted by Task Management and then the funds are released
| |
| | |
| ;Options for the 'Approval' status:
| |
| | |
| 1. Original: If one editor sets it to 'Approval', all current editors of the task need to set its status to 'Approval' as well and if they dont do it, its approved after 7 days.
| |
| | |
| New: <--
| |
| | |
| 2. One editor. Sets it to "Evaluation" (a decision). If another user edits the Task, the status is set back to Draft. 'Task Management' user or Admin approves it for Bidding.
| |
| | |
| 3. Multiple editors ..They discuss. One of them sets it to Eval. Any other user can "support" that decision.
| |
| | |
| 'Decisions' table
| |
| | |
| ==Active Users==
| |
| Each Unit has statistics based on active users, who have logged in or performed an activity within the last 7 days. Activity is also tracked on a 30 day basis. A list of users who were active and the actions they performed within the last 7 or 30 days is maintained.
| |
| | |
| ==Types of Decisions made on the website==
| |
| All decisions should be made with consensus. If there are not enough users to achieve consensus, the site admin can make the decision based on the information available (again comments need to be considered). All 'oppose' decisions require a comment (for example 30 chars minimum). Types of decisions include:
| |
| * Task Approval (status change from 'Draft' to 'Open for Bidding')
| |
| ===Conditions for Decision Making ===
| |
| The following talk about a task being approved but these mechanisms apply to other decisions as well.
| |
| * If a user created the Unit and they're the only active user (within the last week), they'll have the power to approve a task
| |
| * If a user created the unit and there's another active user, the unit creator's votes carry more weight (to help reach consensus)
| |
| * If the Unit creator is not available and there are other task editors working on the task, the System Admin can approve it as well.
| |
| * If there are three or more active users, the voting is done by 2/3rd majority
| |
| | |
| ==Intro==
| |
| The goal is to create a project management system with some unique features. There are some core components of this website such as: Ob, Tasks, Issues, Ideas
| |
| | |
| Ideas and Issues → (are converted to) Tasks (or Objectives if it will be more than one task). Task is a single unit of work that can be completed
| |
|
| |
|
| ==Issues== | | ==Issues== |
| Status: | | Status: |
| * Under Review --> Open --> Resolved (under review when a new issue is created; Users change to 'Open' if the issue is valid/verified; Resolved when associated tasks have been completed) | | * Under Review --> Open --> Resolved |
| ** Instead of Open, we can also vote for Duplicate / Unverifiable | | ** Instead of Open, we can also vote for Duplicate / Unverifiable |
|
| |
|
| Issues are Auto archived after 30 days of being in Resolved/ Duplicate / Unverifiable | | Issues are Auto archived after 30 days of being in Resolved/ Duplicate / Unverifiable |
|
| |
| ===Issue Types===
| |
| Each Unit has an interface for customizing Issue Types.
| |
|
| |
|
| |
| ==Saved Text for later reference==
| |
| ;Possible Status for a Task:
| |
| * Editing, Editable, Draft
| |
| * Definition, Defining
| |
| * Under review, Open, In-work, Pending
| |
|
| |
| ==Units for==
| |
| The following items need a Unit for themselves
| |
| - a City: duplicates all the things the Mayor's office does (city council, issues, everything etc.) -- this completes the City aspect of government. Need to see about State, National and International
| |
| - a specific product
| |
| - a specific service
| |