Open ccotter opened 12 years ago
The user list is automatically populated based on the users in the session. Point two browsers at the same session and you should see two users. The way our server is set up, all users are "anonymous". In a real life scenario, this would be a username instead. Clicking on a user in the attendee list starts the scrum and allots time to each user evenly. You can stop the scrum by clicking on the red stop button next to the clock in the lower left hand corner once it is started. You can resume the scrum again by clicking on a user.
The invites.json functionality serves two purposes. First, it allows you to predefine a list of users in the attendee list. These users will be "disabled" initially. As the actual users join, their names will be "enabled". The invites.json format allows you to specify whether or not a user has moderator privileges as well, which allow you to start and stop the meeting. Still further, a user with moderator privileges can manually enable a user by double clicking on that specific user's name in the attendee list. This was a special design feature for a specific use case: if this app is being used alongside a teleconference, and a user calls in but is unable to access a computer, they can still participate in the scrum. A moderator would simply manually activate that users name.
As part of making sure all demo apps work, I have not been able to determine how to even use the daily scrum app. I have gone through the code and examined the help button text, but I cannot figure out the proper way to use this app.
?invites=users.json
URL option adds the users from theusers.json
file, and another "anonymous" user is added. I cannot figure out how to activate the other users, or become one of the users listed inusers.json
.I believe we should update the help button text and provide some additional documentation for using this app. Can we use this issue to clarify everything here?
https://github.com/opencoweb/coweb/issues/72 https://github.com/opencoweb/coweb/wiki/Coweb-Triage-Design-Discussion