Upgrade to Pro — share decks privately, control downloads, hide ads and more …

What academia can learn from open source

What academia can learn from open source

Practices vary between scientific domains but all too often the sharing of research software is done on an ad hoc basis between individuals and with little thought about the wider community. With code and computation encapsulating an ever-increasing fraction of research activity, now more than ever there is a need to develop a culture of sharing and reuse similar to that found in open source communities.

03e2e7de45b193cac192ae7ea071e5ff?s=128

Arfon Smith

May 21, 2014
Tweet

Transcript

  1. What Academia Can Learn from Open Source Arfon Smith @arfon

    Creative Commons Attribution 3.0 Unported License
  2. !

  3. What is a GitHub?

  4. None
  5. None
  6. None
  7. None
  8. None
  9. None
  10. None
  11. None
  12. Astrophysics for non- astronomers

  13. tl;dr - technical, but brimming with inefficiencies

  14. http://www.flickr.com/photos/blachswan

  15. http://www.flickr.com/photos/esoastronomy/

  16. http://www.flickr.com/photos/esoastronomy/ http://www.flickr.com/photos/jamiegilbert

  17. http://amandabauer.blogspot.com/

  18. None
  19. None
  20. Diffraction grating Telescope Detector

  21. None
  22. None
  23. None
  24. None
  25. None
  26. 130 130 1 2048 189 189 258 258 480 562

    378 378 493 521 390 397 851 851 247 274 319 319 304 580 493 511 610 636 188 188 228 228 > cat bad_pix_mask.txt
  27. Wasteful 2 days work 3 observing runs/week 52 weeks in

    year 15 year detector lifetime ! 2*3*52*15 = 4680 days (13 years)
  28. Wasteful… but the norm 2 days work 3 observing runs/week

    52 weeks in year 15 year detector lifetime ! 2*3*52*15 = 4680 days (13 years)
  29. How is the Open Source community doing it?

  30. Open Source: Ubiquitous culture of reuse

  31. None
  32. None
  33. None
  34. None
  35. None
  36. None
  37. Software composed of many components

  38. Your software is the thing that is different

  39. Low friction collaborations

  40. Open source collaborations Open Source vs Open Collaborations

  41. Open source collaborations Open Source: the right to modify, not

    the right to contribute.
  42. Open source collaborations Open Collaborations: a highly collaborative development process

    and are receptive to contributions of code, documentation, discussion, etc from anyone who shows competent interest.
  43. Open source collaborations Open Collaborations: a highly collaborative development process

    and are receptive to contributions of code, documentation, discussion, etc from anyone who shows competent interest. THIS
  44. How do 4000 people work together?

  45. The pull request

  46. None
  47. None
  48. None
  49. None
  50. None
  51. None
  52. None
  53. Code first, permission later

  54. None
  55. None
  56. None
  57. Merged pull requests

  58. None
  59. None
  60. None
  61. None
  62. “open source is… reproducible by necessity” Fernando Perez http://blog.fperez.org/2013/11/an-ambitious-experiment-in-data-science.html

  63. Better at collaborating because they have to be

  64. (doesn’t have to mean this) Open Public? =

  65. Open (within your team, department or institution)

  66. Electronic & Available

  67. Asynchronous, exposed process

  68. Lock-free

  69. Low friction collaboration

  70. What’s happening in academia today?

  71. Collaboration around code

  72. None
  73. None
  74. None
  75. None
  76. None
  77. Collaborative authoring

  78. None
  79. None
  80. Collaborative teaching

  81. None
  82. None
  83. None
  84. What could be happening in academia?

  85. Where do communities form?

  86. Around a shared challenge?

  87. Around shared data?

  88. None
  89. 10 ? n Level 1 (continual) Level 2 (periodic)

  90. LSST is a project that is inherently open

  91. Supernovae Weak lensing Active Galactic Nuclei Solar System Galaxies Transients/variable

    stars Large-scale structure Stars, Milky Way Strong lensing Informatics and Statistics Dark Energy (DESC)
  92. LSST has the opportunity to do something differently

  93. Copy Open Source

  94. None
  95. Software composed of many components

  96. Your software should be the thing that is different

  97. science too! Your software should be the thing that is

    different
  98. How do we make this behaviour the norm?

  99. Credit

  100. “Academic environments of today do not reward tool builders” Ed

    Lazowska, OSTP event http://lazowska.cs.washington.edu/MS/MS.OSTP.pdf
  101. None
  102. None
  103. None
  104. None
  105. None
  106. None
  107. None
  108. None
  109. “publishing a paper about code is basically just advertising” David

    Donoho http://www.stanford.edu/~vcs/Video.html
  110. None
  111. How to derive meaningful metrics from open contributions?

  112. None
  113. None
  114. Reproducibility Data intensive

  115. Trust

  116. None
  117. None
  118. None
  119. None
  120. None
  121. Discoverability

  122. None
  123. Barriers are cultural, not technical

  124. What can you do today?

  125. Establish a virtuous cycle# •  6%working%groups,%each%with%# •  3:6%faculty%from%each%ins;tu;on# 14# http://lazowska.cs.washington.edu/MS/MS.OSTP.pdf

  126. http://www.flickr.com/photos/tamaleaver/

  127. Why are you sharing?

  128. Share more often

  129. If you’re going to share it then you better put

    a licence on it
  130. None
  131. Treat documentation as a first class entity

  132. Share more often (no matter how small)

  133. 130 130 1 2048 189 189 258 258 480 562

    378 378 493 521 390 397 851 851 247 274 319 319 304 580 493 511 610 636 188 188 228 228 > cat bad_pix_mask.txt > git clone git@github.com:arfon/aat/pixel_masks
  134. None
  135. Open Data is the least we can do

  136. This is not a talk about Open Science

  137. This is a talk about Accelerating Science

  138. Thanks. arfon@github.com @arfon "