Update website license notice to CC BY SA 4.0

The update to the license grant text was already true by implication,
but now it is explicit.

VMware Lawsuit FAQ: technical description example

Written by Denver Gingerich <denver@sfconservacy.org> and me, this
description gives one example of how VMware incorporated Linux code with
vmkernel and distributed the resulting work.

Make rise level consistent for both items.

With this change, both numbers should go up at the same rate.

Increase donation count by 1% each time.

Increasing by one makes it last too long. Doing 1% will make it go just
as fast as the fundraiser.

Better handle no value situations.

The issue where these values were empty was not properly handled.

Support display of donation count in fundraiser.

Allow display of a donation count in the fundraiser pages, with an
optional threshold that must be met before it's displayed.

VMware Lawsuit FAQ entry: Why doesn't FSF enforce?

This FAQ and its answer explain why the FSF can't take care of
enforcement for this particular matter.

When hovering over li,anchor changes background...

.. even though you havent’t yet hovered over the link.

This change corrects that behavior. Suggested by mina86:

<mina86> so when you hover over the LI the link changes background even though
you havent’t yet hovered over the link
<mina86> #container #sidebar li:hover a { background: #577632; color: #fff; }
<mina86> s/li:hover a/li a:hover/ would be IMO better

Better animation effects when donate link clicked.

The banner always faded in/out, but now other texts can be designated
with the class 'donate-box-highlight' and those will fade out and fade
back in with bold and slightly larger font.

Animate the progress bar at page load.

This is perhaps too flashy, but it does successfully animate the
progress bar up to the target amount, and also changes the amount until
it reaches the total raised so far.

Diff CSS for fundraiser-percentage w/ progressbar.

If Javascript is present to generate the pogressbar, then the CSS really
should be radically different.

Graceful degradation.

Rework to simply call with new kwargs.

Redo call so that I just get my own at call time.

Rework fundgoal lookup urls data.

The urls.py is of course only evaluated once: at Apache load time, which
means the data in the template became stale and is not dynamic.

This change should cause the lookup to happen at each page view.

Use caching to, ironically, prevent caching.

Now that I'm updating the database out of band with information about
the fundraiser, I've found that the page does not properly update.

This change will hopefully fix the issue.

Leave text w/ percentage when no progressbar

The progressbar is generated by Javascript. As such, the text here
won't have a progressbar formatted around it when the browser doesn't
support Javascript.

However, since the Javascript does update the text, we can format the
Django template to put in place text that we wish will appear when no
Javascript is turned on, and then allow the Javascript to make it right
when it's available.

Graceful degradation: I may be its last proponent.

Convert VMware fundraiser to new dynamic content.

Use the new dynamic content fundgoal stuff for VMware fundraiser.

Use supporter-page.js & its formatting conventions

The npoacct campaign was launched before the Supporter program, and
parts of its functionality were incorporated into supporter-page.js
ultimately. This commit hopefully now backports that functionality to
npoacct campaign.

Function to compute how far to the goal we are.

This is also inserted by the Javascript code as well, but no reason we
can't compute it server side, too.

Convert npoacct fundraiser to use dynamic content

If this new model works, we should be able to update the fundraiser
amounts in the Django database instead of the HTML.

Correct get call to use arg properly.

This was just a typo in from previous commit, more or less.

Fundraising goal lookup for template: 1st attempt

This seems to be the best approach to pass a fundraising goal record to
a template. While the static hack that tmarble implemented probably
needs work anyway, this is probably the best way currently to interface
certain general data that we seek to place on many different pages
through the templates.

I looked into a templatetags solution, but this seemed more
straightforward and more fitting with Django principles (I think :).

Make defaults for BooleanFields.

According to django-admin check,

(1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.

Just quit it with this relative import stuff.

While I think these relative imports seem to be valid for the running
application, I am having trouble with the django-admin applications
regarding them. I don't see this syntactic sugar as absolutely
essential, so I'm just going to change it now.

Initial hack at a fundraising goal application.

This simple application will simply store the code name and the to goal
of each fundraiser. The so_far number will likely just be updated by
some external script, modifying the appropriate entry in the SQL
database.

Add list of those who support the action to FAQ.

Also, note that when people donate, they may also want to make public
statements of support.