# Interested to contribute to Packetbeat protocols **URL:** \ **Category:** Google Summer of Code\ **Created:** [February 24, 2018, 10:51am UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336 "2018-02-24T10:51:29Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![montem](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/montem/32/28143_2.png) [@montem](https://discuss.elastic.co/u/montem)\ **Post date:** [February 24, 2018, 10:51am UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336/1 "2018-02-24T10:51:29Z")
Hi I am Manthan Sharma, final year undergrad from LNMIIT, Jaipur and currently working at SOROCO, India as Site Reliability Engineer. I have a good experience of Go, and knowledge of network and communication protocol. I have set up my development environment and currently, I'm familiarizing myself with the code and looking at merge request([https://github.com/elastic/beats/pull/5408](https://github.com/elastic/beats/pull/5408)) to understand the requirement of the new protocol features. I would like to know if my full-time internship at SOROCO will not be a problem for the community, as I move forward with GSOC Project. ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [February 26, 2018, 12:06am UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336/2 "2018-02-26T00:06:37Z")
For starting with developing packetbeat protocols have a look at the [code generator](https://github.com/elastic/beats/tree/master/packetbeat/scripts/tcp-protocol) providing you the basic layout/boilerplate required for new protocols. The [cassandra protocol implementation](https://github.com/elastic/beats/tree/master/packetbeat/protos/cassandra) is the only one using the generator in full so far. Some protocols might be a little more tricky. E.g. parsing kafka responses do depend on knowing the request. [This (work in progress) PR](https://github.com/elastic/beats/pull/3390) adds kafka support. We have some more ideas for packetbeat, not just adding new protocols. You can follow project proposals on [https://github.com/elastic/gsoc](https://github.com/elastic/gsoc). We will add some more packetbeat related the next days. ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [February 26, 2018, 3:06pm UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336/3 "2018-02-26T15:06:40Z")
> [@montem](#): > > I would like to know if my full-time internship at SOROCO will not be a problem for the community, as I move forward with GSOC Project. You are expected to work full-time on GSoC from May 14 to August 14. If you have a full-time internship somewhere else at the same time, this will not work out unfortunately. ---
**Author:** ![montem](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/montem/32/28143_2.png) [@montem](https://discuss.elastic.co/u/montem)\ **Post date:** [February 26, 2018, 3:53pm UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336/4 "2018-02-26T15:53:26Z")
@xeraa Hey, I understand your concern regarding my time contribution to the community during GSoC period. As I checked in GSoC FAQ, They have asked 30+ hours of working contribution in a week, which I can cover easily by giving 3-4hrs. on weekdays(Mon-Fri) and on weekends I can work around 6-8 hrs. easily. If you guys think this is sufficient time to complete the GSoC project. Please consider my request. ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [February 26, 2018, 5:40pm UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336/5 "2018-02-26T17:40:15Z")
@montem I don't think this is something we want to do. We want people to work reasonable hours and be able to do their best work. Planning for a 70+ hour work week doesn't sound like that. I've seen GSoC projects fail because of similar reasons and it's a waste for both you and us. ---
**Author:** ![montem](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/montem/32/28143_2.png) [@montem](https://discuss.elastic.co/u/montem)\ **Post date:** [February 27, 2018, 1:41am UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336/6 "2018-02-27T01:41:26Z")
@xeraa Ok, I think you have a reasonable doubt regarding the working hours, but I just want you to know, I am doing the same for last 1 year working 70+ hrs. a week. I don't think this will affect my case in any way. So, I will rest my case here but will love to be part of this community. Thanks ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [February 27, 2018, 4:52pm UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336/7 "2018-02-27T16:52:50Z")
@montem thanks for understanding! It's a model we don't want to encourage. But of course we are welcoming all community contributions and are happy to help with that 🤗 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 5:15am UTC](https://discuss.elastic.co/t/interested-to-contribute-to-packetbeat-protocols/121336/8 "2022-11-04T05:15:03Z")