Weekly Update: Feb 14 - Feb 20, 2015

This post originally appeared on the Software Carpentry website.

Highlights: We're looking for mentors and projects for Google Summer of Code: please get in touch if you have questions or suggestions.
Research Bazaar was again a highlight on Twitter this week, and Damien Irving summarised plans for Software Carpentry in Australia and New Zealand.
Conversations: An interesting conversation about "Library Carpentry" started by James Baker took place on Twitter.
New resources: A new Browsercast tutorial "Creating a workshop website" was published. Please let us know if you have any comments.
An early release of "Effective Computation in Physics" has been made available. The book is relevant to scientists of all kinds
Opportunities: SciPy call for participation is open. Please submit your proposal for tutorials, talks, or posters.
Call for Data Science Fellow applications through the Berkley Institute for Data Science is now open.


  • Thomas Guignard and Jeramia Ory wrote about their experiences during a recent workshop at the University at Albany, SUNY. They specifically mention challenges experienced when trying to find answers in real time but otherwise had a great experience.
  • Noam Ross compiled valuable advice on "Managing GitHub notifications" for people struggling to manage the flood of email from GitHub.
  • Seven workshops were added: UCI Data Science Initiative, iPlant Collaborative (University of Arizona), Jagiellonian University, University of Melbourne (three workshops), and the University of California, Los Angeles (UCLA).
  • Next week workshops will be run by NeSI in Canterbury and Auckland, the Korea Radio Promotion Association, and the Science Library at the University of Oslo

Repository Activity

ProjectIssuesPull Requests
shell-novice 2 2 22 4 8 6
git-novice 1 1 13 4 2 5
sql-novice-survey 2 2 1
python-novice-inflammation 2 4 2 1
r-novice-inflammation 19 1 5
matlab-novice-inflammation 2 1 6 1 1
amy 9 5 36 6 6
site 5 3 39 16 14 4
Total 21 12 151 36 37 16

Dialogue & Discussion

Comments must follow our Code of Conduct.

Edit this page on Github