Repository containing GSoC guidelines, history and ideas lists.

Since its birth, under the umbrella of The Honeynet Project, IntelOwl has been participating in the Google Summer of Code (GSoC)!

Those projects has been successful a lot! They did not only bring IntelOwl to the next level but did open several careers opportunities to the contributors.

Project Summaries (2020-2022):

• 2020: (Mentor: Matteo Lodi)
  • Eshaan Bansal: IntelOwl Work Product
• 2021: (New mentor: Eshaan Bansal)
  • Sarthak Khattar: IntelOwl Improvements
  • Shubham Pandey: IntelOwl Connectors Manager and Integrations
• 2022: (New mentors: Shubham Pandey, Simone Berni, Daniele Rosetti)
  • Aditya Narayan Sinha: Creating Playbooks for IntelOwl
  • Aditya Pratap Singh: IntelOwl v4 improvements
  • Hussain Khan: IntelOwl Go Client

Since 2023 we are proposing IntelOwl and GreedyBear to the GSoC under a new non-profit organization called IntelOwl Project and not anymore under the Honeynet Project. Nothing would change for an aspiring new contributor.

Plus, we are hosting projects from our friends of the following organizations/projects:

• Quark-Engine
• Qiling
• Certego BuffaLogs

Starting from 2023, you may find the updated project ideas list for the current year in the dedicated folder. For example, for 2023 check here.

UPDATE!! We have not been accepted by Google as a new organization for this year. We'll try again in 2024. Meanwhile we are falling back to The Honeynet Project umbrella. So please apply there.

If you are interested in being the next GSoC developer for IntelOwl, join the Honeynet Slack chat for more info.

This is also the place where the majority of the development discussion happens, so feel free to join, have a look and ask questions about the project.

Please remember to read and follow the IntelOwl contributing guidelines rules before doing any kind of contribution.

First of all, and if you have not done that yet, read the contributor guide which will allow you to understand all this process and how the program works overall. Refer to its left side menu to quick access sections that may interest you the most, although we recommend you to read everything.

This is a required step unless you have dived in into the existing codebase and understood everything perfectly (very hard) and the idea you prefer is on the list below.

If your idea is not listed, please discuss it with the mentors in our official channels. We're always open to new ideas and won't hesitate on choosing them if you demonstrate to be a good candidate!

• You're committing to a project and we ask you to publicly publish your weekly progress on it in Github.
• We will ask you to give feedback on our mentorship and management continuously. Communication is key to the success of the project.
• You wholeheartedly agree with the code of conduct.
• You must tell us if there's any proposed idea that you don't think would fit the timeline or could be boring (yes, we're asking for feedback).

We recommend you to follow Google's guide to Writing a Proposal and to leverage our template.

Once you have a draft proposal please share it with us via our official channels in Google Docs. In this way we don't have to download anything and we can comment it and request clarifications in a more structured way.

You can also ask for a review anytime to the community or mentor candidates before the contributor application deadline. It's much easier if you get feedback early than to wait for the last moment.

• Slack chat
• Twitter