Skip to content

Commit 5ca2635

Browse files
mlodicmlodic
committed
draft
1 parent cd8bdf7 commit 5ca2635

File tree

3 files changed

+133
-2
lines changed

3 files changed

+133
-2
lines changed

‎2023/README.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Google Summer of Code 2023
2+
List of project ideas for contributors applying to the Google Summer of Code program in 2023.
3+
4+
## Timeline/milestones
5+
6+
Please always refer to the [official timeline](https://developers.google.com/open-source/gsoc/timeline).
7+
8+
9+
## Application Process
10+
11+
#### 0. Get familiar with GSoC
12+
13+
First of all, and if you have not done that yet, read [the contributor guide](https://google.github.io/gsocguides/student/) 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.
14+
15+
#### 1. Discuss the project idea with the mentor(s)
16+
17+
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.
18+
19+
If your idea is not listed, please discuss it with the mentors in the [IntelOwl Slack Channel](https://gsoc-slack.honeynet.org/). We're always open to new ideas and won't hesitate on choosing them if you demonstrate to be a good candidate!
20+
21+
#### 2. Understand that
22+
23+
- You're committing to a project and we ask you to publicly publish your weekly progress on it in Github.
24+
- We will ask you to give feedback on our mentorship and management continuously. Communication is key to the success of the project.
25+
- You wholeheartedly agree with the [code of conduct](https://github.com/intelowlproject/IntelOwl/blob/master/CODE_OF_CONDUCT.md).
26+
- 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).
27+
28+
#### 3. Fill out the application form
29+
30+
We recommend you to follow [Google's guide to Writing a Proposal](https://google.github.io/gsocguides/student/writing-a-proposal) and to leverage the template we provide [here](https://github.com/intelowlproject/gsoc/blob/main/proposal_template.md)
31+
32+
Once you have a draft proposal please share it with us 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.
33+
34+
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.
35+
36+
## Project Ideas
37+
You can also propose your own.
38+
39+
### Title
40+
<b>Mentors</b>:
41+
42+
<b>Project URL</b>:
43+
44+
<b>Project hours</b>:
45+
46+
<b>Skills required</b>:
47+
48+
<b>Difficulty</b>:

‎README.md

Lines changed: 33 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,33 @@
1-
# gsoc
2-
Repository containing GSoC guidelines, history and ideas
1+
# Google Summer of Code
2+
Repository containing [GSoC](https://summerofcode.withgoogle.com/) guidelines, history and ideas lists.
3+
4+
### General Guidelines
5+
Please read and follow the [contributing guidelines rules]( https://intelowl.readthedocs.io/en/latest/Contribute.html) before doing any kind of contribution.
6+
7+
### History
8+
Since its birth, under the umbrella of [The Honeynet Project](https://www.honeynet.org), this project has been participating in the [Google Summer of Code](https://summerofcode.withgoogle.com/) (GSoC)!
9+
10+
Those projects has been successful a lot! The did not only brought IntelOwl to the next level but opened several careers opportunities to the contributors.
11+
12+
Project Summaries (2020-2022):
13+
14+
- 2020: (Mentor: Matteo Lodi)
15+
- [Eshaan Bansal](https://twitter.com/eshaan7_): [IntelOwl Work Product](https://www.honeynet.org/2020/08/26/gsoc-2020-work-product%e2%80%8a-%e2%80%8aintel-owl/)
16+
- 2021: (New mentor: Eshaan Bansal)
17+
- [Sarthak Khattar](https://twitter.com/Mr_Momo07): [IntelOwl Improvements](https://www.honeynet.org/2021/08/20/gsoc-2021-project-summary-intelowl-improvements/)
18+
- [Shubham Pandey](https://twitter.com/imshubham31): [IntelOwl Connectors Manager and Integrations](https://www.honeynet.org/2021/08/20/gsoc-2021-project-summary-intelowl-connectors-manager-and-integrations/)
19+
- 2022: (New mentors: Shubham Pandey, Simone Berni, Daniele Rosetti)
20+
- [Aditya Narayan Sinha](https://twitter.com/0x0elliot): [Creating Playbooks for IntelOwl](https://www.honeynet.org/2022/10/06/gsoc-2022-project-summary-creating-playbooks-for-intelowl/)
21+
- [Aditya Pratap Singh](https://twitter.com/devmrfitz): [IntelOwl v4 improvements](https://www.honeynet.org/2022/09/26/gsoc-2022-project-summary-intelowl-v4-improvements/)
22+
- [Hussain Khan](https://twitter.com/Hussain41099635): [IntelOwl Go Client](https://www.honeynet.org/2022/09/06/gsoc-2022-project-summary-intelowl-go-client-go-intelowl/)
23+
24+
Since 2023 we are proposing IntelOwl and [GreedyBear](https://github.com/honeynet/GreedyBear) to the GSoC under a new non-profit organization called [IntelOwl Project](https://www.linkedin.com/company/intelowl) (if it gets accepted by Google) and not anymore under the Honeynet Project. Nothing would change for an aspiring new contributor.
25+
26+
Starting from 2023, you may find the updated project ideas list for the current year in the dedicated folder.
27+
28+
### Be the next contributor!
29+
If you are interested in being the next GSoC developer for IntelOwl, join the [Honeynet Slack chat](https://gsoc-slack.honeynet.org/) for more info.
30+
31+
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.
32+
33+

‎proposal_template.md

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
## Project Title
2+
3+
## Personal Information
4+
* Name
5+
* Slack Username
6+
* GitHub
7+
* LinkedIn
8+
* Twitter
9+
* Email
10+
* Nationality
11+
* Location
12+
* Primary Spoken Language
13+
14+
## Top Project of Choice
15+
16+
## Are you willing and able to work on other projects instead?
17+
18+
## Please describe your preferred coding languages and experience
19+
20+
## Please describe your experience with Unix-like system administation
21+
22+
## Please describe any previous cyber security related development experience, including details of any patches, code or ideas you may have previously submitted
23+
24+
## Please describe any previous open-source development experience, including projects you have worked on.
25+
26+
## What school do you attend and what is your specialty/major at the school?
27+
### How many years have you attended there?
28+
### What city/country will you be spending this summer in?
29+
### How much time do you expect to have for this project?
30+
### Please list all jobs, summer classes, vacations, and/or other commitments that you’ll need to workaround.
31+
32+
## Have you participated in any previous Summer of Code projects? If so please describe your projects and experience, including what you liked or didn’t like about the experience
33+
34+
## Have you applied for (or intend to apply for) any other Google Summer of Code projects? If so, which ones?
35+
## If you have a URL for your resume/CV, please list it here
36+
37+
## If you wish to list any personal/blog URLs, do so here
38+
39+
## Project details
40+
41+
### Project Intro
42+
43+
### Task n1 description
44+
### Task n2 description
45+
...
46+
47+
## Timeline
48+
Expected Timeline for each week of work, including tasks previously described. You may use a table.
49+
50+
Please remember to specify the expected deliverables for the 2 evaluation periods.
51+
52+
## Why are you well suited to perform this project and why are you interested in it?

0 commit comments

Comments
 (0)