![Djangocon 2024 logo](../static/images/logo/main_logo.b3feb7e798bc.png)
diff --git a/about/cfp_report/index.html b/about/cfp_report/index.html new file mode 100644 index 00000000..743ec64e --- /dev/null +++ b/about/cfp_report/index.html @@ -0,0 +1,1001 @@ + + + + + + +
+ + ++ We had a whopping total of 174 proposals from 138 submitter. Our content team + worked extra hard to + provide over 750 reviews, allowing for an average of 4+ reviews for + submission. Cudos to all of them, + you can check the team here Programme Team +
+We are working on the schedule, meanwhile you can take a peek at the currently + accepted and confirmed by the + speakers talks.
+ View Currently accepted and confirmed talk + here +We had 156 talks and 18 workshops submissions + From the 138 submitters. 51 were first time speakers. 43 felt + part of an underrepresented group.
+ +Get a glance of the chart below,
+ + + + + + + + + +Answer | +Count | +% | + + +
---|---|---|
+ Never attended + + | ++ 56 + | ++ 42 % + | +
+ Speaker + + | ++ 44 + | ++ 33 % + | +
+ Participant + + | ++ 32 + | ++ 24 % + | +
Answer | +Count | +% | + + + +
---|---|---|
+ Productivity + | ++ 50 + | ++ 29 % + | +
+ General Python + | ++ 50 + | ++ 29 % + | +
+ Architecture + | ++ 50 + | ++ 29 % + | +
+ Community + | ++ 43 + | ++ 25 % + | +
+ Deployment + | ++ 36 + | ++ 21 % + | +
+ Django Internals + | ++ 34 + | ++ 20 % + | +
+ Teamwork + | ++ 29 + | ++ 17 % + | +
+ DB + | ++ 28 + | ++ 16 % + | +
+ Async + | ++ 27 + | ++ 16 % + | +
+ Rest APIs + | ++ 25 + | ++ 14 % + | +
+ Testing + | ++ 22 + | ++ 13 % + | +
+ HTML/CSS/JavaScript + | ++ 19 + | ++ 11 % + | +
+ Django Admin + | ++ 16 + | ++ 9 % + | +
+ Security + | ++ 15 + | ++ 9 % + | +
+ Documentation + | ++ 14 + | ++ 8 % + | +
+ Health + | ++ 13 + | ++ 7 % + | +
+ Forms + | ++ 9 + | ++ 5 % + | +
+ htmx + | ++ 9 + | ++ 5 % + | +
+ DSF + | ++ 5 + | ++ 3 % + | +
+ GraphQL + | ++ 4 + | ++ 2 % + | +
Answer | +Count | +% | + + + +
---|---|---|
+ Intermediate + | ++ 109 + | ++ 63 % + | +
+ Beginner + | ++ 55 + | ++ 32 % + | +
+ Advanced + | ++ 10 + | ++ 6 % + | +
Don't forget to follow us on X (formerly known as Twitter) + @DjangoConEurope, Slack , or LinkedIn for the latest up-to-date + information! +
+ + + + + +You are most welcome to get in touch if you have questions.
+ +If you are a sponsor and wish to offer a company gift / voucher code to the attendees, please get in contact through sponsors@djangocon.eu.
+These are some frequently asked questions, kindly contact us for further assistance if you can't find the answers to your questions here.
+Do I need a visa to Vigo Spain?
+This will depend on the country you will be coming from. Some countries don't need a visa to enter Spain, but others do. You can find out if you need a visa to enter Spain using this link. If your country is part of the list provided in the link given below then you need a visa to visit spain. If you don't find your country, then you don't need a visa. Check it here Countries who needs visa
What are the ticket prices for DjangoCon Europe?
+For everything concerning ticket kindly check it here Tickets
Do you provide Invitation to aid visa application?
+The organizers of DjangoCon offer invitation letters to assist with your travel arrangements. Click here to request one
How do i apply for grant for DjangoCon EU 2024
+Grant Application is closed.
What do i do if i am refused visa but still bought tickets
+Sorry, hopefully that doesn't happen, but if it does send an email to our email here 2024@djangocon.eu
+and the team will get back you.
Are there options for virtual participation?
+Yes there are, but you would need to purchase a ticket before getting access to the platform , allowing you to stream live, you can
+get the virtual ticket here Virtual Tickets
Where is the exact venue for the event
+The venue is located at the very heart of Vigo, on the seafront, facing the Cíes Islands and Mar de Vigo.
+to know more about how to get to the place vist the venue page here. Venue
My company doesn't allow traveling by plane anymore
+Vigo has two railway stations: URZAIZ where departs the AVE (Spain's high-speed train), and GUIXAR, located in Areal St., both of them right in the city centre. Know More
How do i get to Vigo?
+Kindly check this page, it should answer all your questions
Will there be breakfast, lunch and dinner
+Lunch and Coffee breaks are included. Dinners are not included
Would all session be recorded, also the once under the workshop
+ ++ This list of individuals is still growing. Nonetheless, these are our + sincerest alphabetical thanks to everyone who have made contributions to + this conference thus far: +
+ +In addition, the wonderful speakers, + our + amazing sponsors, the + fantastic Django + Software + Foundation members, + and to everyone who bought a ticket.
+ +Everybody who participates in DjangoCon Europe in one way or another is required to conform to this Code of Conduct (CoC). This includes attendees, speakers, sponsors, organizers, volunteers, and event staff.
+The organizers will introduce a Code of Conduct team that will be primarily responsible for handling any incidents. The CoC applies before and throughout the event (including related activities such as social events, and social media). We have also published our response guidelines.
+The team can be reached on conduct@djangocon.eu.
+We would like to thank the DjangoCon Europe 2019 CoC team for the awesome CoC (which we adapted with some minor modifications) and the response guidelines (which we have adopted almost unedited from 2018).
+Our goals with having this Code of Conduct are:
+We ask each attendant to keep the community in mind and do their best to foster a positive environment for everyone.
+Behavior that contributes to a positive environment includes:
+We are dedicated to providing a harassment-free conference experience for everyone, regardless of race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
+This Code of Conduct applies to all conference related spaces. That includes, but is not limited to:
+In case of a Code of Conduct violation, some of the most common actions organisers may take are:
+If a Code of Conduct incident happens to you, or you witness it happening to someone else, please contact the CoC team immediately, either in Slack or by sending an email to conduct@djangocon.eu.
+Your report will be treated confidentially and will only be discussed within the CoC team.
+The team members will be introduced at the conference. You can message any of them at any time to discuss an incident or concern. You can also ask any other staff to help you find them.
+Please do not feel like you may be a burden to us by reporting incidents. Even if you happen to report multiple incidents during the conference. We rather consider reports as an opportunity for us to act: by knowing about an incident, we can act on it, and often prevent it from going on or occuring again. But if we don't know, we can't take action.
+If you're not sure if an incident was already reported by someone else, even if many people saw it, please report it. It is frequent that several people witness an incident and no one reports it, because everyone thought other people would.
+If you are not sure whether the situation was a Code of Conduct violation, or whether it applied to that particular space, we encourage you to still report it. We would much rather have a few extra reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. And knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it.
+If you think you witness something, but you're not sure what you saw, or you don't have proof, it's still very useful to us if you can report on that. You don't have to build up a case before reporting, and it's ok to report things even if you have doubts.
+In your report please include, when possible:
+If you don't have some of this information, or not at this time, please still make the report anyways. You can contact us at any time after your report if you want to add, edit or take back any information you shared.
+If you feel unsafe reporting in person, you may choose someone to represent you. In this case, we'd need their contact information, but we'd ask this person to make clear that they are not reporting in their own name.
+When handling a report, we follow our response guidelines.
+We value your attendance, and look forward to seeing you at DjangoCon Europe.
+Ad Evolutio – DjangoCon Europe 2024 organizers – is responsible for the website 2024.djangocon.eu, DjangoCon Europe 2024 official website. The privacy and security of personal data of our attendees, speakers, sponsors, and volunteers – participants – are very important to us. DjangoCon Europe 2024 organizers are committed to observing the principles of data protection to the best of its ability, in compliance with the (EU) Regulation 2016/679 of the European Parliament and Council, of 27th of April 2016, concerning the protection of natural persons concerning the processing of personal data and the free movement of such data, which revokes Directive 95/46/CE (General Data Protection Regulations), and other additional legislation.
+Please read the following text to know how your personal data will be used by the DjangoCon Europe 2024 organizers. Should any doubts or questions arise, talk with us by email to 2024@djangocon.eu.
+Many moments in our event – conferences, pitches, workshops, and parties – will be photographed and filmed. Many times with live streamings on Youtube. This will give us memories to relive!
+The processing of personal data, by DjangoCon Europe 2024 organizers, is intended to provide a service of interest to the personal data subject. The DjangoCon Europe international conference is the specific purpose of why we treat your personal data. The information we collect serves to correctly identify you and manage the services provided.
+All processing of personal data by DjangoCon Europe 2024 organizers is processed based on the consent of the data subject or for the performance of a contract to which the data subject is part. The DjangoCon Europe 2024 organizers are responsible for processing the personal data collected in the DjangoCon Europe 2024 official website. The DjangoCon Europe 2024 organizers reserve the right to require the help of institutional partners or sponsors in processing personal data when this option can offer more efficiency and more security to the data subject. The organizer will require always and previous a statement of compliance with essential rights foreseen in the European legislation.
+The organizers will not share your personal information with other companies without your consent.
+The data subject will provide their consent by confirming several options, appropriate for each case, by selecting different technical parameters and completing various fields, which demonstrate the data subject’s positive act and unmistakable willingness to provide personal data.
+The DjangoCon Europe 2024 organizers will endeavor to observe the principles of proportionality and necessity by performing a case-by-case analysis, adjusting the need for processing personal data when providing different services. In some cases, only a name and e-mail will be requested. In other cases, like a proposal speaker, more information needs to be collected. We don’t process sensitive data.
+For all attendees, we collect personal data when you voluntarily provide such information to the buy ticket services, and as part of our Code of Conduct handling of any reports.
+The personal data we may collect includes without limitation your name, email address and any other information that attendees choose to provide and/or that enables attendees to be personally identified. In some cases, we may collect your credit card information (e.g., your credit card number and expiration date, billing address, etc.), some of which may constitute personal data, to secure certain payments.
+For code of conduct incident reports handling, we may collect additional information about individuals mentioned in any reports. We may share this information with the Django Software Foundation Code of Conduct Committee as needed. View our Code of Conduct response guidelines for more information.
+If you are a proposal speaker we will need to collect additional personal data from you. And we will request other information different from your personal data (e.g., a title, a description, abstract, a profile photo, etc.) when you do the submission. This information is essential to select the titles and defined the conference program.
+DjangoCon Europe 2024 will publicly share the slides from the presentations.
+For all sponsors, we collect personal data necessary for our contractual relationship.
+For all volunteers, we collect personal data when you voluntarily provide such information. The personal data we may collect includes without limitation your name, email address and any other information that attendees choose to provide and/or that enables attendees to be personally identified.
+Our website may contain links to external websites. This privacy policy applies only to the entirety of our website. We, therefore, recommend that you carefully read the respective websites’ privacy notices.
+We retain your Personal Data for as long as necessary to provide you with our Services, or for other important purposes such as complying with legal obligations, resolving disputes, and enforcing our agreements.
+The data subject has the right to access, rectify or remove, restrict or contest the processing of the personal data at any time, by simply communicating this intention via email to 2024@djangocon.eu.
+This is a guide for the organisers and volunteers of DjangoCon Europe on handling Code of Conduct (CoC) reports. This guide is mostly aimed at conference staff to help us deal with incidents professionally, and reduce the risk of mistakes. This is especially important because conferences are stressful and involve significant time pressure. However, it's always possible that special circumstances require a deviation from this guide.
+Some parts of this guide discuss very severe incidents, like ongoing violence. This is not because these events are common at DjangoCon, but rather because we want to be prepared as well as reasonably possible, for anything from the more common smaller incidents to the most severe cases.
+DjangoCon Europe has a dedicated Code of Conduct Active Response Ensurers (CARE) team, and this team will generally handle any reports. However, other organisers and volunteers are sometimes the first point of contact, or may observe incidents themselves.
+In general, as a representative of the conference, be aware that other participants look toward you for appropriate behaviour within the Code of Conduct.
+When you are an organiser or volunteer not on the CARE team, the general guidelines for observing an incident or receiving a report are:
+In speaking to a reporter, be cautious in your wording. Try to be understanding and compassionate, and make them feel heard and taken seriously. However, do not make commitments on whether the conference will see this as a violation, or what action will be taken.
+In urgent cases, where it is not possible to contact a CARE team member and you believe immediate action is essential, you may intervene unilaterally. For example, you may consider this:
+When possible, even in these cases, consult with another organiser or volunteer if you see one nearby.
+The Code of Conduct Active Response Ensurers (CARE) are in charge of handling reports until their completion. It is their task to ensure all reports are handled timely and professionally. Our CARE team is still in the making - volunteers are welcome.
+Participants look towards the CARE team for appropriate behaviour, even more than other staff, and that makes it essential for their behaviour to remain within the Code of Conduct. Violations by CARE team members can severely erode trust in the Code of Conduct process.
+CARE team members almost never act on their own, including tasks like replying to Code of Conduct related e-mails. If it’s not possible to meet with the entire CARE team in time, at least one other team member should be consulted.
+Reports are typically received by e-mail, in Slack, or from another staff member. If the report was received from someone else, it may be best to meet with the original reporter first, depending on how complete the information is. The information the CARE team aims to collect is listed in the Code of Conduct reporting guide, but sometimes not all information is available.
+When receiving a report, the CARE team acknowledges receipt as soon as possible, and aims to be understanding and compassionate. However, there should be no commitment on whether this is a violation or which action will be taken.
+The CARE team generally works, decides and communicates as a team. If the report indicates that immediate action is required and other CARE team members are not available, any CARE team member may take the action they see appropriate. The same guidelines for unilateral action apply as listed above for other staff members. If possible, it’s still preferred to take action after a brief discussion with at least one other CARE team member, or even any other organiser, rather than acting entirely unilaterally. Formal processes and guidelines must never get in the way of preventing threats to anyone’s safety.
+Based on the report and any other available information, the CARE team will meet to determine, to the best of their ability:
+A written record will be kept of each incident and its review. Although that sometimes seems superflous at the time, hectic environments like conferences can make it easy to forget or confuse details later.
+As a result of the meeting, the CARE team may come to a conclusion about a resolution, or may conclude that additional information should be obtained. In the latter case, this additional information will be collected as soon as possible. Any conversations as part of this should generally be done by two people from the CARE team.
+As soon as reasonable, but at the latest at the report review meeting, team members should declare any conflicts of interest. This can mean being friends with one of the involved parties, or anything else that may make it harder to remain neutral.
+A conflict of interest does not inherently mean the team member can no longer participate in the process, as that would make it very hard for the team to act on reports involving well-known people in the community. However, if a report concerns someone a team member is very close to, they probably should not take part in the process. The team will decide together on where to draw this line in individual cases. Where possible, any conversations with offenders should not be done by their friends, as it can be very unpleasant for everyone involved.
+The most common resolutions the CARE team can decide on are:
+Resolutions are not restricted to these options. Any conversations with bad actors are done by two people from the CARE team, and notes from this conversation will be added to the record of the incident.
+When deciding on a resolution, our basic goal is to address the report in an appropriate way, while also looking to prevent or reduce the risk of continuing harm in the future. For example, we may try to distinguish whether a violation occurred intentionally or not, especially in not too severe cases like inappropriate jokes. In intentional cases, or severe behaviour, we'll probably choose for stronger measures. The CARE team can also use behaviour on social media, the conference Slack, or personal interactions to further build a picture of the person(s) involved.
+After the resolution is complete, the reporter should be informed of the action taken by the CARE team, and the reasoning behind this.
+As a general rule, conference staff should not make any public statements about the behaviour of individual people during or after the conference. An exception to this are situations that happened in a fairly public context, because attendees may otherwise think no action was taken, eroding trust in the Code of Conduct process. The CARE team will decide together whether to make a public statement, and if so, in how much detail. This should not be decided unilaterally.
+After each conference, a Code of Conduct transparency report will be published by the CARE team with anonymised information about any violations that might have occurred.
+Any public statements should be handled with care not to divulge personally identifying information about anyone affected, and should serve as a means to ensure that attendees will be comfortable reporting harassment and that our community will be kept accountable for supporting and encouraging safe spaces.
+RUN BY THE COMMUNITY FOR THE COMMUNITY
+This is the 16th edition of the Conference and it is organized by a team made up of Django practitioners from all levels. We welcome people from all over the world.
+Our conference seeks to educate and develop new skills, best practices and ideas for the benefit of attendees, developers, speakers and everyone in our global Django Community, not least those watching the talks online.
++ Gain valuable exposure for your brand and help us ensure the + success of DjangoCon Europe by becoming a sponsor or exhibitor! +
++ By tapping into this community, your brand can leverage value. We + deliver stock sponsorship packages and/or custom sponsorship + opportunities with high impact in terms of increased visibility + and lead generation, such as prime booth locations, speaking + opportunities, and branding exposure. +
+ DISCOVER THE AVAILABLE SPONSORSHIP OPPORTUNITIES +RUN BY THE COMMUNITY FOR THE COMMUNITY
+This is the 16th edition of the Conference and it is organized by a team made up of Django practitioners from all levels. We welcome people from all over the world.
+Our conference seeks to educate and develop new skills, best practices and ideas for the benefit of attendees, developers, speakers and everyone in our global Django Community, not least those watching the talks online.
++ Gain valuable exposure for your brand and help us ensure the + success of DjangoCon Europe by becoming a sponsor or exhibitor! +
++ By tapping into this community, your brand can leverage value. We + deliver stock sponsorship packages and/or custom sponsorship + opportunities with high impact in terms of increased visibility + and lead generation, such as prime booth locations, speaking + opportunities, and branding exposure. +
+ DISCOVER THE AVAILABLE SPONSORSHIP OPPORTUNITIES +So, DjangoCon Europe 2024 is back again and it’s going to be 5 full days of talks, tutorials and sprints - from June 5 to 9:
+In the near future, we will have more info about the conference, which we will publish on the website. This will include more details about the tickets, talks, workshops, grants, code of conduct, etc. For now, here is a summary of that info.
+As with past years, there will be a travel grants program to assist people with financial difficulties, people who are under-represented or from marginalised groups - allowing access to an event that otherwise would be very difficult position for them to attend;
+If you're interested in sponsoring the event, please get in touch at sponsors@djangocon.eu.
+You can already start to prepare your talk, and for that, we recommend that you watch the talk “How To Get On This Stage (And What To Do When You Get There)” by Mark Smith. If you think you have something great to talk about – start to prepare your talk! If you are unsure, talk it over with somebody, or go to Slack to find previous speakers and participants to discuss your idea with. When in doubt, submit your talk!
+As you can imagine there is a lot to do, but it's very much worth it – DjangoCon Europe is an extremely friendly, open, inclusive, and informative (for beginners and advanced users alike) conference. Join us regardless of your prior experience: this is also an opportunity to learn! In other words, you don't have to be an expert to join. Below are the teams and their activities/responsibilities that we seek help with:
+You can apply through this form here.
+Your location before and during the event is not significant, since it will be hosted in a hybrid format. The only important thing is that you have the energy and free time to help organize a wonderful DjangoCon Europe. The official language of all these prior activities will be English, as well as the conference itself.
+We expect new challenges but pledge our hearts and minds to do the best DjangoCon Europe we can, never giving up under these strenuous conditions. Please consider volunteering and join us, we need you!
+We hope we'll see you all at DjangoCon Europe 2024, and don't forget to follow us @DjangoConEurope on Twitter, and also join our dedicated Slack channel.
+Hoping for the best,
+The DjangoCon Europe 2024 Organisers
We will publish event announcements here.
+Stay tuned and follow us on X (formerly known as Twitter): @DjangoConEurope!
If you are a woman or in another way underrepresented gender-wise (a transgender person, including non-binary, or an intersex person) and want to learn how to make websites, we have good news for you: we are holding a one-day workshop for beginners!
+The Django Girls Vigo will take place on June 8th 2024, as a part of DjangoCon Europe 2024.
+The workshop is free of charge. Don't wait too long: you can apply for the workshop only until May 12th 2024!
+Register HERE.
+For more information, check the Django Girls Vigo website.
+DjangoCon Europe 2024 offers grants so that those who might otherwise not be able to attend won't hesitate to participate. Some expenses for the conference attendance (which could include travel, hotel, registration, etc) will be covered for opportunity grant recipients.
+We actively encourage you to apply for an opportunity grant. While we wish we could give grants to everyone who applies, we do not have the funds to do that. Our goal is to maximize the impact our grant program has, within the limited funds we have.
+We try to do this in a number of ways:
+Our program prioritises anyone who is part of an under-represented or marginalized group. They include, but are not limited to:
+The Grant Application is now closed.. We are currently reviewing all applications and will inform applicants of the results within a few days. Please note that if you missed the deadline, you will need to seek alternative funding sources. Additionally, speakers are reminded that they are automatically entitled to receive a ticket.
+Lastly, we know that some of you reading this will doubt whether it's right and proper for you to apply for a grant. That's why we want to stress:
+With our limited funds, we can't promise you will receive a grant, but if you're not sure, we encourage you to apply. If you're uncomfortable with other people knowing you received a grant, you don't have to tell them - our policy is to never publicly identify grant applicants or recipients without their explicit permission.
+If you have questions, you can write to 2024@djangocon.eu.
+Grant Application now Closed!
+