In Defense of Extreme Openness

In Defense of Extreme Openness

Lightning Talk at Python in Astronomy 2016

56c4053438af8e8b90d6f53cbb7573be?s=128

Jake VanderPlas

March 22, 2016
Tweet

Transcript

  1. In Defense of Extreme Openness Jake VanderPlas Python In Astronomy

    2016
  2. I think we all see the benefit of coding in

    the open . . . Eases Collaboration — Eases Sharing Heightens Visibility — Encourages Reproducibility Encourages Extensibility — Encourages Integrity etc. — etc.
  3. . . . why not do all research in the

    open? Eases Collaboration — Eases Sharing Heightens Visibility — Encourages Reproducibility Encourages Extensibility — Encourages Integrity etc. — etc.
  4. A case study from yours truly . . .

  5. https://github.com/jakevdp/multiband_LS/ We wrote this paper on GitHub from day 1

  6. None
  7. None
  8. None
  9. gh-publisher Each new commit triggers a Travis CI process which

    builds the current paper PDF and pushes it to this website. . . https://github.com/ewanmellor/gh-publisher/
  10. None
  11. None
  12. None
  13. None
  14. Jeff Scargle!!! — as in “Lomb-Scargle Periodogram”!!!!!!!

  15. None
  16. None
  17. None
  18. None
  19. “But I might get scooped!”

  20. . . . putting work on Github is publication!

  21. . . . putting work on Github is publication! “Scooping”

    → “Plagiarism”
  22. “But Jake. . . would you do this if there

    were any real competition?”
  23. Three very similar papers all published within a few months

    last summer . . .
  24. So. . . how did it turn out?

  25. None
  26. None
  27. None
  28. (* not that I’m keeping track . . .)

  29. Be Open. Thank You.