I am not certain knobs are enough. We could add bool to toggle between inclusive and exclusive behaviour. The current behaviour is inclusive where the project adds itself to the group. The exclusive behaviour would only permit adding project to the group from the group's perspective. The exclusive would used a new method on project group and the Ui might user a project picker.
I think this is a hack to address the immediate concern of forging a relationship to socially engineer an attacks.
Projects do not like the limit being a member of one project group. A project might want to be a member of python, twisted, and gnome project groups. A project might want to be a member of several of it's organisation's exclusive groups such a project that is both OEM and PES. Maybe we want to split this bug into several to address the different concerns.
I am not certain knobs are enough. We could add bool to toggle between inclusive and exclusive behaviour. The current behaviour is inclusive where the project adds itself to the group. The exclusive behaviour would only permit adding project to the group from the group's perspective. The exclusive would used a new method on project group and the Ui might user a project picker.
I think this is a hack to address the immediate concern of forging a relationship to socially engineer an attacks.
Projects do not like the limit being a member of one project group. A project might want to be a member of python, twisted, and gnome project groups. A project might want to be a member of several of it's organisation's exclusive groups such a project that is both OEM and PES. Maybe we want to split this bug into several to address the different concerns.