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?
Feature Request: "Me" or "My Projects" Group
Автор темы:
Sunjammer
, июл 18 2009 01:14
#1
Опубликовано 18 Июль 2009 - 01:14
#2
Опубликовано 18 Июль 2009 - 01:31
Not sure that is exactly correct. I have a project Tashema that isn't listed in the Projects of the Dragon Age Toolset Beta Testers group. But it does show under My Content > Projects, or if I fillter projects by "My Projects". It has no associated group.
http://social.bioware.com/project/37/
http://social.bioware.com/project/37/
#3
Опубликовано 18 Июль 2009 - 01:37
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.
#4
Опубликовано 18 Июль 2009 - 04:05
This appears to be the case which I don't think is a good idea. For instance my project of excel utilites files is under the group 'Dragon Age Beta testers'. I don't remember going out of my way to create the project in that group. This really limits who can access those files.
For things like general utilites (ie these spreadsheets) that everyone should have access to they need to be accessable to most people on this site without them having to join a group. Sunjammers idea of a 'my projects' kind of thing is a good one.
For things like general utilites (ie these spreadsheets) that everyone should have access to they need to be accessable to most people on this site without them having to join a group. Sunjammers idea of a 'my projects' kind of thing is a good one.
Сообщение изменено: Beerfish, 18 Июль 2009 - 04:08 .
#5
Опубликовано 18 Июль 2009 - 04:10
Guys, Click "Projects" top right. In the View box select "My Projects" Select the one you want, click "Edit" (top right I think) remove the associated group.
Note, if you are "in" i.e. viewing the comments or something and you create a new project inside that group, it will be automatically associated with that group. But you can select none if you want.
I just moved the "Delete me please" project out of the Builders group and into my own.
Note, if you are "in" i.e. viewing the comments or something and you create a new project inside that group, it will be automatically associated with that group. But you can select none if you want.
I just moved the "Delete me please" project out of the Builders group and into my own.
Сообщение изменено: Jassper, 18 Июль 2009 - 04:12 .
#6
Опубликовано 18 Июль 2009 - 04:21
Thanks Jassper!
#7
Опубликовано 18 Июль 2009 - 04:27
You can also edit them from the left menu "My Content > Projects"
#8
Опубликовано 28 Июль 2009 - 07:59
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.





Наверх







