
| Key: |
VWR-10376
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Normal
|
| Assignee: |
Unassigned
|
| Reporter: |
Boroondas Gupte
|
| Votes: |
2
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Relates
|
|
This issue Relates to:
|
|
|
SVC-2829 New Feature -> Dialog -> Group Information -> IMs/notices to specific group roles
|
|
|
|
|
|
This issue is related to by:
|
|
|
|
|
 |
|
VWR-5325 Ability to easilly add to existing conference.
|
|
|
|
 |
VWR-10386
Invite option for IM Conferences- non friend
|
|
|
|
 |
|
|
|
 |
|
|
|
|
|
VWR-1577 Meta-Issue: Bugs or improvements suitable for open source programmers
|
|
|
|
|
|
|
Requested Feature:
Make it possible to have multiple concurrent IM sessions for a single group.
Use case:
Q&A groups, topic IM sessions etc.
This would allow to have discussions of different topics related to the group but unrelated to each other simultaneously without the confusion caused by seeing two or more unrelated "talks" merged into a single one, as it is now. This is especially important for groups specialized in answering questions in group IM. Another advantage would be that group members could close topic/question sessions in the outcome of/answer to they aren't interested while still seeing the answers to other topics they might want to see, as well as new sessions (if they choose so – this should probably be optional).
Possible implementation:
I'm filing this under VWR, because, as far as I know, the server side infrastructure for this is already there. It's being used e.g. for Ad-Hoc conference IMs, initiated from calling cards in the inventory. I guess it's also used by Dale's SL Viewer to start conference IM sessions with selected nearby Avatars. (see http://sl.daleglass.net/#scanner ) So, when the resident wants to initiate a new topic/question group IM session, the viewer could just use the list of online group members and apply this existing mechanism on it to start the session.
|
|
Description
|
Requested Feature:
Make it possible to have multiple concurrent IM sessions for a single group.
Use case:
Q&A groups, topic IM sessions etc.
This would allow to have discussions of different topics related to the group but unrelated to each other simultaneously without the confusion caused by seeing two or more unrelated "talks" merged into a single one, as it is now. This is especially important for groups specialized in answering questions in group IM. Another advantage would be that group members could close topic/question sessions in the outcome of/answer to they aren't interested while still seeing the answers to other topics they might want to see, as well as new sessions (if they choose so – this should probably be optional).
Possible implementation:
I'm filing this under VWR, because, as far as I know, the server side infrastructure for this is already there. It's being used e.g. for Ad-Hoc conference IMs, initiated from calling cards in the inventory. I guess it's also used by Dale's SL Viewer to start conference IM sessions with selected nearby Avatars. (see http://sl.daleglass.net/#scanner ) So, when the resident wants to initiate a new topic/question group IM session, the viewer could just use the list of online group members and apply this existing mechanism on it to start the session. |
Show » |
made changes - 07/Nov/08 02:26 PM
| Field |
Original Value |
New Value |
|
Description
|
h2. Requested Feature:
Make it possible to have multiple concurrent IM sessions for a single group.
h2. Use case:
h4. Q&A groups, topic IM sessions etc.
This would allow to have discussions of different topics related to the group but unrelated to each other simultaneously without the confusion caused by seeing two or more unrelated "talks" merged into a single one, as it is now. This is especially important for groups specialized in answering questions in group IM. Another advantage would be that group members could close topic/question sessions in the outcome of/answer to they aren't interested while still seeing the answers to other topics they might want to see, as well as new sessions (if they choose so -- this should probably be optional).
h2. Possible implementation:
I'm filing this under VWR, because, as far as I know, the server side infrastructure for this is already there. It's being used e.g. for Ad-Hoc conference IMs, initiated from calling cards in the inventory. I guess it's also used by Dale's SL Viewer to start conference IM sessions with selected nearby Avatars. (see http://sl.daleglass.net/#scanner) So, when the resident wants to initiate a new topic/question group IM session, the viewer could just use the list of online group members and use this existing mechanism to start the session.
|
h2. Requested Feature:
Make it possible to have multiple concurrent IM sessions for a single group.
h2. Use case:
h4. Q&A groups, topic IM sessions etc.
This would allow to have discussions of different topics related to the group but unrelated to each other simultaneously without the confusion caused by seeing two or more unrelated "talks" merged into a single one, as it is now. This is especially important for groups specialized in answering questions in group IM. Another advantage would be that group members could close topic/question sessions in the outcome of/answer to they aren't interested while still seeing the answers to other topics they might want to see, as well as new sessions (if they choose so -- this should probably be optional).
h2. Possible implementation:
I'm filing this under VWR, because, as far as I know, the server side infrastructure for this is already there. It's being used e.g. for Ad-Hoc conference IMs, initiated from calling cards in the inventory. I guess it's also used by Dale's SL Viewer to start conference IM sessions with selected nearby Avatars. (see http://sl.daleglass.net/#scanner) So, when the resident wants to initiate a new topic/question group IM session, the viewer could just use the list of online group members and apply this existing mechanism on it to start the session.
|
made changes - 07/Nov/08 02:34 PM
|
Link
|
|
This issue Relates to SVC-2829
[ SVC-2829
]
|
made changes - 07/Nov/08 02:36 PM
|
Link
|
|
This issue is related to by MISC-678
[ MISC-678
]
|
made changes - 07/Nov/08 02:36 PM
|
Link
|
|
This issue is related to by MISC-389
[ MISC-389
]
|
made changes - 07/Nov/08 02:41 PM
|
Link
|
|
This issue is related to by VWR-1577
[ VWR-1577
]
|
made changes - 08/Nov/08 04:12 PM
|
Link
|
|
This issue is related to by VWR-10386
[ VWR-10386
]
|
made changes - 08/Nov/08 04:12 PM
|
Link
|
|
This issue is related to by VWR-10059
[ VWR-10059
]
|
made changes - 13/Nov/08 11:07 AM
|
Workflow
|
jira-2007-12-22a
[ 61442
]
|
jira-2008-11-14
[ 64557
]
|
made changes - 13/Nov/08 11:29 AM
|
Workflow
|
jira-2007-12-22a
[ 64557
]
|
jira-2008-11-14
[ 72334
]
|
made changes - 13/Nov/08 04:59 PM
|
Workflow
|
jira-2008-11-14
[ 72334
]
|
jira-2008-11-14a
[ 96873
]
|
made changes - 13/Nov/08 05:13 PM
|
Workflow
|
jira-2008-11-14
[ 96873
]
|
jira-2008-11-14a
[ 102252
]
|
made changes - 13/Nov/08 05:23 PM
|
Workflow
|
jira-2008-11-14
[ 102252
]
|
jira-2008-11-14a
[ 105709
]
|
made changes - 13/Nov/08 05:36 PM
|
Workflow
|
jira-2008-11-14
[ 105709
]
|
jira-2008-11-14a
[ 110850
]
|
made changes - 13/Nov/08 06:06 PM
|
Workflow
|
jira-2008-11-14
[ 110850
]
|
jira-2008-11-14a
[ 121213
]
|
made changes - 13/Nov/08 06:32 PM
|
Workflow
|
jira-2008-11-14
[ 121213
]
|
jira-2008-11-14a
[ 130976
]
|
made changes - 13/Nov/08 06:51 PM
|
Workflow
|
jira-2008-11-14
[ 130976
]
|
jira-2008-11-14a
[ 138221
]
|
made changes - 08/Feb/09 01:48 AM
|
Link
|
|
This issue is related to by VWR-5325
[ VWR-5325
]
|
|