Contributing to the development of Gatekeeper

[Sudeep Biswas]

Hello everyone!
I did not submit my proposal for GSoC because of my exams during the GSoC period. But I would still like to contribute to the development of gatekeeper in my free time. I've started playing with the code and submitted a PR as well.
Can someone please guide me as I'm finding it a bit difficult to understand some parts of the code.

Thank you.

[Qiaobin Fu]

Hello Sudeep,

Glad to hear that you are interested in our Gatekeeper project! It's really a good start for making pull requests for the open issues in Gatekeeper (https://github.com/AltraMayor/gatekeeper/issues). Please feel free to ask questions regarding our codebase in our mailing list.

Thank you!

Qiaobin

[Michel Machado]

Complementing Qiaobin's suggestions:

Read Gatekeeper's code and write about it on your blog. Not only will your effort benefit others, but it'll also give you a deep understanding of the code.

Read previous pull requests. There are plenty of good information in the comments.

--
You received this message because you are subscribed to the Google Groups "Linux XIA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-xia+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Edward Hui]

Hi community,

I would also like to make contributions regardless of the application result, for minor adjustments, e.g. typos, minor bugs, what will be the common practice, will it bother the community if I start a pull request only on typos?

Many thanks,
Edward

[Michel Machado]

As long as a pull request improves our codebase, it's a valid pull request. I don't mind merging a pull request that fixes typos. In fact, this kind of pull request can help you to learn/practice the review process. The following links may help you getting started:

https://github.com/AltraMayor/XIA-for-Linux/wiki/General-C-Coding-Style

https://github.com/AltraMayor/XIA-for-Linux/wiki/Code-Reviewing-Guideline