On Mon, 2009-11-02 at 19:36 +0200, Bjorn Tillenius wrote: > I'd say we are already dogfooding. We're dogfooding how to use project > groups. Sure, it might not be the best way of using project groups, > but > what is the best way? I though that projects within a group is usually > quite closely related, no? Thus you want the dupe finder to work > across > project groups, no? And you want to be able to create milestone across > project groups, no? I think these are issue that we should really fix, > not work around them. Or is the grand plan to get rid of project > groups > altogether?
Thanks for bring this matter up Björn. I have been thinking about this in the context of bug 58297 [Making a project part of a project group should require project group owner's approval]. I am not certain if project groups are under engineered pillars or over engineered tags. A project can be a member of many other projects, but in our model, it can have just one. For this reason, I am give this bug serious consideration; the project group is the owner of the sub project. As a pillar, the project group driver can target bugs to the sub project's milestones. I do not think most project groups use this feature since the driver role is poorly understood. Project groups seem woefully ineffective for other planning activities like creating common series and milestones. Project groups use heuristics to guess project milestones, and we prevent *all* projects from having simple milestone names so that we can improve the accuracy of the heuristics. I can search the project group bugs, blueprints, questions and FAQs, but I could do something similar with tags. I cannot create any of these objects for the project group; the user must know enough about the project groups to select the correct project. This was doomed to fail--the blueprint project is the "default" place to report bugs or ask questions. If we keep the project group as a pillar, I think we should allow objects to be created on it, milestones, bugs, FAQs, etc... But we might make better use of tags to accomplish grouping activities; their simplicity allows communities to create structures without models and restrictions. -- __Curtis C. Hovey_________ http://launchpad.net/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
