Reduce the number of possible meeting states about horas HOT 3 CLOSED

At the core the system should:

• facilitate meetings
• manage confirmed meetings
  1. completed 2) cancelled
• remove unused meetings
• collect data to help give or remove possible Whuffie points
  1. cancelled meetings 2) completed meetings, etc.
• provide for mentor or protege comments

So (available, reserved, confirmed, completed, cancelled(deleted))? I'm
not sold on confirmed. How about accepted?

On Thu, May 1, 2014 at 11:03 AM, Giovanni Collazo
[email protected]:

Currently we have a lot of possible meeting stateshttps://github.com/SoPR/horas/blob/master/apps/meetings/states.py.
When this was designed the idea was to track as much information as
possible from meetings. That way we could eventually develop a score for
users based on their actions around meetings.

From the feedback gathered it seems like we are asking too much
interaction from users in order to gather this information and users are
just not responding.

Solution:

• Remove the did_happen and didnt_happen states with their related
  notifications.
• After meetings, just ask users to give feedback and cancel the
  meeting if it didn't actually happen.
• Stop tracking cancelled_by on meetings
• If we start calculating points we can "punish" both mentor and
  protege for cancelled meetings.
• Allow mentor and protege to leave comments in the meeting.
• Anyone can see a meeting's detail view with the exception of contact
  information

Feedback?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59
.

Kevin Shockey
President
Puerto Rico Python Interest Group http://www.prpig.org
Mis Tribus http://blog.mistribus.com/
Twitter Feed: @shockeyk http://www.twitter.com/shockeyk

from horas.

For me, not being to close the loop and identify that the meeting actually took place is awkward. I recently requested a meeting and it was confirmed, and the meeting was held. Looking at my hours will then leave the meeting as confirmed, indefinitely. I'd like to see some closure.

from horas.

@mistribus: we have a new thread going on about this issue. #66

from horas.