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
What is the purpose? If you want to see other users, you can extend UsersController. Or do you want to see other persons stuff? You're right. I'll use the users controller. What if I put nested routes for actions, projects and contexts under users? What I'm thinking is that /users should show the other users and perhaps a sampling of public actions, then you can click through to the user and the actions, projects, etc. The purpose is to be able to discover other people's stuff. I'd suggest to make specific views for other users in the respective todo, project and context folders (controller / views). That way you can reuse a lot of the stuff that's already in there Basically, the use case I have in mind is something like chores, that you could "take off" someone. In general, though, the best way to collaborate will be to 1) create a public/shareable project and then add another person to the project. In this case the actions in the project will be shared by default and completable by anyone. So I guess there will be added shared_status, created_by, assigned_to and completed_by fields. I think you may need the ACL stuff that Nicolas was talking about with some simple roles to be able to controle the acces to the project/context/action (manager, editor, viewer) * ability to "delegate" to another user * workflow that allows the other user to "accept" or "push back" (with a message) the task I think you need to think about the screenflow for these features. How do you show a user that a todo was delegated to him. Perhaps you can combine this with the enhancement request for a way to see todos that have come from the tickler and/or the backend_api. Yeah, I was thinking as part of a messaging system: "User X wants to push an action to you. Accept?" It stays at the top of the page until you accept or decline. I think we could use a generic messaging system for events like this. Then on each action there is a right-arrow (maybe a pushing hand) for delegation. I guess that would mean more icons per action. I'd suggest a context menu or something. We could use this for other enhancement requests too (i.e. convert to project, follow-up, etc.) Thanks for the info. Btw, the recurring actions feature is totally awesome and useful for me. Thanks. It still needs some work on usability though :-) Now to find the time. Reinier
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
