Meshery: [Docs] Revamp the contributing.md

[kushthedude]

Current State:
There are several changes in Meshery & contributing document is not clear enough.

Desired State:
Contributing.md needs some revamping & proper structuring so that new contributors may follow it & get started with Meshery.

---

Contributor Resources

• Meshery documentation site
• Meshery documentation source
• Instructions for contributing to documentation

[Nikhil-Ladha]

@kushthedude if you could highlight the changes you are talking then, it would be easier to make the changes for the person who will take up the issue.

[kushthedude]

@kushthedude if you could highlight the changes you are talking then, it would be easier to make the changes for the person who will take up the issue.

There a lot of changes which need to be then, that is why the issue is not marked as Good-First-Issue. It needs to be someone who already has meshery set-up & can let know what revamping needs to be done. If the issue would have a single area or a heading to change I would have already highlighted it & made it a good first issue.

[PluckyPrecious]

Hi @kushthedude I wanted to open an issue to help solve the typos and some grammatical error in the contributing.md and then I saw this. Just as @Nikhil-Ladha said, it will be great if you could highlight the changes so I can work on the issue. Thanks.

[kushthedude]

Hi @kushthedude I wanted to open an issue to help solve the typos and some grammatical error in the contributing.md and then I saw this. Just as @Nikhil-Ladha said, it will be great if you could highlight the changes so I can work on the issue. Thanks.

You can go ahead with typos & grammatical fixes 👍

[PluckyPrecious]

Hi @kushthedude I wanted to open an issue to help solve the typos and some grammatical error in the contributing.md and then I saw this. Just as @Nikhil-Ladha said, it will be great if you could highlight the changes so I can work on the issue. Thanks.

You can go ahead with typos & grammatical fixes 👍

Should i reference this issue when i'm done with my edit, or i should create a new issue?

[Nikhil-Ladha]

You can mention this issue only, but instead of saying This PR fixes you should use This PR updates. That, will suffice.

[kushthedude]

Please mention this issue when you open the PR.

On Sun, 2 Aug, 2020, 19:40 Kelechi Precious Nwachukwu, <
[email protected]> wrote:

Hi @kushthedude https://github.com/kushthedude I wanted to open an
issue to help solve the typos and some grammatical error in the
contributing.md and then I saw this. Just as @Nikhil-Ladha
https://github.com/Nikhil-Ladha said, it will be great if you could
highlight the changes so I can work on the issue. Thanks.

You can go ahead with typos & grammatical fixes 👍

Should i reference this issue when i'm done with my edit, or i should
create a new issue?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/issues/1344#issuecomment-667678835,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLRCQTQNTCZKUINZIGDR6VXVXANCNFSM4PQI2JIA
.

[chandrashritii]

@kushthedude If you or someone else is not already working on it, I can take this one up.

[kushthedude]

Please go ahead!

On Fri, 14 Aug, 2020, 22:02 Shriti Chandra, [e-mail]
wrote:

@kushthedude https://github.com/kushthedude If you or someone else is
not already working on it, I can take this one up.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/issues/1344#issuecomment-674157866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLXDLCYJVVQGWST3QCLSAVRK7ANCNFSM4PQI2JIA
.

[PluckyPrecious]

Hey @chandrashritii is there something that still need to be done on this issue?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.