Evan Prodromou resigned from Eval Committee.

Evan no longer had time to serve on the committee.

Peter Brown no longer on Board of Directors.

Peter Brown left the Conservancy Board of Directors to focus on his new
job effective 2015-03-01.

Improve formating and linkage to match original.

KCC put this originally on their own website. By inspecting that, I was
able to match some of their formatting a little bit better.

Korean translation of GPL Enforcement Principles.

This translation was kindly done by the Korean Copyright Commission.

Add copyright notice and license of document.

Upon agreement of all the authors mentioned in the earlier commit and
listed herein, the license of the document is as this commit describes.

First publication of GPL Enforcement Principles.

Bradley M. Kuhn wrote the first draft of these principles on 23 May
2015. They were from there rewritten collaboratively over the following
months with the participation (in chronological order) of Karen
M. Sandler, W. John Sullivan, and Allison Randal.

This commit is the first publication of the principles on 1 October
2015.

Rewrite page; fully discuss all compliance effort

This about page now talks about all of Conservancy's compliance efforts.

Symlink for page should now point to about.html.

Now that the VMware case has been running a few months, we should point
this symlink properly to the general about for the project.

Correct link to video.

FSF seems to have moved this video to somewhere else.

Additional facts from in 2015-10-28 announcement.

The news announcement posted on Conservancy's site on 2015-10-28 at:
https://sfconservancy.org/news/2015/oct/28/vmware-update/

had additional facts. This commit incorporates those into the FAQ.

Additionally, a link to additional technical materials was also provided
that day.

Lawsuit FAQ now uses ESXi 6.0 and add minor fixes.

The main change here is that the lawsuit FAQ page now shows one how to
verify that VMware combined Linux source code with their binary-only
components using VMware's ESXi 6.0 rather than ESXi 5.5 Update 2.
This required a couple minor path changes and updates to the memory
addresses and SHA-1 checksums. The analysis steps otherwise remained
the same.

The FAQ is now more generic in its discussion of the ESXi versions
that were originally analyzed, in order to avoid confusion with the
analysis provided in the FAQ, which uses a newer version and reaches
the same conclusion.

Some minor, unrelated fixes were also added. These include:
* add period at end of paragraphs where it was previously missing
* convert ">" in <pre> and <code> to "&gt;" so the page is valid HTML
* convert "&" in <pre> to "&amp;" so the page is valid HTML
* add missing 's' to "truct pci_driver"
* fix the "tg.c" filename - this should be "tg3.c"

Generate JSON output of a fundraiser data

Allow public interface to query the fundraiser data.

Update to denote end of $50k match goal period.

Include link to announcement..

Correct height of progress bar (HT tmarble)

This should be em, not a px size, since text will appear inside it.

Additional feed_dict deprecation issue.

This use of feed_dict was not properly corrected when changes were made
due to feed_dict deprecation.

Improve FAQ entry: VMware violation tech example

Add additional information and details about the technical details of
the VMware violation. This extends the existing example with more
detail and improves various other parts related in the FAQ.

Perform math on number variable without comma

The math performed for the number of donors should be done on the number
without the comma, so that NaN doesn't show on the site.

Add note to reiterate shim layer answer.

It appears that some in the media believe the understand above says the
opposite, so I've corrected it.

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.