> 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.
An ambitious idea. Some questions immediately spring to mind.
> Task is owned by a Project. Project belongs to a User. User is a member of Domain.
Can Tasks have subtasks? Recursively? To an arbitrary depth?
Can Projects have subprojects? (see above)
I assume since a "User" is just an email address, a group email address would implement a "Group" at the "User" level?
In a company setting, Users (Contractors, Employees) come and go during the life of a Project. What happens to Tasks assigned to a User who leaves the (company|Domain|Project)?
Beavers are best known for their dam-building. They maintain their pond-habitat by reacting quickly to the sound of running water, and damming it up with tree branches and mud. Early ecologists believed that this dam-building was an amazing feat of architectural planning, indicative of the beaver's high intellect. This theory was tested when a recording of running water was played in a field near a beaver pond. Despite the fact that it was on dry land, the beaver covered the tape player with branches and mud.
-- Richard P.B. (1983). "Mechanisms and adaptation in the constructive behaviour of the beaver (C. fiber L.)". Acta Zoologica Fennica 174: 105–108.
A front facing camera already flips the image so that the user sees what they usually see when they look in a mirror. So one mirror would end up being right. Except when you open the camera app, the mobile site is no longer displaying the QR code.
https://github.com/direnv/direnv/wiki/Python#uv