“My whole work life the last two years has been trying to achieve what git does”, Daniel Falster on Twitter, quoting feedback from the workshop he taught this week at the University of Technology Sidney.
What’s happening next week
We are holding an online lab meeting for Software Carpentry this week. Everyone is welcome to attend to either of these sessions:
- this Wednesday, Feb 26, at 8 pm, or
- this Thursday, Feb 27, at 11 am.
Both are Eastern time and the meeting will last an hour. Feel free to add your thoughts and items to the lab etherpad, and look there on the day for connection details.
Workshops
Three workshops happened this week:
- James Hetherington, Owain Kenway, Miguel Bernabeu Llinares, and Mayeul d’Avezac, taught a workshop for the University College London faculty and staff.
- Daniel Falster, Rich FitzJohn, and Diego Barneche taught a R-based workshop at the University of Technology in Sidney, Australia.
- Stefano Cozzini and Kwasi Kwakwa taught a workshop at the African Institute for Mathematical Sciences in Biriwa, Ghana.
Lesson development
8 pull requests were merged, 15 issues were closed, and 6 issues were opened. In addition to the merges, we had 23 commits made by Justin Kitzes, Raniere Silva, David Rio Deiros, Bill Mills, Greg Wilson, and John Blischak.
You can always help Software Carpentry by contributing to the lesson repository. Take a look to the open issues or open a new one to fix/improve/extend something in our lessons.
Other news
- In the aftermath of last week’s tutorials on how to setup a workshop repository, Greg is asking for feedback. In case you missed it live or for a quick refresh before a workshop, note that you can always watch the recorded version.
- The paper “Software Carpentry: Lessons learned” has been published on F1000 Research. The paper summarizes the 15-year-long trip of Software Carpentry and the lessons learned on the road. Read about it on the blog.
- Greg Wilson wrote on the blog on how Software Carpentry’s main activity, teaching workshops to scientists, is framed on Software Carpentry’s main goal, make science more open.
- What else is needed for code reuse? Add your thoughts to this issue on the Science Lab’s work towards a best practice for their collaboration around code as a research object.