feedback from Jonas

[MalikaIhle]

• Project Setup: "How do you know you are allowed to copy, edit, and share the two files linked above?" TBH I wouldn't know how to answer the question here because I couldn't find any copyright info in the files. What do you expect here?
• Choose a License: why do you recommend Apache 2.0 over MIT? Just curious as e.g. for tidyverse/posit I often see MIT
• Choose a License: "Note, however, that the copyleft licenses we discuss here do not mandate sharing. Copyleft (and attribution) clauses are only triggered if the work is shared (Creative Commons 2015)." I think here some more explanation would be good. E.g.: "[...] is shared (Creative Commons 2015), but not if you only use it internally." Or even a bit more? I know that the focus is on sharing your work, but I think it's good to know that the restrictions are not given if you only use it internally.
• Choose a License: I think a short section about who can exploit the work should be added. As far as I understand in some jurisdictions the copyright is automatically transferred to the employer, while that is not possible in Germany (https://www.lexology.com/library/detail.aspx?g=a8cba6b5-19ce-429b-9bcb-f1625f3b165c). However, the employer has the right to exploit the work, and therefore one should theoretically consult with a supervisor which license to use. What do you think?
• Choose a License: "Note 4: Using REUSE to Record Licenses": is the pip install reuse into the system python installation good practice? I'm not a python guy, just caught my eye
• Choose a License: typo: "If you want to indicate the license for all files in a particular folder, you can create a filed"
• Choose a License: "sui generis" is often not italicized
• Make a README: Citation: maybe also mention CFF (https://citation-file-format.github.io/) as an alternative?