This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
gsoc:2025-gsoc-iio-driver [2025/02/22 20:47] marcelosc Adjust chip suggestion paragrahp |
gsoc:2025-gsoc-iio-driver [2025/03/29 13:20] (current) marcelosc Update proposal template link |
||
---|---|---|---|
Line 45: | Line 45: | ||
* [[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/iio/accel/adxl313_core.c|drivers/iio/accel/adxl313*]] | * [[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/iio/accel/adxl313_core.c|drivers/iio/accel/adxl313*]] | ||
* [[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/iio/adc/ad7292.c|drivers/iio/adc/ad7292.c]] | * [[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/iio/adc/ad7292.c|drivers/iio/adc/ad7292.c]] | ||
- | |||
- | ===== Tips for writing a good proposal ===== | ||
- | |||
- | * Start with a section telling a bit about you with basic info such as name, summary of skills, email address, etc. | ||
- | * Then provide a short bio and coding skills subsections. | ||
- | * Next, add a section about your motivations for participating in the IIO driver GSoC project. This is a good opportunity to tell your experiences with the IIO subsystem if you have been involved with it before. | ||
- | * If you made any contribution to the Linux kernel or any other open source project, you might list them in a section too. | ||
- | * If you are very excited about participating GSoC and want to do more than the Linux driver you may add more sections describing additional ideas or plans. | ||
- | * Finally, add a section about the project and the planned work schedule. Previous IIO driver GSoC project proposals have presented work schedules divided into weeks. For easy visualization of deadlines, we kindly ask participants to also display GSoC evaluation dates in their work schedules. | ||
- | * Feel free to share your draft before submitting the final version. | ||
===== Frequently Asked Questions (FAQ) ===== | ===== Frequently Asked Questions (FAQ) ===== | ||
Line 94: | Line 84: | ||
**Answer:** No, although having a history of contribution often provides more visibility to a candidate. | **Answer:** No, although having a history of contribution often provides more visibility to a candidate. | ||
+ | |||
+ | ===== Tips for writing a good proposal ===== | ||
+ | |||
+ | There is a [[https://docs.google.com/document/d/1isgIpCIhN8GDS4_iOOD3NpwviFP1euXxs0JIOdxE8Rs/edit?usp=sharing|GSoC IIO Proposal Template]] one can use to make their proposal. It is not mandatory to use the template. However, if they choose to use the template, students are expected to adapt it. As general proposal writing tips, we suggest: | ||
+ | |||
+ | * Start with a section telling a bit about you with basic info such as name, summary of skills, email address, etc. | ||
+ | * Then provide a short bio and coding skills subsections. | ||
+ | * Next, add a section about your motivations for participating in the IIO driver GSoC project. This is a good opportunity to tell your experiences with the IIO subsystem if you have been involved with it before. | ||
+ | * If you made any contribution to the Linux kernel or any other open source project, you might list them in a section too. | ||
+ | * If you are very excited about participating GSoC and want to do more than the Linux driver you may add more sections describing additional ideas or plans. | ||
+ | * Finally, add a section about the project and the planned work schedule. Previous IIO driver GSoC project proposals have presented work schedules divided into weeks. For easy visualization of deadlines, we kindly ask participants to also display GSoC evaluation dates in their work schedules. | ||
===== Contact ===== | ===== Contact ===== |