Design the concept of an owner for projects and their builds. While this feature may be implemented over several releases, it is important to have a model in the beginning since it can be very expensive to back fit the solution later. An initial implementation may only need to help organize a peer to peer distribution of build management and notifications, with minimal enforcement of project boundaries. The model should be scalable (now or later) to the full formal concept of "user", with which comes the notion of enforceable group access - Owner/Group/Others ala unix/linux.
Setting to 'future' until we carry out planning discussions.
Some of the requirements for user types / permissions documented in https://bugzilla.yoctoproject.org/show_bug.cgi?id=9418#c10
This is duplicated elsewhere.