Eine Antwort in diesem Thema

[Sunjammer]

My understanding from the Builder's Event  was that every Project has to be associated with a Group (not sure if this has been implemented yet and I'm holding off testing until we get the ability to delete projects).



If this is the case this may result in many projects being associated with the first group that comes to hand (that the creater is a member of).  For example, Adam Miller associated his Dreamer project with the Beta Testers group when I'm sure he views it as a personal project which he will invite people to help with. Additionally it may cause issues because the owner of the project has the ability to change it's association the owner of the group doesn't.  What happens when this happens? Do the group members lose access? What happens to projects where the owner leaves or is kicked from a group?



My idea was that every user could have an implied "Me" or "My Project" group that would be automatically generated on joining and would be the default option for any projects they create.  This would avoid the situation where they are randomly associating a project with a group, at least until such time as they are ready to invite others to work on it.



A further feature could be that users might see their own implied group as "My Projects" but if I invite people to help they might see it as "Sunjammer's Projects".



Thoughts?

[Jesse van Herk]

Sunjammer wrote...

My memory of exactly what Jesse said at the Builder's Event is hazy but the impression was that every Project would have to be associated with a Group. From what your saying either that requirement has been dropped or hasn't been implemented yet.

Projects *can* be associated with a group; the project owner is free to keep it a solo project, or create their own group(s) to handle project membership, or associate their projects with some other group.   There's not much for restrictions on it, and the system as currently built should support pretty much all of the cases you've listed above.