doc : Improve our CONTRIBUTING guide from a newcomer perspective

[rohanKanojia]

Updated contributing guide so that it's more organized and helpful for newcomers:

• Added table of contents
• Added information about good first issues and first timers only issues
• Added information about how to build project and use local build of plugins (both maven and gradle)
• Added information about how to debug project
• Added information about how to generate project documentation

These changes have been mostly taken from Quarkus CONTRIBUTING.md and LibreOffice Easy Hacks

[manusa]

This is OK, but it's not tackling the initial problem.

We need to clearly define the types of good-first-issues.

For example:

first-timers-only:
These issues are aimed for first-time contributors to get acquainted with the project and the Eclipse Foundation contributing policies.
Users are only allowed to take one of these issues and are also encouraged to tackle one of these before doing more complex code contributions.
These issues are extremely simple to solve. In general, the code changes are already described in the issue.
The main purpose is to ensure that contributors have signed an ECA and are familiar with the GitHub pull request procedures.

good-first-issue:
These issues are aimed for users who have already tackled a first-timers-only and would like to continue their contributing journey on the project.
These issues are slightly more complicated and will require actual work from the contributor.
The main purpose is for contributors to gain confidence while working on the code-base and to keep them engaged in the project.

help-wanted:
These issues are more complex and are aimed for regular contributors of the project or people who are familiar with the code-base.

[rohanKanojia]

Shall I add abovementioned paragraphs in Finding an issue to work on section?

[manusa]

a space seems to be missing here

[manusa]

This is OK, but it's not tackling the initial problem.

We need to clearly define the types of good-first-issues.

For example:

first-timers-only: These issues are aimed for first-time contributors to get acquainted with the project and the Eclipse Foundation contributing policies. Users are only allowed to take one of these issues and are also encouraged to tackle one of these before doing more complex code contributions. These issues are extremely simple to solve. In general, the code changes are already described in the issue. The main purpose is to ensure that contributors have signed an ECA and are familiar with the GitHub pull request procedures.

good-first-issue: These issues are aimed for users who have already tackled a first-timers-only and would like to continue their contributing journey on the project. These issues are slightly more complicated and will require actual work from the contributor. The main purpose is for contributors to gain confidence while working on the code-base and to keep them engaged in the project.

help-wanted: These issues are more complex and are aimed for regular contributors of the project or people who are familiar with the code-base.

It seems you did add these sections but I missed them.

Please, merge anything that's not already stated in yours and add the third entry.

I'm not sure if this is too far down in the page and users might miss it.

[rohanKanojia]

Shall we split this page into multiple small pages?

[manusa]

I would add an but we advise to start with a first-timers-only issue somewhere here.

[rohanKanojia]

I have added this sentence:

[manusa]

Shall we split this page into multiple small pages?

I don't think that's a good idea.

[manusa]

I would ditch the emojis, I think the rendering won't be uniform and the text to the right won't be correctly aligned.

Other than that, LGTM, and ready to go 🚀