About This Site¶
The source of this site is licensed under the GPLv3.
Why apply a software license to a website?
See also this discussion over at LWN.
Why not an Attribution-ShareAlike (CC BY-SA) license?
Like with software that I write, I don’t want anybody to make money with my course material without giving modifications back.
I’m not a lawyer, but I understand that CC BY-SA permits exactly that.
Why not the GNU Free Documentation License
How do I choose a license altogether?
I have no idea. https://choosealicense.com/ appears helpful.
Progress is happening on Github.
$ git clone https://github.com/jfasch/jfasch-home.git
Built with the wonderful Sphinx documentation generator. Homepages generally contain content, which is not much different from documentation - so yes, Sphinx is a really great static website generator. It lets me focus myself on content, with an eye towards structure and built-in link consistency (it won’t let me break links by moving content around).
Clone Repo, create and populate a virtual environment (as yourself,
$ git clone https://github.com/jfasch/jfasch-home.git $ python -m venv ~/venv/jfasch-home-venv $ . ~/venv/jfasch-home-venv/bin/activate (jfasch-home-venv) $ pip install -r requirements.txt
Install external dependencies (as
root). This is Fedorish; your
mileage might vary.
# dnf install pandoc graphviz dia gtest gtest-devel
pandocfor markdown handling in jupyter notebooks
graphvizfor those funky dependency graphs (example)
diafor historical baggage (convert
.diavector drawings to SVG)
Like any software, this is work in progress. That work is sloppily tracked here.