Skip to content

Commit 528568f

Browse files
committed
Fixing formatting
1 parent 274909b commit 528568f

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

website_and_docs/content/blog/2025/selenium-community-live-episode5.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,21 +22,21 @@ While many discussions around open source focus on code contributions and techni
2222

2323
### What motivates Open Source contributors?
2424

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.
2626

2727
Ashley shares her journey with Selenium, highlighting how the warm, caring community has helped her build genuine friendships and good memories.
2828

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
3030

3131
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.
3232

3333
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
3535
- Managing continuous integration (CI) pipelines
3636
- Handling legal or financial aspects
3737
- Organising conferences or community events
3838

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.
4040

4141
A huge spectrum of motivators drives people’s behaviour and keeps the open source project breathing and growing.
4242

@@ -60,20 +60,23 @@ She recounts a meaningful interaction at a conference where a newcomer thanked h
6060
This indicates that motivation in open source is ever evolving with experience and roles within the community.
6161

6262
### 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.
6465
Ashley shares her first experience receiving a non-constructive code review and emphasises the importance of kindness and clarity in feedback:
6566
"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
6667
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.
6768

6869
### Inclusivity
70+
6971
Ashley distinguishes between mentorship and sponsorship as two pillars of inclusion:
7072
- Mentorship: Providing advice, guidance, and support to help someone grow and navigate the community.
7173
- Sponsorship: Actively advocating for someone, opening doors, and recommending them for opportunities
7274

7375
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.
7476

7577
### 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:
7780
- Be kind to yourself and reframe negative thoughts. Add "yet" to statements like "I don’t know how to do this... yet."
7881
- Recognize that many others share the same fears and questions.
7982
- Build a support network of trusted friends, mentors, and peers who understand your journey.

0 commit comments

Comments
 (0)