Hi Sundar. If you want to contribute to Pulsar, that's great. I think your first step will be to read all of the Contributing to Pulsar <https://pulsar.apache.org/en/contributing/> page. That talks about several ways to contribute.
It sounds like you aren't really excited about working on documentation. That's OK. It's necessary, but not everybody enjoys it. Consider doing code reviews, or researching questions that are in existing issues. If you want to code, that's cool - that's what most of us want to do. To help find what code you might want to work on, I suggest you take a look at the list of issues in GitHub. Specifically, look at the ones labeled Help Wanted <https://github.com/apache/pulsar/labels/help%20wanted>. Find something that looks interesting, but also is within your ability to finish. Ask any questions you might have in the issue (as comments). Then give it a try! Nothing ventured, nothing gained. Other resources are Slack (the dev channel in particular) and this mailing list. One last thing. Pulsar isn't just one project - it's many. There's Pulsar itself, but also Bookkeeper <https://github.com/apache/bookkeeper>, Pulsar Manager <https://github.com/apache/pulsar-manager>, the various clients, and the documentation (and translations <https://github.com/apache/pulsar-translation> to other languages.) (If you are really ambitious, take a look at the open issues <https://issues.apache.org/jira/projects/ZOOKEEPER/issues/ZOOKEEPER-3866?filter=allopenissues> for ZooKeeper!) Other companies have pulsar related projects too. For example, KOP <https://github.com/streamnative/kop> and PulsarCtl <https://github.com/streamnative/pulsarctl> by StreamNative. Streamlio <https://github.com/streamlio/> has some tutorials that could probably use some love. Good luck. ______________________________ - David Lanouette - david.lanoue...@gmail.com We Fear What We Do Not Understand - Unknown On Tue, Jun 16, 2020 at 12:18 PM Sundarrajan Kannan < sundarrajan.k...@gmail.com> wrote: > Hello all, > > I am a college student currently using pulsar for the final year thesis. I > really liked working with pulsar and this has prompted me to contribute to > it. I saw the first issues page and most of it was documentation issues. > > While I understand that documentation is extremely important - I faced this > issue myself while working - I am interested in writing code and making bug > fixes. > > As of now looking at the issues page and seeing the code is overwhelming. > Could anyone of you help me with this by giving me a point to start off? > And/or give a first bugfix/feature to solve? > > > -- > Regards > Sundar >
