Dajana Gnther daj@trifork.com @dajanaguenther Why? old, dusty, - - PowerPoint PPT Presentation

▶
dajana g nther
SMART_READER_LITE
LIVE PREVIEW

Dajana Gnther daj@trifork.com @dajanaguenther Why? old, dusty, - - PowerPoint PPT Presentation

Jul 05, 2023 301 likes •1.07k views

Dajana Gnther daj@trifork.com @dajanaguenther Why? old, dusty, public school system new literacy theres a need! What? How? weekend workshops several different topics working with mentors out of the communities max. 3 juniors to 1

slide-1
SLIDE 1

Dajana Günther

daj@trifork.com @dajanaguenther

slide-2
SLIDE 2

Why?

there’s a need!

  • ld, dusty, public school system

new literacy

slide-3
SLIDE 3

What?

slide-4
SLIDE 4

How?

weekend workshops several different topics

  • max. 3 juniors to 1 mentor

working with mentors out of the communities

slide-5
SLIDE 5

Next steps

  • 1. talk to local IT communities

mentors facilities sponsors juniors!

  • 3. find
  • 2. set up a program
slide-6
SLIDE 6

Questions?

cat tax
slide-7
SLIDE 7

Working Effectively with Pull Requests

Georgios Gousios // @gousiosg Radboud University Nijmegen

slide-8
SLIDE 8

The pull-based development model

Here are my changes Please fix those issues Here are my updates Looks great, thanks!

contributor integrator

changes integrated changes examined changes re- examined

slide-9
SLIDE 9

GitHub: made pull requests popular

slide-10
SLIDE 10

45% of collaborative projects

Projects with > 1 committers

slide-11
SLIDE 11

45% of collaborative projects

Projects with > 1 committers 55% use shared repository 45% use pull requests

slide-12
SLIDE 12

Widely popular and increasing

slide-13
SLIDE 13

90k repositories 400k pull requests

Widely popular and increasing

slide-14
SLIDE 14

Per month 90k repositories 400k pull requests

Widely popular and increasing

slide-15
SLIDE 15

Large scale collaboration

  • http://www.gousios.gr/blog/The-triumph-of-online-collaboration/
slide-16
SLIDE 16

Large scale collaboration

  • http://www.gousios.gr/blog/The-triumph-of-online-collaboration/

23,501

slide-17
SLIDE 17

Too successful?

slide-18
SLIDE 18

“Lack of knowledge of git from contributors; most don’t know how to resolve a merge conflict.” “Sifting through the GitHub information flood to find what, if any, I should address.” “Dealing with loud and trigger-happy developers.”

Too successful?

slide-19
SLIDE 19

GitHub Research @ RU Nijmegen

slide-20
SLIDE 20

GHTorrent.org

  • Query-able offline mirror of all

data from the GitHub API

  • Since Feb 2012
  • 7TB in MongoDB
  • 1,600B rows in MySQL
  • 2GB per hour

Georgios Gousios: The GHTorrent dataset and tool suite. MSR 2013: 233-236

slide-21
SLIDE 21
slide-22
SLIDE 22

How do projects use pull requests?

slide-23
SLIDE 23

Pull Requests

Georgios Gousios, Martin Pinzger and Arie van Deursen:An exploratory study of the pull-based software development model. ICSE 2014: 345-355

slide-24
SLIDE 24

Pull Requests

are small (< 20 lines); merged in < 1 day; are briefly discussed

Georgios Gousios, Martin Pinzger and Arie van Deursen:An exploratory study of the pull-based software development model. ICSE 2014: 345-355

slide-25
SLIDE 25

Pull Requests

are small (< 20 lines); merged in < 1 day; are briefly discussed are merged when they affect a hot project area

Georgios Gousios, Martin Pinzger and Arie van Deursen:An exploratory study of the pull-based software development model. ICSE 2014: 345-355

slide-26
SLIDE 26

Pull Requests

are small (< 20 lines); merged in < 1 day; are briefly discussed are merged when they affect a hot project area are processed fast when project has test suite

Georgios Gousios, Martin Pinzger and Arie van Deursen:An exploratory study of the pull-based software development model. ICSE 2014: 345-355

slide-27
SLIDE 27

Pull Requests

are small (< 20 lines); merged in < 1 day; are briefly discussed are merged when they affect a hot project area are processed fast when project has test suite are processed fast when contributor has good track record

Georgios Gousios, Martin Pinzger and Arie van Deursen:An exploratory study of the pull-based software development model. ICSE 2014: 345-355

slide-28
SLIDE 28

Pull Requests

are small (< 20 lines); merged in < 1 day; are briefly discussed are merged when they affect a hot project area are processed fast when project has test suite are processed fast when contributor has good track record are rejected mostly due to insufficient task articulation

Georgios Gousios, Martin Pinzger and Arie van Deursen:An exploratory study of the pull-based software development model. ICSE 2014: 345-355

slide-29
SLIDE 29

How do developers use of pull requests?

http://perceptionvsfact.com/ti5
slide-30
SLIDE 30

Technical challenges

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-31
SLIDE 31

Technical challenges

maintaining quality

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-32
SLIDE 32

Technical challenges

impact assessment maintaining quality

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-33
SLIDE 33

Technical challenges

impact assessment contributor experience maintaining quality

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-34
SLIDE 34

Technical challenges

impact assessment contributor experience maintaining quality volume

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-35
SLIDE 35

Technical challenges

impact assessment contributor experience maintaining quality volume understanding the code

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-36
SLIDE 36

Technical challenges

impact assessment contributor experience maintaining quality volume understanding the code compliance

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-37
SLIDE 37

Technical challenges

impact assessment contributor experience maintaining quality volume understanding the code compliance infrastructure setup

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-38
SLIDE 38

Social challenges

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

slide-39
SLIDE 39

Social challenges

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

workload

slide-40
SLIDE 40

Social challenges

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

workload responsiveness

slide-41
SLIDE 41

Social challenges

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

explaining rejection workload responsiveness

slide-42
SLIDE 42

Social challenges

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

explaining rejection workload responsiveness explaining rationale

slide-43
SLIDE 43

Social challenges

  • G. Gousios, A. Zaidman, M.-A. Storey, and A. van Deursen, “Work Practices and

Challenges in Pull-Based Development: The Integrator’s Perspective,” ICSE, 2015.

explaining rejection workload responsiveness motivating contributors explaining rationale

slide-44
SLIDE 44

Advice for projects owners

http://varshadaswani.com/2014/01/giving-a-17-year-old-advice/
slide-45
SLIDE 45

Project owners

1.Provide submission guidelines 2.Invest in good tests 3.Automate 4.Be reactive and proactive 5.Monitor PR performance

slide-46
SLIDE 46

Submission Guidelines

  • Setting up development environment
  • Setting up branches
  • Coding style
  • Commit guidelines
  • Communication options. PRs are post-hoc communication.
  • Include updated list of low hanging fruit for beginners

People generally expect a CONTRIBUTING.md file

slide-47
SLIDE 47

Submission Guidelines

slide-48
SLIDE 48

Invest in good tests

  • Run everything with a single command
  • Use tools like Vagrant and Docker to simulate

environments

  • Measure PR coverage in CI
slide-49
SLIDE 49

Automate

  • Building/CI
  • Quality checks
  • Testing
  • Shipping

The Github API is brilliant. Take advantage of it.

slide-50
SLIDE 50
slide-51
SLIDE 51

Be (pro/re)active

  • Don’t allow PRs to linger
  • Reply to contributed requests
  • Close unwanted pull requests
  • Be there when discussion diverges from

technical

slide-52
SLIDE 52

Monitor Performance

  • Compare against the norm
  • Average pull request merged in 1 day
  • Average project merges 85% of PRs
  • Monitor slow pull reqs
  • Keep track of your backlog
  • Monitor community engagement
slide-53
SLIDE 53

Backlog

http://ghtorrent.org/pullreq-perf/

slide-54
SLIDE 54

Slow pull reqs

http://ghtorrent.org/pullreq-perf/

slide-55
SLIDE 55

Community engagement

http://ghtorrent.org/pullreq-perf/

slide-56
SLIDE 56

Monitoring with GHTorrent

http://ghtorrent.org/

slide-57
SLIDE 57

Monitoring with GHTorrent

http://ghtorrent.org/

slide-58
SLIDE 58

Monitoring with GHTorrent

http://ghtorrent.org/

slide-59
SLIDE 59

Monitoring with GHTorrent

http://ghtorrent.org/

slide-60
SLIDE 60

Monitoring with GHTorrent

http://ghtorrent.org/

slide-61
SLIDE 61

Monitoring with GHTorrent

http://ghtorrent.org/

slide-62
SLIDE 62

Monitoring with GHTorrent

http://ghtorrent.org/

slide-63
SLIDE 63

Contributors

slide-64
SLIDE 64

Minimize friction

slide-65
SLIDE 65

Contributors

1.Obey the guidelines (when available) 2.Invest time to learn the tools 3.Keep it short, hot and isolated

slide-66
SLIDE 66

@gousiosg

slide-67
SLIDE 67

There%is%more%to%Scrum%than%Scrum%

Bianca%Griffioen!

bgriffioen@vxcompany.com! h4ps://nl.linkedin.com/in/biancagriffioen! @BiaGrif! 06@21506814!
slide-68
SLIDE 68
slide-69
SLIDE 69

Being%with%several%people%in%one%room%is%not%the%same%as%being%a%team% Bruce%Tuckman%–%%Stages%of%group%development%

Forming! Storming! Norming! Performing! Adjourning!

slide-70
SLIDE 70
slide-71
SLIDE 71

Two!types!of!Scrum!Master! ! the!Scrum!Master!who!guides!the!Scrum!process! ! the!Scrum!Master!who!guides!the!Scrum!process!and!works!with!the!team!

  • n!items!of!the!Sprint!Backlog!

! Scrum!Master!has!to! ! have!good!communicaQon!skills! ! have!organizaQonal!awareness!and!sensiQvity! ! be!able!to!be!a!servant!leader! ! …!understand!Scrum!! !

A%Scrum%Master%does%not%need%to%have%any%special%skills%(1)%

slide-72
SLIDE 72

Scrum!Master!has!many!different!stances! ! Coach! ! Teacher! ! Mentor! ! Advisor! ! Servant!Leader! ! Facilitator!

A%Scrum%Master%does%not%need%to%have%any%special%skills%(2)%

slide-73
SLIDE 73
slide-74
SLIDE 74

Not%every%organisaEonal%culture%is%“fit”%for%Scrum% Schneider%Culture%Model%

CulQvaQon! CollaboraQon! Control! Competence!

reality!
  • riented!
possibility!
  • riented!
people!
  • riented!
(personal)! company!
  • riented!
(impersonal)! we&succeed&by& working&together& we&succeed&by&growing& people&who&fulfill&our&vision& we&succeed&by&ge8ng& and&keeping&control& we&succeed&by& being&the&best& affiliaEon% teams% partnership% diversity% synergy% egalitarian% trust% involvement% interacEon% security% power% standardizaEon% predictability% stability% process% hierachical% systemaEsm%
  • rder%
certainty% efficiency% achievement% experEse% craLmanship% meritocracy% be%the%best% creaEvity% excellence% professionalism% autonomy% purpose% faith% growth% dedicaEon% evolvement% values% subjecEvity% humanism% creaEvity%
slide-75
SLIDE 75

Dutch!soccer!team:! h4p://www.goal.com/nl/news/7131/ek@2016/2014/10/10/5173984/in@beeld@ nederland@kazachstan/netherlands@kazakhstan@euro@2016@qualifier@10102014!! ! Inspector!Gadget:!tohruichi.deviantart.com! ! Culture:! h4p://www.yourarQclelibrary.com/culture/culture@the@meaning@ characterisQcs@and@funcQons/9577/!!

Pictures%