Contact Information
- Email Address: enzo.matsumiya@gmail.com
- Blog URL: https://inficererk.wordpress.com
- Freenode IRC Nick: enzolovesbacon
- Code Forges (GitHub, GitLab, BitBucket, etc.):
- Github : https://github.com/enzolovesbacon
- Social Media Accounts:
- Twitter : https://twitter.com/enzolovesbacon
Questions to answer
Why do you want to work with the Fedora Project?
I'm a long time Linux user, Red Hat 7 being my first distro. Since day 0, I knew I wanted to be a kernel developer. This hasn't changed and I feel now is the time to get involved so I can start my journey, and I believe GSoC, alongside with Fedora, make the perfect opportunity for this to happen.
Do you have any past involvement with the Fedora Project or another open-source project as a contributor?
No, I do not have any past involvement with Fedora Project, but I did contribute to Capstone Engine (disassembly framework).
Have you participated in GSoC in the past? If so, what year(s) and which organization(s)?
No, this is my first time applying/participating.
Do you plan to continue contributing to the Fedora Project after GSoC? If yes, what sub-project(s) are you interested with?
Yes. After GSoC, I intend to start research and development on the kernel security area (such as vulnerability research and defense mechanisms).
Why should we choose you over other applicants?
Being very curious and self-taught for every subject I encounter, I believe I will have more to contribute than simply code.
Have you contributed to any other open source organizations or projects? If so, do you have artifacts you can show so we can see your skill set(s)?
The only Pull Request I sent: https://github.com/aquynh/capstone/pull/75
But I maintained contact with its creator and I kept doing tests to make it work with Mac OS X kernel extensions.
I did a good part of the Portuguese (pt_BR) translation pack for Cryptocat, but I do not have artifacts to link.
Proposal Description
Overview and The Need
My main interest is in the tinykdump utility, which I believe will be a very useful tool for kernel and driver developers.
Any relevant experience you have
I don't have any knowledge about the topic itself, but I'll rely on my experience with related fields and languages (C and python) to help me carry on with the project.
How do you intend to implement your proposal
A secondary tool will be created, with research based on, but not to replace, the current kdump implementation.
A rough timeline for your progress
- Introductions - getting to know my mentor, discuss ideas, existing alternatives
- General research - getting to know the environment, current kdump (implementation, issues, etc)
- Start of development - goal is to get a minimum viable product
- First round of tests - try to catch most of issues here and maybe get some help from my mentor
- Refactoring and bug fixes
- Second round of tests
- Final refactoring and bug fixes
- Final delivery