Using some of the reasons listed here to draft a blog and invite more reasons

[malvikasharan]

Describe the issue in as much detail as possible

I drafted a blog for SSI 10 - year anniversary and used a few reasons listed in your repo.
I will share the repo link with people in the blog and ask them to respond if they have more reasons to add.

Update:

The post is up under the title "Ten arguments against Open Science that you can win" https://www.software.ac.uk/blog/2020-12-17-ten-arguments-against-open-science-you-can-win

What page(s) does it occur on?

People can comment below, which we can compile in the reasons folder.

[nuest]

https://twitter.com/nordholmen/status/1341003203459112969

Thanks @malvikasharan for a very helpful and thought-provoking article. I've added a few throughts to the Twitter thread above. Whatever I say is certainly from an extremely privileged position, but I'm eager to learn and become more aware.

[caha42]

Hi @malvikasharan, thanks for the nice post. I have one hint to the argument "My work is not good enough to share" I would like to mention. I have heard this argument a lot and what worked best is to tell them to state the intention of the code in the readme. Example "This code was developed as a proof of conept of paper XYZ" - this way everybody knows what to expect and people feel much more secure about putting their code out there, while it is also a valuable information for everybody looking at it.