News for hackers. Stuff that matters.
Re:Global Task Exchange Protocol by madospace on Saturday April 16, 2016 @12:12PM (#11511102)
So any task with `Parent-Id` will be a sub-task. If User owns the tasks he can see the subtasks tree also. but if you own the sub task alone, for you it is like a normal task with an out of scope parent.

Recursive tasks works exactly like recursive calendar events.

I have not thought about Sub-Projects, any suggestions?

User-Group - That is interesting, I think it should not change the behaviour based on the Type of email, which is difficult to determine.

When a user leaves do the same thing as email - either purge them all or re assign it to someone else.

Re:Global Task Exchange Protocol by cjp on Saturday April 16, 2016 @12:43PM (#11511234)
> So any task with `Parent-Id` will be a sub-task. If User owns the tasks he can see the subtasks tree also. but if you own the sub task alone, for you it is like a normal task with an out of scope parent.

That should work.

> Recursive tasks works exactly like recursive calendar events.

I'm not sure what a recursive calendar event is. Are you reading "recurring" instead of recursive?

> I have not thought about Sub-Projects, any suggestions?

The same `Parent-Id` solution as subtasks should also work here.

Re:Global Task Exchange Protocol by madospace on Saturday April 16, 2016 @01:03PM (#11511308)
> I'm not sure what a recursive calendar event is. Are you reading "recurring" instead of recursive?

yes! sorry i misunderstood. and now we have solution to both recurring and recursive!

> The same `Parent-Id` solution as subtasks should also work here. Yes, it will - but does it complicate the architecture ?