My plan which I never got around to finishing was to change the multi-user model slightly.
The idea was to slight the users model into user and lists or 'tracks'. Use roles to define a simple acl: "manager", "editor", and "viewer". Finally allow tasks/items to be transfer between lists, and some sort of combined summary viewpoint. So a user would have a primary list, could view or edit another user's list and the possibility would exist to have "shared" company or group lists. Later steps would be to define work flows on the basis of a shared list and some additional status flags. The above means changing a lot of code, (everywhere "users" used) is but the current MU model I wrote is not very flexible. I was hoping the above with only two new models and some changes to existing models would be flexible enough. I'd be interested in seeing some expanding MU functionality - I was hoping to find some time but you know how that goes. Nicholas On Sun, Aug 31, 2008 at 5:28 AM, Joseph Method <[EMAIL PROTECTED]> wrote: > Hi, I have the branch tristil on github. I haven't done anything yet except > update webrat so that the spec tests can run. I'm planning to hack on the > following features: > * an "other users" controller > * ability to make a whole project or individual todos "public" to other > users > * ability to see the visible todos/projects in the other users controller > * ability to "delegate" to another user > * workflow that allows the other user to "accept" or "push back" (with a > message) the task > > I'd like to hear what ideas other people have had wrt to these features. > I'd also like to get clear on which set of tests is preferred, the > unit/tests or the spec tests? I prefer writing specs myself, but for > autotest and TDD I'd rather use the more complete set of tests. Is anyone > coding using an autotest setup and which set are you using? >
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
