Embedding Openness in Our Universities

Transcript

1. Embedding Openness in Our Universities Arfon Smith @arfon Creative Commons Attribution 3.0 Unported License
2. Three ideas we should steal from Open Source Creative Commons Attribution 3.0 Unported License Arfon Smith @arfon
8. !
9. What is a GitHub?
11. GitHub
13. 0 3,000,000 6,000,000 9,000,000 2007 2008 2009 2010 2011 2012 2013 2014 Users
14. 4,000,000 8,000,000 12,000,000 16,000,000 20,000,000 2007 2008 2009 2010 2011 2012 2013 2014 Repositories
15. Why build a GitHub?
16. Made writing code a social experience 1.
21. Changed the collaborative model of open source 2.
23. ‘May I have access to your codes please?’
25. From 653314448c7c6f6ec2f93de346896895f786773f Mon Sep 17 00:00:00 2001 From: Arfon Smith <arfon@github.com> Date: Mon, 13 Oct 2014 16:37:46 -0500 Subject: [PATCH] Bust that cache --- lib/linguist/repository.rb | 14 ++++++++++++-- test/test_repository.rb | 12 ++++++++++++ 2 files changed, 24 insertions(+), 2 deletions(-) diff --git a/lib/linguist/repository.rb b/lib/linguist/repository.rb index 1f9e09c..9998ee6 100644 --- a/lib/linguist/repository.rb +++ b/lib/linguist/repository.rb @@ -1,6 +1,6 @@ require 'linguist/lazy_blob' require 'rugged' - +require 'pry' module Linguist # A Repository is an abstraction of a Grit::Repo or a basic file # system tree. It holds a list of paths pointing to Blobish objects. @@ -128,13 +128,23 @@ def current_tree protected def compute_stats(old_commit_oid, cache = nil) - file_map = cache ? cache.dup : {} old_tree = old_commit_oid && Rugged::Commit.lookup(repository,
26. GitHub delivered on a theoretical promise of open source
27. Open source collaborations Open Source: the right to modify
28. Open source collaborations Open Source: the right to modify, not the right to contribute.
29. "
30. Open source collaborations Forking a project was done as a last resort
31. Open source collaborations GitHub made forking the norm
34. 1. Open Collaborations
35. Open source collaborations Open Source vs Open Collaborations
36. Open source collaborations Open Source: the right to modify
37. 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.
38. 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
39. How do 4000 people work together?
40. The pull request
48. discuss improve Code first, permission later
49. Exposed process
50. Every time this happens the community learns
51. Academia makes the same promise
54. Explain what you did
55. So that others can repeat
56. Everybody learns
58. (doesn’t have to mean this) Open Public? =
59. Open (within your team, department or institution)
60. Electronic & Available
61. Exposed process
62. Exposed process
63. Exposed process
64. Asynchronous & Lock-free
65. Open, low friction collaborations
66. Culture of Reuse 2.
67. A story from my life (~10 years ago)
68. http://amandabauer.blogspot.com/
70. 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
71. 2 days work 3 observing runs/week 52 weeks in year 15 year detector lifetime 2*3*52*15 = 4680 days (13 years)
72. A second story from my life (~6 months ago)
79. Software composed of many components
80. Your software is the thing that is different
81. Open Source: Ubiquitous culture of reuse
82. Verification 3.
95. Robots doing work
96. “open source is… reproducible by necessity” Fernando Perez http://blog.fperez.org/2013/11/an-ambitious-experiment-in-data-science.html
97. Why steal ideas from open source?
98. Academic landscape is changing
101. A VISION AND STRATEGY FOR SOFTWARE FOR SCIENCE, ENGINEERING, AND EDUCATION
102. Open is the new normal
103. Software & Data Services
108. New tools. New ways of working.
109. New tools. New ways of publishing.
110. http://www.flickr.com/photos/tamaleaver/
111. Reproducibility Data intensive
112. Complex (unpublished) things Numbers, data Science!
113. Verification & benchmarking services Likely thing #1:
119. Software is an unforgiving medium
120. Automating processes
121. Benchmarking services
131. Most innovation around shared challenges/data products Likely thing #2:
132. 10 ? n Level 1 (continual) Level 2 (periodic)
133. Software composed of many components
134. Your software is the thing that is different
135. Open Source: Ubiquitous culture of reuse
136. Ecosystem around data products
137. Stars Rocks SN WR NEOs Josh Bloom’s Type Ia supernovae Level 1 (continual) 10 n
141. ‘Normal’ citations won’t be sufficient for software Likely thing #3:
142. “Academic environments of today do not reward tool builders” Ed Lazowska, OSTP event http://lazowska.cs.washington.edu/MS/MS.OSTP.pdf
146. “publishing a paper about code is basically just advertising” David Donoho http://www.stanford.edu/~vcs/Video.html
147. Transitive Credit
148. Paper Author 1 Author 2 Paper Software Data 0.2 0.2 0.4 0.1 0.1 Paper Software Software Author 1 0.5 0.3 0.1 0.1 http://arxiv.org/abs/1407.5117, Katz & Smith
149. Authorship isn’t static
158. Where does progress come first?
159. Where do communities form?
160. Around a shared challenge?
161. Around shared data?
162. Be more exact
163. Where peers can most easily recognise value
164. Open source has solved much of what academia needs
165. The challenge is to adapt and evolve the academy in this new collaborative age
166. Thanks. arfon@github.com @arfon #