of knowledge about what it was supposed to do.
I produced a patch to make aulawiki-1.6 work on tw-2.2 without ever knowing what aulawiki-1.5 was doing in tw 1.9
So I would like to point a few major doubts I've been carrying with
me for a while, probably common to anyone trying to evaluate workspaces for any project
1) How can 'teacher' create a GrupoC?
Can he be limited to create GrupoC only of predefined
types? Be/become automatically admin of 'GrupoC'?
Should having object perms 'p_admin_workspace' on a
workspace allow you to to assign perms to all WS resources?
And also to all/certain child workspaces'?
3) is 'Owner' a special role that has not to be deleted and how
can one replicate its role setup? Has it to do with
'Portfolio'and 'Personal' WS types and how can be replicated?
4) workspace_resources module
Was the 'New Category' button in the admin bar intended to
create a child workspace?
Why are child workspaces listed as categories and can be
deleted as categories?
Sure new ones will come in mind.
Then, as a developer, I'd like to ask you links to any docu, mailing
lists periods, whatever to search about discussions held at the
design of workspaces and its features
Last wiki comments