My apologies as I have had a busy week this week (ask me elsewhere...) and am way behind in the lengthy thread this relates to. If I'm asking a question that is already answered I apologise and request a pointer to the answer.
On Jul 11, 2008, at 00:31, John Plocher wrote: > > Putting things together for comparison: > Communities Consolidations Projects UserGroups > Makes webpages Yes Yes Yes Yes > Makes mailinglists Yes Yes Yes Yes > Publishes components No Yes No No > Makes relationships Yes Yes Yes Yes > Makes Contributers No Yes Yes Yes > Makes Projects No Yes Yes No > > What other abilities/behaviors are there that are or should be > associated with these top level groups? Why do we need to make this abstract classification? Why can we not just treat all entities as "groups" and leave them to decide for themselves which of these facilities they need? All that really seems to matter as far as I can work out is that we define a set of top- level groups that reflect the current top-level structure of the community and then leave them to self-organise using the tools offered by the web application. Those top-level entities would be things like SFW, ON, ARC, User Groups, Advocacy and so on, not abstract classifications. S.
