forked from oyd/ozgurkon-2020-site
Compare commits
90 Commits
aa-patch-1
...
master
murat emir cabaroğlu
@ -1,3 +1,3 @@ |
||||
[submodule "themes/devfest-theme-hugo"] |
||||
path = themes/devfest-theme-hugo |
||||
url = https://github.com/GDGToulouse/devfest-theme-hugo.git |
||||
[submodule "themes/ozgurkon-theme-hugo"] |
||||
path = themes/ozgurkon-theme-hugo |
||||
url = https://git.oyd.org.tr/oyd/ozgurkon-theme-hugo.git |
||||
|
||||
@ -1,75 +1,59 @@ |
||||
--- |
||||
title: Call For Paper |
||||
brief: The CFP is opened till May the 25th 2019 |
||||
brief: We are waiting for your talks at May 16-17! |
||||
image: /images/blog/cfp.jpg |
||||
date: 2019-03-23 |
||||
date: 2020-04-10 |
||||
draft: false |
||||
--- |
||||
|
||||
DevFest Toulouse will take place on October 3rd, 2019 at Pierre Baudis congress center. Our fourth edition will gather 1000 attendees! |
||||
Due to the COVID-19 pandemic, cancellation of almost all events in worldwide and Turkey caused a gap on free software related events that are hold in April-May. Free Software Association in Turkey (Özgür Yazılım Derneği) will organize ÖzgürKon with the experience from organizing one of the biggest free software conferences in the world, LibrePlanet 2020 remotely. |
||||
|
||||
While waiting for the D-day do not hesitate to propose a talk at [DevFest Toulouse CFP](https://conference-hall.io/public/event/HJRThubF4uYPkb7jSUxi). It is now open and this year it will be for 2 months only (from March the 25th to Mai the 25th.) |
||||
ÖzgürKon will be held internationally because it is a "événement sans frontières". The conference's languages are English and Turkish. We are planning two parallel tracks, but depending on demands tracks may be increased or decreased. |
||||
|
||||
Be aware that at mid terms, we will select our “early speakers”, so do not wait till the end! |
||||
The final selection will happen within 4 weeks after the end of the CFP. |
||||
In following years, it's planned to organize the event in person internationally. |
||||
|
||||
## Team |
||||
This year, the main theme of ÖzgürKon is decided as "COVID-19 pandemic and freedom struggles". In this concept, main topics of the event are: |
||||
|
||||
This year, we will add even more community members that the core team already represent (GDG Toulouse, Toulouse Data Science, Duchess France, Toulouse DevOps, PitchMeUp, JAM) with the addition of .NET, React, JUG, Rust, Python & Linux / Embedded communities. |
||||
* Free software philosophy and struggle |
||||
* Internet freedom |
||||
* Hardware freedom and free hardware projects |
||||
* Art libre (free art) and its applications |
||||
* Information freedom, information access and free information sharing platforms |
||||
* Document freedom, press freedom and free media(s) |
||||
* Free software and hardware in health and medicine fields |
||||
* Literacy of informatics |
||||
* Digitalization and transformation |
||||
* Privacy and confidentiality |
||||
* Remote education and free software in education |
||||
* Extincting languages and Internet |
||||
* Hack, hack culture and hacktivism |
||||
* Diversity and inclusivity in digital cultures |
||||
* Free licenses |
||||
* "Public money, public code" project |
||||
* Cryptology, cryptography |
||||
* Copyright and patents |
||||
* Digital libraries and e-librarianship |
||||
|
||||
The complete list: <https://devfesttoulouse.fr/team/> |
||||
Every session is 50 minutes long. |
||||
|
||||
## Categories |
||||
Talk (1 session): |
||||
|
||||
* Big Data / ML / AI : Big Data, Machine Learning, AI |
||||
* Cloud/infra : GCP, AWS, Azure, Kubernetes etc. |
||||
* IoT |
||||
* Languages : talk related to a specific language e.g: Rust, Golang, Swift etc. |
||||
* Methods & Tools : Craftsmanship, DevOps, CD, CI, IaC (Infrastructure as Code) etc. |
||||
* Native mobile apps : Android, iOS, React Native, Flutter etc. |
||||
* Web : PWA, Web Components, services workers etc. |
||||
* UX |
||||
* WTF and other : if your talk does not fit in any of the previous categories. |
||||
Talks that covering main topics of the event which may be interested for a larger part of community. It takes one session including question-answer part. They will be broadcasted live. |
||||
|
||||
## Formats |
||||
Short talk (½ session): |
||||
|
||||
Two types of conferences are available: |
||||
Talks that covering specific subtopics which are for people with special interest in them. It takes half session including question-answer part. They will be broadcasted live. |
||||
|
||||
- The **lightning talks**, lasting **15 minutes**, no questions asked. |
||||
- The **conferences**, lasting **40 minutes**, no questions asked. |
||||
Lightning talk (1/8 session): |
||||
|
||||
Speakers are invited to join the speaker booth after their conference, where they can interact with spectators who wish to continue the dialogue. |
||||
It is enlightening talks that do not exceed 6:30 minutes about any subject that the participants wish to record and broadcast in the conference by their own means. The lightning talks will be broadcasted from the tape. There will be no question-answer sections. In a session, 8 lightning talks will be broadcasted. |
||||
|
||||
## Can I submit a talk with another speaker? |
||||
Freestyle: |
||||
These are the sessions that will be broadcasted during the event, selected from a system where the participants can present their opinions and vote on the subject. There are no subject restrictions. If ze gets enough votes, the speaker can play a ukulele and sing a session. A maximum of 8 freestyle speeches will be broadcasted. The difference between lightning talks and free style is that the sessions will go through the approval of the community, not the approval of the event committee. |
||||
|
||||
Yes but 2 maximum (you included). On the CFP website, fill in the e-mail of the other speaker, they must have previously registered on the CFP with the same address. |
||||
Event committee: |
||||
|
||||
## Perks |
||||
|
||||
If you are selected for a 40 minutes talk you will get: |
||||
|
||||
* Conference ticket |
||||
* Speaker Dinner access |
||||
* One or two nights in an hotel close to the venue (if you ask for it in the speaker form) |
||||
* Flight/train tickets remboursed up to 250 euros within Europe (more on a case by case basis) |
||||
|
||||
If you are selected for a 15 minutes talk you will get: |
||||
|
||||
* Conference ticket |
||||
* Speaker Dinner access |
||||
* One or two nights in an hotel close to the venue (on a case by case basis) |
||||
|
||||
For all Flight/train reservations, please contact `speakers AT devfesttoulouse.fr` with the details of your prefered journey and we will get it for you. |
||||
|
||||
In case your subject is not accepted, you will still be able to buy your ticket after the notification, at the normal price. |
||||
|
||||
## What is the expected format for slides? |
||||
|
||||
You can present your conference from your own computer, or provide us with the slides in PDF format in advance. |
||||
The slides theme is entirely free, and the presentations will then be broadcast on the YouTube channel GDG France, which already hosts the presentations of previous years. |
||||
|
||||
## Let's propose a talk! |
||||
|
||||
As explained above, the CFP will be opened till May the 25th 2019. Last year we got around 350 propositions, so do not wait till the last minute to [propose yours](https://conference-hall.io/public/event/HJRThubF4uYPkb7jSUxi)! |
||||
|
||||
If you have any questions, you can contact us at `contact AT devfesttoulouse.fr` or via Twitter [@DevFestToulouse](https://twitter.com/DevFestToulouse). |
||||
* Alper Atmaca |
||||
* Neslihan Turan |
||||
* Özcan Oğuz |
||||
* Cemre Demircioğlu |
||||
|
||||
@ -1,78 +1,60 @@ |
||||
--- |
||||
title: Appel À Orateurs |
||||
brief: Les soumissions sont ouvertes jusqu’au 25 Mai 2019 |
||||
title: Etkin katılım çağrısı |
||||
brief: 16-17 Mayıs'ta çevrimiçi yayındayız! |
||||
image: /images/blog/cfp.jpg |
||||
date: 2019-03-23 |
||||
date: 2020-04-10 |
||||
draft: false |
||||
--- |
||||
|
||||
Le DevFest Toulouse aura lieu, pour sa 4ème édition, le 03 Octobre 2019 au Centre des Congrès Pierre Baudis de Toulouse et réunira 1000 développeurs, personnes travaillant dans les métiers techniques de l’informatique et étudiants. |
||||
İçinde bulunduğumuz COVID-19 pandemisi sebebiyle, dünya çapında ve Türkiye'de yüzyüze gerçekleştirilen neredeyse bütün etkinliklerin iptal olması, normal şartlarda özgür yazılım etkinlikleri açısından zengin geçen Nisan-Mayıs aylarının boşta kalmasına sebebiyet verdi. Dünyanın özgür yazılım alanındaki en büyük konferanslarından LibrePlanet 2020'nin çevrimiçi düzenlenmesi sürecinden kazanılan tecrübe ile Özgür Yazılım Derneği, 16-17 Mayıs 2020 tarihlerinde çevrimiçi olarak ÖzgürKon konferansını düzenliyor. |
||||
|
||||
En attendant le jour J, le [CFP](https://conference-hall.io/public/event/HJRThubF4uYPkb7jSUxi) (Call For Papers / Appel à Orateurs) du DevFest Toulouse est désormais ouvert ! Cette année, vous pouvez soumettre du 25 Mars jusqu’au 25 Mai (2 mois). |
||||
Fiziksel engeller bulunmadığı için uluslararası olarak düzenlenmesi planlanan ÖzgürKon, İngilizce-Türkçe dillerinde yapılacaktır. Konferansın iki paralel aksta olması planlanmaktadır, talebe göre bu sayı artabilir ya da azalabilir. |
||||
|
||||
A mi-CFP, une pré-sélection de nos “early speakers” sera effectuée, ne tardez donc pas à soumettre vos propositions! ;) |
||||
La délibération finale se fera ensuite pendant le mois de Juin. |
||||
İlerleyen yıllarda konferansın fiziksel alanda yine uluslararası olarak düzenlenmeye devam edilmesi planlanmaktadır. |
||||
|
||||
## Equipe |
||||
Bu seneki ÖzgürKon'un ana teması "COVID-19 pandemisi ve özgür yazılım özelinde özgürlük mücadeleleri" olarak belirlenmiştir. Bu ana tema dahilinde konferansın konuları şunlardır: |
||||
|
||||
Cette année, en plus des communautés déjà représentées par notre core team (GDG Toulouse, Toulouse Data Science, Duchess France, Toulouse DevOps, PitchMeUp, JAM) nous élargissons encore plus notre panel en ajoutant nos amis des communautés .NET, React, JUG, Rust, Python & Linux / Embedded |
||||
* Özgür yazılım felsefesi ve mücadelesi |
||||
* İnternet özgürlüğü |
||||
* Donanım özgürlüğü ve özgür donanım projeleri |
||||
* Özgür sanat ve uygulamaları |
||||
* Bilgi özgürlüğü, bilgiye erişim ve özgür bilgi paylaşım platformları |
||||
* Belge özgürlüğü, basın özgürlüğü, özgür medya(lar) |
||||
* Sağlık ve tıp alanlarında özgür yazılım ve özgür donanım |
||||
* Bilişim okur yazarlığı |
||||
* Dijitalleşme ve dönüşüm |
||||
* Mahremiyet ve gizlilik |
||||
* Uzaktan eğitim ve eğitimde özgür yazılım |
||||
* Kaybolmakta olan diller ve İnternet |
||||
* Hack ve hack kültürü, hacktivizm |
||||
* Dijital kültürlerde çeşitlilik ve kapsayıcılık |
||||
* Özgür lisanslar |
||||
* "Halkın parası, halkın kodları" projesi |
||||
* Kriptoloji, kriptografi |
||||
* Telif hakları ve patentler |
||||
* Dijital kütüphaneler ve e-kütüphanecilik |
||||
|
||||
La liste de l'équipe au complet : <https://devfesttoulouse.fr/team/> |
||||
Her bir oturum 50 dakikadır. |
||||
|
||||
## Catégories |
||||
Konuşma (1 oturum): |
||||
|
||||
* Big Data / ML / AI : Small et Big Data, Machine Learning et Intelligence Artificielle |
||||
* Cloud/infra : GCP, AWS, Azure, Kubernetes ... |
||||
* IoT : Objets connectés |
||||
* Languages : Une conf sur un langage en particulier ? A propos de Rust, Golang, Swift … vous pourrez choisir cette catégorie |
||||
* Methods & Tools : Ici on parle de craftsmanship, de DevOps, d’intégration et de déploiement continu, d’IaC (Infrastructure as Code) ... |
||||
* Native mobile apps : Android, iOS, React Native et autres développements mobiles |
||||
* Web : Les dernières technos web (PWA, Web Component, services workers ...)... |
||||
* UX : Ergonomie et expérience utilisateur |
||||
* WTF et autres : Une idée de talk mais qui n'entre pas dans les précédentes catégories ? Pas de souci, vous pouvez également soumettre votre talk. |
||||
Konferansın ana konuları kapsamında geniş bir kitle açısından önem arz eden konuşmalar/sunumlardır. Soru-cevap bölümü dahil süresi 1 oturumdur. Canlı yayınlanır. |
||||
|
||||
Kısa konuşma (½ oturum): |
||||
|
||||
## Formats |
||||
Spesifik alt konular dahilinde katılımcıların özel ilgi alanlarında olabilecek kısa konuşmalardır. Soru-cevap bölümü dahil süresi yarım oturumdur. Canlı yayınlanır. |
||||
|
||||
Deux types de présentations sont proposés : |
||||
Yıldırım konuşma (1/8 oturum): |
||||
|
||||
- Les **lightning talks**, d’une durée de **15 minutes**, sans question. |
||||
- Les **classical talks**, d’une durée de **40 minutes**, sans question. |
||||
İsteyen katılımcıların kendi imkanlarıyla kaydedip konferansta yayınlanması için gönderdiği herhangi bir konu hakkında 6:30 dakikayı aşmayan aydınlatıcı konuşmalardır, banttan yayınlanır. Soru-cevap alınmayacaktır. Bir oturumda sekiz adet yıldırım konuşma yayınlanacaktır. |
||||
|
||||
Serbest stil: |
||||
|
||||
Les orateurs sont invités à rejoindre le speaker booth après leur présentation : ils pourront y interagir avec les spectateurs désireux de poursuivre le dialogue. |
||||
Etkinlik süresince yayınlanacak, katılımcıların fikir sunup konu oylayabildikleri bir sistemden seçilen konuşmalardır. Konu kısıtlaması yoktur. Eğer yeterli oyu alırsa konuşmacı, ukulele çalıp bize dinletebilir. En çok oy alan en fazla 8 serbest stil konuşma yayınlanacaktır. Yıldırım konuşmalardan farkı; konuların etkinlik komitesi onayından değil, topluluğun onayından geçecek olmasıdır. |
||||
|
||||
## Puis-je soumettre un talk avec un autre intervenant ? |
||||
Etkinlik komitesi: |
||||
|
||||
Oui mais maximum à deux (vous inclu). Le deuxieme intervenant doit aussi avoir un compte sur la platforme CFP pour pouvoir l'ajouter avec son adresse e-mail. |
||||
|
||||
## Avantages |
||||
|
||||
Si votre talk de 40 min est sélectionné vous aurez droit à : |
||||
|
||||
* Ticket pour la conference |
||||
* Accès au dîner speaker |
||||
* Une ou deux nuits d'hôtel proche de la conférence |
||||
* Un remboursement jusqu'à 250 euros en Europe (plus au cas par cas) |
||||
|
||||
|
||||
Si votre talk de 15 min est sélectionné vous aurez droit à : |
||||
|
||||
* Ticket pour la conference |
||||
* Accès au dîner speaker |
||||
* Une ou deux nuits d'hôtel proche de la conférence (au cas par cas) |
||||
|
||||
Pour toute réservation de vols/trains, merci de contacter `speakers AT devfesttoulouse.fr` avec les détails d’horaires / préférences et nous nous chargerons de la réservation/paiement. |
||||
|
||||
Au cas où votre sujet ne serait pas accepté, il vous sera encore possible d’acheter votre place après la notification, au tarif normal. |
||||
|
||||
## Quel est le format attendu pour les slides ? |
||||
|
||||
Vous pouvez projeter à partir de votre propre ordinateur ou bien nous fournir au préalable vos slides au format PDF. |
||||
Le thème des slides est entièrement libre. Les présentations seront ensuite diffusées sur la [chaîne YouTube GDG France](https://www.youtube.com/channel/UCx83f-KzDd3o1QK2AdJIftg) qui héberge déjà les présentations des années précédentes. |
||||
|
||||
## Vous m’avez convaincu, je soumets ! |
||||
|
||||
Comme dit ci-dessus, les soumissions sont ouvertes jusqu’au 25 Mai 2019. L’année dernière nous avons reçu plus de 350 soumissions ! N’attendez pas le dernier moment, [soumettez un talk dès à présent](https://conference-hall.io/public/event/HJRThubF4uYPkb7jSUxi) ! |
||||
|
||||
Vous avez des questions ? Vous pouvez écrire un message à l’équipe à `contact AT devfesttoulouse.fr` ou bien sur notre compte Twitter [@DevFestToulouse](https://twitter.com/DevFestToulouse). |
||||
* Alper Atmaca |
||||
* Neslihan Turan |
||||
* Özcan Oğuz |
||||
* Cemre Demircioğlu |
||||
|
||||
@ -1,29 +0,0 @@ |
||||
--- |
||||
title: Lancement du DevFest Toulouse édition 2019 |
||||
brief: Soyez prêt ! |
||||
image: /images/blog/hello-2019.jpg |
||||
date: 2019-01-28 |
||||
draft: false |
||||
--- |
||||
|
||||
Aujourd’hui, nous avons le plaisir de vous annoncer que la 4ème édition du DevFest Toulouse se déroulera **le jeudi 03 Octobre 2019 au Centre des Congrès Pierre Baudis**. |
||||
|
||||
Tout comme l’année dernière, la journée se déroulera en plein coeur de Toulouse, dans le quartier de Compans Cafarelli. Le Centre de Congrès est accessible en transport en commun et en voiture. Nous aurons l’occasion d’accueillir **plus de conférences**, **plus de partenaires** et surtout **plus de participants**. |
||||
|
||||
{{< centered-img src="/images/blog/baudis.jpg" alt="Pierre Baudis" width="800" >}} |
||||
|
||||
## La suite des réjouissances : |
||||
|
||||
* Ouverture du [CFP](https://conference-hall.io/public/event/HJRThubF4uYPkb7jSUxi) : 1er Avril |
||||
* Ouverture de la billetterie (environ 1000 places disponibles) : en Avril. |
||||
|
||||
Dans les jours/semaines à venir nous communiquerons sur le thème de l'édition 2019. Suivez-nous sur [Twitter](https://twitter.com/devfesttoulouse), [LinkedIn](https://www.linkedin.com/company/devfesttoulouse/) ou sur ce site afin de rester informés ! :-) |
||||
|
||||
## Vous en voulez encore ? |
||||
|
||||
* [Vidéo des meilleurs moments 2018](https://www.youtube.com/watch?v=ZQGRMJzi6yU) |
||||
* [Retrouvez toutes les conférences de l’édition 2018](https://www.youtube.com/watch?v=ZQGRMJzi6yU&list=PLuZ_sYdawLiXmCwIYJs7AcBaXmUsVgPMU) |
||||
* [Revivez l’édition 2018 avec les photos officielles](https://photos.google.com/share/AF1QipNXrf4emzX-sHvtCLQ6oJOHoTKs-JpNS34QLOQ3J_vQPIwAOS6mA1svo_-EUsLAdA?key=TVY3dlFTMHBkX2tYazR0U0lBTGhJMEpHZWE4UHR3) |
||||
* [Le programme et toutes les infos : sur le site Edition 2018](https://2018.devfesttoulouse.fr/) |
||||
|
||||
On vous attends le 3 Octobre 2019 ! :-) |
||||
@ -1,29 +0,0 @@ |
||||
--- |
||||
title: Get ready for DevFest Toulouse 2019! |
||||
brief: DevFest season is back |
||||
image: /images/blog/hello-2019.jpg |
||||
date: 2019-01-28 |
||||
draft: false |
||||
--- |
||||
|
||||
Today it is with great pleasure that we announce you that the 4th edition of DevFest Toulouse will take place **October 3rd 2019 at the center of congress Pierre Baudis**. |
||||
|
||||
As last year, the event will be right in the city center, in the Compans Cafarelli neighborhood. The center of congress Pierre Baudis is accessible by the subway, bus or even by car. This year we will have **more space**, **more sponsors** and **more attendees** |
||||
|
||||
{{< centered-img src="/images/blog/baudis.jpg" alt="Pierre Baudis" width="800" >}} |
||||
|
||||
## What's next? |
||||
|
||||
* The [CFP](https://conference-hall.io/public/event/HJRThubF4uYPkb7jSUxi) will open April the 1st |
||||
* Tickets will open in April as well (1000 tickets available) |
||||
|
||||
We will be communicating about this year theme pretty soon on Twitter [@DevFestToulouse](https://twitter.com/DevFestToulouse/), stay tuned! |
||||
|
||||
## How was 2018 edition? |
||||
|
||||
* [A video recap of 2018](https://www.youtube.com/watch?v=ZQGRMJzi6yU) |
||||
* [Youtube playlist with 2018 talks](https://www.youtube.com/watch?v=ZQGRMJzi6yU&list=PLuZ_sYdawLiXmCwIYJs7AcBaXmUsVgPMU) |
||||
* [2018 Official pictures](https://photos.google.com/share/AF1QipNXrf4emzX-sHvtCLQ6oJOHoTKs-JpNS34QLOQ3J_vQPIwAOS6mA1svo_-EUsLAdA?key=TVY3dlFTMHBkX2tYazR0U0lBTGhJMEpHZWE4UHR3) |
||||
* [2018 website](https://2018.devfesttoulouse.fr/) |
||||
|
||||
We are waiting for you October 3rd, 2019! :-) |
||||
@ -0,0 +1,96 @@ |
||||
--- |
||||
title: GDPR and Data Protection Policy |
||||
|
||||
draft: false |
||||
--- |
||||
|
||||
Data Protection Policy |
||||
|
||||
This document is about our data processing, the basis of it and your rights as data subject regarding the Özgürkon attendence. |
||||
|
||||
## 1. Who is responsible for your data? |
||||
|
||||
Özgür Yazılım Derneği, as a legally founded association in Turkey is responsible for your data. For any inqury about your data you may contact bilgi@oyd.org.tr from your registery e-mail adress. |
||||
|
||||
Özgür Yazılım Derneği is a registered association in Republic of Turkey with the number 34-242-113. |
||||
|
||||
If you are from European zone or European citizen General Data Procetion Regulation and if you are not, 6698 Kişisel Verilerin Korunması Kanunu (local personal data protection law) is applicable. |
||||
|
||||
## 2. Personal Data we process |
||||
|
||||
### 2.1. Your Name and Surname |
||||
|
||||
2.1.1. Your legal name or nick is required to list you in speakers page and announce you in your presentation according your concent. |
||||
|
||||
2.1.2. Your name will be listed on speakers page with or withour your speech's record. |
||||
|
||||
2.1.3. Your name will be shared with unknown third party indirectly on our web page. |
||||
|
||||
### 2.2. Your picture |
||||
|
||||
2.2.1. You are not required to provide any picture of you for your application. You may provide any graphic you deem appropiate. If you do not provide one we will choose one for you. |
||||
|
||||
2.2.2. If you choose to share a picture with us it will be listed on speakers page with your speach. |
||||
|
||||
2.2.3. By putting your picture on our web page, we will be sharing it with unknown third party indirectly. |
||||
|
||||
### 2.3. Your personal info |
||||
|
||||
2.3.1. Your personal info such as your prefered language, the language of your speach, where you are from is required to inform viewers about you and your speech. |
||||
|
||||
2.3.2. Your personal information will be listed on our web page for your biography and for your speech. |
||||
|
||||
2.3.3. By listing your information on our web page, we will be sharing it with unknown third party indirectly. |
||||
|
||||
### 2.4. Your email adress |
||||
|
||||
2.4.1. An email address is required to contact you for any development during prior and during the conferance. You are not required to provide an email address. If you choose not to we won't be able to inform you about conferance related issues. |
||||
|
||||
2.4.2. Depending on your consent your email address will be used exclusively communicate with you about the conference. |
||||
|
||||
2.4.3. We will not share your email adress with any third party. |
||||
|
||||
2.4.4. If you concent us we may keep your email address for future contacts. |
||||
|
||||
2.4.5. If your consent is absent we will delete your email info after the conference and related issues are over. |
||||
|
||||
### 2.5. IP adress |
||||
|
||||
2.5.1. Your IP adress is not required admistratively but our online conferance software and web page as any other server-client based system requires your IP address to function. |
||||
|
||||
2.5.2. Your IP address is only processed during your use of our online conference software or web page. |
||||
|
||||
2.5.3. We will not share your IP adress with any third party. |
||||
|
||||
2.5.4. Upon your termination of connection your IP address will be deleted. |
||||
|
||||
## 3. Your rights |
||||
|
||||
At any point you may request; |
||||
|
||||
3.1. If your personal data is processed and if it is, any information about the processing. |
||||
3.2. The purposes of the processing for which the personal data are intended as well as the legal basis for the processing |
||||
3.3. If your personal data is transfered to any third party. |
||||
3.4. Rectification of inaccurate personal data. |
||||
3.5. Erasure of personal data |
||||
3.6. Restriction of processing |
||||
3.7. Your processed data on a portable format. |
||||
|
||||
Your speechs recording and any personal data that may include is considered as copyleft creation where usage is regualted by the terms of the license of the creation. |
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,94 @@ |
||||
--- |
||||
title: Veri Koruma Politikası |
||||
|
||||
draft: false |
||||
--- |
||||
Bu metin Özgürkon kapsamında veri işleme politikamıza, kaynağına ve ilgili kişi olarak haklarınıza ilişkindir. |
||||
|
||||
## 1. Kişisel verilerinizin sorumlusu kimdir? |
||||
|
||||
Özgür Yazılım Derneği kişisel verilerinizin sorumlusudur. Kişisel verileriniz ile ilgili haklarınızı bilgi@oyd.org.tr'ye kayıt sırasında veridiğiniz e-posta adresi ile yazarak soru ve taleplerinizi yöneltebilirsiniz. |
||||
|
||||
Özgür Yazılım Derneği, Türkiye Cumhuriyeti'nde 34-242-113 kütük numarası ile kayıtlı resmi bir dernektir. |
||||
|
||||
Eğer Avrupa Birliği bölgesinden veya Avrupa vatandaşı iseniz General Data Protection Regulation ve eğer değilseniz 6698 Kişisel Verilerin Korunması Kanunu geçerlidir. |
||||
|
||||
## 2. İşlediğimiz kişisel veriler |
||||
|
||||
### 2.1. Adınız ve Soyadınız |
||||
|
||||
2.1.1.Yasal adınız veya rumuzunuz sizi konuşmacılar sayfasında listeleyebilmek ve sunumunuzda tanıtmak için rızanız kapsamında gereklidir. |
||||
|
||||
2.1.2.Adınız konuşmacılar sayfasında konuşmanızın kaydı ile birlikte veya ayrı olarak listelenecektir. |
||||
|
||||
2.1.3.İsminiz belirsiz üçüncü kişilerle dolaylı olarak sayfamıza listelenmekle paylaşılacaktır. |
||||
|
||||
### 2.2. Fotoğrafınız |
||||
|
||||
2.2.1. Başvurunuz ile birlikte bir fotoğrafınızı vermek zorunda değilsiniz. Herhangi bir uygun gördüğünüz görseli sunabilirsiniz. Eğer bir tane sunmazsanız biz yerinize uygun bir görsel seçeceğiz. |
||||
|
||||
2.2.2. Eğer bizimle fotoğrafınızı paylaşmayı seçerseniz fotoğrafınız konuşmacılar sayfasında konuşmanıza ilişkik olarak yayınlanacaktır. |
||||
|
||||
2.2.3. Fotoğrafınızı web sayfasında yayınlamakla dolaylı olarak bilinmeyen üçüncü kişilerle paylaşmış olacağız. |
||||
|
||||
### 2.3. Kişisel bilgileriniz |
||||
|
||||
2.3.1. Tercih ettiğiniz dil, konuşmanızın dili, bulunduğunuz ülke bilgileri konferans katılımcılarını siz ve konuşmanız hakkında bilgilendirmek için gereklidir. |
||||
|
||||
2.3.2. Kişisel bilgileriniz web sayfamızda biyografiniz ve konuşmanız ile birlikte listelenecektir. |
||||
|
||||
2.3.3. Kişisel bilgilerinizi web sayfamızda yayınlamakla dolaylı olark bilinmeyen üçüncü kişilerle paylaşmış olacağız. |
||||
|
||||
### 2.4. E-posta adresiniz |
||||
|
||||
2.4.1.Bir e-posta adresi sizinle konferans öncesi veya sonrasında olabilecek gelişmeler hakkında size ulaşabilmemiz için gereklidir. Bir e-psota adresi vermek zorunda değilsiniz. Şayet vermemeyi seçerseniz konferansla ilgili sizinle iletişime geçmemiz mümkün olmaz. |
||||
|
||||
2.4.2.Rızanıza bağlı olarak e-posta adresinizi sadece sizinle iletişime geçmek için kullanacağız. |
||||
|
||||
2.4.3.E-posta adresinizi herhangi bir üçüncü kişi ile paylaşmayacağız. |
||||
|
||||
2.4.4.Eğer rıza gösterirseniz e-postanızı sizinle ileride temasa geçmek için saklayabiliriz. |
||||
|
||||
2.4.5.Eğer rızanız yok ise e-posta adresinizi konferans ve ilgili konuların bitimi ertesinde derhal yok edeceğiz. |
||||
|
||||
### 2.5. IP adresi |
||||
|
||||
2.5.1. IP adresiniz herhangi bir yönetimsel sebeple gerekli değildir fakat çevrimiçi konferans yazılımımız ve web sayfamız tüm diğer sunucu-istemci tabanlı sistemler gibi IP adresinize işlev göstermek için gerek duymaktadır. |
||||
|
||||
2.5.2. IP adresiniz sadece çevrimiçi konferans sistemini veya web sayfamızı kullandığınız sürece işlenecektir. |
||||
|
||||
2.5.3. IP adresinizi herhangi bir üçüncü kişi ile paylaşmayacağız. |
||||
|
||||
2.5.4. Bağlantıyı kesmeniz üzerine IP adresiniz derhal yok edilecektir. |
||||
|
||||
## 3. Haklarınız |
||||
|
||||
Herhangi bir anda aşağıdaki haklarınızı talep edebilirsiniz: |
||||
|
||||
3.1. Kişisel verinizin işlenip işlenmediğini ve işleniyor ise işleme ile ilgili bilgi. |
||||
3.2. Belirli veya genel olarak işlenen kişisel verinizin işlenme amacını ve amacına uygun kullanılıp kullanılmadığını. |
||||
3.3. Kişisel verilerinizin aktarıldığı üçüncü kişileri talep edebilirsiniz. |
||||
3.4. İşlenen kişisel verilerinizin eksikliklerinin tamamlanmasını veya yanlışların düzeltilmesini. |
||||
3.5. Rızanıza bağlı işlenen kişisel verilerinizin her zaman, kanuni sebeplerle işlediğimiz verilerinizi ise kanunini gerekliliklerin yerine getirilmesi üzerine yok edilmesini talep edebilirsiniz. |
||||
3.6. İşlenen verilerinizin işlenmesini sınırlandırılmasını. |
||||
3.7. İşlenen verilerinizin taşınabilir biçimde size teslimini. |
||||
|
||||
Konuşmanızın kaydı ve buna dahil olabilecek tüm kişisel veriler copyleft ruhsat altında eser sayılmakla size sunulan eser sözleşmesi dahilinde değerlendirilecektir. |
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,37 @@ |
||||
--- |
||||
title: Live |
||||
draft: false |
||||
--- |
||||
|
||||
|
||||
|
||||
|
||||
<!-- <script src="https://vjs.zencdn.net/7.7.6/video.js"></script> |
||||
|
||||
<div class="hero"> |
||||
<video |
||||
id="ozgurkon-live" |
||||
class="video-js" |
||||
controls |
||||
preload="auto" |
||||
width="960" |
||||
height="540" |
||||
poster="/ozgurkon.jpg" |
||||
data-setup="{}" controls> |
||||
<source src="rtmp://live.ozgurkon.org:1936/live/live" type="rtmp/flv"> |
||||
<p class="vjs-no-js"> |
||||
To view this video please enable JavaScript, and consider upgrading to a |
||||
web browser that |
||||
<a href="https://videojs.com/html5-video-support/" target="_blank" |
||||
>supports HTML5 video</a |
||||
> |
||||
</p> |
||||
</video> |
||||
</div> |
||||
<script> |
||||
<script> |
||||
var player = videojs('ozgurkon-live'); |
||||
player.play(); |
||||
player.hlsQualitySelector(); |
||||
</script> --> |
||||
|
||||
@ -0,0 +1,3 @@ |
||||
--- |
||||
title: Canlı |
||||
--- |
||||
@ -0,0 +1,38 @@ |
||||
--- |
||||
key: fsf |
||||
title: Free Software Foundation |
||||
category: partners |
||||
order: 20 |
||||
logo: /images/partners/fsf.svg |
||||
website: 'https://fsf.org' |
||||
lang: tr |
||||
socials: |
||||
- icon: twitter |
||||
link: 'https://twitter.com/fsf' |
||||
name: fsf |
||||
--- |
||||
The Free Software Foundation (FSF) is a nonprofit with a worldwide mission to promote computer user freedom. We defend the rights of all software users. |
||||
|
||||
As our society grows more dependent on computers, the software we run is of critical importance to securing the future of a free society. Free software is about having control over the technology we use in our homes, schools and businesses, where computers work for our individual and communal benefit, not for proprietary software companies or governments who might seek to restrict and monitor us. The Free Software Foundation exclusively uses free software to perform its work. |
||||
|
||||
The Free Software Foundation is working to secure freedom for computer users by promoting the development and use of free (as in freedom) software and documentation—particularly the GNU operating system—and by campaigning against threats to computer user freedom like Digital Restrictions Management (DRM) and software patents. |
||||
|
||||
The free software movement is one of the most successful social movements to arise from computing culture, driven by a worldwide community of ethical programmers dedicated to the cause of freedom and sharing. But the ultimate success of the free software movement depends upon teaching our friends, neighbors and work colleagues about the danger of not having software freedom, about the danger of a society losing control over its computing. |
||||
Our Core Work |
||||
|
||||
The FSF maintains historic articles covering free software philosophy and maintains the Free Software Definition—to show clearly what must be true about a particular software program for it to be considered free software. |
||||
|
||||
The FSF sponsors the GNU Project—the ongoing effort to provide a complete operating system licensed as free software. We also fund and promote important free software development and provide development systems for GNU software maintainers, including full email and shell services and mailing lists. We are committed to furthering the development of the GNU Operating System and enabling volunteers to easily contribute to that work, including sponsoring Savannah the source code repository and center for free software development. |
||||
|
||||
The FSF holds copyright on a large proportion of the GNU operating system, and other free software. We hold these assets to defend free software from efforts to turn free software proprietary. Every year we collect thousands of copyright assignments from individual software developers and corporations working on free software. We register these copyrights with the US copyright office and enforce the license under which we distribute free software — typically the GNU General Public License. We do this to ensure that free software distributors respect their obligations to pass on the freedom to all users, to share, study and modify the code. We do this work through our Free Software Licensing and Compliance Lab. |
||||
|
||||
The FSF publishes the GNU General Public License (GNU GPL), the world's most popular free software license, and the only license written with the express purpose of promoting and preserving software freedom. Other important licenses we publish include the GNU Lesser General Public License (GNU LGPL), the GNU Affero General Public License (GNU AGPL) and the GNU Free Document License (GNU FDL). Read more about our free software licensing and related issues. |
||||
|
||||
The FSF campaigns for free software adoption and against proprietary software. Threats to free software include Digital Restrictions Management (DRM), Software Patents and Treacherous Computing. Find out more about our campaigns, and ways to volunteer. |
||||
|
||||
The FSF also provides important resources to the community including the FSF/UNESCO free software directory. |
||||
Support Our Mission |
||||
|
||||
The most important support you can give to free software is to use free software on your own computer and advocate within your business or community for others to adopt it. Subscribe to our monthly newsletter the Free Software Supporter to hear about ways you can get involved. |
||||
|
||||
You can directly support our mission by donating or becoming a card carrying associate member of the Free Software Foundation. |
||||
@ -0,0 +1,20 @@ |
||||
--- |
||||
key: fsfe |
||||
title: Free Software Foundation Europe |
||||
category: partners |
||||
order: 20 |
||||
logo: /images/partners/fsfe.svg |
||||
website: 'https://fsfe.org' |
||||
lang: tr |
||||
socials: |
||||
- icon: twitter |
||||
link: 'https://twitter.com/fsfe' |
||||
name: fsfe |
||||
--- |
||||
Free Software Foundation Europe is a charity that empowers users to control technology. |
||||
|
||||
Software is deeply involved in all aspects of our lives; and it is important that this technology empowers rather than restricts us. Free Software gives everybody the rights to use, understand, adapt and share software. These rights help support other fundamental freedoms like freedom of speech, press and privacy. |
||||
|
||||
Avrupa Özgür Yazılım Vakfı, kullanıcıları, teknolojiyi denetimleri altında tutmaları yönünde güçlendiren bir vakıftır. |
||||
|
||||
Yazılım, yaşamımızın bütün boyutlarını derinliğine kuşatmış durumda. Bu teknolojinin bizi kısıtlamaktan ziyade güçlendirmesi önemlidir. Özgür Yazılım herkese yazılımı kullanma, anlama, uyarlama ve paylaşma hakkını verir. Bu haklar ifade özgürlüğü, basın özgürlüğü ve mahremiyet gibi diğer özgürlükleri desteklemekte yardımcı olur. |
||||
@ -0,0 +1,25 @@ |
||||
--- |
||||
key: mercode |
||||
title: Mercode |
||||
category: partners |
||||
order: 20 |
||||
logo: /images/partners/mercode.png |
||||
website: 'http://mercode.org/' |
||||
lang: tr |
||||
socials: |
||||
- icon: twitter |
||||
link: 'https://twitter.com/mercodeorg' |
||||
name: mercodeorg |
||||
- icon: github |
||||
link: 'https://github.com/mercode-org' |
||||
name: mercode-org |
||||
--- |
||||
Mercode is a libre software community which gathers coders, hackers, activists and designers worldwide. Also it is the Turkish name of planet Mercury, the first planet of the solar system. |
||||
|
||||
Mercode is not an enterpreneurship, company or a brand and is very strict about your privacy and rights. Mercode’s cause is to dominate the world with decentralised internet friendly open source products and people using them in order to crush the monopoly of companies like Microsoft, Apple, Amazon, Google and many others. The Mercode team keeps working for achieving this cause of humanity. |
||||
|
||||
Mercode and its subprojects are existing thanks to the donations of our users and team members. So the progression of Mercode is in the hands of the community. If you would like to see this team contributing more to the community, you can donate us on Patreon or send Etherium to our wallet to help us paying our server bills or to order us a coffee (because we need it after long hours of coding). If Mercode wouldn’t be able to keep contributing, *they* will win. |
||||
|
||||
At Mercode, there isn't such a big division between the community and the team. Everyone, from every type of background and age can apply to our team. The only rule to be applied is to contribute and give support to this beautiful libre community. |
||||
|
||||
We believe the humanity can outgo the borders, nations and flags with the Internet. Unfortunatelly the web which was ment to be unowned is being invaded by the server monopoly of big companies co-operating with states. The only solution to overthrow that invasion is to decentralize! |
||||
@ -0,0 +1,162 @@ |
||||
--- |
||||
key: stf |
||||
title: Small Tech Foundation |
||||
category: partners |
||||
order: 20 |
||||
logo: /images/partners/stf.png |
||||
website: 'https://small-tech.org' |
||||
lang: tr |
||||
socials: |
||||
- icon: email |
||||
link: 'mailto:hello@small-tech.org' |
||||
name: hello@small-tech.org |
||||
--- |
||||
__We’re a tiny and independent two-person not-for-profit based in Ireland.__ We advocate for and build small technology to protect personhood and democracy in the digital network age. |
||||
|
||||
Read on to learn more about [the foundation](#the-foundation) and [small technology](#small-technology). |
||||
|
||||
## The foundation |
||||
|
||||
We’re [Laura Kalbag](https://laurakalbag.com) and [Aral Balkan](https://ar.al) (and Oskar the huskamute). We live and work in Cork, Ireland. |
||||
|
||||
Since 2014, we’ve been advocating for regulation of surveillance capitalism, investment in ethical alternatives, and carrying out [research and development](/research-and-development) on ethical alternatives. |
||||
|
||||
After [leaving the UK](https://ar.al/notes/so-long-and-thanks-for-all-the-fish/) and [moving to Ireland](https://laurakalbag.com/move-to-ireland/), we set up the Small Technology Foundation with the mission to evolve the Internet so each one of us can own and control our own place on it. |
||||
|
||||
We strive to follow [the principles of Small Technology](#small-technology) in our work. |
||||
|
||||
We don’t take money from surveillance capitalists and we exist thanks to [the support of individuals like you](/fund-us). |
||||
|
||||
### History |
||||
|
||||
Here is a short timeline of important events in our history. |
||||
|
||||
<ul class='timeline'> |
||||
<li> |
||||
<h3>2014</h3> |
||||
<p>We set up <a href='https://ind.ie'>Ind.ie</a> as a not-for-profit in Brighton, UK</p> |
||||
</li> |
||||
<li> |
||||
<h3>2015</h3> |
||||
<p>We release the <a href='https://ind.ie/heartbeat'>Heartbeat</a> pre-alpha. Heartbeat is the spiritual precursor to Tincan. We realise, however, that our current technology stack is not fit to take the project further. In dire need of funds, we invest our remaining money to develop <a href='https://better.fyi'>Better Blocker</a>.</p> |
||||
</li> |
||||
<li> |
||||
<h3>2015</h3> |
||||
<p>The Conservatives win re-election in the UK with a manifesto that details plans to pass a draconian surveillance law (the IP Act), hold a referendum on leaving the EU, and scrap the Human Rights Act. As this is fundamentally incompatible with our mission, <a href='https://ar.al/notes/so-long-and-thanks-for-all-the-fish/'>we decide to leave the UK</a>.</p> |
||||
</li> |
||||
<li> |
||||
<h3>2016</h3> |
||||
<p>We move to Sweden. We release <a href='https://better.fyi'>Better Blocker</a>, a no-nonsense tracker blocker. Laura’s book, <a href='https://abookapart.com/products/accessibility-for-everyone'>Accessibility For Everyone</a>, is published.</p> |
||||
</li> |
||||
<li> |
||||
<h3>2017</h3> |
||||
<p>We start working with the City of Ghent on project Indienet to explore how Small Technology principles can be applied at the city level.</p> |
||||
</li> |
||||
<li> |
||||
<h3>2018</h3> |
||||
<p>We leave Sweden and <a href='https://laurakalbag.com/move-to-ireland/'>move to Ireland</a>.</p> |
||||
</li> |
||||
<li> |
||||
<h3>2019</h3> |
||||
<p>We launch the Small Technology Foundation and <a href='https://sitejs.org'>Site.js</a>. We continue our research and development with project Tincan.</p> |
||||
</li> |
||||
</ul> |
||||
|
||||
## Small Technology |
||||
|
||||
Small Technology are everyday tools for everyday people designed to increase human welfare, not corporate profits. |
||||
|
||||
### Small Tech is… |
||||
|
||||
<ul class='box-list'> |
||||
<li><a href='#easy-to-use'>easy to use</a></li> |
||||
<li><a href='#personal'>personal</a></li> |
||||
<li><a href='#private-by-default'>private by default</a></li> |
||||
<li><a href='#share-alike'>share alike</a></li> |
||||
<li><a href='#peer-to-peer'>peer to peer</a></li> |
||||
<li><a href='#interoperable'>interoperable</a></li> |
||||
<li><a href='#zero-knowledge'>zero knowledge</a></li> |
||||
<li><a href='#non-commercial'>non-commercial</a></li> |
||||
<li><a href='#non-colonial'>non-colonial</a></li> |
||||
<li><a href='#inclusive'>inclusive</a></li> |
||||
</ul> |
||||
|
||||
### Personal |
||||
|
||||
Small Technology are everyday tools for everyday people. They are not tools for startups or enterprises. |
||||
|
||||
### Easy to use |
||||
|
||||
Personal technology are everyday things that people use to improve the quality of their lives. As such, in addition to being functional, secure, and reliable, they must be convenient, easy to use, and inclusive. If possible, we should aim to make them delightful. |
||||
|
||||
__Related aspects:__ [inclusive](#inclusive) |
||||
|
||||
### Non-colonial |
||||
|
||||
Small technology is made by humans for humans. They are not built by designers and developers for users. They are not built by Western companies for people in African countries. If our tools specifically target a certain demographic, we must ensure that our development teams reflect that demographic. If not, we must ensure people from a different demographic can take what we make and specialise it for their needs. |
||||
|
||||
__Related aspects:__ [share alike](#share-alike), [non-commercial](#non-commercial), [interoperable](#interoperable) |
||||
|
||||
### Private by default |
||||
|
||||
A tool respects your privacy only if it is private by default. Privacy is not an option. You do not opt into it. Privacy is the right to choose what you keep to yourself and what you share with others. “Private” (i.e., for you alone) is the default state of small technologies. From there, you can always choose who else you want to share things with. |
||||
|
||||
__Related aspects:__ [zero knowledge](#zero-knowledge), [peer to peer](#peer-to-peer) |
||||
|
||||
### Zero knowledge |
||||
|
||||
Zero-knowledge tools have no knowledge of your data. They may store your data, but the people who make or host the tools cannot access your data if they wanted to. |
||||
|
||||
Examples of zero-knowledge designs are end-to-end encrypted systems where only you hold the secret key, and peer-to-peer systems where the data never touches the devices of the app maker or service provider (including combinations of end-to-end encrypted and peer-to-peer systems). |
||||
|
||||
__Related aspects:__ [private by default](#private-by-default), [peer to peer](#peer-to-peer) |
||||
|
||||
|
||||
### Peer to peer |
||||
|
||||
Peer-to-peer systems enable people to connect directly with one and another without a person (or more likely a corporation or a government) in the middle. They are the opposite of client/server systems, which are centralised (the servers are the centres). |
||||
|
||||
On peer to peer systems, your data – and the algorithms used to analyze and make use of your data – stay on devices that you own and control. You do not have to beg some corporation to not abuse your data because they don’t have it to begin with. |
||||
|
||||
__Related aspects:__ [zero knowledge](#zero-knowledge), [private by default](#private-by-default) |
||||
|
||||
|
||||
### Share alike |
||||
|
||||
Most people’s eyes cloud over when technology licenses are mentioned but they’re crucial to protecting your freedom. |
||||
|
||||
Small Technology is licensed under Copyleft licenses. Copyleft licenses stipulate that if you benefit from technology that has been put into the commons, you must share back (“share alike”) any improvements, changes, or additions you make. If you think about it, it’s only fair: if you take from the commons, you should give back to the commons. That’s how we cultivate a healthy commons. |
||||
|
||||
__Related aspects:__ [interoperable](#interoperable), [non-colonial](#non-colonial), [non-commercial](#non-commercial) |
||||
|
||||
### Interoperable |
||||
|
||||
Interoperable systems can talk to one another using well-established protocols. They’re the opposite of silos. Interoperability ensures that different groups can take a technology and evolve it in ways that fit their needs while still staying compatible with other tools that implement the same protocols. Interoperability, coupled with share alike licensing, helps us to distribute power more equally as rich corporations cannot “embrace and extend” commons technology, thereby creating new silos. |
||||
|
||||
Interoperability also means we don’t have to resort to colonialism in design: we can design for ourselves and support other groups who design for themselves while allowing all of us to communicate with each other within the same global network. |
||||
|
||||
__Related aspects:__ [share alike](#share-alike), [non-colonial](#non-colonial) |
||||
|
||||
|
||||
### Non-commercial |
||||
|
||||
The primary purpose for Small Technology is not to make a profit but to increase human welfare. As such, they are built by not-for-profit organisations. Eventually, we hope that small technologies will be recognised for their contribution to the common good and therefore supported from the commons (e.g., from our taxes). In the interim, some methods for monetising Small Technology include: |
||||
|
||||
- Charging for hosting and maintenance services |
||||
- Sales on App Stores (for native apps) |
||||
- Donations and patronage |
||||
- Grants and awards |
||||
|
||||
Equity-based / Venture Capital investment is incompatible with Small Technology as the success criterion is the sale of the organisation (either to a larger organisation or to the public at large via an IPO). Small Technology is not about startups (temporary companies designed to either fail fast or grow exponentially and get sold), it’s about _stayups_ (sustainable organisations that contribute to the common good). |
||||
|
||||
__Related aspects:__ [non-colonial](#non-colonial), [share alike](#share-alike), [interoperable](#interoperable) |
||||
|
||||
### Inclusive {#inclusive} |
||||
|
||||
Being inclusive in technology is ensuring people have equal rights and access to the tools we build and the communities who build them, with a particular focus on including people from traditionally marginalised groups. Accessibility is the degree to which technology is usable by as many people as possible, especially disabled people |
||||
|
||||
Small Technology is inclusive and accessible. |
||||
|
||||
With inclusive design, we must be careful not to assume we know what’s best for others, despite us having differing needs. Doing so often results in colonial design, creating patronising and incorrect solutions. |
||||
|
||||
__Related aspects:__ [easy to use](#easy-to-use), [non-colonial](#non-colonial) |
||||
@ -0,0 +1,14 @@ |
||||
--- |
||||
key: yercizenler |
||||
title: Yerçizenler Derneği |
||||
category: partners |
||||
order: 20 |
||||
logo: /images/partners/yercizenler.png |
||||
website: 'http://yercizenler.org/' |
||||
lang: tr |
||||
socials: |
||||
- icon: email |
||||
link: 'mailto:info@yercizenler.org' |
||||
name: info@yercizenler.org |
||||
--- |
||||
Yer Çizenler, Temmuz 2017’den bu yana faaliyette olan ve insani yardım amaçlı çalışmalarda kullanılmak üzere açık ve özgür uzamsal veri kullanımını destekleyen bir sivil toplum kuruluşudur. Humanitarian OpenStreetMap Team (HOT) ile ortak çalışmalar gerçekleştiren Yer Çizenler, çok sayıda gönüllünün katılımıyla İstanbul’daki hassas gruplara yönelik hizmetlerin kapsamlı ve çok dilli haritalarını üretirken, bu toplulukları haritalar üzerinde görünür kılmak için çalışmaktadır. Yer Çizenler, şu ana kadar gerçekleştirdiği etkinlikler ve saha çalışmaları sonucunda 150 binin üzerinde bina sayısallaştırıp, 17 binin üzerinde servis noktası (POI) toplayarak İstanbul’un özgür veri altlığının iyileştirilmesine katkı sağlamıştır. |
||||
@ -1,24 +0,0 @@ |
||||
--- |
||||
key: apside |
||||
title: APSIDE |
||||
category: sponsors |
||||
order: 20 |
||||
logo: /images/partners/logo-apside.png |
||||
website: 'http://www.apside.com' |
||||
lang: tr |
||||
socials: |
||||
- icon: facebook |
||||
link: 'https://facebook.com/ApsideGroupe' |
||||
name: ApsideGroupe |
||||
- icon: twitter |
||||
link: 'https://twitter.com/ApsideGroupe' |
||||
name: ApsideGroupe |
||||
--- |
||||
APSIDE est une société de conseil en ingénierie qui accompagne tous les acteurs de l'écosystème IT sur leurs projets innovants. |
||||
Tous nos ingénieurs ont leur spécialité : JAVA, JS, BDD, C#, PHP, C++ ... |
||||
Nous sélectionnons rigoureusement les projets sur lesquels peuvent intervenir nos ingénieurs : caractère innovant, phase d'architecture, produits complets, sujets porteurs et utiles... |
||||
C'est ce qui rend totalement satisfaits de leur mission plus de 96% de nos ingénieurs. |
||||
Alors, prêt à tenter l'aventure ? |
||||
|
||||
APSIDE, c'est un groupe de plus de 2600 collaborateurs à travers la France... tous répartis en équipes d'experts localisées. |
||||
|
||||
@ -0,0 +1,20 @@ |
||||
--- |
||||
key: arkakapi |
||||
title: Arka Kapı |
||||
category: sponsors |
||||
order: 20 |
||||
logo: /images/partners/arkakapi.png |
||||
website: 'https://arkakapimag.com/' |
||||
lang: tr |
||||
socials: |
||||
- icon: twitter |
||||
link: 'https://twitter.com/arkakapimag' |
||||
name: arkakapimag |
||||
- icon: facebook |
||||
link: 'https://facebook.com/arkakapimag' |
||||
name: arkakapimag |
||||
- icon: instagram |
||||
link: 'https://instagram.com/arkakapimag' |
||||
name: arkakapimag |
||||
--- |
||||
BIMONTHLY CYBER SECURITY MAGAZINE / 2 AYLIK SİBER GÜVENLİK DERGİSİ |
||||
@ -1,20 +0,0 @@ |
||||
--- |
||||
key: axileo |
||||
title: AXILEO |
||||
category: sponsors |
||||
order: 22 |
||||
logo: /images/partners/logo-axileo.png |
||||
website: 'http://www.axileo.com' |
||||
lang: tr |
||||
socials: |
||||
- icon: facebook |
||||
link: 'https://www.facebook.com/Axileo75' |
||||
name: AXILEO |
||||
- icon: twitter |
||||
link: 'https://twitter.com/AXILEO1' |
||||
name: AXILEO1 |
||||
- icon: linkedin |
||||
link: 'https://www.linkedin.com/company/axileo' |
||||
name: AXILEO |
||||
--- |
||||
AXILEO est spécialisée dans l'innovation et la transformation digitale des entreprises. La société se distingue par un management innovant, sur le modèle de l'entreprise libérée, où les salariés participent et définissent la stratégie de l'entreprise. |
||||
@ -0,0 +1,22 @@ |
||||
--- |
||||
key: mbs |
||||
title: Made by Sense |
||||
category: sponsors |
||||
order: 20 |
||||
logo: /images/partners/madebysense.jpg |
||||
website: 'http://madebysense.co/' |
||||
lang: tr |
||||
socials: |
||||
- icon: email |
||||
link: 'mailto:info@madebysense.co' |
||||
name: info@madebysense.co |
||||
--- |
||||
|
||||
|
||||
Tanır, tanıtır. |
||||
|
||||
İstiklal Cad. 189 / 2 Beyoğlu, İstanbul |
||||
|
||||
+90 212 951 06 27 |
||||
|
||||
info@madebysense.co |
||||
@ -0,0 +1,30 @@ |
||||
--- |
||||
key: mono |
||||
title: Mono Bilişim |
||||
category: sponsors |
||||
order: 20 |
||||
logo: /images/partners/mono.png |
||||
website: 'https://mono.net.tr' |
||||
lang: tr |
||||
socials: |
||||
- icon: twitter |
||||
link: 'https://twitter.com/MonoBilisim' |
||||
name: MonoBilisim |
||||
- icon: facebook |
||||
link: 'https://www.facebook.com/MonoBilisim' |
||||
name: MonoBilisim |
||||
- icon: instagram |
||||
link: 'https://www.instagram.com/MonoBilisim' |
||||
name: MonoBilisim |
||||
- icon: github |
||||
link: 'https://github.com/MonoBilisim' |
||||
name: MonoBilisim |
||||
- icon: bitbucket |
||||
link: 'https://bitbucket.org/mono' |
||||
name: mono |
||||
--- |
||||
Mono Informatics Ltd. is founded in Istanbul, Turkey at February 4, 2010. Mono is specialised on free/libre software solutions. Develops informatic and communication technologies, serves consultancy, education, system administration and software development services. |
||||
|
||||
Mono Bilişim Limited Şirketi, 4 Şubat 2010 tarihinde, İstanbul’da kuruldu. Mono, özgür yazılım çözümleri üzerine uzmanlaşmıştır. Özgür yazılımlar kullanarak bilişim ve iletişim teknolojileri geliştirir; danışmanlık, eğitim, sistem yönetimi ve yazılım geliştirme hizmetlerini sunar. |
||||
|
||||
Asterisk, Caddy, CentOS, Ceph, Debian, Drupal, Endian Firewall, FreePBX, FreeSWITCH, FreeNAS, GNU/Linux, Graylog, KVM, LXD, MariaDB, MySQL, Nginx, Openfire, pfSense, PHP, PostgreSQL, Prestashop, Proxmox, Redmine, Ubuntu, WordPress, XMPP, Zabbix, Zentyal, ZFS, Zimbra, Z-Push |
||||
@ -1,30 +0,0 @@ |
||||
--- |
||||
key: neo_soft_groupe |
||||
title: NEO-SOFT Groupe |
||||
category: sponsors |
||||
order: 12 |
||||
logo: /images/partners/logo-neo_soft_groupe.png |
||||
website: 'https://www.neo-soft.fr/' |
||||
lang: tr |
||||
socials: |
||||
- icon: facebook |
||||
link: 'https://facebook.com/neo.soft.groupe' |
||||
name: Néo-Soft Groupe |
||||
- icon: twitter |
||||
link: 'https://twitter.com/neosoft_' |
||||
name: NeoSoft |
||||
- icon: linkedin |
||||
link: 'http://www.linkedin.com/company/neo-soft-services' |
||||
name: Néo-Soft Groupe |
||||
--- |
||||
Créé en 2005 à Rennes par son PDG actuel Soïg, le Groupe Néo-Soft est aujourd’hui reconnu pour l’expertise de ses 1 300 consultants et ses 16 implantations. |
||||
Néo-Soft est une société de Conseil en Informatique et Technologies spécialisée dans 5 domaines : |
||||
- Conseil & Gestion de projet |
||||
- Domaine applicatif |
||||
- Infrastructures & Réseaux |
||||
- Cybersécurité grâce notre filiale dédiée Cogital |
||||
- Data |
||||
Intégrer Néo-Soft c'est la possibilité de développer son expertise dans une entreprise innovante et responsable où la proximité est une réalité. |
||||
Nous recrutons sur toute la France et dans divers secteurs d'activités (Banques & Assurances, Aéronautique, Domotique, Télécoms & Médias etc.). |
||||
Client grands comptes, PME ou start-up innovantes, évoluez dans l'environnement de votre choix. |
||||
|
||||
@ -0,0 +1,45 @@ |
||||
--- |
||||
key: omega |
||||
title: Omega Hukuk |
||||
category: sponsors |
||||
order: 20 |
||||
logo: /images/partners/omega.png |
||||
website: 'https://omegahukuk.com/' |
||||
lang: tr |
||||
socials: |
||||
- icon: email |
||||
link: 'mailto:bilgi@omegahukuk.com' |
||||
name: bilgi@omegahukuk.com |
||||
--- |
||||
|
||||
Omega ismi Alman biliminsanı Georg Simon Ohm'un elektriksel direnç kavramına verdiği simgenin Yunanca sembolünden gelmektedir. Bugün genel bir hal olsa da Büromuzun çalıştığı temel alanların çoğunun bir direnç konusu olmasına bir göndermedir. |
||||
Üç nesilin birlikte çalıştığı, herkesin keyifle ilgilendiği alanlarda hukuki çalışmalarını sürdürüldüğü Büromuzda kapsayıcı olarak hukuki uygulamanın pek çok alanında faaliyet gösterilmektedir. |
||||
Yeni bir Dünya'nın eşiğinde tüm Avukatlarımız gerekli gördüğünüz özeni özverili olarak göstermek için çalışmaktadır. |
||||
Büromuzun belirgin ayrımlarından bir tanesi bize güvenilerek verilen bilgileri saklamak adına gösterdiğimiz çabadır. Bu bakımdan; |
||||
|
||||
- Büromuz dahilindeki tüm sistemler, imkan dahilinde özgür veya açık kaynak yazılımlarla ve en güncel güvenlik tedbirleri ile donatılmıştır. |
||||
- Büromuzda kayıtlı tutulan tüm sayısal veriler, güncel teknolojinin sunduğu en güvenlilir şifreleme imkanları ile saklanır. |
||||
- Kayıtlı elektronik veriler hiçbir şekilde bulut benzeri uzak sunucularda kaydedilmez. |
||||
- Taşınabilir tüm cihaz ve depolama araçları da Büro standartlarında şifreli olarak kullanılır. |
||||
- Büromuz Kolektif House Levent dahilinde 7/24 kamera ve özel güvenlik ile korunmaktadır. |
||||
- Büromuz ile iletişiminizin güvenliğini teminat altına almak için çağdaş teknolojilerin en güvenilir yöntemleri kullamınıza hazırdır. |
||||
- E-posta servisimiz, İsviçre'de bir nükleer sığınakta bulunan sunucuları ile tanınan, en güvenli e-posta hizmet sağlayıcısı Protonmail tarafından sağlanmaktadır. |
||||
- Gerekli görülmesi durumunda büromuza ait GPG anahtarı gönderilecek tüm e-posta ve dosya içeriklerini güvenle korumak üzere kullanıma hazırdır. |
||||
- Tüm Avukatlarımıza telefonlarından sesli veya yazılı ulaşmak için bugün anlık yazışmanın altın standardı olan Signal yazılımı kullanılabilir. |
||||
- OTR şifreleme ile XMPP üzerinden ofisimize anonim şekilde ulaşılabilir. |
||||
- Fiziki olarak Büromuzda bulunan Nextcloud sunucusu aracılığı ile e-posta ile gönderilemeyen büyük dosyalar tarafımıza doğrudan gönderilebilir. |
||||
|
||||
## Emine Susi Atmaca |
||||
|
||||
İstanbul Hukuk Fakültesinden mezun. 30 yıllık meslek hayatına 1991 yılından beri bağımsız avukatlık yaparak sürdürmekte. Mesleki çalışmalarını iş, ticaret, miras ve borçlar hukuk çerçevesinde sürdürdü. 2011 yılı itibari ile mal rejimlerinin tasviyesi konusunda bilirkişilik yapmakta ve adli yardımda bulunmakta. |
||||
|
||||
## Alper Atmaca |
||||
|
||||
İstanbul Bilgi Üniversitesi Hukuk Fakültesi mezunu. Meslek geçmişini ağırlıklı olarak ceza ve iş hukuku alanında sürdürdü. Çocukluktan teknoloji düşkünü ve konu üzerine yazmakta. Kişisel verilerin korunmasına ilişkin hem hukuki hem de sivil toplumda çalışmalarda bulunmakta. |
||||
|
||||
## Serkan Atak |
||||
|
||||
İstanbul Üniversitesi Hukuk Fakültesi mezun olmuştur. Uzun yıllardır İş |
||||
Hukuku ve Ceza Hukuku alanlarına dair çalışmaktadır. Çeşitli sitelerde |
||||
bilim-kurgu kitapları incelemeleri yapmakla birlikte, halen Sinema |
||||
Kolektifi sitesinin yayın yönetmenidir. |
||||
@ -1,22 +0,0 @@ |
||||
--- |
||||
key: smile |
||||
title: SMILE |
||||
category: sponsors |
||||
order: 13 |
||||
logo: /images/partners/logo-smile.png |
||||
website: 'https://www.smile.eu/' |
||||
lang: tr |
||||
|
||||
socials: |
||||
- icon: facebook |
||||
link: 'https://facebook.com/smileopensource' |
||||
name: Smile - Open Source Solutions |
||||
- icon: twitter |
||||
link: 'https://twitter.com/GroupeSmile' |
||||
name: GroupeSmile |
||||
--- |
||||
Avec de l’audace et des beaux projets, ajoutez une pincée de culture visionnaire, une bonne dose d’innovation, saupoudrez le tout d’une expertise technique pluridisciplinaire et vous obtenez Smile, le leader européen de l’intégration et de l’infogérance de solutions open source. |
||||
|
||||
Agiles, open et engagés, chez Smile, nous adorons avoir un coup d’avance pour garder notre place sur le podium des acteurs majeurs du digital. Pour cela, nous avons développé 4 offres pour vous accompagner dans votre transformation numérique : Digital, Business App, Embedded & IoT et Infra. |
||||
|
||||
Pour finir cette première présentation, une question primordiale… « Que serions-nous sans les femmes et les hommes qui font tourner la jolie machinerie Smile ? ». Au quotidien, ce sont 1700 smiliens présents dans 7 pays qui s’agitent et cogitent pour mener à bien les projets stratégiques de nombreux grands comptes français et européens. |
||||
@ -0,0 +1,17 @@ |
||||
--- |
||||
key: stickker |
||||
title: Stickker |
||||
category: sponsors |
||||
order: 20 |
||||
logo: /images/partners/stickker.png |
||||
website: 'https://stickker.net/' |
||||
lang: tr |
||||
socials: |
||||
- icon: twitter |
||||
link: 'https://twitter.com/stickkernet' |
||||
name: stickkernet |
||||
|
||||
--- |
||||
Stickker.net is the first e-commerce sticker shop located in Turkey. In stickker, you can find various stickers about including but not limited to programming, software and design. |
||||
|
||||
Stickker.net 2016 Ocak ayında kurulmuş Türkiye’nin ilk stickker e-ticaret sistemidir. Stickker'da genellikle yazılım ve tasarım üzerine olmakla birlikte pek çok farklı sticker'ı bulabilirsiniz. |
||||
@ -0,0 +1,26 @@ |
||||
--- |
||||
key: tutanota |
||||
title: Tutanota |
||||
category: sponsors |
||||
order: 20 |
||||
logo: /images/partners/tutanota.svg |
||||
website: 'https://tutanota.com/' |
||||
lang: tr |
||||
socials: |
||||
- icon: twitter |
||||
link: 'https://twitter.com/TutanotaTeam' |
||||
name: TutanotaTeam |
||||
--- |
||||
Tutanota is the world's most secure email service, easy to use and private by design. Sign up for free to take control of your mailbox. |
||||
|
||||
### Safe from Attackers |
||||
|
||||
With end-to-end encryption and 2FA, your emails have never been more secure. The built-in encryption guarantees that your mailbox belongs to you: Nobody can decrypt or read your data. |
||||
|
||||
### We Love Free Software |
||||
|
||||
Tutanota is free software so security experts can verify the code that protects your emails. Our Android app is Google-free making Tutanota the best libre email service. |
||||
|
||||
### On Your Favorite Device |
||||
|
||||
With apps for iOS and Android, your secure emails are available anytime. Our fast web client & fully-featured apps make sure encrypted emails are a pleasant experience. |
||||
@ -1,21 +0,0 @@ |
||||
--- |
||||
key: 10_est_une_puissance_de_2 |
||||
title: 10 est une puissance de 2 |
||||
id: jABRUDzqext8Rx8CmA4j |
||||
language: Français approximatif |
||||
format: quickie |
||||
tags: |
||||
- _wtf |
||||
level: beginner |
||||
speakers: |
||||
- gilles_debunne |
||||
videoId: 3XIAC098fAI |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Le code barre est une invention qui a radicalement modifié nos sociétés. Sans elle, pas d'inventaire efficace, de supermarchés ou de vente en ligne. |
||||
|
||||
Mais comment coder les chiffres de façon fiable avec des petites barres noires et blanches ? Quand les contraintes matérielles empêchent d'utiliser le binaire, l'ingéniosité et un peu de chance ont permis de créer ce produit, maintenant présent partout. |
||||
|
||||
|
||||
Nous découvrirons les détails de ce codage, et comment il pourrait même contenir davantage d'informations. |
||||
@ -1,19 +0,0 @@ |
||||
--- |
||||
key: 3_techniques_faciles_de_manipulation |
||||
title: 3 techniques faciles de manipulation |
||||
id: zVUXQkHQtSiGJeIwVd05 |
||||
format: quickie |
||||
tags: |
||||
- _wtf |
||||
level: beginner |
||||
speakers: |
||||
- marie_viley |
||||
videoId: OgOAMs6b5R0 |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Qui ne s’est jamais fait manipuler ? Évidemment, on est tous allé à une soirée alors qu’on en avait pas envie, on a tous acheté un truc sans en avoir besoin et on a tous été influencé par nos proches. |
||||
|
||||
L’idée de cette présentation est de vous ouvrir les yeux sur les relations et les influences entre les gens. Je vous exposerai les mécanismes de prise de décision au travers de 3 techniques simples de manipulation. |
||||
|
||||
A la sortie de ce talk, vous devriez être moins influençable et maître de vos décisions (voire même manipuler les autres). |
||||
@ -1,26 +0,0 @@ |
||||
--- |
||||
key: _47_ans___ils_nont_toujours_pas_remarque__ |
||||
title: '« 47 ans : ils n’ont toujours pas remarqué … »' |
||||
id: pY6MCQBMfIYlIKfHdhL4 |
||||
language: French |
||||
format: quickie |
||||
tags: |
||||
- _wtf |
||||
level: beginner |
||||
speakers: |
||||
- qj7nbl6wiyug1rhqtxf818a46po1 |
||||
videoId: JADZMaRL4cE |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
L’âgisme dans les fonctions IT, et en particulier dans le Développement Soft, est incontournable. |
||||
|
||||
Les « vieux » n’ont décidément pas la cote, le marché de l'emploi des softeux cinquantenaires en est la preuve ! |
||||
Pourtant, codage et sénioritude semblent loin d'être incompatibles. |
||||
|
||||
- Alors quels préjugés peuvent en être la cause ? |
||||
- L’avance rapide de la technologie numérique est-elle incompatible avec le ralentissement biologique ? |
||||
- Les cheveux gris sont-ils un Handicap pour la Sécurité de l’Info ? |
||||
- Le Cloud doit-il être « Arthrose-free » ? |
||||
|
||||
Et surtout, comment se fait-il qu’à 47 ans je vienne d’intégrer l’équipe Devops & Tools de Continental Digital Services et que personne ne m’ait encore rien dit ? |
||||
@ -1,10 +0,0 @@ |
||||
--- |
||||
key: __lunch |
||||
title: Déjeuner |
||||
format: lunch |
||||
tags: |
||||
- lunch |
||||
speakers: [] |
||||
draft: false |
||||
--- |
||||
Bon appétit |
||||
@ -1,10 +0,0 @@ |
||||
--- |
||||
key: __open |
||||
title: 'Accueil, Thé, Café et Chocolatines' |
||||
format: open |
||||
tags: |
||||
- open |
||||
speakers: [] |
||||
draft: false |
||||
--- |
||||
Accueil, Thé, Café et Chocolatines |
||||
@ -1,10 +0,0 @@ |
||||
--- |
||||
key: __party |
||||
title: Party time... |
||||
format: party |
||||
tags: |
||||
- party |
||||
speakers: [] |
||||
draft: false |
||||
--- |
||||
🎉 Party time |
||||
@ -1,10 +0,0 @@ |
||||
--- |
||||
key: __pause |
||||
title: Pause |
||||
format: pause |
||||
tags: |
||||
- pause |
||||
speakers: [] |
||||
draft: false |
||||
--- |
||||
Pause |
||||
@ -0,0 +1,13 @@ |
||||
--- |
||||
key: food-vs-hardware |
||||
title: Healthy Food vs Healthy Software & Hardware |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- freedom |
||||
speakers: |
||||
- bager |
||||
draft: false |
||||
--- |
||||
Personal, family and government nutrition strategies has developed amazingly in the last decades. These strategies are related to allergies, intolerance, diet or just being healthy. We need to understand how they have developed and look for similarities we can create for current software and hardware ecosystems. |
||||
@ -1,28 +0,0 @@ |
||||
--- |
||||
key: >- |
||||
_numerique_et_environnement__ou__on_aurait_pu_sauver_les_abeilles__on_a_prefere_sortir_un_nouvel_iphone_ |
||||
title: >- |
||||
"Numérique et environnement" ou "On aurait pu sauver les abeilles, on a |
||||
préféré sortir un nouvel iPhone" |
||||
id: zDbtrtvdLPG1okj07wyI |
||||
format: conference |
||||
tags: |
||||
- _wtf |
||||
level: beginner |
||||
speakers: |
||||
- sebastien_brault |
||||
videoId: jA8aHSMZ_DI |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Le numérique fait-il partie du problème ou de la solution quand on parle de réchauffement climatique ? |
||||
|
||||
5 milliards de smartphones en circulation en 2020, ça représente quoi en consommation énergétique, en gaz à effet de serre, en pollution chimique ? |
||||
|
||||
Le streaming illimité à 10 euros par mois c'est le pied mais aujourd'hui Netflix a à peu près l'empreinte carbone du plus gros cimentier mondial, qui va payer la facture environnementale ? |
||||
|
||||
Tous les mails de votre vie (que vous ne lirez plus jamais) disponibles sur Gmail, très utile, mais après 2020 on ne saura peut-être plus produire industriellement les équipements nécessaires à leur stockage. |
||||
|
||||
On arrive dans "l'âge des limites", pour le numérique comme pour le reste. Quels sont les leviers pour basculer vers un numérique durable ? |
||||
|
||||
Et si malgré tout on décidait de s'en foutre ? 2 degrés en plus, c'est juste un pull en moins non ? Non. Par contre c'est 30% en moins sur les rendements agricoles pour ... 30 % de population en plus en 2050. En 1970, Dennis Meadows modélisait sur les ordinateurs du MIT un crash du système planétaire pour les décennies 2020-2030. Pour l'instant, c'est cette trajectoire que notre monde suit. |
||||
@ -1,14 +0,0 @@ |
||||
--- |
||||
key: a_kotlin_multiplatform_evolution |
||||
title: A Kotlin multiplatform evolution |
||||
language: English |
||||
format: conference |
||||
tags: |
||||
- _languages |
||||
level: advanced |
||||
speakers: |
||||
- liliia_abdulina |
||||
draft: false |
||||
--- |
||||
Have you heard of the code-sharing feature in Kotlin, accompanied with "Write once, run everywhere" slogan? Among its users not only libraries and frameworks authors; there are some projects which have already adopted multiplatform for production. Their applications, written in Kotlin for *both* iOS and Android, are published in stores. |
||||
With this talk, you'll get a brief overview of the evolution of multiplatform technology in Kotlin, concerning the tasks it's evolved to solve. How it was and how it is expected to be; what has changed and which tasks can be already solved with it. What are the facilities right now and which real projects already use multiplatform? |
||||
@ -1,21 +0,0 @@ |
||||
--- |
||||
key: a_la_decouverte_de_la_realite_augmentee_avec_arcore |
||||
title: A la découverte de la réalité augmentée avec ARCore |
||||
id: qXAvodXoMK3db8ZLcVwb |
||||
language: France |
||||
format: conference |
||||
tags: |
||||
- _native_mobile_apps |
||||
level: beginner |
||||
speakers: |
||||
- christophe_jollivet |
||||
- jeremy_voisin |
||||
videoId: MPnesJY8f0s |
||||
presentation: https://github.com/JeremyVoisin/discovering-arcore |
||||
draft: false |
||||
--- |
||||
Avec les annonces de l'arrivée de la réalité augmentée (ou RA) dans Google Maps et Google Search sur Android lors de Google IO 2019, nous constatons que la RA va prendre une place de plus en plus importante dans notre quotidien. La sortie d'ARCore en mars 2018 sur Android a simplifié le développement d’application en RA sur Android. |
||||
|
||||
Au cours de cette session, nous vous proposons de découvrir ARCore, via l’utilisation dans un navigateur, des applications natives ou des moteurs 3D comme Unity ainsi que les CloudAnchors qui permettent la persistance et le partage de positions d’objets dans les scènes de réalité augmentée, y compris avec des utilisateurs d’iOS. |
||||
|
||||
Après une initiation aux concepts liés à la RA (meshes, 6 DoF,...), nous présenterons les différentes fonctionnalités d’ARCore. Nous discuterons aussi des différentes approches d’utilisation, de leurs limitations et avantages au travers d'une application de cartographie 3D en réalité augmentée. |
||||
@ -0,0 +1,13 @@ |
||||
--- |
||||
key: ai |
||||
title: AI for preserving privacy |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- privacy |
||||
speakers: |
||||
- pinar |
||||
draft: false |
||||
--- |
||||
Privacy is a major concern in collaborative Web systems, such as online social networks or Internet of Things applications. Contrary to traditional Web systems, collaborative systems allow their users to create and share content about themselves as well as about others. When multiple entities start distributing content without a control, information can reach unintended individuals. Further, many times, shared content contains information about multiple users, whose privacy constraints may be different from each other, resulting in conflicts. This talk will discuss how distributed, artificial intelligence-based approaches can help detect privacy violations, resolve disputes, and overall help manage users' privacy. |
||||
@ -1,19 +0,0 @@ |
||||
--- |
||||
key: allo_paris__ici_san_francisco__et_si_on_codait_ensemble_avec_vs_code_ |
||||
title: 'Allo Paris, ici San Francisco. Et si on codait ensemble avec VS Code?' |
||||
id: Cej88MtlRVZrJRK0FJ2p |
||||
format: conference |
||||
tags: |
||||
- _method___tools |
||||
level: beginner |
||||
speakers: |
||||
- olivier_leplus |
||||
- tiffany_souterre |
||||
videoId: 6KR0rNN4coU |
||||
presentation: https://slides.com/olivierleplus/vscode-collaboration#/3 |
||||
draft: false |
||||
--- |
||||
Vous aimez VS Code car il est simple, intuitif et qu'il fait ce que vous lui demandez. |
||||
Mais saviez-vous que vous pouviez coder à plusieurs dans VS Code? et même permettre à une personne tierce de jouer avec votre débugger depuis l'autre bout du monde? Saviez-vous que vous pouviez avoir un client slack dans VS Code, et même un chat audio? |
||||
Et avez-vous exploré toutes les possibilités que VS Code offre quand vous utilisez GitHub? |
||||
Nous verrons dans ce talk tout ce qui fait de VS Code l'éditeur de code parfait pour faire du code collaboratif. |
||||
@ -1,18 +0,0 @@ |
||||
--- |
||||
key: applications_de_brainfuck__langage_minimaliste_mais_turing_complet |
||||
title: 'Applications de Brainfuck, langage minimaliste mais Turing-complet' |
||||
id: oiZTE4THbAJeaNVlLc03 |
||||
language: Français |
||||
format: quickie |
||||
tags: |
||||
- _wtf |
||||
level: beginner |
||||
speakers: |
||||
- theophile_wallez |
||||
videoId: deswvXZ0Sjc |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Brainfuck est probablement le plus connu des langages de programmation ésotériques. Ses 8 instructions en font un langage Turing-complet avec lequel il est théoriquement possible d’écrire n’importe quel programme. |
||||
|
||||
Et en pratique ? Après une explication du langage (avec 8 instructions c’est rapide !) on verra comment j’ai utilisé Brainfuck pour les qualifications au concours d’informatique Prologin, sur un problème de parcours de graphes ! |
||||
@ -0,0 +1,13 @@ |
||||
--- |
||||
key: art-with-free-software |
||||
title: "At the crossroads of practice, education and advocacy: art with free software" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- freedom |
||||
speakers: |
||||
- eylul |
||||
draft: false |
||||
--- |
||||
Free software is more than just a product. It is the search of an alternative ecosystems around software and tool creation. However, what does this mean to the end user? What should it mean to the end user? What does it end up meaning if one is also in the business of creativity? Join Eylul Dogruel as she talks about her journey integrating free/libre software to her workflow that instead landed her in the intersection of art practice, art education and free software advocacy. |
||||
@ -1,18 +0,0 @@ |
||||
--- |
||||
key: authentication_authorization_starters_battle |
||||
title: Authentication/Authorization Starters Battle |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: français |
||||
format: conference |
||||
tags: |
||||
- _method___tools |
||||
level: beginner |
||||
speakers: |
||||
- valeriane_venance |
||||
videoId: yU_Uvm3m3VY |
||||
presentation: https://docs.google.com/presentation/d/1C2MGwFFdAUrry6EJl1Wdy_pKyjU0str9RB7US3Ta77Y/edit#slide=id.g5048a032ca_0_61 |
||||
draft: false |
||||
--- |
||||
When you start a brand new app or service, you need to think about how you will manage authentication and permissions. But if you are like everyone else, you genuinely do not want to actually think about this. If someone else could do that for you, life would be great. And this has actually happened, you have the choice between several boilerplate projects or authentication/authorization libraries. In fact, you have a lot of options. Which one to choose? Let's have a closer look to them! |
||||
|
||||
At the end of this talk, you will have a good overview of the common existing solutions and their benefits. |
||||
@ -0,0 +1,13 @@ |
||||
--- |
||||
key: closing |
||||
title: "Closing talk" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- closing |
||||
speakers: |
||||
- oyd |
||||
draft: false |
||||
--- |
||||
Closing talk |
||||
@ -1,26 +0,0 @@ |
||||
--- |
||||
key: >- |
||||
comprendre_le_role_du_noyau_d_un_systeme_d_exploitation_en_creant_un_from_scratch |
||||
title: >- |
||||
Comprendre le rôle du noyau d'un système d'exploitation en en créant un from |
||||
scratch |
||||
id: tOexEcqeKEztPbNmR4JT |
||||
format: conference |
||||
tags: |
||||
- _cloud___infra |
||||
level: beginner |
||||
speakers: |
||||
- alessio_coltellacci |
||||
videoId: y928d3uVEys |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Programmer le noyau d'un système d'exploitation est un très bon moyen pour en comprendre le fonctionnement et le scope de son travail (IO, gestion de la mémoire, etc). |
||||
Cette présentation a pour but de présenter et de développer les composants élémentaires d'un micro noyau UNIX. |
||||
|
||||
Dans ce talk je présenterai: |
||||
- L'émulateur QEMU |
||||
- La réalisation d'un secteur de boot avec une micro console |
||||
- Comment gérer les interruptions hardware (clavier) et software |
||||
- La gestion des appels systèmes |
||||
- Un système multi-process simple qui va permettre de découvrir le surcoût des changements de contexte liés à la programmation concurrentielle |
||||
@ -1,22 +0,0 @@ |
||||
--- |
||||
key: de_java_a_un_executable_natif___graalvm_et_quarkus_changent_la_donne |
||||
title: 'De Java à un exécutable natif : GraalVM et Quarkus changent la donne' |
||||
id: Qy836EfpA0wC4M6jYcTk |
||||
language: French |
||||
format: conference |
||||
tags: |
||||
- _method___tools |
||||
level: beginner |
||||
speakers: |
||||
- guillaume_smet |
||||
videoId: cLyw7vPr3mo |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Les microservices, la scalabilité instantanée et les plates-formes à haute densité comme Kubernetes nécessitent des applications à faible empreinte mémoire et démarrage rapide. Java n'était pas bien positionné car il favorise les temps de traitement aux dépens du CPU et de la RAM. |
||||
|
||||
Plus maintenant. |
||||
|
||||
Entre en scène Quarkus, une stack Java orientée microservices qui supporte vos composants favoris (Hibernate, Vert.x, Camel, RESTEasy ...) sur GraalVM et HotSpot avec une faible empreinte mémoire et un démarrage rapide. Tout ce qu'il faut pour tirer pleinement parti des containers. |
||||
|
||||
La gestion de la donnée est souvent l'aspect le plus complexe : découvrons comment Quarkus gère la persistance avec Hibernate ORM. Venez explorer le live reload, notre vision de la persistance avec Hibernate Panache, l'indexation full text avec Hibernate Search, l'environnement de test, la compilation native GraalVM et bien plus. Quarkus se vit plus qu'il ne se verbalise, attendez-vous à une démo détaillée. |
||||
@ -0,0 +1,21 @@ |
||||
--- |
||||
key: decentralized-web |
||||
title: "The Absolute State of Decentralized Web Compatibility in 2020: The Good, The Bad and The Ugly" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- decentralization |
||||
speakers: |
||||
- yutyo |
||||
- maciej |
||||
draft: false |
||||
--- |
||||
The Web was free and decentralized when it was invented by Tim Berners-Lee in March 12, 1989. But today, the Web that no one could own is under the feudal invasion of big IT companies that own many of the servers existing in the world. |
||||
|
||||
## What is that buzz about decentralization? |
||||
|
||||
The Web was free and decentralized when it was invented by Tim Berners-Lee in March 12, 1989. But today, the Web that no one could own is under the feudal invasion of big IT companies that own many of the servers existing in the world. |
||||
|
||||
## What can we do/ are we doing about it? |
||||
As a response to that problem that threatens the solidarity of the Web, there have been many projects going on. I am gonna talk about those projects, showing several examples of centralised, federative and decentralized ongoing/abandoned Web projects and making a conversation about what we can do more. |
||||
@ -1,18 +0,0 @@ |
||||
--- |
||||
key: developpeurs_en_reconversion__developpeurs_quand_meme__ |
||||
title: 'Développeurs en reconversion, développeurs quand même !' |
||||
id: adcMAUSbsAK27dQJA4Iw |
||||
language: Français |
||||
format: quickie |
||||
tags: |
||||
- _wtf |
||||
level: beginner |
||||
speakers: |
||||
- juliane_blier |
||||
videoId: jyTISfF8MTo |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Ces dernières années, les "fabriques de dev" et autres formations courtes explosent. C'est un fait, tout dev a été ou sera amené à travailler avec l'un de ces jeunes développeurs.euses. Mais qui sont-ils ? Pourquoi une reconversion dans ce genre d'organisation ? Qu'ont-ils appris lors de leur formation express ? C'est fiable ce genre de dev ? Comment puis-je les intégrer au mieux dans ma structure ? |
||||
|
||||
Autant de questions que vous vous êtes sans doute déjà posées. Pendant ces 15 minutes, je vous présenterai mon retour d'expérience en tant que développeuse provenant de l'une de ces écoles de dev et maintenant développeuse Javascript depuis 2 ans au sein d'une startup Toulousaine. |
||||
@ -1,17 +0,0 @@ |
||||
--- |
||||
key: devops_at_scale |
||||
title: DevOps at scale |
||||
id: aOHds477R7FiM3cnWAXp |
||||
format: conference |
||||
tags: |
||||
- _method___tools |
||||
level: beginner |
||||
speakers: |
||||
- adrien_anceau |
||||
videoId: ww-Kg0bH6E4 |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
DevOps is everywhere, and every new or existing project is at least considering to follow its principles. While implementing DevOps for single projects become more and more straightforward, it's still a challenge to have a coherent DevOps approach at Enterprise level. |
||||
|
||||
Let's dig in what it takes to achieve DevOps in large companies, with Airbus as an example. |
||||
@ -0,0 +1,12 @@ |
||||
--- |
||||
key: dijital-esitsizlikler |
||||
title: "Dijital eşitsizlikler" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: Turkish |
||||
format: keynote |
||||
tags: |
||||
- social-inequalities |
||||
speakers: |
||||
- bilgenarin |
||||
draft: false |
||||
--- |
||||
@ -0,0 +1,21 @@ |
||||
--- |
||||
key: event-sourcing |
||||
title: Path to Event Sourcing with OpenSource Framework |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: Turkish |
||||
format: keynote |
||||
tags: |
||||
- freedom |
||||
speakers: |
||||
- derya |
||||
draft: false |
||||
--- |
||||
Açık kaynak kodlu bir kütüphane olan EventApis Türkiye'de geliştirilmiş ve canli ortamda kullanılmaktadır. Bu konuşmada Event Sourcing in ne olduğu ve kütüphanenin desteklemesi gereken fonksiyonlardan bahsedeceğim. |
||||
|
||||
Katılımcılarin event bazlı yapılar hakkında temel bilgi sahibi olması beklenmektedir. |
||||
|
||||
CQRS/Event Sourcing kavramı özellikle ağır yük altında ayakta kalabilen uygulamalar geliştirmek için yeni nesil bir yaklaşımdır. Geliştirdiğimiz açık kaynak kodlu EventApis kütüphanesi ile bu dünyaya yazılımcıların daha kolay geçiş yapmasını hedefledik. |
||||
|
||||
Konuşmamda, CAP teorisi, CQRS ve Event Sourcing kavramlarına bolca değinerek, açık kaynak kodlu kütüphanenin getirdiği özelliklerden bahsedeceğim. |
||||
|
||||
Katılımcılardan temel Event bazlı sistemler hakkında bilgi sahibi olması beklenmektedir. CAP teorisi hakkında da on bilgi sahibi olunması sunumun efektif anlaşılması için önerilmektedir. |
||||
@ -1,19 +0,0 @@ |
||||
--- |
||||
key: four_diseases |
||||
title: Four Diseases |
||||
id: PmoMEVHO3imfUIMXsPai |
||||
language: English |
||||
format: conference |
||||
tags: |
||||
- _wtf |
||||
level: beginner |
||||
speakers: |
||||
- piotr_przybyl |
||||
videoId: E9EKWrRcyYk |
||||
presentation: http://przybyl.org/pres/2019/DevFestToulouse-4Diseases/#/title-slide |
||||
draft: false |
||||
--- |
||||
How a developer can tell if the system is sick just by taking a look at the input and the output? If you'd like to know that (plus you like standup comedy), come an see! The treatment is safe ;-) |
||||
|
||||
One approach to get familiar with a system is a long and intense reading the manual (and to run an eye over the source code sometimes). Another approach is to take a deep dive into the data model (often in the DB) and to surf the user interface. Both are natural ends of the system, the legendary Input and Output. By examining these ends one can check if there's good digestion or if guts are rotten. Careful examination can confirm "common DDDosis", "malignant stringosis", "regex diarrhoea" or "not-made-here syndrome". |
||||
Unfortunately, sometimes developers get infected in their prenatal life (meaning: at their university). Let me invite you to treatment. A laxative one. (That is: a sequel of "Passwords. Do you keep them safe?") |
||||
@ -0,0 +1,15 @@ |
||||
--- |
||||
key: how-wikipedia-covid19 |
||||
title: How is the Wikipedia responding to COVID-19 crisis? |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- free-knowledge |
||||
speakers: |
||||
- netha |
||||
draft: false |
||||
--- |
||||
Wikipedia is a good example for how people come together at times of crises to build up well-curated, frequently updated and fairly reliable content about various aspects of the crisis. During the 2019-20 coronavirus pandemic, several Wikimedians, including experts, came together to create articles, media and structured data about pandemic. I will provide an overview of the how Wikimedians work to create and update information on Wikipedia and its sister projects. |
||||
|
||||
Wikipedia and its sister projects responded to the COVID-19 pandemic by making well-curated information about COVID-19 available freely online. Wikipedia is now a major landing point for people searching for latest information related to COVID-19 on the internet. The information on Wikipedia is updated frequently, thanks to the efforts of thousands of volunteers, including experts, from around the world. Volunteers also work on Wikidata, a sister project of Wikipedia, where structured data related to the pandemic is available. In this session, I will give a brief overview of the projects and initiatives happening on Wikipedia related to COVID-19. |
||||
@ -1,25 +0,0 @@ |
||||
--- |
||||
key: introduction_a_la_programmation_par_contraintes |
||||
title: Introduction à la programmation par contraintes |
||||
id: iU4EzEThVDvpaHDsGjOO |
||||
language: Français |
||||
format: conference |
||||
tags: |
||||
- _big_data___ml___ai |
||||
level: beginner |
||||
speakers: |
||||
- cyril_delmas |
||||
videoId: l44o4gt62GM |
||||
presentation: https://cyrildelmas-drive.mycozy.cloud/public?sharecode=SbIDrGv5mU9h |
||||
draft: false |
||||
--- |
||||
Quel est le point commun entre un jeu de sudoku, la planification d'une conférence et les déplacements d'un commercial ? |
||||
|
||||
Quand on souhaite les traiter automatiquement, tous ces problèmes peuvent être résolus par un solveur de contraintes. Dans ce talk, je vais essayer de vous faire une introduction pratique à la programmation par contraintes, en présentant les concepts de base, puis en les mettant en application avec plusieurs exemples de problèmes connus de tout le monde (ou presque), pour finir par un cas plus complexe sur lequel je travaille actuellement. |
||||
|
||||
--- |
||||
|
||||
<blockquote class="twitter-tweet"> |
||||
<p lang="fr" dir="ltr">Les slides de ma présentation au <a href="https://twitter.com/hashtag/DevFestToulouse?src=hash&ref_src=twsrc%5Etfw">#DevFestToulouse</a> sur la programmation par contraintes sont ici : <a href="https://t.co/2lk9XoGnzN">https://t.co/2lk9XoGnzN</a><br>Pour le code, ça se passe sur github : <a href="https://t.co/f6Ndt8zdB4">https://t.co/f6Ndt8zdB4</a></p>— Cyril Delmas 🐧🍺 (@cyril_delmas) <a href="https://twitter.com/cyril_delmas/status/1180104468295278593?ref_src=twsrc%5Etfw">October 4, 2019</a> |
||||
</blockquote> |
||||
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
||||
@ -0,0 +1,14 @@ |
||||
--- |
||||
key: kadin-yazilimci |
||||
title: But is not it sexist to say “women” developer? |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- feminism |
||||
speakers: |
||||
- ayse |
||||
- gulcin |
||||
draft: false |
||||
--- |
||||
In this session, Ayse Bilge and Gulcin will talk about "Kadin Yazilimci" (Women in Tech organization from Turkey) and how they both involved in it, what they have been doing for the organization, what they have learned from their experience doing community work. After a quick introduction, they will get questions from the audience. |
||||
@ -1,16 +0,0 @@ |
||||
--- |
||||
key: keynote_close |
||||
title: Une analyse critique des "Tech Trends" |
||||
format: keynote |
||||
tags: |
||||
- keynote |
||||
speakers: |
||||
- christian_faure |
||||
draft: false |
||||
videoId: aYA_a0-bplY |
||||
--- |
||||
Notre secteur d'activité est régulièrement abreuvé de prévisions et de tendances : quel sera le prochain langage, le prochain framework, la nouvelle architecture, les nouveaux "use cases", les prochaines technologies disruptives ? Etc. |
||||
|
||||
De nombreuses sociétés publient des "tech trends" et certaines ont même fait de cette publication un coeur de métier (notamment les grands cabinets d'analystes). En marge du discours très "marketing oriented" des entreprises, il y a également l'omni-présence de nombreux gourous, futurologues ou prospectivistes qui jouent aux oracles. Mais il y a aussi de nombreuses personnalités indépendantes qui ont un discours sur l'innovation technologique plus libre, comme par exemple Kevin Kelly ou Simon Wardley. |
||||
|
||||
Je vous propose non pas une vision du futur de plus, mais de vous faire part des résultats d'une étude, que j'ai mené avec d'autres, qui analyse et compare les différentes méthodes et approches utilisées pour prédire l'avenir des technologies informatiques. |
||||
@ -1,10 +0,0 @@ |
||||
--- |
||||
key: keynote_close_overflow |
||||
title: Keynote de fermeture (overflow) |
||||
format: keynote |
||||
tags: |
||||
- keynote |
||||
speakers: [] |
||||
draft: false |
||||
--- |
||||
[Keynote de fermeture](../keynote_close) |
||||
@ -1,21 +1,29 @@ |
||||
--- |
||||
key: keynote_open |
||||
title: 'Une histoire de l''informatique, du métier à tisser à la machine de Babbage...' |
||||
title: 'Freedom in a time of pandemics' |
||||
format: keynote |
||||
language: English |
||||
tags: |
||||
- freedom |
||||
- keynote |
||||
speakers: |
||||
- fabien_tregan |
||||
- aral |
||||
draft: false |
||||
videoId: LHzVkjHjSso |
||||
--- |
||||
...où l'on parle aussi de la Pascaline, de table de logarithmes et d'éviter les erreurs. Et d'en faire. |
||||
Covid-19 isn’t the only pandemic facing humankind in 2020. Others include fascism, capitalism, environmental destruction, and mass surveillance by corporations and governments. As we find ourselves two decades into the century that will define the character of our societies in a digital and networked world, how we respond to these crises will define what it means to be human in an age when our humanity is no longer defined by the boundaries of our physical bodies. |
||||
|
||||
--- |
||||
While technology alone will not solve any of the challenges facing us, its central role in shaping the boundaries of our freedoms cannot be emphasised enough. |
||||
|
||||
Technology is a multiplier. How we fund it, design it, and the success criteria we set for it are defined by ideologies and interests. The technology that is built, in turn, amplifies the ideologies and interests of its creators. |
||||
|
||||
Big Tech amplifies Big Business and Big Brother. Big Tech – funded by venture capital and sharing the same success criteria as cancer (exponential growth in a finite context) – exacerbates inequality and centralises power. Big Tech amplifies the interests of a handful of billionaires in a world in which millions die every year of malnutrition and preventable disease. A world in which, according to Oxfam, “2,153 billionaires have more wealth than the 4.6 billion people who make up 60 percent of the planet’s population.” |
||||
|
||||
The problem isn’t just technology. The problem is fascism, capitalism, and neoliberalism. But if we want a progressive alternative, we cannot expect to construct it by using their tools. To paraphrase Audre Lorde, neoliberalism’s tools will never dismantle neoliberalism’s house. |
||||
|
||||
So what is the alternative to Big Tech? |
||||
|
||||
In this talk, I will argue that it is Small Tech. |
||||
|
||||
[Histoires de Mathématiques](https://hist-math.fr/) |
||||
[Small Technology](https://small-tech.org/about/small-technology) is technology funded from the commons and owned and controlled by individuals. It works to amplify the interests of individuals, not corporations or governments. |
||||
|
||||
<blockquote class="twitter-tweet"> |
||||
<p lang="fr" dir="ltr">Petit thread complément indispensable à mon talk d'hier au <a href="https://twitter.com/DevFestToulouse?ref_src=twsrc%5Etfw">@DevFestToulouse</a> , deux choses que je n'ai pas réussi à dire dans le temps : D'abord si je vous ai donné un tout petit peu envie d'en savoir plus sur l'histoire des maths et de l'informatique, le site de Bernard Ycart <a href="https://t.co/ejtAam5Kjy">pic.twitter.com/ejtAam5Kjy</a></p>— Fabien Trégan (@FTregan) <a href="https://twitter.com/FTregan/status/1180059776371306496?ref_src=twsrc%5Etfw">October 4, 2019</a> |
||||
</blockquote> |
||||
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
||||
In the digital network age, the difference between Big Tech and Small Tech is the difference between tyranny and freedom. |
||||
|
||||
@ -1,10 +0,0 @@ |
||||
--- |
||||
key: keynote_open_overflow |
||||
title: Keynote d'ouverture (overflow) |
||||
format: keynote |
||||
tags: |
||||
- keynote |
||||
speakers: [] |
||||
draft: false |
||||
--- |
||||
[Keynote d'ouverture](../keynote_open) |
||||
@ -0,0 +1,26 @@ |
||||
--- |
||||
key: kimin-ozgurlugu |
||||
title: "COVID-19, Free Software but who's freedom?" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: Turkish |
||||
format: keynote |
||||
tags: |
||||
- freedom |
||||
speakers: |
||||
- chris |
||||
draft: false |
||||
--- |
||||
COVID-19, Free Software but who's freedom? |
||||
Free Software idea is almost 40 year old now. It succeeded, conquered the Earth. Does it solved the problems it aimed? Covid19 caused an environment made us question everything. In this situation how programmers can defend freedom? |
||||
|
||||
Free software successes and benefits. A short story. |
||||
|
||||
Where did success came from? How success turned into failure? |
||||
|
||||
The problems that free software movement does/can not see. Gender, color, poverty, language, culture. Priorities forced by market. |
||||
|
||||
How these problems are dealt in the future? A view from Free Software base. |
||||
|
||||
In the days of Covid, new threats and opportunities. New solutions to new problems. Possibilities and impossibilities. Technology and humankind. Is technology became an enemy of humankind? |
||||
|
||||
What to do? |
||||
@ -1,39 +0,0 @@ |
||||
--- |
||||
key: l_histoire_de_la_decouverte_d_une_backdoor_signe_oneplus |
||||
title: L'histoire de la découverte d'une backdoor signée OnePlus |
||||
id: Kwery1cbJrx3ZFj6x1JU |
||||
format: conference |
||||
tags: |
||||
- _native_mobile_apps |
||||
level: intermediate |
||||
speakers: |
||||
- fs0c131y |
||||
videoId: XyczLWRnD8M |
||||
presentation: https://github.com/fs0c131y/ConPresentations/blob/master/DevfestToulouse2019.BackdoorOnePlus.pdf |
||||
draft: false |
||||
--- |
||||
## Résumé |
||||
En Novembre 2017, j'ai découvert "une backdoor" dans tous les téléphones de la marque OnePlus. À l'aide d'une simple ligne de commande, un attaquant ayant un accès physique au téléphone, pouvait devenir root et ainsi obtenir un contrôle total du téléphone de la victime. |
||||
|
||||
## Détails |
||||
Dans ce talk, j'expliquerai le processus qui m'a permis de faire cette découverte : |
||||
1. Extraction du build |
||||
2. Récupération des applications dites "système" |
||||
3. Détection de la vulnérabilité dans l'application Android "EngineeringMode" |
||||
4. Exploitation de la vulnérabilité |
||||
|
||||
## Sujet abordés |
||||
Lors de la détection et l'analyse de cette faille, nous aborderons la philosophie du **hacking**, comment faire du **reverse engineering** sur des applications **Android** et une **librairie native**. Nous analyserons du **Java** ainsi que du **C**. |
||||
|
||||
## Categorie |
||||
Native mobile apps |
||||
|
||||
## Format |
||||
Une conférence de 40 min |
||||
|
||||
--- |
||||
|
||||
<blockquote class="twitter-tweet"> |
||||
<p lang="en" dir="ltr">It was a pleasure for me to speak at <a href="https://twitter.com/hashtag/DevFestToulouse?src=hash&ref_src=twsrc%5Etfw">#DevFestToulouse</a>! Thank you all for your very nice feedbacks 🥰<br><br>The video will be available soon and I will publish the slides tomorrow <a href="https://t.co/CCJXQL03Bp">pic.twitter.com/CCJXQL03Bp</a></p>— Elliot Alderson (@fs0c131y) <a href="https://twitter.com/fs0c131y/status/1179807694041108480?ref_src=twsrc%5Etfw">October 3, 2019</a> |
||||
</blockquote> |
||||
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
||||
@ -1,29 +0,0 @@ |
||||
--- |
||||
key: le_burn_out_agile |
||||
title: Le burn-out agile |
||||
id: KAH9Lyx0b2TKNSQVZNw2 |
||||
language: Français |
||||
format: conference |
||||
tags: |
||||
- _method___tools |
||||
level: intermediate |
||||
speakers: |
||||
- cedric_moulard |
||||
videoId: ciAORrJYHc8 |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
En 2019, le monde de l’informatique n’a que l’agilité à la bouche. Ca groome à tous les coins de rue, ça s’excite en daily, ça colle des post-it et ça empile les serious game en rétro. Bien sûr, ça gère la transformation numérique (désolé, même au second degré, je ne peux pas employer “digitale”) et au final plus personne ne comprend rien. |
||||
|
||||
Des chefs de projet subitement propulsés ScrumMaster qui ne savent pas ce qu’ils doivent faire. Des PO qui découvrent la priorisation. Des développeurs qui doivent composer avec des specs floues et changeantes sans vision globale du projet. Pour compléter le tableau, la subite apparition de coachs agile à peine sortis de l’école qui n’ont jamais vu un projet de leur vie et qui viennent expliquer des concepts qu’ils ne maîtrisent qu’à moitié. |
||||
|
||||
En 2019 le monde de l’informatique rêve secrètement de cycles en V, de stabilité, de spécifications générales et de dossier d’architecture. |
||||
|
||||
En 2019 le monde de l’informatique est au bord du burn-out agile. |
||||
|
||||
## Plan du talk |
||||
|
||||
- Petit historique : l’évolution des pratiques sur les 20 dernières années |
||||
- Pourquoi ce bordel agile ? |
||||
- Finalement l’agilité c’est quoi ? |
||||
- Est-ce qu’il faut revenir au cycle en V ? |
||||
@ -1,24 +0,0 @@ |
||||
--- |
||||
key: le_design_de_l_erreur |
||||
title: Le design de l'erreur |
||||
id: pAMZmFT2wrfqPr9IdeXv |
||||
language: French |
||||
format: conference |
||||
tags: |
||||
- _method___tools |
||||
level: beginner |
||||
speakers: |
||||
- francois_teychene |
||||
videoId: 9P8FZIqUuTM |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Nos systèmes sont designés de manière optimiste, de la gestion technique des erreurs à la modélisation de nos interfaces. |
||||
Que ce soient les codes d'erreurs, les exceptions ou les modélisations plus avancées, elles servent pour arrêter un traitement et _potentiellement_ afficher un message d'information à un utilisateur. |
||||
|
||||
Mais avec les architectures microservices, la distribution des traitements ou une simple volonté de résilience, la gestion des erreurs est devenue un enjeu important de tous les systèmes afin qu’ils restent accessibles de tous, tout le temps tout en maintenant le système dans un état cohérent. |
||||
|
||||
Que fait-on lorsqu’une erreur intervient ? Peut-on compenser voire gérer l’erreur depuis le système pour l’utilisateur ? |
||||
|
||||
La réponse à ces questions se trouve autant dans la définition du produit que dans le choix technique. |
||||
Un outil bien conçu est un outil intelligent qui peut faire les bons choix au bon moment pour l'utilisateur. Et si on apprenait ensemble à concevoir nos erreurs ? |
||||
@ -1,24 +0,0 @@ |
||||
--- |
||||
key: le_jaillissement_de_l_esprit |
||||
title: Le jaillissement de l'esprit |
||||
format: conference |
||||
tags: |
||||
- _method___tools |
||||
level: beginner |
||||
speakers: |
||||
- lois_blanc |
||||
- saskia_blanc |
||||
- sebastien_blanc |
||||
draft: false |
||||
videoId: 3r12HslMosQ |
||||
--- |
||||
Les enfants sont eux-mêmes les bâtisseurs actifs de leurs propres structures intellectuelles et l'informatique y joue un rôle déterminant, disait Piaget, un célèbre biologiste, psychologue et logicien. Son collaborateur, Seymour Papert, inventera le langage Logo, langage qui fait qu'aujourd’hui je suis un développeur épanoui. |
||||
Qu'en est-il aujourd'hui ? Comment donner le goût du code à nos enfants et surtout pourquoi est-ce important ? |
||||
Avec Saskia, Loïs et leur père nous voyagerons à travers le temps, en partant de la tortue sur ce bon vieux M05 en passant par Scratch, le Logo hipster de nos jours, jusqu’à Groovy et Python. |
||||
|
||||
--- |
||||
|
||||
<blockquote class="twitter-tweet"> |
||||
<p lang="fr" dir="ltr">Pas mal de personnes m'ont demandé le lien vers les cartes d'activités <a href="https://twitter.com/scratch?ref_src=twsrc%5Etfw">@scratch</a> : <a href="https://t.co/QwgHepwZ7Z">https://t.co/QwgHepwZ7Z</a> et voici le lien vers les cartes d'activités <a href="https://twitter.com/makeymakey?ref_src=twsrc%5Etfw">@makeymakey</a> faites par <a href="https://twitter.com/Saskia_Blanc?ref_src=twsrc%5Etfw">@Saskia_Blanc</a> : <a href="https://t.co/MMFimwixbY">https://t.co/MMFimwixbY</a> <a href="https://twitter.com/hashtag/DevFestToulouse?src=hash&ref_src=twsrc%5Etfw">#DevFestToulouse</a></p>— Sébastien Blanc 🇪🇺 🥑 (@sebi2706) <a href="https://twitter.com/sebi2706/status/1180413658612092929?ref_src=twsrc%5Etfw">October 5, 2019</a> |
||||
</blockquote> |
||||
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
||||
@ -1,28 +0,0 @@ |
||||
--- |
||||
key: >- |
||||
le_troll_dans_ta_machine_____une_courte_introduction_a_la_pensee_de_jean_yves_girard |
||||
title: >- |
||||
Le troll dans ta machine --- Une courte introduction à la pensée de Jean-Yves |
||||
Girard |
||||
id: hoiS7Cs5sWwXb632pLh2 |
||||
format: quickie |
||||
tags: |
||||
- _wtf |
||||
level: intermediate |
||||
speakers: |
||||
- guillaume_andrieu |
||||
videoId: w_KFjqAxEu8 |
||||
presentation: https://t.co/76fMgZnksI?amp=1 |
||||
draft: false |
||||
--- |
||||
Jean-Yves Girard, le génial inventeur des indispensables [montres à moutarde](http://girard.perso.math.cnrs.fr/moutarde.pdf) (1990), est certes un joyeux trublion. |
||||
|
||||
Mais avant d'en arriver à ce sommet indépassable, il a tout de même publié deux-trois petites choses en chemin: |
||||
|
||||
- Rust, vous connaissez? L'idée première du système de typage de Rust est la logique dite "[linéaire](http://girard.perso.math.cnrs.fr/linear.pdf)", due à Jean-Yves Girard (1987). |
||||
- Haskell, ça vous dit quelque chose? Les systèmes de typage de Haskell mais aussi Scala (et d'une certaine manière Java) sont basés sur le "[système F](https://en.wikipedia.org/wiki/System_F)" (ou lambda-calcul de second ordre), dû à... Jean-Yves Girard (1972). |
||||
- Idris, vous avez entendu parler? Le système de typage d'Idris est basé sur la théorie des types de Per Martin-Löf, dont la première version a été prouvée incorrecte par... Jean-Yves Girard, qui depuis possède un [paradoxe](https://en.wikipedia.org/wiki/System_U#Girard's_paradox) à son nom. (Girard et Martin-Löf sont par ailleurs de très bons potes et ont ferraillé sec contre les logiciens classiques dans leur prime jeunesse.) |
||||
|
||||
Très méconnu mais probalement l'un des penseurs les plus influents pour l'informatique de ce début de XXIe siècle, Girard est tout aussi sérieux que fantasque. Son style toujours acéré et polémique s'appuie sur une vision très claire de ce que devrait être la logique: vivante, joyeuse, fertile. |
||||
|
||||
Dans cette courte présentation, on s'attachera à comprendre pourquoi Girard est aussi virulent dans son discours, quels sont les objectifs de sa pensée, et pourquoi elle a déjà porté tant de fruits dans le monde de l'informatique. |
||||
@ -0,0 +1,16 @@ |
||||
--- |
||||
key: let-there-be-copies-tr |
||||
title: "[TR] Let there be copies" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English Turkish |
||||
format: keynote |
||||
tags: |
||||
- free-knowledge |
||||
speakers: |
||||
- nevit |
||||
draft: false |
||||
--- |
||||
Let there be copies! |
||||
|
||||
There is no agreement on what exactly ought to be done, but it is certainly recognised that the current system is neither satisfactory nor sustainable. |
||||
We have more questions than answers. We have to speak about it. |
||||
@ -0,0 +1,16 @@ |
||||
--- |
||||
key: let-there-be-copies |
||||
title: "[ENG] Let there be copies" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English Turkish |
||||
format: keynote |
||||
tags: |
||||
- free-knowledge |
||||
speakers: |
||||
- nevit |
||||
draft: false |
||||
--- |
||||
Let there be copies! |
||||
|
||||
There is no agreement on what exactly ought to be done, but it is certainly recognised that the current system is neither satisfactory nor sustainable. |
||||
We have more questions than answers. We have to speak about it. |
||||
@ -1,31 +0,0 @@ |
||||
--- |
||||
key: >- |
||||
live_coding_musical___vous_savez_coder___devenez_compositeur_avec_webaudio_et_webmidi__ |
||||
title: >- |
||||
Live coding musical : vous savez coder ? Devenez compositeur avec WebAudio et |
||||
WebMIDI ! |
||||
id: WwHpapkCgEg5IMW5vTId |
||||
language: Français |
||||
format: conference |
||||
tags: |
||||
- _web |
||||
level: intermediate |
||||
speakers: |
||||
- sylvain_wallez |
||||
videoId: LShM4QzMOxY |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Sans nécessiter de formation musicale pointue, tout développeur peut créer des morceaux qui sonnent bien et faire du "live coding" pour improviser en direct. |
||||
|
||||
Après un rapide tour d'horizon des environnements de codage musical comme Sonic-Pi en Ruby ou FoxDot en Python, on codera/composera en live un morceau de musique électro avec comme seul outil un navigateur web, les API WebAudio et WebMIDI et la librairie Tone.js. |
||||
|
||||
Quelques samples bien choisis, une pincée de séquences harmonieuses, une bonne dose d'aléatoire encadré, et hop, tout le monde se mettra à danser ! Et puisque la musique c'est aussi des maths, on parlera de musique générative avec des chaînes de Markov et des L-Systems. |
||||
|
||||
David Guetta n'a qu'à bien se tenir ! |
||||
|
||||
--- |
||||
<blockquote class="twitter-tweet"> |
||||
<p lang="en" dir="ltr">The code for my music live coding talk at <a href="https://twitter.com/DevFestToulouse?ref_src=twsrc%5Etfw">@DevFestToulouse</a> and the code used on stage are available at <a href="https://t.co/DCT1k4UQss">https://t.co/DCT1k4UQss</a><br><br>And here's a quick recording of the "grand finale"<br>🎶 <a href="https://t.co/TXPrfnHRXG">https://t.co/TXPrfnHRXG</a></p>— Sylvain Wallez (@bluxte) <a href="https://twitter.com/bluxte/status/1180535831477530624?ref_src=twsrc%5Etfw">October 5, 2019</a> |
||||
</blockquote> |
||||
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
||||
@ -1,16 +0,0 @@ |
||||
--- |
||||
key: machine_learning_avec_des_allumettes_et_des_cotillons |
||||
title: Machine learning avec des allumettes et des cotillons |
||||
id: cnRUAtQNZybQsQa03lAx |
||||
language: Français |
||||
format: quickie |
||||
tags: |
||||
- _big_data___ml___ai |
||||
level: beginner |
||||
speakers: |
||||
- nicolas_decoster |
||||
videoId: KrKEAaNQVTQ |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Dans ce talk je vous montrerai comment expliquer simplement le fonctionnement de l'apprentissage par renforcement. Pour cela pas besoin d'ordinateur : quelques allumettes, des sacs de cotillons et un peu de pédagogie sont suffisants pour mettre en évidence les mécanismes intrinsèques de cette technique et pour aborder les enjeux et les limites des algorithmes d'"intelligence artificielle" basés sur l'apprentissage. |
||||
@ -0,0 +1,13 @@ |
||||
--- |
||||
key: meeting |
||||
title: "Meeting" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- meeting |
||||
speakers: |
||||
- oyd |
||||
draft: false |
||||
--- |
||||
Online meeting after event |
||||
@ -1,16 +0,0 @@ |
||||
--- |
||||
key: modern_forms_in_react |
||||
title: Modern Forms in React |
||||
id: McfMVcKDdZv68NSo2JIJ |
||||
language: English |
||||
format: conference |
||||
tags: |
||||
- _web |
||||
level: intermediate |
||||
speakers: |
||||
- erik_rasmussen |
||||
videoId: DDLqhCMaMLU |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
If the new React Context API and Suspense killed Redux (they didn't), surely Hooks kill the need for a form library, right? Well, not exactly. Managing form state is more than just holding your current values in state; it's about sync and async validition errors, and much more! But that doesn't mean that Hooks are irrelevant to the situation. Hooks make building forms in React easier than ever before. |
||||
@ -1,33 +0,0 @@ |
||||
--- |
||||
key: >- |
||||
mon_p____de_voyant_moteur_est_encore_allume___comment_debugger_mon_moteur___plongeon_dans_les_entrailles_des_calculateurs_moteur |
||||
title: >- |
||||
Mon p*** de voyant moteur est encore allumé ! Comment debugger mon moteur ? |
||||
Plongeon dans les entrailles des calculateurs moteur |
||||
id: fW4yvmVxjXb57vQJhIXu |
||||
format: conference |
||||
tags: |
||||
- _wtf |
||||
level: beginner |
||||
speakers: |
||||
- mathieu_passenaud |
||||
videoId: 1o5v8Ew9FjE |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Depuis les années 70 tous les constructeurs autos intégrent des calculateurs électroniques. |
||||
Les moteurs des voitures modernes sont des systèmes informatiques complexes qui s'appuient sur des dizaines de capteurs... et du code. |
||||
Comment ça fonctionne ? A quoi ressemble ce code et que fait-il ? |
||||
Qu'est-ce qu'il se passe lorsqu'on fait une "reprog" ? |
||||
Que signifie le voyant moteur allumé ? Comment débugger tout ça ? |
||||
Soulevons le capot (électronique), analysons le matériel mis en oeuvre mais surtout le logiciel grâce aux sources des calculateurs "Megasquirt" et allons explorer la face cachée numérique de nos voitures. |
||||
|
||||
--- |
||||
|
||||
Le code utilisé pendant ma conf pour les intéressés : <https://github.com/mathieupassenaud/devfesttoulouse-python-obd> |
||||
|
||||
|
||||
<blockquote class="twitter-tweet"> |
||||
<p lang="fr" dir="ltr">Cette année au <a href="https://twitter.com/DevFestToulouse?ref_src=twsrc%5Etfw">@DevFestToulouse</a> j'ai fait tourner un mock de moteur. Du coup, puisque vous me l'avez demandé voici comment j'ai pu en arriver là <a href="https://t.co/iq5juHH3MT">pic.twitter.com/iq5juHH3MT</a></p>— Mathieu Passenaud (@mathieupassenau) <a href="https://twitter.com/mathieupassenau/status/1180873060272021505?ref_src=twsrc%5Etfw">October 6, 2019</a> |
||||
</blockquote> |
||||
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
||||
@ -1,19 +0,0 @@ |
||||
--- |
||||
key: monitoring_ovh__300k_serveurs__27_dcs_une_plateforme_de_metriques |
||||
title: 'Monitoring OVH: 300k serveurs, 27 DCs une plateforme de métriques ' |
||||
id: xwAvvIJJfDdBD7N4oGa5 |
||||
format: conference |
||||
tags: |
||||
- _big_data___ml___ai |
||||
level: beginner |
||||
speakers: |
||||
- horacio_gonzalez__lostinbrittany_ |
||||
videoId: lnW1_X9WxkM |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
Comment faire quand on doit faire le suivi de toute l'infrastructure du plus grand fournisseur de cloud Européen ? Comment choisir un outil quand les plus populaires ne tient pas la marée à cette échelle ? Comment construire une plateforme Metrics pour unifier, concilier et remplacer des années de legacy fragmenté et des solutions partielles ? |
||||
|
||||
Dans ce talk nous racontons notre expérience sur la construction et la maintenance d'OVH Metrics, la plateforme utilisée pour monitorer toute l'infrastructure OVH. Nous avions besoin d'aller à des endroits où la plupart des solutions de monitoring ne sont jamais allées, opérer à l'échelle du plus grand fournisseur Européen de cloud et hosting : 27 data centers, plus de 300k serveurs (physiques !) et des centaines de produits pour accomplir notre mission avec nos 1,3 millions de clients. |
||||
|
||||
Venez pour entendre cette histoire de séries temporelles, de solutions open-sources poussées à l'extrême, de clusters HBase opérés en limite de capacité, et de comment une petite équipe s'est appuyée sur une poignée de solutions open-source et une bonne dose de code maison pour construire une des solutions de monitoring parmi les plus performantes au monde. |
||||
@ -1,17 +0,0 @@ |
||||
--- |
||||
key: office-hour-00 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- fabien_tregan |
||||
draft: false |
||||
officeHours: |
||||
- keynote_open |
||||
- keynote_open_overflow |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* [Une histoire de l'informatique, du métier à tisser à la machine de Babbage...](../keynote_open) |
||||
* [Keynote d'ouverture (overflow)](../keynote_open_overflow) |
||||
@ -1,26 +0,0 @@ |
||||
--- |
||||
key: office-hour-01 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- sebastien_brault |
||||
- liliia_abdulina |
||||
- christophe_jollivet |
||||
- jeremy_voisin |
||||
- loic_ortola |
||||
draft: false |
||||
officeHours: |
||||
- the_rise_of_the_web |
||||
- a_kotlin_multiplatform_evolution |
||||
- >- |
||||
_numerique_et_environnement__ou__on_aurait_pu_sauver_les_abeilles__on_a_prefere_sortir_un_nouvel_iphone_ |
||||
- a_la_decouverte_de_la_realite_augmentee_avec_arcore |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* ["Numérique et environnement" ou "On aurait pu sauver les abeilles, on a préféré sortir un nouvel iPhone"](../_numerique_et_environnement__ou__on_aurait_pu_sauver_les_abeilles__on_a_prefere_sortir_un_nouvel_iphone_) |
||||
* [A Kotlin multiplatform evolution](../a_kotlin_multiplatform_evolution) |
||||
* [A la découverte de la réalité augmentée avec ARCore](../a_la_decouverte_de_la_realite_augmentee_avec_arcore) |
||||
* [The rise of the web](../the_rise_of_the_web) |
||||
@ -1,25 +0,0 @@ |
||||
--- |
||||
key: office-hour-02 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- fs0c131y |
||||
- cedric_moulard |
||||
- vincent_ogloblinsky |
||||
- wassim_chegham |
||||
- aleksey_kladov |
||||
draft: false |
||||
officeHours: |
||||
- l_histoire_de_la_decouverte_d_une_backdoor_signe_oneplus |
||||
- le_burn_out_agile |
||||
- rust_as_a_high_level_langage |
||||
- rockin_in_the_angular_world |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* [L'histoire de la découverte d'une backdoor signée OnePlus](../l_histoire_de_la_decouverte_d_une_backdoor_signe_oneplus) |
||||
* [Le burn-out agile](../le_burn_out_agile) |
||||
* [Rockin’ in the Angular World](../rockin_in_the_angular_world) |
||||
* [Rust as a High-Level Langage](../rust_as_a_high_level_langage) |
||||
@ -1,26 +0,0 @@ |
||||
--- |
||||
key: office-hour-03 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- olivier_leplus |
||||
- tiffany_souterre |
||||
- gautier_mechling |
||||
- clement_duffau |
||||
- melanie_ducoffe |
||||
- corentin_wallez |
||||
draft: false |
||||
officeHours: |
||||
- webgpu__next_generation_3d_graphics_on_the_web |
||||
- quand_les_rates_des_ias_nous_renvoient_a_nos_propres_biais_societaux |
||||
- allo_paris__ici_san_francisco__et_si_on_codait_ensemble_avec_vs_code_ |
||||
- premiers_pas_avec_un_microcontroleur_et_google_cloud_iot_core |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* [Allo Paris, ici San Francisco. Et si on codait ensemble avec VS Code?](../allo_paris__ici_san_francisco__et_si_on_codait_ensemble_avec_vs_code_) |
||||
* [Premiers pas avec un microcontrôleur et Google Cloud IoT Core](../premiers_pas_avec_un_microcontroleur_et_google_cloud_iot_core) |
||||
* [Quand les ratés des IAs nous renvoient à nos propres biais sociétaux](../quand_les_rates_des_ias_nous_renvoient_a_nos_propres_biais_societaux) |
||||
* [WebGPU: Next-generation 3D Graphics on the Web](../webgpu__next_generation_3d_graphics_on_the_web) |
||||
@ -1,27 +0,0 @@ |
||||
--- |
||||
key: office-hour-04 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- guillaume_smet |
||||
- lois_blanc |
||||
- saskia_blanc |
||||
- sebastien_blanc |
||||
- sylvain_wallez |
||||
- steve_klabnik |
||||
draft: false |
||||
officeHours: |
||||
- rust__webassembly__and_the_future_of_serverless |
||||
- >- |
||||
live_coding_musical___vous_savez_coder___devenez_compositeur_avec_webaudio_et_webmidi__ |
||||
- le_jaillissement_de_l_esprit |
||||
- de_java_a_un_executable_natif___graalvm_et_quarkus_changent_la_donne |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* [De Java à un exécutable natif : GraalVM et Quarkus changent la donne](../de_java_a_un_executable_natif___graalvm_et_quarkus_changent_la_donne) |
||||
* [Le jaillissement de l'esprit](../le_jaillissement_de_l_esprit) |
||||
* [Live coding musical : vous savez coder ? Devenez compositeur avec WebAudio et WebMIDI !](../live_coding_musical___vous_savez_coder___devenez_compositeur_avec_webaudio_et_webmidi__) |
||||
* [Rust, WebAssembly, and the future of Serverless](../rust__webassembly__and_the_future_of_serverless) |
||||
@ -1,25 +0,0 @@ |
||||
--- |
||||
key: office-hour-05 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- noel_mace |
||||
- alessio_coltellacci |
||||
- francois_teychene |
||||
- andrew_radev |
||||
draft: false |
||||
officeHours: |
||||
- le_design_de_l_erreur |
||||
- the_freedom_of_static_typing |
||||
- >- |
||||
comprendre_le_role_du_noyau_d_un_systeme_d_exploitation_en_creant_un_from_scratch |
||||
- brace_yourself__vanilla_is_coming__back__ |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* [Brace yourself, 🍦Vanilla is coming … back 🕶!](../brace_yourself__vanilla_is_coming__back__) |
||||
* [Comprendre le rôle du noyau d'un système d'exploitation en en créant un from scratch](../comprendre_le_role_du_noyau_d_un_systeme_d_exploitation_en_creant_un_from_scratch) |
||||
* [Le design de l'erreur](../le_design_de_l_erreur) |
||||
* [The Freedom of Static Typing](../the_freedom_of_static_typing) |
||||
@ -1,24 +0,0 @@ |
||||
--- |
||||
key: office-hour-06 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- valeriane_venance |
||||
- adrien_anceau |
||||
- piotr_przybyl |
||||
- horacio_gonzalez__lostinbrittany_ |
||||
draft: false |
||||
officeHours: |
||||
- monitoring_ovh__300k_serveurs__27_dcs_une_plateforme_de_metriques |
||||
- authentication_authorization_starters_battle |
||||
- devops_at_scale |
||||
- four_diseases |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* [Authentication/Authorization Starters Battle](../authentication_authorization_starters_battle) |
||||
* [DevOps at scale](../devops_at_scale) |
||||
* [Four Diseases](../four_diseases) |
||||
* [Monitoring OVH: 300k serveurs, 27 DCs une plateforme de métriques ](../monitoring_ovh__300k_serveurs__27_dcs_une_plateforme_de_metriques) |
||||
@ -1,25 +0,0 @@ |
||||
--- |
||||
key: office-hour-11 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- marie_viley |
||||
- juliane_blier |
||||
- guillaume_andrieu |
||||
- nicolas_decoster |
||||
draft: false |
||||
officeHours: |
||||
- 3_techniques_faciles_de_manipulation |
||||
- machine_learning_avec_des_allumettes_et_des_cotillons |
||||
- >- |
||||
le_troll_dans_ta_machine_____une_courte_introduction_a_la_pensee_de_jean_yves_girard |
||||
- developpeurs_en_reconversion__developpeurs_quand_meme__ |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* [3 techniques faciles de manipulation](../3_techniques_faciles_de_manipulation) |
||||
* [Développeurs en reconversion, développeurs quand même !](../developpeurs_en_reconversion__developpeurs_quand_meme__) |
||||
* [Le troll dans ta machine --- Une courte introduction à la pensée de Jean-Yves Girard](../le_troll_dans_ta_machine_____une_courte_introduction_a_la_pensee_de_jean_yves_girard) |
||||
* [Machine learning avec des allumettes et des cotillons](../machine_learning_avec_des_allumettes_et_des_cotillons) |
||||
@ -1,24 +0,0 @@ |
||||
--- |
||||
key: office-hour-12 |
||||
title: Office Hours |
||||
format: office-hours |
||||
tags: |
||||
- office-hours |
||||
speakers: |
||||
- gilles_debunne |
||||
- qj7nbl6wiyug1rhqtxf818a46po1 |
||||
- theophile_wallez |
||||
- richard_fagot |
||||
draft: false |
||||
officeHours: |
||||
- _47_ans___ils_nont_toujours_pas_remarque__ |
||||
- applications_de_brainfuck__langage_minimaliste_mais_turing_complet |
||||
- un_distributeur_automatique_d_argent_de_poche_pour_les_enfants |
||||
- 10_est_une_puissance_de_2 |
||||
--- |
||||
Venez poser vos questions aux speakers de manière plus calme et détendue. |
||||
|
||||
* [10 est une puissance de 2](../10_est_une_puissance_de_2) |
||||
* [« 47 ans : ils n’ont toujours pas remarqué … »](../_47_ans___ils_nont_toujours_pas_remarque__) |
||||
* [Applications de Brainfuck, langage minimaliste mais Turing-complet](../applications_de_brainfuck__langage_minimaliste_mais_turing_complet) |
||||
* [Un distributeur automatique d'argent de poche pour les enfants](../un_distributeur_automatique_d_argent_de_poche_pour_les_enfants) |
||||
@ -0,0 +1,15 @@ |
||||
--- |
||||
key: open-data |
||||
title: Open/data in the time of COVID-19 |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- free-knowledge |
||||
speakers: |
||||
- pinar_dag |
||||
draft: false |
||||
--- |
||||
In my session, which will last for 25 minutes, it includes how open data is used and discussed in the covid19 process. It is important to open the data, but it is more important to benefit from it. We can access a lot of data sources; including health data, but are they able to respond adequately to us in combating the epidemic? As Opendatawatch notes, the current COVID-19 pandemic raises important questions about opening, sharing and using data, and highlights the challenges associated with data use. So the session will explain whether these questions have answers. |
||||
|
||||
What is the importance of open data in the fight against Covid19? What are open data sources? Which governments around the world focus on open access, open data, open state data? Why the quality of the data produced in the field of health has gained importance especially recently. What about Turkey in this context? In this context, in my session that will take 25 minutes, it includes how open data is used and discussed in the covid19 process. It is important to open the data, but it is more important to benefit from it. We can access a lot of data sources; including health data, but are they able to respond adequately to us incombating the epidemic? As Opendatawatch notes, the current COVID-19 pandemic raises important questions about opening, sharing and using data, and highlights the challenges associated with data use. The session will explain whether these questions have answers. |
||||
@ -0,0 +1,13 @@ |
||||
--- |
||||
key: open |
||||
title: Opening |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- opening |
||||
speakers: |
||||
- ozcan |
||||
draft: false |
||||
--- |
||||
Opening talk of ÖzgürKon 2020 |
||||
@ -0,0 +1,18 @@ |
||||
--- |
||||
key: ozgurluk-celiskisi |
||||
title: "Özgürlük Çelişkisi: Özgür Yazılım Kullanmamak, Özgür Yazılım Üretmekle Çelişir mi?" |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: Turkish |
||||
format: keynote |
||||
tags: |
||||
- freedom |
||||
speakers: |
||||
- fatih |
||||
- ugur |
||||
draft: false |
||||
--- |
||||
Birçok yazılımcı, özgür olmayan yazılımlar kullanarak kod yazarken aynı zamanda özgür yazılım / açık kaynak ekosistemlerine katkı sağlarlar. Peki bu bir çelişki mi? Özgür Yazılım üretmek mi, Özgür Yazılım kullanmak mı? Özgür yazılımlar neden sahipli yazılımlara göre daha az kullanılıyor? |
||||
|
||||
Topluluk içerisinde "özgür yazılım" ya da "özgür araçlar" kullanmayarak topluluklara destek olan ve özgür yazılım / açık kaynak üreten birçok geliştirici var. Ve bu geliştiriciler özgür olmayan birçok araç kullanıyorlar. Bu araçları kullanmak özgür yazılım felsefesine olan bir "ihanet" mi? PHPStorm'la özgür yazılım üretmek bir çelişki mi? Yoksa ekosisteme katkıya giden yolda, her özgür olmayan yazılım mübah mı? Bu sorulara cevaplar arayacağız, bu "çelişkinin" altında yatan nedenleri inceleyeceğiz. |
||||
|
||||
Bu konuşma temelde üretime teşviği hedefleyecektir. Üretmek kullanmaktan farklı bir alandır ve gelecekte kullanacağımız daha iyi araçlar üretebilmek için, bugün her aracı kullanabileceğimiz argümanını savunacaktır. Özgür yazılım / açık kaynak araçların kullanıcının aradığı kaliteye yükseltebilmek için neler yapacağını tartışacağız. |
||||
@ -1,21 +0,0 @@ |
||||
--- |
||||
key: premiers_pas_avec_un_microcontroleur_et_google_cloud_iot_core |
||||
title: Premiers pas avec un microcontrôleur et Google Cloud IoT Core |
||||
id: R9O1S7M9oRMmwd0cNBaz |
||||
format: conference |
||||
tags: |
||||
- _iot |
||||
level: beginner |
||||
speakers: |
||||
- gautier_mechling |
||||
videoId: kQYepd4mFLo |
||||
presentation: null |
||||
draft: false |
||||
--- |
||||
De nombreux services en ligne existent pour gérer en toute sécurité des appareils IoT à grande échelle : "Azure IoT" de Microsoft et "AWS IoT" d'Amazon sont parmi les plus connus. |
||||
|
||||
Google propose également sa solution : "Cloud IoT" basée sur la plate-forme Google Cloud (GCP). |
||||
Dans ce talk, nous partirons d'un microcontrôleur neuf ultra connu et abordable, et notre but sera tout d'abord de découvrir comment écrire du code pour ce composant nous permettant de récupérer des informations sur notre environnement. |
||||
Ensuite, nous ferons en sorte que ce composant envoie ses données vers un service Cloud, pour enfin découvrir ce que permettent ces solutions en ligne dédiées à l'IoT. |
||||
|
||||
Pour l'exemple, et parce qu'il faut bien choisir une solution, nous utiliserons Google Cloud IoT Core, les concepts restant similaires sur les autres plates-formes. |
||||
@ -0,0 +1,13 @@ |
||||
--- |
||||
key: privacy |
||||
title: Privacy issues in the aftermath of Covid-19 |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- privacy |
||||
speakers: |
||||
- engels |
||||
draft: false |
||||
--- |
||||
Gregory Engels is the International Coordinator of Pirate Party |
||||
@ -0,0 +1,19 @@ |
||||
--- |
||||
key: public_money_public_code |
||||
title: Public Money Public Code – Global problems need global solutions! |
||||
id: 6E03tbU6L5w0IyjMi7yF |
||||
language: English |
||||
format: keynote |
||||
tags: |
||||
- freedom |
||||
speakers: |
||||
- sander |
||||
draft: false |
||||
--- |
||||
In a time when humanity needs to work together to find solutions for a crisis, we cannot afford to reinvent the wheel again and again. Global problems need global solutions! It is Free Software that enables global cooperation for code development. Any proprietary solution will inevitably lead to countless isolated solutions and waste energy and time which we as humanity cannot afford in such a critical situation. |
||||
|
||||
Free Software licences allow sharing of code in any jurisdiction. Solutions developed in one country can be reused and adapted in another one. International development agencies and humanitarian movements can help to contain the spread of COVID-19 in any country around the world with the availability of Free Software solutions. |
||||
|
||||
Already before this crisis hundreds of organisations and tens of thousands of people demanded that publicly financed software developed for the public sector must be made publicly available under Free Software licences. It is now even more important than ever before to tackle this crisis. |
||||
|
||||
Do you want to promote Free Software as well? Then the campaign framework of "Public Money? Public Code!" might be the right choice for you; no matter if you want to do it as an individual or as a group; no matter if you have a small or large time budget. |
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in new issue