Projects currently support a Context (which really doesn't make a lot of sense since you can't do a project, only the the tasks within the project), but what projects should really have is support for setting a tag on the project that is applied to all tasks in the project.
I use tags for denoting area of responsibility and every task in the project would have the same area of responsibility.
+ 1
I do not understand the need for setting a Context for a Project. A Project is made up of a series of Tasks. Each Task should have a Context in which it should be done (email, phone, computer, etc), but given that the Project is simply the sum off all the Tasks contained within it, I don't understand how the Project itself could have a Context. I guess if it was a home improvement project and you had a Context @Home then you could apply it, but this really doesn't make sense to me. Specifically because you could have a Task "Call potential contractors to get bids" and this would be under the context of @Phone versus @Home.
I understand how some people like to have an Area of Responsibilty function so that they can seperate different area's of their life. @Folke has written about this extensively and either by using Context or Goals in Doit you can create a hack that will do that for you with Doit. However, I don't think that assigning a Context to a Project is appropriate. I do however, feel that adding Tags to projects makes sense. This will still allow those who want or need Areas of Responsibilities to Tag their projects and have the same functionality, especially if it is not the intent for Doit it to implement an Area of Responsibilities as a formal part of the App.
