├── assets ├── X.png ├── X-white.png ├── linkedin.png ├── mastodon.png ├── linkedin-white.png └── mastodon-white.png ├── LICENSE.md ├── getting-started-volunteer.md ├── getting-started-participants.md ├── captains.md ├── docs ├── core_values.md ├── financial-aid-guidelines.md └── governance.md ├── README.md ├── navigators.md ├── djangonauts.md └── CODE_OF_CONDUCT.md /assets/X.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/djangonaut-space/program/HEAD/assets/X.png -------------------------------------------------------------------------------- /assets/X-white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/djangonaut-space/program/HEAD/assets/X-white.png -------------------------------------------------------------------------------- /assets/linkedin.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/djangonaut-space/program/HEAD/assets/linkedin.png -------------------------------------------------------------------------------- /assets/mastodon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/djangonaut-space/program/HEAD/assets/mastodon.png -------------------------------------------------------------------------------- /assets/linkedin-white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/djangonaut-space/program/HEAD/assets/linkedin-white.png -------------------------------------------------------------------------------- /assets/mastodon-white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/djangonaut-space/program/HEAD/assets/mastodon-white.png -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2024 Djangonaut Space 4 | Permission is hereby granted, free of charge, to any person obtaining a copy 5 | of this software and associated documentation files (the "Software"), to deal 6 | in the Software without restriction, including without limitation the rights 7 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 8 | copies of the Software, and to permit persons to whom the Software is 9 | furnished to do so, subject to the following conditions: 10 | 11 | The above copyright notice and this permission notice shall be included in all 12 | copies or substantial portions of the Software. 13 | 14 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 15 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 16 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 17 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 18 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 19 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 20 | SOFTWARE. 21 | -------------------------------------------------------------------------------- /getting-started-volunteer.md: -------------------------------------------------------------------------------- 1 | # I want to volunteer, where do I start? 2 | 3 | So you know what [we are about](README.md), you have read our [Code of Conduct](CODE_OF_CONDUCT.md), and you are interested in volunteering, so what now? First of all, thank you! Our community thrives because of people like you. 4 | 5 | ## Types of Volunteers 6 | There are a few ways to volunteer with this community: as a [Navigator](navigators.md), [Captain](captains.md), or Organizer. We have summarized those roles here as an overview but please read their detailed guidelines to get a more in-depth understanding of each. 7 | 8 | **Navigator:** 9 | - Navigators can expect to commit 3 hours of their time each week over the 8-week session. 10 | - This would involve showing up to our virtual meetings/co-working hours and assisting other members or helping out members in the discord channel. 11 | - More details: [Navigator Guideline](navigators.md) 12 | - Detailed guidance can be found in the [Navigator workbook](https://djangonaut.space/resource/navigator-workbook/) 13 | 14 | 15 | **Captain:** 16 | - Attend welcome and closing sessions and be available on discord. 17 | - Check-in with Navigators and Djangonauts regularly throughout the program. 18 | - Commit 2 hours a week for 8-weeks. 19 | - More details: [Captain Guidelines](captains.md) 20 | - Detailed guidance can be found in the [Captain workbook](https://djangonaut.space/resource/captain-workbook/) 21 | 22 | 23 | **Organizer:** 24 | - Responsible for organizing and leading meetings, update statuses on our website and GitHub, organization communication, Code of Conduct follow through, and recruiting volunteers. 25 | 26 | ## I want to volunteer, how do I sign up? 27 | There are a few things: 28 | 29 | 1. Check out our website for the latest information: [djangonaut.space](https://djangonaut.space) 30 | 2. [Subscribe to our 🗞️ newsletter!](https://buttondown.com/djangonaut-space) 31 | 3. Reach out to us and we can help you find your fit by emailing contact@djangonaut.space! 32 | -------------------------------------------------------------------------------- /getting-started-participants.md: -------------------------------------------------------------------------------- 1 | # I want to participate, where do I start? 2 | 3 | So you know what [we are about](README.md), you have read our [Code of Conduct](CODE_OF_CONDUCT.md), and you are interested in getting started, so what now? 4 | 5 | Because we are an inclusive community with a large range of skill levels we want to make sure we all have some understanding of a few points: Django, Python, Open Source Contributing, and Git. You aren't expected to be an expert in any of these but some knowledge will definitely help get you started. Please read the through the questions below to find a question that you can relate with to help you find your starting point. 6 | 7 | 8 | **What is Django/Python?** 9 | - If you haven't yet, you probably want to start with going over the [Django Girls Tutorial](https://tutorial.djangogirls.org/en/) to get familiar with Django, Python, and Git. If you have some experience in one but not all of these, maybe skim through the parts you are familiar with. 10 | 11 | **What is Git/GitHub?** 12 | - If you are unfamiliar with Git and GitHub, [this tutorial](https://docs.github.com/en/get-started/quickstart/hello-world) might be helpful. 13 | 14 | **What is Open Source Contributing?** 15 | - GitHub has created a great [Contributing Guide](https://opensource.guide/how-to-contribute/) to go over what it's about, the process, and best practices. We'd encourage you to read it over. 16 | - Django also has a [contributing tutorial](https://docs.djangoproject.com/en/dev/internals/contributing/). Going through this will make sure you're set up to tackle tickets. 17 | 18 | **What are the expectations of participants?** 19 | - Have good standing throughout the program and uphold the [Code of Conduct](CODE_OF_CONDUCT.md). 20 | - Attend weekly meetings to receive feedback and support. 21 | - A commitment of 4 hours a week over the course of 8-weeks. 22 | - For more details about being a participant, please read our [Djangonaut Guidelines](djangonauts.md). 23 | 24 | **I want to join, how do I sign up?** 25 | Check out our website for the latest information: [djangonaut.space](https://djangonaut.space) 26 | 27 | You should also [subscribe to our 🗞️ newsletter!](https://buttondown.com/djangonaut-space) 28 | -------------------------------------------------------------------------------- /captains.md: -------------------------------------------------------------------------------- 1 | ## Captain Guidelines 2 | 3 | A sustainable program requires a crew of people ensuring its success. Clearly defined 4 | roles which share responsibilities across a group help us to mitigate against the risk 5 | of burnout. While we want the program to be successful, we want everyone to be happy 6 | and healthy above all else, and our Captains our critical to this. 7 | 8 | Captains are community managers who coordinate the program, advise Navigators, and 9 | engage in periodic 1:1 sessions with Djangonauts. They keep the ship on course. :boat: 10 | 11 | 12 | ## Responsibilities and Expectations 13 | 14 | In this 8-week program, you will support Djangonauts and Navigators to have a successful 15 | experience. Detailed guidance about Captains can be found in the [Captain workbook](https://djangonaut.space/resource/captain-workbook/). 16 | 17 | 18 | - Your goal is to embody the inclusive warm community that we have at Django. This 19 | may include celebrating successes or sharing personal stories (humanising yourself and 20 | others). 21 | 22 | - Manage onboarding for Djangonauts with the program. Help set expectations and get them 23 | up to speed. 24 | 25 | - On Discord 1-2 hours a week to help connect others. 26 | 27 | - Set up 1:1 and attend sessions with Djangonauts every 2 weeks to offer support. 28 | This is optional for the Djangonauts, they do not have to use these. 29 | 30 | - Attend the program welcome and closing sessions. 31 | 32 | - Coordinate with program Navigators. Share feedback from your personal 1:1s with 33 | Djangonauts and help with the running of the program. 34 | 35 | - Make introductions to resources and people for the Djangonaut - this is sponsorship 36 | which is equally important as mentorship. 37 | 38 | - Help to build relationships amongst the group - this can be as simple as initiating 39 | conversations and sharing in Discord. 40 | 41 | As a rough guide, being a Captain should be roughly a 2 hour per week commitment for 8-weeks. 42 | Later in the program the time commitments may reduce as the Djangonauts should become 43 | more independent. There may also be a drop-off in the number of Djangonauts which would 44 | also reduce a Captain's time commitments. 45 | 46 | We have a fantastic community, and we appreciate the time you dedicate to ensuring 47 | its future! :heart: 48 | -------------------------------------------------------------------------------- /docs/core_values.md: -------------------------------------------------------------------------------- 1 | # Djangonaut Space Core Values 2 | 3 | Our values define who we are and guide how we nurture the next generation of Django contributors. 4 | 5 | ### 🤝 Community & Belonging 6 | We rise together. Our strength comes from collective learning, peer support, and genuine connections. We actively welcome people of all backgrounds, identities, and experience levels. Inclusion is woven into everything we do. We celebrate successes both big and small, share stories, and remember that behind every commit is a person deserving of recognition and respect. 7 | 8 | ### 🌱 Sustainable Growth 9 | Health and happiness over speed. We believe in steady, sustainable progress that enriches lives rather than drains them. We embrace mistakes as learning opportunities and value both those who move fast and those who move slow, as long as they keep coming back. Contributing to open source should be fulfilling and fun, not a source of burnout. 10 | 11 | ### 🚀 Empowerment Through Access 12 | Remove barriers, create pathways. We guide without gatekeeping, sharing knowledge, resources, and connections generously. We recognize that time and resources aren't equally available to everyone, so we work to provide financial support and ensure opportunities reach those who need them most. The organization creates the pathways, our volunteers help guide members to grow into Django leadership roles. 13 | 14 | ### 💫 Excellence with Empathy 15 | Professional, patient, kind. We conduct ourselves with respect, choosing words carefully and assuming good intentions. We operate with transparency, communicate clear expectations, and handle conflicts with care and confidentiality. No one has all the answers; we value curiosity, encourage questions, and believe everyone is continuously learning. 16 | 17 | ### 🚀 Space Puns 18 | We build connections beyond code. This means we love and encourage sharing photos and discussions of pets, hobbies, and travels. And we will always go for a space pun and an extra emoji where possible! 🌌 What might seem silly to some, we’ve found very helpful in helping our global distributed community connect and relate to each other as people, because as we all know we “Came for the code, but stayed for the community”. 19 | 20 | --- 21 | 22 | *These values are our commitment: to each other, to our Djangonauts, and to everyone who joins our journey through the Django universe.* 23 | 24 | -------------------------------------------------------------------------------- /docs/financial-aid-guidelines.md: -------------------------------------------------------------------------------- 1 | # Financial Aid Guidelines 2 | 3 | This document outlines Djangonaut Space’s selection process and award amount process for financial aid recipients. 4 | 5 | This is meant to be able to be shared publicly, so this should not contain sensitive information. 6 | 7 | ## Guiding Principles 8 | Our guiding principles for the financial aid awards are as follows: 9 | - Connect budding community members with the community 10 | - Provide a platform for recipient to advance their career 11 | - Recruit future Djangonauts and Navigators 12 | 13 | ## Selection process 14 | People can apply for financial aid at any time. This makes it a challenge to select recipients because there’s a finite amount of money to be awarded and there can be several qualified conferences and candidates. 15 | 16 | ### Qualified candidates 17 | An applicant must do the following: 18 | - Be an active member(see below) of Djangonaut Space 19 | - Explain how the event will benefit them 20 | 21 | An active member is someone who fits one of the criteria: 22 | - Was a Djangonaut who attended at least three Navigator meetings during a session within the last six months 23 | - A Star who has done any of the following: 24 | - Attended a Djangonaut Space community event in the last month 25 | - Had at least three messages on the server within the last three months 26 | - A Navigator who held at least four meetings in a session in the last six months 27 | - A Captain who met with their Djangonauts at least half the time in a session in the last six months 28 | - A Session Organizer who attended at least half the Session Organizer meetings in the last 12 months 29 | 30 | ### Qualified conferences/events 31 | The conference or event the application is being submitted for must be the following: 32 | - Django or Python related, or an event local to the applicant 33 | - Be publicly visible so it can be verified 34 | - Align with Djangonaut Space’s Code of Conduct and spirit 35 | - Expenses can only be used for conference tickets, lodging and travel 36 | 37 | ### Other qualified request reasons 38 | An applicant can request equipment, software or tools that would significantly improve their ability to do any of the following: 39 | - Participate in Djangonaut Space 40 | - Participate in the Django community 41 | - Contribute to open source 42 | 43 | An example of this type of request may be a quality microphone so they can communicate more effortlessly. 44 | 45 | ### Application ranking 46 | In the likely case multiple applications are submitted, the applications must be compared to each other. The following criteria should be used to identify which applications should be prioritized. To be clear, the following criteria are for ranking. They should not be used to reject an application. These are in order of importance from greatest to least. 47 | 48 | 1. First-time conference attendees 49 | 2. First-time conference speakers 50 | 3. Current Djangonauts 51 | 4. Presenting on Djangonaut Space 52 | 5. Level of participation in Djangonaut Space and/or Django community 53 | 6. Has not requested financial aid from Djangonaut Space before 54 | 55 | ## Award amount process 56 | To help make awarding financial aid easier for multiple applications for a variety of events throughout the year, the following constraints must be followed: 57 | 58 | - A limit of $300 per person, per event 59 | - A limit of $600 per person, per year 60 | - One of the events must be attended in service of Djangonaut Space 61 | - A limit of $150 per person for equipment, for five years 62 | - A limit of $900 total financial awards per event 63 | A limit of $2400 in total financial awards per year 64 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Djangonaut Program 2 | 3 | This program places an emphasis on group-learning, sustainability and longevity. 4 | Djangonauts are members of the community who wish to level up their current Django 5 | code contributions and potentially take on leadership roles in Django in the 6 | future. :unicorn: 7 | 8 | This is a free, 8-week group mentoring program where individuals will work self-paced in a 9 | semi-structured learning environment. 10 | 11 | Want to be involved in the future direction of Django? Confidently vote on proposals? 12 | This could be a great way to launch your Django contribution career! :rocket: 13 | 14 | [Subscribe to our newsletter!](https://buttondown.com/djangonaut-space) 15 | 16 | 17 | 18 | 19 | 20 | icon | X 21 | 22 | 23 | 24 | 25 | 26 | 27 | icon | Mastodon 28 | 29 | 30 | 31 | 32 | 33 | 34 | icon | LinkedIn 35 | 36 | 37 | 38 | ## How this works 39 | 40 | ### Cohorts 41 | 42 | - No more than 4 Djangonauts per 1 Navigator[^1] and no more than 8 total Djangonauts in 43 | a group. 44 | - Every Djangonaut has the same goal and is at a relatively similar level. 45 | - Programs last 8 weeks. 46 | - Each cohort has access to a private Discord server[^2]. 47 | - Programs receive support from Captains. 48 | 49 | Each week there are stand-ups facilitated by the Navigators with the expectation that 50 | cohort members check-in with a form of status update, ask questions and receives feedback. 51 | Navigators can rotate in attending these. 52 | 53 | Captains help organise the program and reduce the admin burden for Navigators. They are 54 | community managers who help orchestrate the warm, welcoming environment at Django we all 55 | know and love. :heart: 56 | 57 | [^1]: Having multiple Djangonauts per Navigator scales better than a 1:1 mentorship 58 | relationship. This has an added benefit that peers can help each other in a community 59 | setting. 60 | [^2]: It can be intimidating to post questions and ask for help in very public settings. 61 | The program will aim to uplift Djangonauts to be comfortable with this by the end of the 62 | program, but aims to create a welcoming, inclusive, and safe space for those that need a 63 | little more encouragement. 64 | 65 | ### Benefits of a Cohort 66 | 67 | - Peer mentoring. 68 | - Clear goals, objectives, and timelines. 69 | - All Djangonauts are working towards the same goal. 70 | - Navigators share time commitments and responsibilities. 71 | - Exposure to multiple mentorship relationships in an open and collaborative environment. 72 | 73 | 74 | ## Program Goals 75 | 76 | - Increase sustainable and regular contributions and community involvement with Django. 77 | - Provide an actively accessible and inclusive space for the development of Djangonauts. 78 | - Improve sustainability of Django's development through empowering others to progress 79 | into Django leadership roles. 80 | 81 | 82 | ## Important Links 83 | 84 | - [Djangonaut Guide](djangonauts.md) 85 | - [Djangonaut workbook](https://djangonaut.space/resource/djangonaut-workbook/) 86 | - [Djangonaut workbook - third-party packages](https://djangonaut.space/resource/djangonaut-workbook/third-party/) 87 | - [Navigator Guide](navigators.md) 88 | - [Navigator workbook](https://djangonaut.space/resource/navigator-workbook/) 89 | - [Captain Guide](captains.md) 90 | - [Captain workbook](https://djangonaut.space/resource/captain-workbook/) 91 | - [Code of Conduct](CODE_OF_CONDUCT.md) 92 | - [Newsletter](https://buttondown.com/djangonaut-space) 93 | -------------------------------------------------------------------------------- /navigators.md: -------------------------------------------------------------------------------- 1 | ## Navigator Guidelines 2 | 3 | After over 15 years since it was first released, the Django framework and its ecosystem of packages has become vast 4 | and no one has all the answers. So it's not surprising that many find contributing to 5 | Django to be intimidating. 6 | 7 | Our contributors rely on our docs, commenting on tickets, and interacting with others 8 | to get up to speed. Whether it's using the Django Forum, Discord, mailing list, 9 | DjangoCons, or similar, contributors want to discuss the technical specifics, the landscape, or how 10 | to best to add value. 11 | 12 | By being a Navigator you engage in this conversation and can help accelerate someone's 13 | path to being integrated and productive within the Django universe. :rocket: 14 | 15 | This program is designed to take everyone's time into consideration. We know it is 16 | difficult to carve out steady time to support someone. When you're a Navigator in this 17 | program, the communication framework has been set up for you so your expectations are 18 | set for when you are ready to dig into mentoring. 19 | 20 | You are serving two roles - coach and advisor. You are a problem solver that doesn't 21 | have all the answers but will know the best resources to go to get the guidance that is 22 | needed. You are helping to create a culture of continuous improvement, collaboration and 23 | feedback. As well as ensuring all Djangonauts feel included and welcome. :heart: 24 | 25 | > "Came for the language, stayed for the community." 26 | 27 | 28 | ### Myths 29 | 30 | - You have to know everything about Django - or even about your area of expertise. 31 | - You have to spend a lot of time with your allocated Djangonauts. 32 | - Only new contributors need mentoring. 33 | 34 | 35 | ## Responsibilities and Expectations 36 | 37 | In this 8-week program, Djangonauts will be asked to take responsibility for their 38 | growth and improvement, as it's a semi-structured self-paced program; however, you are 39 | there to help guide them by sharing your methodologies, resources, tips and experience. 40 | Detailed guidance about Navigators can be found in the [Navigator workbook](https://djangonaut.space/resource/navigator-workbook/). 41 | 42 | - Your goal is to be a guide and not a teacher. If you have the time to teach someone the 43 | fundamentals in git, please do, but know that isn't required. In this scenario, you 44 | should be able to help identify resources for learning git for the Djangonaut. 45 | 46 | - Expect to spend 1-2 hours a week fielding questions on Discord asynchronously. 47 | 48 | - Attendance of a weekly 30 to 60 minute synchronous meeting with your Djangonauts. 49 | If you have a fellow Navigator, only one of you is required. 50 | 51 | - Attend the program welcome and closing sessions. 52 | 53 | - Coordinate with program Captains. They will share feedback from their personal 1:1s 54 | with Djangonauts and help with the running of the program. 55 | 56 | - Make introductions to resources and people for the Djangonaut - this is sponsorship 57 | which is equally important as mentorship. 58 | 59 | - Help the Djangonaut to be productive. 60 | 61 | - Help to build relationships amongst the group - this can be as simple as initiating 62 | conversations and sharing in Discord. 63 | 64 | - Practice patience and empathy. Through repetition, people learn, we cannot expect a 65 | Djangonaut to meet all expectations. Through the removal of rigid expectations and 66 | bias, and with a sprinkle of compassion, we can better support our Djangonauts. 67 | 68 | - Have some fun and learn together! 69 | 70 | As a rough guide, being a Navigator should be roughly a 2-hour per week commitment for 8 weeks. 71 | Later in the program the time commitments may reduce as the Djangonauts should become 72 | more independent. There may also be a drop off in the number of Djangonauts which would 73 | also reduce a Navigator's time commitments. 74 | 75 | 76 | ## Benefits of being a Navigator 77 | 78 | - Personally ensure the sustainability and longevity of Django. Help the growth of a 79 | Django contributor and reduce the risk of burnout. 80 | 81 | - Grow as a leader in the community, improve your communication skills. 82 | 83 | - Gain perspective. Learn where we have holes in our processes and documentation first 84 | hand. 85 | 86 | 87 | We have a fantastic community, and we appreciate the time you dedicate to ensuring 88 | its future! :heart: 89 | -------------------------------------------------------------------------------- /docs/governance.md: -------------------------------------------------------------------------------- 1 | # Djangonaut Space Governance 2 | 3 | This document outlines the formal governance of the Djangonaut Space organization. 4 | 5 | ## Roles 6 | This section identifies the roles of the organization. 7 | 8 | ### Admin 9 | All admins are of equal status. Each admin’s vote counts the same as another’s. An admin can call a meeting with other admins at their discretion. 10 | 11 | An admin can be removed from the team via a formal decision in [Decision Making](#decision-making). 12 | 13 | #### Expected contributions 14 | Admins should be on the server and engaged. They should be responsive via email or via their Discord mentions of the @admins tag. They should attend most of admin meetings. They should be supportive of session admins while session admins are active. 15 | 16 | These numbers exist to provide a minimum baseline. They are meant to be easily achievable and should not be target levels of interaction. They can be used to remove an inactive admin though. 17 | 18 | - One productive conversation with a non-admin and non-advisor on the Discord per month 19 | - A reaction or message response to 50% of `@admins` tag mentions by session admins 20 | - Attendance of 50% of meetings with admins 21 | - Attend one session admin meeting per session 22 | - Be assigned one action item every two admin admin meetings 23 | 24 | #### Role size 25 | The admin role should strive to be staffed by three to five people. There are no hard limits if the team wants to run smaller or larger for periods of time. 26 | 27 | #### Adding Admins 28 | Admins are invited by admins where there is a 50% approval to invite a person. Advisors can suggest and/or recommend additional admins. 29 | 30 | #### Term limits 31 | An admin is welcome on the team for as long as they’d like. They need to confirm their desire to be a part of the team every 12 months. 32 | 33 | ### Advisor 34 | Advisors are intended to be a group of people who can provide feedback, advice and opinions. They should be connected with the broader Django, Python and open source communities. 35 | 36 | Advisors are not able to vote on measures or decisions. They can call for a meeting with admins, but do not need regular meetings. 37 | 38 | #### Expected contributions 39 | Advisors should be on the server and sporadically interactive. They should be responsive via email or via their Discord mentions of the `@advisors` tag. They should attend most of the meetings that are arranged with admins. 40 | 41 | These numbers exist to provide a minimum baseline. They are meant to be easily achievable and should not be target levels of interaction. They can be used to remove an inactive advisor though. 42 | 43 | - One productive conversation with a non-admin on the Discord per quarter 44 | - A reaction or message response to 50% of `@advisors` tag mentions by advisors 45 | - Attendance of 50% of meetings with admins. If there are more than 6 of said meetings, advisors only need to attend 3 total for the year. 46 | 47 | #### Role size 48 | There can be zero to nine advisors. 49 | 50 | #### Adding Advisors 51 | Advisors are invited by admins where there is a 50% approval to invite a person. Existing advisors can suggest and/or recommend additional advisors. 52 | 53 | #### Term limits 54 | An advisor can be on the team for up to three consecutive years. They need to confirm their desire to be a part of the team every 12 months. 55 | 56 | ## Processes 57 | This section identifies the defined processes of the Djangonaut Space organizing team. 58 | 59 | ### Decision making 60 | A formal decision, such as approving this document or making a change to it, requires approval of more than 50% of admins. The decision should be added to the Decision Record document. 61 | 62 | Before voting on a structural decision, it must be announced at least three days before the meeting and must be done in a way that actively notifies all other admins. 63 | 64 | ### Annual Reports 65 | Every year the admins should put together an annual report. It must account for the following: 66 | 67 | - Session participation metrics 68 | - Financial report 69 | - Donations per source 70 | - Tools 71 | - Financial aid 72 | - [Open Collective](https://opencollective.com/djangonaut-space) / fiscal fees 73 | - Marketing 74 | - Goals for the next year 75 | 76 | ### Code of Conduct Reporting 77 | Code of Conduct violations have two routes. For reports with Djangonauts, Captains, Navigators please refer to the [program documentation](https://github.com/djangonaut-space/program/blob/main/CODE_OF_CONDUCT.md). If the violation involves a fellow admin, you can email CoC@djangonaut.space If you’re uncomfortable with that route, please report the violation following [Django’s Code of Conduct reporting guidelines](https://www.djangoproject.com/conduct/reporting/). 78 | -------------------------------------------------------------------------------- /djangonauts.md: -------------------------------------------------------------------------------- 1 | ## Welcome and Summary 2 | 3 | Welcome prospective Djangonaut! 4 | This is an 8-week group mentoring program where individuals will work self-paced in a 5 | semi-structured learning environment. 6 | 7 | Want to be involved in the future direction of Django? Confidently vote on proposals? 8 | This could be a great way to launch your Django contribution career! :rocket: 9 | 10 | During the 8-week period, you will work to level up your Django contributions 11 | along with peers who have the same goal. This cohort will include Navigators who have 12 | specialised knowledge and experience. Think of them as pilots guiding you through the 13 | Django universe. :stars: 14 | 15 | At the end of the 8-week period, you will have a number of contributions credited 16 | to your name, be integrated into the Django contributor community, and have an 17 | understanding as to what comes next! :muscle: 18 | 19 | **Important Note** 20 | 21 | This program will have a focus on sustainability and longevity throughout. 22 | Remember that, while we want you to be successful, your health and happiness comes 23 | above all else. :heart: 24 | 25 | > "I would be very proud of a program that has some move fast and some move slow, 26 | > but keep coming back." -- Dawn Wages, Djangonaut Organiser 27 | 28 | 29 | ## Expectations 30 | 31 | - Good standing throughout the program and uphold our [Code of Conduct](CODE_OF_CONDUCT.md). 32 | - Attendance during weekly stand-up meetings between Djangonauts and Navigators. 33 | Here you will receive feedback and support. 34 | - Be helpful to your peers in the program. 35 | - Mutual respect to fellow Djangonauts, Navigators and all who you interact with 36 | throughout the program. 37 | 38 | 39 | ## Benefits of the Program 40 | 41 | There are many benefits to being active in the Django open source community. We will 42 | discuss a few of these below. 43 | 44 | ### Upskilling 45 | 46 | Contributing to Django will have you work with some incredibly talented and 47 | knowledgeable members of the community. 48 | 49 | You will learn to work at a level which may be completely different to what is 50 | required from you in other settings. Whether this is having to consider the 51 | differences between multiple databases, that `.join()` is faster for a `list` object 52 | than a `generator` object, or how to rebase your commits for a coherent commit 53 | history - you are guaranteed to learn while also bringing your unique skills and 54 | experience to the table. 55 | 56 | ### Finding your dream job 57 | 58 | Open source contributions can help you stand out from the crowd when looking for 59 | your next role. Having this experience on your CV can get you interviews and help 60 | you skip steps in a hiring process! You will also build a network of people who have 61 | seen how you work and can recommend you for a role. 62 | 63 | This is particularly useful for anyone early in their career, those looking for a 64 | role change, or when the job market is particularly competitive. 65 | 66 | ### Visibility 67 | 68 | Open source contributions get you noticed. They give you a level of credibility and 69 | confidence which you can use as rocket fuel for your career. 70 | 71 | Are you in awe when someone says they actively contribute to Django? Lots of people 72 | are! 73 | 74 | You can use this for: 75 | 76 | - Joining Django's Steering Committee / technical leadership. 77 | - The subject of a conference talk. 78 | - Promoting your blog and/or books! 79 | - Invitations to podcasts. 80 | - Part of your journey into the PSF and Python contributions. 81 | 82 | Those are just a few ideas! Once you have launched, there is no telling where this 83 | journey could take you. 84 | 85 | 86 | **Important Note** 87 | 88 | Time investment in anything without receiving a paycheck is difficult to justify. 89 | Your time is valuable, and we respect that monetary concerns may limit or prevent 90 | your ability to participate in this program. In the future we would love to accept 91 | applications to have certain participants sponsored to partake in this program. 92 | 93 | If this is the case for you, please reach out to the team, so we can contact you in 94 | the future if we have budget to support: 95 | [contact@djangonaut.space](mailto:contact@djangonaut.space). 96 | 97 | 98 | ## Resources 99 | 100 | - [Code of Conduct](CODE_OF_CONDUCT.md) 101 | - [Djangonaut Space - Djangonaut workbook](https://djangonaut.space/resource/djangonaut-workbook/) 102 | - [Contributing Guide](https://docs.djangoproject.com/en/dev/internals/contributing/) 103 | - [Djangonaut Space - Launch](https://www.youtube.com/watch?v=SO5GGTZYK70) 104 | - [Djangonaut Space Ask Me Anything video](https://youtu.be/6bjCIOCpdM4) 105 | - [Contributing to Django - David Smith - DjangoChat]( 106 | https://djangochat.com/episodes/contributing-to-django-david-smith) 107 | - [Feeding the Pony: Contributing back to Django & How to make that work for you - 108 | DjangoCon Talk](https://www.youtube.com/watch?v=F4StlMFb5Ms) 109 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | Djangonaut Space is a place where we look to facilitate the growth of 4 | some of the future contributors to the Django community. To that end 5 | we are dedicated to providing a harassment-free environment for everyone, 6 | regardless of gender, gender identity and expression, sexual orientation, 7 | disability, personal appearance, body size, race, ethnicity, age, religion, 8 | or nationality. 9 | 10 | Our code of conduct is based on [Django's Code of Conduct](https://www.djangoproject.com/conduct/). 11 | This code of conduct applies to 12 | all areas involved with Djangonaut Space. This includes Discord, email, 13 | video conferences, and any channels community uses for communication. 14 | In addition, violations of this code outside these spaces may affect a 15 | person's ability to participate within them. 16 | 17 | If you believe someone is violating the code of conduct, we ask that you 18 | report it by emailing CoC@djangonaut.space. 19 | 20 | - **Be friendly and patient.** 21 | 22 | - **Be welcoming.** We strive to be a community that welcomes and supports 23 | people of all backgrounds and identities. This includes, but is not 24 | limited to members of any race, ethnicity, culture, national origin, 25 | colour, immigration status, social and economic class, educational 26 | level, sex, sexual orientation, gender identity and expression, age, 27 | size, family status, political belief, religion, and mental and 28 | physical ability. 29 | 30 | - **Be considerate.** Your work will be used by other people, and you in turn 31 | will depend on the work of others. Any decision you take will affect 32 | users and colleagues, and you should take those consequences into 33 | account when making decisions. Remember that we're a world-wide 34 | community, so you might not be communicating in someone else's primary 35 | language. 36 | 37 | - **Be respectful.** Not all of us will agree all the time, but disagreement 38 | is no excuse for poor behavior and poor manners. We might all experience 39 | some frustration now and then, but we cannot allow that frustration to 40 | turn into a personal attack. It’s important to remember that a community 41 | where people feel uncomfortable or threatened is not a productive one. 42 | Members of the Djangonaut Space community should be respectful when dealing 43 | with other members as well as with people outside the community. 44 | 45 | - **Be careful in the words that you choose.** We are a community of professionals, 46 | and we conduct ourselves professionally. Be kind to others. Do not insult 47 | or put down other participants. Harassment and other exclusionary behavior 48 | aren't acceptable. This includes, but is not limited to: 49 | - Violent threats or language directed against another person. 50 | - Discriminatory jokes and language. 51 | - Posting sexually explicit or violent material. 52 | - Posting (or threatening to post) other people's personally identifying information ("doxing"). 53 | - Personal insults, especially those using racist or sexist terms. 54 | - Unwelcome sexual attention. 55 | - Repeated or inappropriate direct messaging on any communication platform. 56 | - Advocating for, or encouraging, any of the above behavior. 57 | - Repeated harassment of others. In general, if someone asks you to stop, then stop. 58 | 59 | - **When we disagree, try to understand why.** Disagreements, both social and 60 | technical, happen all the time and Django is no exception. It is important 61 | that we resolve disagreements and differing views constructively. Remember 62 | that we’re different. Different people have different perspectives on issues. 63 | Being unable to understand why someone holds a viewpoint doesn’t mean 64 | that they’re wrong. Don’t forget that it is human to err and blaming each 65 | other doesn’t get us anywhere. Instead, focus on helping to resolve issues 66 | and learning from mistakes. 67 | 68 | 69 | ## Reporting a code of conduct violation 70 | 71 | If you believe someone is violating the code of conduct we ask that you report it 72 | to the Djangonaut Space organizers by emailing CoC@djangonaut.space. All 73 | reports will be kept confidential. In some cases we may determine that a public 74 | statement will need to be made. If that's the case, the identities of all victims 75 | and reporters will remain confidential unless those individuals instruct us otherwise. 76 | 77 | **If you believe anyone is in physical danger, please notify appropriate law enforcement 78 | first.** If you are unsure what law enforcement agency is appropriate, 79 | please include this in your report and we will attempt to notify them. 80 | 81 | ### What to include in your report 82 | 83 | In your report please include: 84 | - Your contact info (so we can get in touch with you if we need to follow up) 85 | - Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well. 86 | - When and where the incident occurred. Please be as specific as possible. 87 | - Your account of what occurred. If there is a publicly available record please include a link. 88 | - Any extra context you believe existed for the incident. 89 | - If you believe this incident is ongoing. 90 | - Any other information you believe we should have. 91 | 92 | ### What happens after you file a report? 93 | 94 | You will receive an email from the Djangonaut Space organizers acknowledging 95 | receipt as quickly as we can. 96 | 97 | The organizers will immediately meet to review the incident and determine: 98 | 99 | - What happened. 100 | - Whether this event constitutes a code of conduct violation. 101 | - Who the bad actor was. 102 | - Whether this is an ongoing situation, or if there is a threat to anyone's physical safety. 103 | 104 | If this is determined to be an ongoing incident or a threat to physical safety, the 105 | organizers' immediate priority will be to protect everyone involved. This means we 106 | may delay an "official" response until we believe that the situation has ended and 107 | that everyone is physically safe. 108 | 109 | Once the organizers have a complete account of the events they will make a 110 | decision as to how to response. Responses may include: 111 | 112 | - Nothing (if we determine no violation occurred). 113 | - A private reprimand from the working group to the individual(s) involved. 114 | - A public reprimand. 115 | - A permanent or temporary ban from Djangonaut Space's platforms and/or the 116 | program itself. 117 | - A request for a public or private apology. 118 | - An escalation to the Django Code of Conduct Working Group for action 119 | within the broader Django community. 120 | 121 | We'll respond within one week to the person who filed the report with 122 | either a resolution or an explanation of why the situation is not yet resolved. 123 | 124 | Once we've determined our final action, we'll contact the original 125 | reporter to let them know what action (if any) we'll be taking. We'll 126 | take into account feedback from the reporter on the appropriateness of 127 | our response, but we don't guarantee we'll act on it. 128 | 129 | ### What if your report concerns a possible violation by an organizer? 130 | 131 | If you feel uncomfortable filing a report with the Djangonaut Space organizers 132 | we recommend that you file a report with Django's Code of Conduct Working Group. 133 | [You can find those guidelines here.](https://www.djangoproject.com/conduct/reporting/) 134 | --------------------------------------------------------------------------------