1 of 8

https://codeisscience.github.io/manifesto/

@codeisscience

2 of 8

Background & Inspiration

  • Science is often computing

​

  • Science requires peer review

​

  • Software contains errors

​

@codeisscience

3 of 8

Let’s do a mini-workshop!

@codeisscience

4 of 8

A first draft is born...

  • Open over closed
  • Code for the future
  • Incorrect code results in incorrect science
  • Availability over perfection
  • Code deserves credit

​

https://codeisscience.github.io/manifesto

5 of 8

The Team

​

  • Selina Aragon
  • Alex Konovalov
  • Yo Yehudi

@codeisscience

6 of 8

How we worked

  • Google Docs brainstorm
  • Move to GitHub once draft finalised
    • PR new changes
    • Manage future work in issues

https://github.com/codeisscience/manifesto

@codeisscience

7 of 8

Future Steps

  • 60 day consultation period on draft text
  • Blog about the hackday!
  • Paper?!
  • Code is Science ambassadors
    • (This means you tell everyone about us and get a bunch of stickers to share)

@codeisscience

8 of 8

We need your help!

  • We’re looking for feedback about the text of the manifesto.
  • You can also look at the issues on github and see if there’s anything else you can pick up.
  • You can also look at our roadmap to get an understanding of our timeline.

@codeisscience