Update 'Tech to do list'
parent
ded1d9a90c
commit
90cbe165ea
|
@ -1,7 +1,26 @@
|
|||
Development proccess
|
||||
|
||||
1. Choose a well maintaqined open source wiki to be the base of the functionality
|
||||
2. Find a team who are skilled in the languages, data storgae and frameworks used to build the chosen wiki (recute from the maintenainers initaly)
|
||||
3. Define/design the tempaltes and wiki page structure needed to support the project
|
||||
4. Define the roles required to
|
||||
|
||||
|
||||
## ideantery “objects” with admin access privileges.
|
||||
|
||||
use the roales
|
||||
|
||||
|
||||
|
||||
## group “objects” with memberships, the content of the groups is stored on a wiki (we use an off the shelf one)
|
||||
|
||||
Group
|
||||
Wiki
|
||||
member list
|
||||
|
||||
|
||||
|
||||
We need ideantery “objects” with admin access privileges.
|
||||
|
||||
We need group “objects” with memberships, the content of the groups is stored on a wiki (we use an off the shelf one)
|
||||
|
||||
We need structure and workflow – the 3 way split with sliders
|
||||
|
||||
|
|
Loading…
Reference in New Issue