[colicoid]

David Allen thinks that you should name your projects so that they state how you want something to be when its done. He says that it makes it a more positive experience to look at your projects. The problem is that I can't figure out how to do that. I tried names like "application x has zero bugs" or "documentation for X is ready" but it just felt a bit silly.
Any ideas?

I am also interested in what kind of naming conventions people add as an extra layer of organization on top of all the regular OF tricks. I for example might name actions so I can identify what action-group they belong to when I am in context-view. E.g.

Project X
action1
action2
bugs to fix
-> bug - action3
-> bug - action4

In the above example "bugs to fix" would be an action group.

Any other interesting takes on naming conventions?