New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Objectives for 2024. #24
Comments
📧 Promotion request submitted: |
📧 Proposition submitted to the team managing the podcast, in french, as we are all french native speakers and the podcast is made in french 😀: 💬 Translation:
|
You'll need to translate for us. 😀 Thanks! |
Added into original post 😃 |
Nice 💯 |
📡 Record scheduled for the 2024-03-11 evening... @riramar I need the help of your memory for some points:
Thanks a lot in advance 😃 |
Hi @righettod In 2015, during a conversation with Jim Manico about HTTP headers, he mentioned that the OWASP Secure Headers project had been inactive for nearly two years. Jim then proposed that I assume responsibility for the project, to which I agreed. Consequently, on December 14th, 2015, I made my inaugural contribution to the OWASP Secure Headers wiki page. Best regards, |
Thanks a lot for the information 👍 |
👨💻 Work started via: |
📋 My preparation for the podcast is here as a Google Document in French (easier for me to use the notes during the recording). 🌏 It is possible to translate the content from French to any language via Google Translate using a DOCX downloaded version of the content: |
✅ Completed. |
📩 Status kindly asked to the project committee: 📡 Feedback received: Our application is under review. |
✅ Podcast recorded and published: |
✅ Done via OWASP/www-project-secure-headers#175 |
✅ Done in the following PR: |
The text was updated successfully, but these errors were encountered: