You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website_and_docs/content/blog/2025/selenium-community-live-episode5.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,21 +22,21 @@ While many discussions around open source focus on code contributions and techni
22
22
23
23
### What motivates Open Source contributors?
24
24
25
-
Ashley’s LinkedIn states that “My driving principle is simple: people first” and building on that, Ashley and Puja both highlight that open source is "by the community, for the community," where collaboration and human connections are foundational motivating factors for them.
25
+
Ashley’s LinkedIn states that “My driving principle is simple: people first” and building on that, Ashley and Puja both highlight that open source is "by the community, for the community," where collaboration and human connections are key motivating factors for them.
26
26
27
27
Ashley shares her journey with Selenium, highlighting how the warm, caring community has helped her build genuine friendships and good memories.
28
28
29
-
"In the end, do people really remember what we build? They're going to remember how we made them feel." — Ashley Hunsburg”
29
+
"In the end, do people really remember what we build? They're going to remember how we made them feel." — Ashley Hunsburg
30
30
31
31
Ashley states that for her, a main motivational factor is community, and what she thinks drives people is the altruistic purpose of giving back to the community beyond their organisation and serving a great purpose. Accordingly to Ashley, motivation drives behaviour, and if you have clear motivation, that will drive your place in the community in the long run.
32
32
33
33
Beyond altruism, Puja thinks there is a diversity of motivators, emphasising that contributions extend far beyond code. Contributions might include:
34
-
-Helping with documentation
34
+
- Helping with documentation
35
35
- Managing continuous integration (CI) pipelines
36
36
- Handling legal or financial aspects
37
37
- Organising conferences or community events
38
38
39
-
These roles are often in the spotlight but critical to the health and growth of open source projects.
39
+
These roles are often not in the spotlight but critical to the health and growth of open source projects.
40
40
41
41
A huge spectrum of motivators drives people’s behaviour and keeps the open source project breathing and growing.
42
42
@@ -60,20 +60,23 @@ She recounts a meaningful interaction at a conference where a newcomer thanked h
60
60
This indicates that motivation in open source is ever evolving with experience and roles within the community.
61
61
62
62
### Handling Conflict in Open Source
63
-
Both Ashley and Puja acknowledge that interactions on platforms like GitHub or chat channels can include harsh or unexpected comments, or the project itself can have some differences of opinion. This difference of opinion and thought diversity is what makes the group awesome, but certain situations need to be resolved with care..
63
+
64
+
Both Ashley and Puja acknowledge that interactions on platforms like GitHub or chat channels can include harsh or unexpected comments, or the project itself can have some differences of opinion. This difference of opinion and thought diversity is what makes the group awesome, but certain situations need to be resolved with care.
64
65
Ashley shares her first experience receiving a non-constructive code review and emphasises the importance of kindness and clarity in feedback:
65
66
"Be kind, but clear. Clear is kind. You don't have to be nice, but be clear about what happened, why, and how to improve." — Ashley Hunsburg
66
67
Effective conflict resolution involves open questions, understanding the intent, and focusing on shared goals. It’s important to remember that conflicts are natural in any group, but they can be handled constructively with the key focus being the what is important for the situation. It is also essential to make sure an open source project has a code of conduct that is implemented in such situations and that the community is aware they have a safe space to report their issue and that they will be heard.
67
68
68
69
### Inclusivity
70
+
69
71
Ashley distinguishes between mentorship and sponsorship as two pillars of inclusion:
70
72
- Mentorship: Providing advice, guidance, and support to help someone grow and navigate the community.
71
73
- Sponsorship: Actively advocating for someone, opening doors, and recommending them for opportunities
72
74
73
75
Ashley further discussed that inclusivity needs to be beyond code. Such as ensuring inclusive language and removing any barriers of entry for new contributors. The key focus should be on building an inclusive environment and creating a welcoming space for new contributors and the community.
74
76
75
77
### Overcoming Impostor Syndrome
76
-
Impostor syndrome is a common challenge for developers, especially when engaging in large, visible open-source projects. Ashley shares candidly about her own struggles and offers practical advice:
78
+
79
+
Impostor syndrome is a common challenge for developers, especially when engaging in large, visible open-source projects. Ashley shares candidly about her own experience and offers practical advice:
77
80
- Be kind to yourself and reframe negative thoughts. Add "yet" to statements like "I don’t know how to do this... yet."
78
81
- Recognize that many others share the same fears and questions.
79
82
- Build a support network of trusted friends, mentors, and peers who understand your journey.
0 commit comments