1 réponse à ce sujet

[Sunjammer]

The more I use site the less the "a Project inherits it's members from the Group (or no Group)" thing is  working for me.



For example ...

• In order to work on the project an individual needs to join the parent group: this prevents me from simply inviting an individual to work on a project.  If I own the project but don't have the ability to invite people to the group I'm going to have to request the groups owner/officiers to do that for me.

• There can only be 0 or 1 parent group associated with a project: if I want to draw people from 2+ groups or 1 group and a bunch of non-members I need to set up a new group, invite everyone individually and this also has the prerequisite of being friends with them.

• If someone leaves a Project but not a Group what then?  They still have access to the all the project's resources and discussions, etc.  If there was bad blood (and lets face it half the Community will fall out with each other over the course of the next few years) project leads/members may feel exposed.

• When I want to send a message to a Project member I have to navigate to the appropriate Group (which fortunately appears in the little project summary box) and go to its members tab to find them.  It's only a couple of extra clicks but it seems unnecessary.  Even if the Group-Project relationship is unchange this could be resolved by duplicating the Member's tab from the Group in the Project.

Also a wee Group/Project feature request:

• Ability to message everyone on a Project and/or in a Group (currently the same thing).

Modifié par Sunjammer, 11 août 2009 - 11:08 .

[Jesse van Herk]

That was what we were assuming people would do, yes.



If we did split the link between groups and projects, we would lose the ability to see the list of projects that a group is involved with. Is that a reasonable loss?