[Doc] Tracking issue for contribution guide

[tisonkun]

Motivation

I'm working on the development guide (contribution guide) for Apache Pulsar. The guide page can be found at https://pulsar.apache.org/contribute/.

This movement is to collect all the topics related to Pulsar development scattered everywhere and provides a completed, one-stop doc page for existing and potential contributors.

The final structure is pending to be like: https://devguide.python.org/

Implementation

Here are the subtasks:

• [cleanup][doc] Remove resources moved to pulsar-site #18267
• Introduce the first version of contribution guide pulsar-site#268
• Flatten files (slug) and use a siderbar config to categorize documents #18494
• [Doc] Move Security Policy and Supported Versions to an appropriate category in the website #18103
• [Doc] Fix links to Google docs page in the documentation guide #18297
• [Doc] Update the release process about how to release C++ and Python client #17918
• Migrate Contributing page #19116
• Migrate Coding Style page #19117
• Move development tools under https://pulsar.apache.org/docs/next/developers-landing to the new development guide page
  • This is for application/integration developers also, keep it under the user doc. We may duplicate a bit in the contribution guide if we talk about technical internals.
• Describe how to review
• Describe how to report an issue
• Describe how to triage an issue
  • Add issue triaging doc pulsar-site#485
• Describe how to report a security issue
• Describe the security policy (https://pulsar.apache.org/security)
• [feat][workflow] add instructions on "How to Contribute Connector" #19547

[momo-jun]

@tisonkun thanks for putting all of these together. I think it also makes sense to relocate the Security Policy page to this development guide. WDYT?
See more context at #18103.

[tisonkun]

cc @momo-jun

Make sense. Added as a work item. I'm going to handle it by the next week. Although, I think it's still valuable to hold an entry in the user doc since security topics are also users' concerns.

[momo-jun]

I agree. It can still be linked in the Security Overview or somewhere fits better.

Make sense. Added as a work item. I'm going to handle it by the next week. Although, I think it's still valuable to hold an entry in the user doc since security topics are also users' concerns.

[github-actions]

The issue had no activity for 30 days, mark with Stale label.

[tisonkun]

Cross refer to https://lists.apache.org/thread/qfz1c52ddndf6rqj0nxc0p9ktz6goh7g that we should document what is breaking changes and cross-refer in release process and label strategy.

cc @eolivelli @codelipenghui @dave2wave

I can prepare a draft in March. And feel free to take over it if you have time to do it.

[github-actions]

The issue had no activity for 30 days, mark with Stale label.

[tisonkun]

Most done. Others are abandon from my personal motivation.

Closing...