Leading an Open Source Community
•Télécharger en tant que PPTX, PDF•
0 j'aime•507 vues
talking about improving leadership skills
![LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015
My name is Tessa. Hi!!!
College Instructor. Curriculum Developer.
Web Developer.
Snowboarder.
Love to Speak – Educate - Inspire
3](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (16)
Similaire à Leading an Open Source Community
Similaire à Leading an Open Source Community (20)
Plus de Tessa Mero
Plus de Tessa Mero (20)
Dernier
Dernier (15)
Leading an Open Source Community
- 1. Leading an Open- Source Project Developer Advocate for Joomla! @tessamero
- 2. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 My name is Tessa. Hi!!! College Instructor. Curriculum Developer. Web Developer. Snowboarder. Love to Speak – Educate - Inspire 3
- 4. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Open Source Enthusiast • Joomla contributor for 4 years • Joomla Leadership for 2 years • My roles in Joomla • Organizer of Joomla User Group Seattle & Seattle PHP User Group • Organizer of PNWPHP Conference (with Jeremy Lindblom, SHOUT OUT!) 3
- 5. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Summary • What is Joomla! • Community & Communication • Management/Representation • Behavior • Hiring/Firing Effectively • Encouragement • Dealing with Change • Preventing Burnout • Steps to Becoming a Leader 3
- 6. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 JOOMLA! • Fork of Mambo CMS in 2005 • Swahili for “All Together” (Jumla) • Free and Open Source Software • Created by over a dozen co-founders • No paid staff • 100% volunteers • 35 Million+ Downloads • Approx 9,500 Extensions for latest version • 65+ Teams in Organization 3
- 7. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Current Joomla! Structure 3
- 8. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Community & Communication Demonstrate leadership with communication and listening to your community 2
- 9. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Getting There (User to Leader) • User • Participation • Contributor • Leader (multiple meanings) • Being in an official leadership team • Leading a Team / Leading a Sub Team • Assisting with leading a team • Being a great example of a good community member 3
- 10. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Documentation & Transparency • Documentation of Processes • Transparency • Team Reports • Keep things as open as possible (no contract signing!) • Make it easy for newcomers to begin and grow! 3
- 11. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Communications • TRUST • Community Feedback • It’s OK to disagree! • Learn to compromise • Accept outside advice (3rd party) • Have Decision Making Processes • Ideas floating around endlessly – NOTY • Voting • Don’t shoot down ideas quickly • Give people a chance to speak 3
- 12. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Assume people mean well until proven otherwise. 3
- 13. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Mentoring • Help create future leaders • Train them • Delegate your work to others • Don’t make 1 person a single point of failure, train multiple people for the same roles • Encourage and be thankful. Empower people. (more on this later) 3
- 14. Why should we train and mentor contributors?
- 15. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 The Importance of Follow Through • Respect • Reputation • Trust • Help teammates follow through by staying organized and following up Wait, let me explain the next slide….don’t judge too quickly! =P 3
- 17. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Management/Representing The correct way to manage people and representing your community 2
- 18. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Representing Open Source • Be a good representative by exhibiting positive and good behavior internally and externally (social media) • Speak highly of others (and other Open Source) and don’t put down other people • Make newcomers feel welcome • Don’t wait for things to happen (maybe they are waiting on you?) • Have fallback plans on changes (if…then..) 3
- 19. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Invest in being motivated, not miserable 3
- 20. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Behavior Let’s be grown-ups! Oh, look, an ice-cream shop! 2
- 21. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Code of Conducts • My initial views on it back in 2012 • Why is it important? • Sense of safety for all • Increases diversity • Keep the COC simple • Representatives outside of Project • Why is it important? Code of conduct allows you to agree that you will be respectful and to cooperate with each other, and make others feel welcomed 3
- 23. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Dealing with Conflict • Try resolving 1 on 1 (don’t humiliate them in public) • Try using a mediator to resolve conflict • Let people know if they are making you feel uncomfortable or if they hurt you • DON’T HOLD GRUDGES (hardest one of all, since I have some…) • Don’t Blame OTHERS! • Accept fault and accept being wrong. It’s OK! 3
- 24. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Why can’t we all just get along?!!!??? How hard is it? 3
- 25. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Toxic Volunteers & Negativity • Stop the Gossip Train! • Don’t talk about people negatively • Get actual information before talking! • A great contributor/leader will NOT tolerate toxicity 3
- 27. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 What to do? • Don’t contribute to toxic behavior. That’s what they want. • First try to understand. Compromise • Listen – Reasons why people are upset • Alleviate situations – Don’t instigate! • Still doesn’t work? Document extremely bad behavior (insults, harassment, threats, etc) • Create a Ban process for different parts of the project if COC is violated 3
- 29. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Hiring and Firing Effectively We all know this is the toughest part of leadership! 2
- 31. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Interview Process • Call for Volunteers • Interview (Or Rejection Letter) • Hiring • Look for someone who is motivated and excited to get started • Willing to read documentation • Not afraid to ask questions • Training 3
- 32. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Firing Process • “Firing” is too strong… the real term is “Let them Step Down”. (unless there is a term) • Remind them they haven’t contributed in awhile • Give them a chance to continue their contributions (let them know it’s ok for breaks) • Let them know there is someone (or someone’s) willing to take over their role. • (It’s not a big deal. It’s OK to step down!! Please do if you don’t have the time! Please!) 3
- 33. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Encouragement Good job, want a cookie?????? 2
- 35. Remind people on how awesome they are. Your minute of time can make a positive impact.
- 36. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Positivity • Stay positive, even in extremely stressful situations • Helps make wiser decisions • Prevents you from immature behavior 3
- 37. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Team Building • May not always be “productive”. • The best thing out of team building? • Effective communication • See “emotions” in person • Collaborating more positively • Creating “New” things (like friendships, ideas, processes, etc) • Understanding each other better 3
- 38. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Dealing With Change Isn’t it easier if we keep everything the same? 2
- 39. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 And How? • Have things well planned out • Implement In SMALL STEPS! • Prevents community outrage • Prevents resignations from people that disagree with the change 3
- 40. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 My Response Timeline on Major Change Day 1: “WHAT? SERIOUSLY????” Day 5: “You’ve got to be kidding me. I can’t believe we are doing this” Week 2: “Okay, maybe we can do this. I’m feeling confident about it” Month 3: “Wow, this is amazing. Why didn’t we do this a long time ago?” 3
- 41. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Preventing Burn-out Careful, don’t jump into the hot flames! 2
- 42. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Make your priorities • Don’t choose open source over family • Focus on work. Then open source. It’s really easy to forget what your priorities are in life when open source is SO amazing 3
- 43. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 “Yes, yes, and yes!” • Don’t say “yes” to everything. This is how you overwhelm yourself with work. If you don’t have the time, be honest about it • Don’t start too many projects and leave it unfinished. Make priorities and focus on it • Learn to Delegate work • Don’t be afraid to step back or ask for help 3
- 44. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Steps to Becoming a Leader So you want to be a leader? Follow me!!!!!! 2
- 46. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 2015 Traits of Leaders • Demonstrating Confidence • Listening to the community • Making and Enforcing unpopular decisions • Real leaders listen. Gather information, wait for timely opening, and demand action • Keep a good reputation • Mentor people. Bring in new people • Demonstrate positivity everywhere (influencial) 3
- 47. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 20153 Leadership is not a popularity contest. It’s okay for people to disagree and not like you.
- 48. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 20153 Create a Culture where people respect each other
- 49. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 20153 What does it mean to be a leader in an open source project?
- 50. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 20153 “Honesty - people want to work with people they trust. They want someone with high values morals and integrity” -JessicaDunbar
- 51. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 20153 “It’s an opportunity explore ideas, solve your own problems at scale, and learn how little you know about some subjects” -KeithCasey
- 52. LEADING AN OPEN-SOURCE PROJECT – TESSA MERO - php[world] 20153 “Work with the community. When it fails, don't get disgusted at the failure; get involved and help solve the problem.” -CalEvans
Notes de l'éditeur
- It’s important to have a good community and to make the right choices being a leader. A good community will be a successful community. A failed community is a failed software. The goal of this presentation is to give you insights on how to become a better leader, or a better community member. I’m going to use the Joomla! Community as an example by sharing my experiences working with others.
- I’m Tessa! I’m a college instructor teaching web development at a college and currently doing curriculum development work. Previously, I spent many years as a web developer for a Ski & Snowboard company, which is how I discovered Joomla. While I was still in college learning how to code, I was hired at the company and needed a platform to begin working on. I found Joomla as a solution and was sent to a 2 day joomla training course in a live classroom with OSTraining and then sent to a Joomla Day conference in New york City. The rest is history. On my free time, during the winter, I love to snowboard. Since I worked at a Ski and snowboard company, I happen to be hooked up with all the gear I needed. I worked with a lot of semi professionals and had colleagues give me lessons in exchange for beer. I love speaking. I may not be the best speaker. I may not be the most confident speaker. But I am here because I love to educate and I love to inspire. If you see this as your dream to speak, I’d love to mentor you and help you become your dream.
- Started as a user, then participated in a team, and contributed, then applied to leadership positions.
- One of the most important things is documentation and transparency. It’s important to keep documentation of all your work flow processes to make it easy for people to adapt and get started. Transparency is key by keeping team reports and meeting notes public so people do not create rumors and false information about what is going on behind closed doors. I’ve seen this happen too many times in Joomla with particular teams not being transparent and how they end up being the bad guys. But over time I’ve seen a lot of teams, including a team I’m in, slowly make things more transparent. Trasnparency and having documented processes make it easy for newcomers to begin and grow within your community.
- Trust is a very important role in communicating. If you don’t trust them, they won’t trust you. Learn to trust people (of course until they’ve proven not to be trusted). Community feedback also plays a role in being trusted. Having the community as part of your decision making with feature changes or maybe changes in processes in the community could play a major role. Without trusting them, they won’t have trust in the project. It’s okay to disagree with people. It’s part of the culture of respect. Learn to act like an adult and compromise with others and listen to feedback. It’s okay to accept outside advice. This is something I do quite often. It doesn’t hurt to hear advice from people in other communities to see what they’d do in particular situations. Have decision making processes or else ideas will float around endlessly. Be very clear on your goals and ideas and have a timeline and a vote. With communication, it’s good to give people a chance to speak and not shoot ideas down so quickly. Good communication is key to a successful community.
- To be a great community member or being viewed as a leader in the community, you need to assume people always mean well. We are all here on good intentions and want to do great things for the open source project. Don’t jump to conclusions and think people are out to benefit themselves or their company. Don’t assume people are trying to “drain” the budget or do things to only help themselves. People spend many hours of their time and use up their vacation days from work to be here to make our open source projects better. Ask questions and learn to understand people.
- Mentor others. You can help create future leaders by mentoring and training them. Learn to delegate your work to others. Don’t make 1 person a single point of failure and train multiple people to understand the same roles. Encourage others and be thankful for the work they put in. Empower others to strive to do better.
- The whole point of mentoring contributors is so we can set a precedent on our future contributors and leaders of the project. Some of us won’t be around forever. Let’s keep our contributors generating and make our project more successful.
- Following through helps gain respect from others. Without following through, it can hurt your reputation. If you cannot follow through on something, it’s important to say something to your team and have someone take over your work. It’s okay to not follow through if you speak up about it. This also helps gain trust from others. You can help teammates follow through by staying organizes and following up with them.
- Don’t worry Nikki. I’m just as confused as you are. Let’s move on now….
- When you are representing open source, you need to be a good representative by exhibiting positive and good behavior both internally and externally. Most importantly on social media, whether it’s twitter, facebook, forums, or pubic mailing lists. Speak highly of others. Find the good things in people. Don’t put other people down. Speak well of other open source projects. We’re all working hard as communities doing good for the project. There is no need to put down other projects. We are all awesome. Make newcomers feel welcome. The more welcome they feel, the more likely they will stay in the community and stick around. Don’t wait for things to happen. Step up and take action when it’s necessary. Make sure you have fallback plans on major changes. Sometimes things don’t always work out.
- Invest in being motivated, not miserable. I’ve seen too many times where people will waste their time complaining and being miserable on social media. Spend your time being motivated. Spend your time talking about how you can help and how you can make a difference.
- It’s time that people start adjusting their behavior. Leaders should be setting examples of what respectful behavior is.
- Back in 2012, I used to think how ridiculous the code of conduct was. I’ve always been so used to sticking up for myself I always imagined that others should do the same thing. Now that I’ve read and heard so many stories of other people who were harassed, I understand how a COC could help with correcting the situation and making sure it doesn’t happen again. COC’s are important because it gives people a sense of safety, which in turn can help increase the diversity in the community. The document doesn’t need to be complex. It can be a short and simple document. There are open source code of conduct documents available online. Also, to make the COC process better, have representatives from outside of your project to help with making decisions. This is where Joomla made a mistake and has failed with a working process. Fortunately, we have a process that will be in place soon that will work within our newly transitioned organization. So I’m very happy for their hard work.
- This is how I feel a lot, especially in the last couple weeks of dealing with certain situations. As much as I want to punch someone in the face, we need to act like adults. We need to make mature decisions and do the right thing. If we acted childish and constantly fought everyone for every reason, it would spiral into a failed community.
- So, how do you deal with a jerk face?
- Remember, we all view the world differently and have different perspectives. You may see a situation as one way, while another person see’s it completely differently.
- How do you hire new contributors to join your team?
- This is my own little process
- This is my own little process
- Wait – It’s not over yet! It’s Okay to be thankful
- This is my own little process
- This is my own little process
- So what does it mean to be a leader or becoming a leader?