What do you think? https://github.com/apache/pulsar/discussions/22176

I think adding some getting started resources is a good idea but at the same time, let’s say a university student comes to the website and sees this very big list of things to know they will probably get scared away. For someone less experienced in my opinion the ideal way is to start with a some issue/feature with a small scope that can be understood easily, get a quick “achievement” with the contribution which motivates to maybe contribute more and then get deeper knowledge along the way. Good code reviews provide “mentorship” in this case. Keeping a huge list of resources up to date is a serious effort and if they get out of date it ends up being even more confusing, this is something we need to consider as well

Of course, it’s not requirements, but rather recommendations on what topics to learn. It may be in the form of a blog post by someone who knows the subject well. Having an answer to the question of where to start would eliminate many obstacles for many people. The “developer-roadmap” repository has 268,000 GitHub stars ⭐ for a reason️. https://github.com/kamranahmedse/developer-roadmap

> Having a clear roadmap of what to learn and where to start would bring more contributors to the project. I believe that to attract more contributors to the project, the best thing to do is to increase awareness of Pulsar. Nevertheless, we need to lower the barrier to entry for contributions. Your proposal will surely help. Another effective method to lower this barrier and support interested contributors is to invest time in identifying 'good first issues' and featuring them on this page. Fixing or improving the documentation is also an excellent way to start contributing. @Kiryl Valkovich, your recent contributions have been very helpful in this regard gratitude thank you - 'suggest changes' link...