In this particular case the other coaches don't need to view the CV of
the "new" coach. Since they all work at the same school they pretty
much know already what's going on. This just gives them a way to
manage their own "permissions" to view the team records that doesn't
involve an email to the
Alright, forget the cron job. Whenever a vote comes in, compute
percentage, check to see if voting is done and set permissions.
On Mar 8, 2:43 am, Álvaro Justen [Turicas]
wrote:
> On Mon, Mar 8, 2010 at 02:31, weheh wrote:
> > Seems like a straight-forward thing to implement on top of auth. You
Don't they need to read the CV of the new coach? If so, send them
the email inviting them to 'meet' the new candidate on-line. Then
once they are online, ask them to log in. Only allow those who are
logged in with the right permission to vote.
Or, if it has to be a single click from the email:
This sounds promising guys. I was thinking that a single "no" could veto
the new coach but it might take a majority of "yes" votes to confirm him.
Or something similar. I need to create a UUID to represent the vote and I
presume a /yes and /no page for the link. It has to be a UUID the new coach
On Mon, Mar 8, 2010 at 02:31, weheh wrote:
> Seems like a straight-forward thing to implement on top of auth. You
> create a group and allow new user membership to the group if you get a
> majority of votes. Add vote-count percentage as a field to auth_user.
> And then run a cron job that periodic
Seems like a straight-forward thing to implement on top of auth. You
create a group and allow new user membership to the group if you get a
majority of votes. Add vote-count percentage as a field to auth_user.
And then run a cron job that periodically looks at percentage and
determines whether or n
6 matches
Mail list logo
