Skip to content
This repository has been archived by the owner on Feb 27, 2018. It is now read-only.

Personal schedule #118

Open
martian-a opened this issue Oct 27, 2011 · 2 comments
Open

Personal schedule #118

martian-a opened this issue Oct 27, 2011 · 2 comments

Comments

@martian-a
Copy link
Member

Add a feature that allows people to build a list of talks that they want to attend; a personalised schedule.

@martian-a
Copy link
Member Author

An edited excerpt from a comment from tommorris on duplicate ticket (#127):

This has been a recurring topic of conversation during and after BCL9. [This would be] very useful [and by] marking talks you want to go to [...] we can work out scheduling stuff better. That is, if we've got a talk with 50 stars in a room for 40 people and another talk with only 5 stars in a room for 100 people, it would make sense to swap the two (obviously, notifying that person too would be helpful - perhaps a reason to integrate with Twitter or ask for the person to provide an e-mail address or mobile number for notifications).

@martian-a
Copy link
Member Author

An edited excerpt from a comment by markstickley on duplicate ticket (#127):

The session flagging idea is an excellent one and would be very useful for marking which session(s) you are interested in and which you went to.

Of course the signing in thing wouldn't just be for notifications as there would have to be the concept of a user to tie the flags to whether they were identifiable or anonymous based on a session id or whatever. Really though I think it would be more beneficial to have identifiable users than to provide this functionality to the few who would object to having to sign in. I'm not sure forcing the user to sign in with twitter is that good a move, however. There should probably be an option of a quick sign in with twitter or a full native registration. I have a little experience with this kind of user journey having working on the BBC's single sign on system, and am happy to work out flows and edge cases :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

1 participant