- Create a new repository with the name
lecture_xyz
and selectslds-lmu/lecture_template
as template repository. - Start editing everything to suite your needs. For important (editing) workflows see the
README
files in the directoriesslides
,exercises
, andcode-demos
. - Note: When creating new subchapters, it is important to copy the
Makefile
from one of the existing subchapters into the new one! Otherwise, the automatic rendering will not work.
- The very basic structure of the template contains
slides
: Raw.tex
files of your lecture. PDFs are rendered automatically and moved toslides-pdf
.exercises
: Raw.tex
exercise files. PDFs are rendered automatically and moved toexercises-pdf
.code-demos
: Raw.tex
files for code demos. PDFs are rendered automatically and moved tocode-demos-pdf
.quizzes
: Raw.csv
files for quizzes.cheatsheets
: Material for cheatsheets (images, source, etc.).latex-math
: Submodule included fromgithub.com/slds-lmu/latex-math
.style
: All relevant style files.
- Each folder contains a
README.md
with more details.
- We have two branches, the
main
andrelease
branch. - Work is exclusively done in a subbranch of the
main
branch! - When you have finished a task, write a short understandable commit message, the smaller and more precise your commit is the better. PLEASE DO NOT FORCE PUSH PDF FILES! PDFs are rendered automatically via an actions workflow. If you want to skip CI add a tag
[skip ci]
to your commit (details see here). - Create a PR to the
main
branch and describe what you have done, reference issues, etc. Also assign a reviewer if necessary. - The responsible person for the lecture then merges the PRs.
- A release is done once a while when enough new content was added. Therefore, the main branch is merged into the
release
branch.
More workflows are described in this gdoc (in German). If you don't have permission, ask one of the responsible pearsons.
Please see the main course site.
We hope to continously improve and expand this course over the coming years. We strongly believe in open source and collaborative work. Please contact us if you think likewise and would like to contribute. See also our contributing guidelines
- Are you an ML expert and like the course, but have some feedback or consider extending it? Write an email to Bernd and Fabian (see Team page) or Open an issue.
- Are you a student taking the lecture - either at the LMU or online - and you spotted a typo, think we should rephrase something be or even would like to provide a new quiz question or coding example? Please consider providing a pull request. To do so, please check out the devel branch of the repo and add your fixes there. Writing an e-mail or opening an issue with suggested improvements is obviously very welcome as well!
- You are none of the above but would like to contribute, get in touch / open issues / create pull requests! We are happy about any help.
This work is licensed under a Creative Commons Attribution 4.0 International License.
We would appreciate if you contact us in case you are re-using our course. Knowing this helps us to keep the project alive. Thank you!