Most of the constraints in this particular domain stem from intellectual property laws: laws that make abstract things like designs, stories, or computer programs resemble physical objects by allowing them to be owned.
List primary areas of law? Copyright, Patent, & Trade mark.
the most open of these is the CC BY 4.0.
I think CC0 is technically the most open as this carries not obligation to attribute the work.
Many journals accept methods articles and there are also journals that are methods only such as Nature Methods and BMC Medical Research Methodology which is discipline specific.
Good place to have a mention of JoVE https://www.jove.com/
Is mastodon and a few of the academic instances worth a mention here now?
Some of the websites that offer these resources for free are:
Also: - bioicons.com/ - https://openmoji.org
that you can subscribe to and listen to on an app
Podcast are also an open! with distribution based on XML and RSS.
If you are starting a new podcast keep podcasting open by avoiding exclusive distribution through platforms like Spotify that are attempting to consolidate the ecosystem with proprietary distribution and DRM locked content.
Use the podcasting 2.0 name space for new features like chapters and transcripts baked into and backwards compatible with existing podcast RSS feeds: https://github.com/Podcastindex-org/podcast-namespace/blob/main/podcasting2.0.md
Academic writing is usually not accessible to researchers outside of your discipline as well as those in non-academic roles.
This is a potentially relevant citation to include here "The readability of scientific texts is decreasing over time" https://elifesciences.org/articles/27725
Google analytics
Might be worth considering the ethics of analytics trackers and alternatives to google analytics. see: https://rigorousthemes.com/blog/open-source-google-analytics-alternatives/
docx require access to Microsoft Word
docx is now mostly an open spec that can be used with open source office suites like LibreOffice and OnlyOffice. Though the .ODT open document text format is preferable.
ways to fix these types of mistakes.
A reference to BFG repo cleaner https://rtyley.github.io/bfg-repo-cleaner/ would probably be useful here.
It is, nevertheless, possible to ignore files that are already tracked by Git. To do this, you will first need to delete the file from your repository and then add a new rule to your .gitignore file.
Should probably emphasise that this does not remove any such files from the git history.
Use software like BleachBit (Linux, Windows), BC Wipe, DeleteOnClick and Eraser (Windows) or Permanent Eraser or ‘secure empty trash’ (Mac) to safely delete the data.
Note that some conventional secure deletion methods do not translate well from HDDs to SSDs and data on SSDs deleted with software designed for HDDs may not always be physically overwritten as SSDs often 'pretend' to behave like HDDs to operating systems for legacy compatibility and actually do different things from what they report.
Assurances
(Accurate assurances that you can back up in practice - there should be clarity about limitations & risks)
genetically-modified plants
Is it a good idea to include GM plants on this list as 'posing a direct threat to humans...'? This may unnecessarily contribute to unfounded heath concerns over GM plants.
setting up a string, or an if(false) statement:
This fine to mention but should probably not be recommended. It will likely upset linters and syntax highlighting. The recommend approach would I think definitely be commenting out multiple lines.
(The RStudio short-cut for block comments is Ctrl+Shift+C)
hashtag
A hash (#) is used. A hashtag is a hash symbol prepended to a string for example: #hashtag. The 'tag' part of a 'hashtag' is the string following the hash until the next space.
It is important to choose one style and stick to it:
It can be useful to use different conventions for different things. function, objects, global variables etc. might each have their own style to make them immediately visually identifiable.
Versioning
Cross-reference to section on semantic versioning?
This needs writing
Some of this looks as though it has already been written the next sub-chapter do these need deleting from here?
(for compiled programming languages, this could even mean the exact same binary file)
Discussion of reproducible binary builds?
reproduce
reuse?
Pitfall: The illusion of good coverage
Are there any cover coverage tools that tell you what proportion of your code is run how many times by your test suite and give you a coverage histogram?