diff --git a/content/community/.DS_Store b/content/community/.DS_Store index b759a6d..d896acd 100644 Binary files a/content/community/.DS_Store and b/content/community/.DS_Store differ diff --git a/content/community/_index.md b/content/community/_index.md index ead77b8..f488ce1 100644 --- a/content/community/_index.md +++ b/content/community/_index.md @@ -3,48 +3,11 @@ title: "Community Guide" shortcutDepth: 2 --- -{{< notice warning >}} -This is a draft document. -{{< /notice >}} - -Welcome to the Community Guide! Here you will find useful resources that will help you get familiar with the Scientific Python community. - -## Community interviews - -Meet some of the members of the Scientific Python community. - -{{< youtube page="melissa-webber" levelOffset=3 >}}{{< /youtube >}} - -{{< youtube page="dan-schult" levelOffset=3 >}}{{< /youtube >}} - -{{< youtube page="alex-desiqueira" levelOffset=3 >}}{{< /youtube >}} - -{{< youtube page="kira-evans" levelOffset=3 >}}{{< /youtube >}} - -{{< youtube page="ross-barnowski" levelOffset=3 >}}{{< /youtube >}} - -{{< youtube page="isabela-presedo" levelOffset=3 >}}{{< /youtube >}} - -{{< youtube page="pamphile-roy" levelOffset=3 >}}{{< /youtube >}} - -## Join the community - -Scientific Python is community driven since projects are developed and maintained by open source communities. This is why we are looking for ways to expand our community in a welcoming and inclusive way. We have several ways for you to join us: - -### Discussions - -Join the discussion on our [Discord server](https://discord.gg/vur45CbwMz) and on [Discourse](https://discuss.scientific-python.org). We want everyone to share their perspective with all the members of our community! - -### Social media - -Follow us on our social media channels and share our content with the community! - -![socials youtube](icons/youtube_icon.svg) [ScientificPython-org](https://www.youtube.com/ScientificPython-org) - -![socials twitter](icons/twitter_icon.svg) [@scientific_py](https://twitter.com/scientific_py) - -![socials facebook](icons/facebook_icon.svg) [scientific.python](https://www.facebook.com/scientific.python) - -![socials instagram](icons/instagram_icon.svg) [scientific.python](https://www.instagram.com/scientific.python/) - -![socials tiktok](icons/tiktok_icon.svg) [@scientific.python](https://www.tiktok.com/@scientific.python) +Welcome to the Community Managers Guide! Here you will find useful resources that will help you foster your community better. + +- [Community Manager Role]({{< relref "/contributors/role" >}}) +- [Skills and Techniques]({{< relref "/contributors/skills" >}}) +- [Community Meetings]({{< relref "/contributors/community-meetings" >}}) +- [Community Outreach]({{< relref "/contributors/community-outreach" >}}) +- [Onboarding]({{< relref "/contributors/onboarding" >}}) +- [Project Management]({{< relref "/contributors/project management" >}}) diff --git a/content/community/alex-desiqueira.md b/content/community/alex-desiqueira.md deleted file mode 100644 index a901cbe..0000000 --- a/content/community/alex-desiqueira.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Alex de Siqueira" -about: "Alex de Siqueira from Scikit-image talks about how he started contributing to the Scientific Python community and how he became a maintainer for Scikit-image. " -youtube_id: yd03a_gsN7I ---- - -Transcript. diff --git a/content/community/community-meetings.md b/content/community/community-meetings.md new file mode 100644 index 0000000..3712efe --- /dev/null +++ b/content/community/community-meetings.md @@ -0,0 +1,70 @@ +--- +title: "Community Meetings" +--- + +## How to initiate a community meeting? +- Before starting the meeting, having a few items and discussion points in the agenda will help kick-start the meeting. These discussion points could be a mix of: +- Issues or PRs from the GitHub repositories which need attention +- Announcing any upcoming events/conferences to check if someone is going to attend them or is planning to +- Important updates: + - These could be recent releases/new feature additions + - Addition/changes in the maintainer/contributor team + - Convergence of an ongoing discussion - a summary of how the community reached a decision + - Anything important which needs to be brought up before the community + - Let everyone know that the meeting is governed by a CoC + +## Ice-breakers +- Ice-breakers are usually effective when the participants are not familiar with each other +- Apart from the general introduction, which is usually name and role, it’s effective to add a fun question (generally non-technical) to ask around; these are: + - Favourite song, movie, dish, sport, game, tourist spot etc. + - If you could teach the world one thing, what would it be? + - What’s one interesting fact about yourself? + +## How to address any critical issues in the project/community +- Sometimes, there are certain matter which needs to be brought up before the community for a more open and inclusive discussion +- This helps in taking into account various perspectives from the community and choosing a solution which is in the best interest of the community + +## How to keep the conversation going? +- Occasionally, there are situations when the conversation during a community meeting dies, and it feels like you’re in a graveyard 🪦 + - Having a set up of backup discussion points can help remove the awkward silence + - Going around in the audience to ask if they have something interesting to share with the community + - What projects are they working on? + - Something they learned which could be shared with the community + - Asking around if the attendees need any help + +## How to conclude the meeting successfully +- The meeting should end on a positive note - if there has been any heated discussion/arguments, try to conclude before the end. And generally, in the end, you should: + - Conclude important points + - Revise tabled items - which were supposed to be discussed but didn’t get time + - Tell them about the next meeting + +## How to run office hours? +- Office hours are a great way to invite the community and answer their questions, guide them, help them understand any specific about your OSS project etc. + - Usually, the structure of office hours is open, but there are certain tips which could make it run smoother; they are: + - Greet and acknowledge every participant during the office hours + - Try to answer at least 1 question from everyone + - Maintain a document so that everyone can jot down their questions, so it’s easier to go through them + - Invite them to the community meetings for broader discussions + +## How to take meeting notes? +- Every community meeting should have some form of public record which can be stored as an archive - taking meeting notes is one way to do it. There are several ways to take notes efficiently, which is helpful for the community + - Record the essential things, decisions, and resolutions that were discussed during the meeting + - Writing cues during the meeting and then converting them into proper sentences is a helpful thing to do when you’re moderating/running the meeting + - Try to have a TL;DR section at the top - this would help the reader to decide if they want to dive into the full notes or not + - Example at: https://zarr.dev/community-calls/2023/2023-05-03.html + +## Some tips for your meetings + +- Make time for demos/showcases/presentation + - The community members are always looking for exciting/innovative ways to use OSS projects in their workflow, and making time to showcase the work is a good element of a community meeting + - The demos/showcases could be - how your project is used to solve a problem in a specific domain +- Make time for newcomers + - New contributors or newcomers are the users who have the potential of becoming future maintainers and helping them in the initial phase is beneficial for both the project and the individual and is in the spirit of open-source + - Having a dedicated time slot for the newcomers to help them +- Make community meetings accessible to the broader community + - Take into account community members in different time zones, differently abled, unavailability etc. + - Take notes and upload them to the website + - Record the meeting + +## Meeting templates (TODO) +[NumPy Community Meeting template](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg) \ No newline at end of file diff --git a/content/community/community-outreach.md b/content/community/community-outreach.md new file mode 100644 index 0000000..8e7a191 --- /dev/null +++ b/content/community/community-outreach.md @@ -0,0 +1,47 @@ +--- +title: "Community Outreach" +--- + +# Community Outreach + +## Outreaching to Social Media +Use various social Media channels for outreach: + - Twitter: + - Utilize hashtags relevant to the scientific Python community to increase visibility. + - Engage with users by responding to questions, sharing resources, and participating in discussions. + - Retweet and mention influential users and organizations to foster connections. + - Share updates on project releases, new features, and bug fixes. + - Highlight community contributions and achievements. + + - LinkedIn: + - Create a LinkedIn group for the project to facilitate networking and discussions among professionals. + - Share project updates, news, and job opportunities. + - Encourage community members to share their experiences and insights related to the project. + - Connect with other professionals and organizations in the scientific Python field. + +## Tools for community outreach(TODO) + +## Speaking at Conferences and Events: + - Submit proposals to relevant conferences, emphasizing the project's unique features and benefits. + - Prepare engaging presentations that demonstrate the project's capabilities and use cases. + - Provide live demos or tutorials to showcase the project in action. + - Connect with attendees during and after the event, answer their questions, and collect feedback. + +## Teaching Tutorials + - Organize regular online tutorials or sprints to educate the community about using the project. + - Cover various skill levels, from beginners to advanced users. + - Provide clear documentation and code examples. + - Encourage community members to share their own tutorials and best practices. + +## Writing Blog Posts: + - Keep the community updated on important news, such as project milestones, partnerships, and funding. + - Announce major releases, highlighting new features and improvements. + - Share technical insights, tips, and tutorials related to the project. + - Recognize and appreciate community contributors through dedicated blog posts. + +## Creating content + - Create video tutorials, screencasts, or live coding sessions to demonstrate the project's usage. + - Develop interactive Jupyter notebooks showcasing practical applications. + - Produce podcasts or interviews with community members or domain experts. + - Collaborate with other scientific Python projects for joint content creation, such as tutorials or blog posts. +- Create illustrations on how your project works: https://github.com/zarr-developers/zarr-illustrations-falk-2022 \ No newline at end of file diff --git a/content/community/dan-schult.md b/content/community/dan-schult.md deleted file mode 100644 index ec730e7..0000000 --- a/content/community/dan-schult.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Dan Schult" -about: "Dan Schult from NetworkX talks about how he joined the Scientific Python community and help it grow through his work at NetworkX. " -youtube_id: mmrFrakXuJc ---- - -Transcript. diff --git a/content/community/icons/.DS_Store b/content/community/icons/.DS_Store deleted file mode 100644 index 5008ddf..0000000 Binary files a/content/community/icons/.DS_Store and /dev/null differ diff --git a/content/community/icons/facebook_icon.svg b/content/community/icons/facebook_icon.svg deleted file mode 100644 index 80dcf0b..0000000 --- a/content/community/icons/facebook_icon.svg +++ /dev/null @@ -1 +0,0 @@ - diff --git a/content/community/icons/instagram_icon.svg b/content/community/icons/instagram_icon.svg deleted file mode 100644 index 02825f6..0000000 --- a/content/community/icons/instagram_icon.svg +++ /dev/null @@ -1,95 +0,0 @@ - - - - diff --git a/content/community/icons/tiktok_icon.svg b/content/community/icons/tiktok_icon.svg deleted file mode 100644 index 9a968bc..0000000 --- a/content/community/icons/tiktok_icon.svg +++ /dev/null @@ -1,74 +0,0 @@ - - diff --git a/content/community/icons/twitter_icon.svg b/content/community/icons/twitter_icon.svg deleted file mode 100644 index b7ca68c..0000000 --- a/content/community/icons/twitter_icon.svg +++ /dev/null @@ -1 +0,0 @@ - diff --git a/content/community/icons/youtube_icon.svg b/content/community/icons/youtube_icon.svg deleted file mode 100644 index 327e6c5..0000000 --- a/content/community/icons/youtube_icon.svg +++ /dev/null @@ -1 +0,0 @@ - diff --git a/content/community/isabela-presedo.md b/content/community/isabela-presedo.md deleted file mode 100644 index 24d74b8..0000000 --- a/content/community/isabela-presedo.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Isabela Presedo-Floyd" -about: "Isabela Presedo-Floyd from Quansight talks about the accessibility, community, and UX/UI work that she has been doing in open source projects like Spyder and JupyterLab. " -youtube_id: hwbrclfpO2U ---- - -Transcript. diff --git a/content/community/kira-evans.md b/content/community/kira-evans.md deleted file mode 100644 index e16d1f4..0000000 --- a/content/community/kira-evans.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Kira Evans" -about: "Kira Evans from the Napari Project talks about how she joined the Scientific Python community and became a maintainer. " -youtube_id: tqDxGxCDfKU ---- - -Transcript. diff --git a/content/community/melissa-webber.md b/content/community/melissa-webber.md deleted file mode 100644 index 0ef2d20..0000000 --- a/content/community/melissa-webber.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: "Melissa Weber Mendonça" -about: "Melissa Weber Mendonça from NumPy talks about how she joined the Scientific Python community, why she loves it, and some of the challenges she has faced. " -youtube_id: 7nD64R-hPoA ---- - -Hello everyone, I'm Juanita welcome to the Scientific Python interview! Today we have Melissa from NumPy. She is an applied mathematician and she is also a former university professor who turned into a software engineer. She has been involved with the Brazilian Python community for some time and she has focused on outreach and education. Right now she's working at Quansight developing open source software and she is also the maintainer for NumPy so thanks for being with us Melissa, can you introduce yourself? - -Thanks Juanita, so yes I am based in Brazil and I have my background in mathematics but right now I'm working on Numpy specifically focusing on documentation, community and a little bit of code. I actually... As I came from a mathematics background and an education background, working with documentation is something that is really close to my heart and I like doing that a lot just because I like teaching people and writing technical documentation seems like a good fit for me. -Yeah it does sound like it. I really love writing documentation as well. - -So so what drove you to contribute to open source and and what was your first open source contribution? So yeah, I had been around open source for about 10 years since I started my phd and started investigating different ways of doing open science and started investigating ways of not using um software you know using open source software to do research and around that time Python was exploding around scientific communities and so I ended up learning Python and understanding that the community was actually larger than the language in the sense that um I felt welcomed in the community and so I stuck around. However, I didn't think I was fit for contributing for a long time, I think I had a lot of other responsibilities and work and family and being a mom and not having that much free time. I just felt like I didn't have the necessary commitment to contribute to open source and so my first contributions were actually um already tied to my recent work at Quansight. So I started working at Quansight around two years ago and that's when I actually started contributing. - -How did you end up becoming a maintainer and and what do you think was the greatest challenge to to become that? -I think because of the transition from academia to developer I call myself a junior senior. I had to relearn a bunch of stuff even though I had a lot of experience in academia and so figuring out the right processes and workflow for software development were sometimes a challenge but at the same time there's also the challenge of people and the dynamics of the communities and understanding how people decide things in an environment that is sometimes chaotic like an open source community where you don't necessarily have rigid structures and processes and just understanding every little piece of the project. And when you maintain a project obviously there are smaller pieces that you're kind of comfortable with and others that you're not, but sometimes you're required to do code review or to guide people through a contribution and you have to figure things out as you go and so this has been super fun but at the same time it can be uh it can be very challenging. - -Yeah it sounds like it. So so what do you think you enjoy the most about working in open source? I think one of the things that drove me to open source in the first place and that makes me stick around is the community. Like I said before and I really like working with people and so even though we do have that thought sometimes that developers like computers and they don't necessarily like other people. I don't think that's true and I think there's no way to have a successful open source project if you're not able to communicate, if you're not able to empathize and to be able to just reach other people. I think it's it's very much a people-oriented job or at least some parts of it are and so um I think working at NumPy has been super fun because the people are so nice and it's been wonderful learning with them and so as I do documentation or you know code review or I have questions, they are always so open to answering questions, to mentoring, to teaching, and i think that's a very valuable thing just having the experience of being near people um who can teach you stuff is wonderful and so I think that's the part that I like the most. - -That sounds great ! So now that you've talked about documentation and community um I would like you to maybe talk about the other contributions that people can make to open source without much coding experience, which I'm assuming it's like a big questions for a lot of people. - -Yeah so I think there's of course there is a focus on code when you talk about open source projects because ultimately there's code um at the core of it, but there's just so much more that needs to happen for an open source project to to be successful. And so i think recently people have started to realize that one person cannot do everything and so in the past it was common to expect of maintainers, especially code maintainers, that they would also do all other sorts of things like documentation, community work, translations and graphic design and that's how we end up with like really ugly logos and uh people who don't know how to write technical documentation end up doing that because there's no one else to do it. And sometimes we say that people don't do that because they don't want to, but that's because we're only looking at the people who write code and we're not giving space for people who like writing documentation or doing community work or doing design to approach these open source projects. So I think one of the things that we've been working towards is improving uh not only diversity inclusion and equity inside these projects (and this is part of a recent czi grant that NumPy, SciPy, Matplotlib and pandas have just received to work on diversity inclusion and equity in our projects), but it's also a part of diversifying the past for contribution and making sure that people from different backgrounds and from different uh life histories and that have different levels of knowledge can also contribute. So it doesn't have to be just code it can be just organizing, community, translation, it can be technical writing, it can be design, it can be website development. There's there.. I think we're starting to realize in several different projects and communities that a lot of thing has to happen for a successful project to move forward and to be sustainable. - -Yeah I think that that pursuit of diversity it's really necessary in open source because like many skills are needed for for an open source project to be successful so I think it's really great that you you're also part of like this "chasing people" with other skills. So I also wanted to know what are the things that you find challenging about the open source community and what would you like it to see go in the future? - -Yeah so I think that's very tied to the previous question and we we want more people to be involved in open source but it's not just all more of the same people; we also want to make sure that different groups of people especially what we call today underrepresented groups in open source or in technology or in STEM have access to these projects and can also contribute their own thoughts and knowledge and experience to these projects. And so I think there's a real problem for example, because a lot of these open source projects are volunteer based uh it is clear that not everyone has the financial security, or the free time, or the life organization to be able to dedicate their free time to open source to volunteer and do software development for many hours a week. And so this ends up selecting a group of people that we know uh it's it's um a homogenous group of people, so we would like to see more people from the global south, we would like to see more people from indigenous communities, we would like to see more people of color, we would like to see more different people participating in open source; and so um I think the opportunity to invest in open source as professional development and making sure that people are actually paid for their work pay for their labor is something that has a lot of potential in terms of improving our communities and so I think the challenge of that is finding funding but also rationalizing and deciding the path forward for each community and deciding uh where people want to go. um yeah - -Yeah I think diversity would be like a very good thing for for our open source community and I think those um like mentoring program programs I that you work at I think they're going to take us there like soon so I really i'm really grateful that you're working on that. Okay so so one last question: can you give some advice to someone that wants to contribute to open source? - -I think the basic advice that everyone gives and, I don't know if it's correct or not, is to scratch your own itch, which means find a project that you're interested in that will maybe help you do your work better, or that is maybe something that you're already familiar with and that interests you that actually drives you to contribute and to offer that time to your open source project, and so find something that really sparks you know sparks joy um and this will make you feel more comfortable and this will also make you feel more motivated to contributing. On the other side i think it's also important to find ways of communicating with people from the projects and when I was a professor I used to tell my students: "you have to have study groups, you have to get together and do things together and feel empowered as a group and this will help you move forward because if you have a question you have a colleague that might help you and you will support each other" and the same goes for open source development. If you feel like other people are in the same situation as you and they are also learning and they are also needing help, it's usually easier not to feel that isolated. So communicating with other people who are also working in the project, both in a peer group or in a mentor relationship, I think is super important if you have that opportunity. So I know that a few projects at least have you know slack spaces, or discord spaces, or forums where you can reach out to other people and ask questions and and maybe work together and I think that's super important; so that's my advice. - -Thank you, I think those were two great advices: so look for the project that is right for you and look for the best way of communicating with people from projects that you are working on. I think that's all for today and thank you so much for joining us um bye bye and welcome to the Scientific Python community! diff --git a/content/community/onboarding.md b/content/community/onboarding.md new file mode 100644 index 0000000..6eb86e0 --- /dev/null +++ b/content/community/onboarding.md @@ -0,0 +1,12 @@ +--- +title: "Onboarding" +--- + +{{< notice warning >}} +This is a draft document. +{{< /notice >}} + +- Organizing sprints + - Organising sprints are an excellent way to invite new collaborators, solve issues, gather contributions and broaden the project community. Some helpful tips for organising a sprint efficiently: + - Have a list of issues from the issue tracker that can be worked on. The issues should have a mix of code (bugs, features, fixes) and no-code (documentation) tasks so that they can accommodate a diverse set of participants +- Handling a storm of new contributors during peak season (GSoC, Outreachy, GSOD etc.) \ No newline at end of file diff --git a/content/community/pamphile-roy.md b/content/community/pamphile-roy.md deleted file mode 100644 index 3c596de..0000000 --- a/content/community/pamphile-roy.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Pamphile Roy" -about: "Pamphile Roy talks about how he became a maintainer for SciPy and shares the work he has been doing with the Scientific Python project! " -youtube_id: RwBGDqN4AHk ---- - -Transcript. diff --git a/content/community/project-management.md b/content/community/project-management.md new file mode 100644 index 0000000..9efbe64 --- /dev/null +++ b/content/community/project-management.md @@ -0,0 +1,24 @@ +--- +title: "Project Management" +--- + +## Project management + +As a community manager, you might need to onboard contributors who may not contribute in technical ways. + +* Send a personalized welcome message expressing gratitude and introducing the project. +* Provide an overview of the project's mission, values, and community culture. +* Highlight non-technical contribution opportunities like documentation, user support, translations, design, and community management. +* Create clear contribution guidelines with step-by-step instructions and templates. +* Maintain regular communication to share updates and opportunities. +* Recognize and appreciate all contributions, both technical and non-technical. +* Foster a welcoming and inclusive community environment. +* Ensure adherence to the project's code of conduct. + +### OSS management (TODO) +- Overview of issues and PRs among several repositories + - Reviewing PRs or assigning reviewers to the PRs + - Solving the issues/responding to the issues + - Responding - to maintain communication with the author + - Closing stale PRs and old issues + - Labelling issues \ No newline at end of file diff --git a/content/community/role.md b/content/community/role.md new file mode 100644 index 0000000..89d90d5 --- /dev/null +++ b/content/community/role.md @@ -0,0 +1,29 @@ +--- +title: "Community Manager Role" +--- + +## Who’s a community manager? +A community manager for an Open Source scientific Python project is a dedicated and enthusiastic contributor who plays an important role in building and nurturing a thriving community. They act as a bridge between the project and its community members, creating an inclusive and collaborative environment. +This person has a strong understanding of scientific Python and open source principles. They actively engage with community members, address their needs, offer support, and encourage their active participation. By organizing community events, facilitating discussions, and promoting knowledge-sharing, they ensure that the project's community remains vibrant and connected. The community manager is passionate about Python programming and committed to promoting diversity and inclusion in the scientific open source software community. + +## What is the role of a community manager? + +- Designate time for engaging community. (Social media, hosting events) +- Empowering others to become leaders.(Setting example, having initiatives) +- Guidance for conflict resolution. +- Making the community "Welcoming". (Having resources that make people want to stay, Good communication) +- Being a communication channel between users and developers (Understanding the user's needs to be able to participate in the road map.) + +## Why do you need a community manager? + +1. A community manager acts as a bridge between the project and its community members. They facilitate communication, engagement, and collaboration, ensuring that users feel heard, valued, and supported. By fostering a sense of belonging and inclusivity, a community manager helps to create a strong and loyal user community. +2. A community manager plays a critical role in building and sustaining an active and vibrant community around the project. They organize and promote community events, facilitate discussions, and encourage knowledge-sharing. This helps to foster connections, drive participation, and create a positive and collaborative atmosphere within the community. +3. A community manager serves as a trusted resource for community members, offering support, answering questions, and resolving conflicts. They act as a point of contact, providing guidance, feedback, and assistance when needed. +4. A community manager helps to promote the project's values, goals, and mission. They advocate for the project and its benefits, both within the existing user community and to potential new users. This can lead to increased visibility, growth, and adoption of the project. +5. A community manager plays a crucial role in gathering user feedback and insights. They act as the voice of the community, conveying user needs, preferences, and concerns to the project team. + +## How to find the best community manager for your project? (TODO) + +- Find what do you need exactly (Determine scope) +- Understanding of science (how much understanding of the domain area) +- Word of mouth for spreading the word diff --git a/content/community/ross-barnowski.md b/content/community/ross-barnowski.md deleted file mode 100644 index 9ecd8d9..0000000 --- a/content/community/ross-barnowski.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Ross Barnowski" -about: "Ross Barnowski from NumPy and NetworkX talks about how he helps grow the Scientific Python community through his work at these two projects. " -youtube_id: egt_LkiLoUg ---- - -Transcript. diff --git a/content/community/skills.md b/content/community/skills.md new file mode 100644 index 0000000..5a7a3a1 --- /dev/null +++ b/content/community/skills.md @@ -0,0 +1,52 @@ +--- +title: "Skills and Techniques" +--- + +The OSS Management Skills Wheel describes 24 skills, divided into 4 core competencies, used by OSS community managers. It was initiated by Inessa Pawson and Sanket Verma during the 2023 Scientific Python Project Developer Summit (Seattle, WA). + +**Interpersonal** +- Engagement +- Collaboration +- Moderation, mediation, and intervention +- Emotional integration +- Train and teach +- Mentoring +- Cultural competence +- Networking + +**Technical** +- Git and GitHub +- Dev tools +- PR and issues +- Triage + + +**OSS Management** +- Growth and sustainability +- Governance +- Meeting facilitation +- Program design +- Change management +- Record keeping +- Event planning +- Recruiting + + +**Communication** +- Content creation and curation +- Speaking and presenting +- Advocacy +- Social media + +**Other useful skills** + +- Scaffolding + - Removing barriers/making it easy for the new contributors to join - could like the scientific python guide here (https://learn.scientific-python.org/contributors/) + - Removing barriers/making it easy for the maintainers to work + - Removing barriers/making it easy for the users to discover the documentation/tutorials + - And removing barriers and helping wherever necessary +- Dealing with conflicts in the community + - Between developers/maintainers + - CoC enforcing +- How to gracefully exit a project for a maintainer - + - How a CM can help it onboarding the next maintainer \ No newline at end of file