Skip to content
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

GSoC 2020 discussion thread #269

Closed
terriko opened this issue Jan 8, 2020 · 9 comments
Closed

GSoC 2020 discussion thread #269

terriko opened this issue Jan 8, 2020 · 9 comments
Labels
gsoc Tasks related to our participation in Google Summer of Code

Comments

@terriko
Copy link
Contributor

terriko commented Jan 8, 2020

Feel free to use this thread for discussion about GSoC that doesn't fit into #267 or #266.

The Full CVE Binary Tool Ideas page has answers some some frequently asked questions.

@terriko terriko added the gsoc Tasks related to our participation in Google Summer of Code label Jan 8, 2020
@SinghHrmn
Copy link
Contributor

@terriko will you be selecting only a single project for GSoC? or more than 1 project will be selected?

@terriko
Copy link
Contributor Author

terriko commented Jan 31, 2020

@SinghHrmn We've currently got enough mentors for 2 students, but if we have a bunch of really good applications that aren't all for the same project, it's not a problem to find more mentors and take on a few more people. It's more dependent on the number of really good applications we get than anything else.

@AbhinavMir
Copy link

Hi, I'd love to work with implementing checkers for CVE. Where do I contact someone for this?

@terriko
Copy link
Contributor Author

terriko commented Feb 7, 2020

You contact someone right here in the issues! We also have a gitter setup here if you prefer: https://gitter.im/cve-bin-tool/community -- our mentors are mostly online during US Pacific working hours, but we'll chat asynchronously too if you don't mind waiting a bit for an answer. I will warn you that I'm speaking at pyCascades this weekend (Feb 8-9), so I'm not sure how much I'll be online for the next couple of days.

If you want to just dive in and start writing some code, the instructions for the new checkers project are all here:
#266

You can go ahead and try implementing a checker directly, but we usually recommend people start with writing an easier test, that way you can see that your development setup is working and get an easier first commit before you dive into harder work.

@FReeshabh
Copy link
Contributor

Hello @terriko I added #241 and #232 for Gnutls and Bluez some time back. And recently found out about GSoC 2020. And I'd be interested in continuing to contribute to this project for now and the summer!

@terriko
Copy link
Contributor Author

terriko commented Feb 18, 2020

@FReeshabh Glad to have you!

@mariuszskon
Copy link
Contributor

@terriko Hi, I submitted a draft proposal "Python CVE Binary Tool: Enhancing Quality of Output" and was wondering if these are getting reviewed? Thanks!

@terriko
Copy link
Contributor Author

terriko commented Mar 22, 2020

I'm hoping to get started on proposal feedback on Monday. (I prioritized pull requests last week because a few people haven't had first merged code yet.).

Everyone: please make sure there's a way to contact you if you want feedback (eg comments turned on in your doc, an email you actually check in the doc). We can't leave comments in the Google system itself.

@terriko
Copy link
Contributor Author

terriko commented Sep 9, 2020

GSoC 2020 is over, so closing this thread. We'll open a new one for 2021 if it gets announced!

@terriko terriko closed this as completed Sep 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gsoc Tasks related to our participation in Google Summer of Code
Projects
None yet
Development

No branches or pull requests

5 participants