Skip to content

GSoC2021 Student Guideline

Jump to bottom
Attila Szakacs edited this page Feb 8, 2021 · 1 revision

If you want to participate in syslog-ng GSoC occasion you should do the followings

Those who fixed issues in the syslog-ng could gain advantages: they could provide better proposals, and we are favoring somebody who contributed against somebody who did not. You could pick an easy bug in syslog-ng, and try to solve it, or contribute something worthwhile.

  1. Please checkout the syslog-ng from the GitHub, and build it. If something isn't clean, or you faced with a problem, ask on the syslog-ng mail lists or on our Gitter room.

  2. Look at our idea page. Select a project for which you want to work. If you have an idea, but it isn't not contained by our idea page please let us know about it.

  3. Before you submit a proposal, please read our descriptions about what we expect in a proposal

  4. To submit a proposal, please create a new Wiki page for it, as described here, and don't forget to record it on GSoC with google page, with a link back to the created wiki page.

Additional information:

  1. Please be prepared that during the application/evaluation period, you are going to receive a task related to your chosen project. This task have to be done with high quality at a given deadline, as that also going to have significant effect choosing the student.
  2. The gitbook is a good source to learn more about syslog-ng as a developer, please check it first if you have a question. If you find some issues in it, please open an issue or pull request in order to improve it.

Creating a proposal for GSoC

  1. Write a brief description about the project. A few sentences will be enough.

  2. Describe why the project will be useful for syslog-ng and/or the community. Also, describe why the project is interesting for you (because we are also interested in your motivation). If you can, provide us with some use cases in addition.

  3. Define the goal of the project. Also, write a Definition of Done: when you consider the project ready and successful. If you have stretch goals (even if they probably will not get done, but can be a part of a further development), describe them too.

  4. What knowledge areas are required for the success of the project? Which areas are you familiar with and which areas you have to improve?

  5. Define a time schedule. Define milestones with dates (for example in weekly resolution) - with that you can easily split your project into smaller tasks, and it also facilitates following the progress and whether you are on track or not.

Clone this wiki locally