alex-LE / yourTinyTodo

Simple way to manage your todo list in AJAX style.
Demo Nightly Build: http://www.yourtinytodo.net/demo
GNU General Public License v3.0
64 stars 22 forks source link

limit view of comments #10

Open alex-LE opened 12 years ago

alex-LE commented 12 years ago

requested by @kilolife And please add an option to display only my own notes. As well as the ability to designate the owner of the notes of another user. And get a perfect system. I feel that we are just a few steps from it. And sorry for my bad English.

alex-LE commented 12 years ago

hey @kilolife, what is the reason for that? Do you want hide all notes created by other users? Whats about the tasks they've created?

kilolife commented 12 years ago

Imagine Bob and Mary, who work in small company. Bob does not care about concerns of Mary. Mary left a note on the memory. Using mytinytodo. Do note, which makes Mary, interfere with Bob? No. Bob and so enough of their notes. But Mary should be able to write a note to Bob.

Multi-user service involves conducting independent Todo list. But it also implies the ability to create an entry for another user. This will be a great lightweight solution for small groups. A couple of years ago I corresponded about it with Max Pozdeev. I am glad that there was a man, who continued the project. And I hope to convince you that this is a good idea - separate entries for each user. For my part I promise to be a good tester.

alex-LE commented 12 years ago

I like the idea, but i think i didn't understood it totally. Lets talk about lists, tasks and notes. So in your case, it should be possible to create list for Bob and one for Mary. Bob can see only his own list, but Mary can see (and edit) both? Or do you want to have tasks in a single list which can see only Mary? I think currently notes are just a option to enter more text about a task.

What i think we can do:

  1. Limit lists to specific users (readonly and read/write users, admin can see all lists, read/write users can create lists with or without the limitation that other users can see/edit it)
  2. Limit tasks to specific users (a read/write user can set the option to show tasks to others or not)
  3. Limit notes to specific users (a user can set a note to be visible only for some users, the other ones will not see it, only the task title)
  4. Add a comment function - it will be possible to write comments to tasks which be defined to be visible or not to other users

-> to manage this i think we should add "user groups" so that a admin can group users together

Is that the function you want?

kilolife commented 12 years ago

Imagine simple structure (for start point).

We have 3 group. Admins<-member<-other.

Admin have all rigths.

Member(Bob for exampe) have rights for:

  1. Create own list. (own - mean that this list have\include r\w right for Bob)
  2. Edit own lists. (see top)
  3. View the lists, which have read access to Bob. Through the group rights or user rights.
  4. Create list and transfer the rights (read or read\write) of them to another member(s) or group(s). For this case creator auto-assigned to read\write this list. But new owner can change this.

Other have rights for:

  1. Read list assigned for Other group.

Typical tasks of Bob (Bob in Member group):

  1. Create private list. Solution: just create list.
  2. Create reminder for group Member. Solution: a) create list, b) assign read rights to Member group.
  3. Create welcome for newbies. Solution: a) create list, b) assign read rights to Other + Member group.
  4. Create TODO list for Mary Solution: a) create list, b) assign read\write rights to Mary. (Bob auto-assigned too, Mary can change this later)
  5. Create hmm ... opinion poll for members. Solution: a) create list, b) assign read\write rights to Members group.

Typical tasks of admin.

  1. Create\modify groups.
  2. Create\modify users.
  3. Assign users to groups. (The user can belong to several groups)
  4. Add read only flag for group or user. (For create "Other" group for example, or for restrict the user.)

This simple scheme, I think, is well suited to work together with one or several working groups. If the admin to add these additional groups.

Note that the holders of rights in this scheme are the Lists. It makes no sense to restrict access to records in the list, if you have access to the list. This will be unnecessary complication of the structure.

P.S. I see the list as a sticky yellow sheet of paper with a few lines, glued to the Bob's PC monitor. :) P.P.S Sorry for bad english again :(