Meeting states

[gcollazo]

@jpadilla, @crm114:

Acabo de añadir un montón de "states" para los meetings y me gustaría que los vieran y me dijeran si esto cubre todos los casos. La idea es tener un state para cada posible situación, esto nos va a ayudar mucho con métricas para generar data interesante de como se está usando la plataforma. Obviamente esta data estará disponible para que cualquiera pueda jugar con ella.

Abajo reproduzco el comment que le puse al file de app/meetigns/states.py para documentar esto.

Feedback, comments, fixes?

Possible states
---------------

available:
    A new meeting.

reserved:
    A meeting that was available and reserved by protege.

confirmed:
    A meeting that was reserved by a protege and later accepted
    by the meeting's mentor.

cancelled:
    A meeting that was either reserved or confirmed and
    then cancelled by the mentor or protege.

waiting_reply:
    At least 1 hour have passed from the meeting's start datetime
    and mentor or protege have not replied to our how was the
    meeting email.

didnt_happen:
    Mentor or protege replied to our how was the meeting email
    saying the meeting did not happen.

did_happen:
    Mentor or protege replied to our how was the meeting email
    saying the meeting did happen.

unused:
    at least 1 hour have passed from the meeting's start datetime
    and the meeting is still in the available state, meaning
    it was not reserved by a protege.

deleted:
    A meeting in available state can be transitioned to deleted
    by the system after a user updates his/her meeting settings.
    This transition will produce a new available meeting.

[jpadilla]

:+1:

[crm114]

Esto? https://github.com/kmmbvnr/django-fsm

[gcollazo]

Estoy usando django-states2

[crm114]

Ok. looks good.