About: currently how to cite software is not clear or technically resolved, and secondly the documentation of basic information (kind of metadata) is also not clearly defined so that researchers looking to use published works do not have enough information to act on.
Guidance is needed on both issues and we can engage with key players working on these issues.
We can produce three articles, get the community on the forum and point to others how-tos.
#Questions 1. needs 3. improving systems #Editorial 1. empowering 2. discourse 3. bottom-up 5. replicable models #Brand 3. Gender equality 4. Co-creation #Strategy 1. three channel #Audience 1. carreer 2. engaged
Note: Blog comparators are not carrying stories on this topic
#oscibar https://etherpad.wikimedia.org/p/oscibar2018_session10
Blogs/articles
Resources
2016 Force11 working group running through Dec' 18 https://github.com/force11/force11-sciwg/ https://www.force11.org/software-citation-principles https://peerj.com/articles/cs-86/
2018 Nature Software Submission Guidelines’, 2018. https://doi.org/10.1038/d41586-018-02741-4
Lobby OpenAIRE to include software. Currently OpenAIRE policy is not to include it – forum issue
Discover and run scientific code, Code Ocean https://codeocean.com/
Simulations in the browser, Jupyter https://jupyter.org/ and Binder to republish https://mybinder.org
Continuos Integration and validation, with dependencies and full contributor audit
To include: timeline, issues, keywords, who to name check, questions to ask.