BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:Europe/Stockholm
X-LIC-LOCATION:Europe/Stockholm
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20220812T074334Z
LOCATION:Samarkand Room
DTSTART;TZID=Europe/Stockholm:20220628T113000
DTEND;TZID=Europe/Stockholm:20220628T120000
UID:submissions.pasc-conference.org_PASC22_sess145_msa101@linklings.com
SUMMARY:Incentives and Frictions in Community Software Projects
DESCRIPTION:Minisymposium\n\nIncentives and Frictions in Community Softwar
 e Projects\n\nKatz\n\nResearch software is pervasive in research today; mo
 st research is dependent on software. Much of this research software is bu
 ilt and maintained by communities. And most of the communities have or dev
 elop a strong voluntary aspect, at least over time, particularly because a
 ny one funding award for research software is usually shorter term that th
 e life span of the software itself. Therefore, the software's leaders and 
 team need to be concerned with how developers join and remain in the softw
 are community. Specifically, they need to think about the reasons people j
 oin (incentives) and the reasons people leave (frictions). Some of these a
 re cultural issues around research software generally, and require widespr
 ead cultural changes to improve, but others are issues that a specific pro
 ject can work on. This talk will discuss some examples of incentives and f
 rictions that software projects have worked on to encourage and support th
 eir developer communities.\n\nDomain: Computer Science and Applied Mathema
 tics, Humanities and Social Sciences, Engineering
END:VEVENT
END:VCALENDAR