do before & after coding? 2. How do they assess their contribution’s quality? 3. How do they communicate the intended change? RQ2: What are the key challenges they face? Research Questions
do before & after coding? 2. How do they assess their contribution’s quality? 3. How do they communicate the intended change? RQ2: What are the key challenges they face? Research Questions
Look up open issues Check for similar PRs Check rel. discussions Check guidelines Communicate changes Check other forks 0 50 100 150 20 Never or Occasionaly Often or Always 100 0 100
similar PRs Check other branches 0 50 100 150 20 Never or Occasionaly Often or Always % of responses The contributor’s perspective: After coding a contribution 100 0 100
do before & after coding? 2. How do they assess their contribution’s quality? 3. How do they communicate the intended change? RQ2: What are the key challenges they face? Research Questions
containment Documentation Building 0 15 30 45 60 % of responses The contributor’s perspective: Assessing their contribution’s quality What is evaluated How it is evaluated
containment Documentation Building 0 15 30 45 60 % of responses The contributor’s perspective: Assessing their contribution’s quality What is evaluated How it is evaluated
containment Documentation Building 0 15 30 45 60 % of responses The contributor’s perspective: Assessing their contribution’s quality What is evaluated How it is evaluated
do before & after coding? 2. How do they assess their contribution’s quality? 3. How do they communicate the intended change? RQ2: What are the key challenges they face? Research Questions
do before & after coding? 2. How do they assess their contribution’s quality? 3. How do they communicate the intended change? RQ2: What are the key challenges they face? Research Questions
Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts Technical challenges Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts “Missing knowledge about inner workings of a project [...] sometimes caused by missing documentation”
to not being intimately familiar with the entire code base.” The contributor’s perspective: Key challenges they face Implications for researchers Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts Technical challenges Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts
etc.” The contributor’s perspective: Key challenges they face Implications for researchers Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts Technical challenges Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts
[one] who does not contribute regularly, it is every time a challenge to [use it]” The contributor’s perspective: Key challenges they face Implications for researchers Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts Technical challenges Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts
Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts Technical challenges Implications for researchers Dealing with unresponsiveness Explaining the rationale Fearing rejection Social challenges Dealing with unresponsiveness Explaining the rationale Fearing rejection
Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts Technical challenges Implications for researchers Dealing with unresponsiveness Explaining the rationale Fearing rejection Social challenges Dealing with unresponsiveness Explaining the rationale Fearing rejection “The owner of the repo doesn’t ever respond to the PR and leaves it hanging open forever”
Some teams will immediately reject them without analyzing them properly The contributor’s perspective: Key challenges they face Implications for researchers Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts Technical challenges Implications for researchers Dealing with unresponsiveness Explaining the rationale Fearing rejection Social challenges Dealing with unresponsiveness Explaining the rationale Fearing rejection
Understanding the code Evaluate the impact Ensure project compliance Dealing with git and conflicts Technical challenges Implications for researchers Dealing with unresponsiveness Explaining the rationale Fearing rejection Social challenges Dealing with unresponsiveness Explaining the rationale Fearing rejection “Fear of looking stupid.” “Fear of rude response.”
for merging Untangle code changes Analyze impact of changes Improve awareness & communication Implications for researchers Recommendations for contributors Minimize friction Maximize awareness Build a solid profile Recommendations for contributors