<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chris Bogart on The Carpentries</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/author/chris-bogart/</link><description>Recent content in Chris Bogart on The Carpentries</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 Nov 2024 10:51:28 -0500</lastBuildDate><atom:link href="https://deploy-preview-705--carpentries-website.netlify.app/blog/author/chris-bogart/index.xml" rel="self" type="application/rss+xml"/><item><title>Rewarding Software Sharing by Mapping Scientific Software</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/02/rewarding-software-sharing/</link><pubDate>Sat, 07 Feb 2015 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/02/rewarding-software-sharing/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>
 Sharing software you write with other scientists can magnify the impact of
 your research, but there can be a surprising amount of sometimes thankless
 extra work involved. I work with a group at Carnegie Mellon's Institute for
 Software Research who have been asking scientists what that extra work is, and
 what motivates them to do it&amp;mdash;despite a sometimes uncertain link between that
 extra work and the ways many of them are evaluated in their jobs. We're
 looking at ways of measuring and mapping software and its impacts, in order
 to help scientists demonstrate the positive impact that
 their work on shared software has on science. We're running an experiment
 that you can help with.
&lt;/p></description></item></channel></rss>