| Message |
 |
Date: 2009-05-29 21:55
Sender: Leif Baradoy
Complete! |
Date: 2009-05-29 21:50
Sender: Jeff Rickard
done |
Date: 2009-05-29 17:17
Sender: Jeff Rickard
Yes, I can do that after lunch |
Date: 2009-05-29 17:11
Sender: Leif Baradoy
Hi Jeff,
A close campaign button is acceptable for now. I'm not sure
if we have anything running a cron job--I think so. I think
we run a cron job for finding unused gift cards and expired account
ablances, which are then put to project 11.
Any chance you could add a "close campaign" button
to http://slice2.christmasfuture.org:3000/dt/campaigns/admin |
Date: 2009-05-29 15:30
Sender: Jeff Rickard
Right now they are not automatically allocated, you have to close
the campaign using the close button.
The easy and lowest impact way to do this is to create a cron
script that will look at the database once a day and determine
which campaigns are completed and should be close.
Are there already some timed processes like this on the server
or would this be the first one? |
Date: 2009-05-29 06:30
Sender: Leif Baradoy
I just tried to test this by creating a campaign and then pledging
to a participant in the campaign. I sent the "allocate
fund by date" using the time field (essentially 5 min after
I created the campaign). The funds were not allocated automatically
at the time I specified. I'm not sure if this is a minor problem
with the clock (not a big deal and no requirement to fix asap)
or a larger problem with a general inability to allocated
automatically.
|
Date: 2009-05-27 17:32
Sender: Jeff Rickard
I think the primary functionality for this is complete with commit
3111. There is going to be some peripheral changes I am sure
but I think the logic works.
This is deployed on slice2 now. |
Date: 2009-05-20 13:59
Sender: Leif Baradoy
Hi Jeff,
Right now there is no process for closing a campaign. At minimum,
we need (1) campaigns to stop accepting new teams/participants
(2) no more funds to be raised for that campaign (3) funds are
allocated to projects automatically.
You're helping build the skeleton out for ending a campaign,
including valid and effectual end dates and automatic allocation.
Eventually, I'd like the admin to get an email when the campaign
is finished, with the option to "allocate funds to project
now" (let the automation be a safeguard for admins). This
give the admin the feeling of more control. I've raised some
of the process in other bugs. I'd also like to build out some
notifications to participants, pledgers, and admins that summarize
the success of the campaign. All in good time... (these are
raised as other bugs)
NOTE: The priority in this bug is automatically allocating. If
turning any additional funds into an account balance that gets
sent out to participants significantly extends the time line
of this bug, then simply make additional funds go directly to
project 11 and raise the account deposit thing as a separate
bug for later. I don't want you wasting major cycles on edge
cases. |
Date: 2009-05-19 20:32
Sender: Jeff Rickard
Hey Leif, what is the current process for closing a campaign?
How would I go about doing this, or is that part of the issue,
that the closing of a campaign needs to be created still? |
Date: 2009-05-19 17:07
Sender: Leif Baradoy
Hi Jeff,
Thanks for recording this. Although the second alternative has
some merit, the downfall is that it would encourage partners
to submit projects with high budgets--something we do not want
to encourage.
The way out of the infinite loop is, as you suggested, sending
users an email that all the projects supported by the campaign
met their funding goals and that a portion of the funds they
raised is available to allocate to other projects. This additional
money essentially autmoatically becomes an account deposit to
the users account. If they don't allocate it in 30 days, it goes
to project 11 (let ChristmasFuture decide). Any funds allocated
to this project are eventually distributed to other projects--never
to operations. |
Date: 2009-05-19 16:56
Sender: Jeff Rickard
We discussed this breifly when we met at the office the other
day and I thought I should write it down for posterity.
The problem with this design is that we are required to iterate
over the projects until the funds are all allocated and it is
possible to get into an inifinite loop allocating smaller and
smaller peices of the pie out to the remaining project.
Another issue that might exist is that projects under this model
that have greater financial requirements are penalized because
they will get a smaller proportion of the funds than projects
that require less money. This means that smaller projects are
more likely to get full funding than big projects.
An alternative to the model above would be to just calculate
the weighted average of the required funds of an individual project
as compared to the total required funds for all projects. Money
would then be proportionally split between all projects. The
incentive in this model is to always ask for the most money possible
in a campaign because you will get a bigger peice of the pie,
so to speak.
This second alternative is much easier to define though and less
error prone.
I believe as part of this we also discussed the possiblity that
users should receive an email update if there is unallocated
money left over that they have contributed where they can go
and allocate the money to other projects of their choosing for
up to 30 days after a campaign has ended and then the money
automatically goes into the "Let ChristmasFuture decide
for me" bucket.
Without any confirmation on this bug, I would follow the outlined
procedure in the bug, this comment is for information purposes
only. |
Date: 2009-05-08 02:31
Sender: Leif Baradoy
This relates to #25241 (ability for Campaign Admin to limit which
projects the campaign is raising funds for) and should be developed
alongside it. |
