Update 'Tech to do list'
parent
0051482a97
commit
e7f60e6b1d
|
@ -3,21 +3,29 @@
|
|||
## Requirements
|
||||
**[Can we list what the key behaviours of the system should be. In part I want to be certain that a wiki is the most suitable candidate - the initial list here was taken from the end of the previous version of this document]**
|
||||
|
||||
- We need structure and workflow
|
||||
– the 3 way split with sliders **[link please]**
|
||||
- We need drag and drop UX to build this structure and workflow out of democracy “objects”
|
||||
Function:
|
||||
- “objects” voting/consensus process/decisions
|
||||
- We need activity streams of any “object” and “action”
|
||||
- Flagging is built from the existing “objects”
|
||||
- We need “security” workflow/check “objects”
|
||||
- Lottery code (random numbers)
|
||||
- Mersene twister is probably fine
|
||||
- The groups have membership
|
||||
- when a group is set up, default templates are provided (e.g. a set of "skeleton" wiki pages)
|
||||
- Groups
|
||||
- membership
|
||||
- **[can one account belong to many groups?]**
|
||||
- when first set up, default templates are provided (e.g. a set of "skeleton" wiki pages)
|
||||
|
||||
UI/X:
|
||||
- We need structure and workflow
|
||||
– the 3 way split with sliders **[link please]**
|
||||
- We need drag and drop
|
||||
- to build this structure and workflow out of democracy “objects”
|
||||
|
||||
### Definitions
|
||||
**[Feel free to link to other pages if the content is already elsewhere]**
|
||||
|
||||
- `Object`: ...
|
||||
- `Action`: ...
|
||||
- `Flagging`: ...
|
||||
- ...
|
||||
|
||||
|
|
Loading…
Reference in New Issue