Update src/blog-posts/your-guide-to-contributing-well-in-wave by bcccrmr · Pull Request #1905 · drips-network/app

bcccrmr · 2026-05-20T15:28:17Z

No description provided.

efstajas · 2026-05-20T15:36:47Z

+Be selective. Read the issue properly, understand the scope, and check the repo before applying. Make sure it’s something you can realistically deliver well.
+
+A strong application doesn’t need to be long, but it should be specific. A couple of sentences explaining how you’d approach the task or why you’re a good fit is usually enough.
+
+Generic applications (or obvious AI copy-paste jobs) are easy to spot and rarely get picked. A bit of effort here can make you immediately stand out.


Suggested change

Be selective. Read the issue properly, understand the scope, and check the repo before applying. Make sure it’s something you can realistically deliver well.

A strong application doesn’t need to be long, but it should be specific. A couple of sentences explaining how you’d approach the task or why you’re a good fit is usually enough.

Generic applications (or obvious AI copy-paste jobs) are easy to spot and rarely get picked. A bit of effort here can make you immediately stand out.

**Be selective.** Read the issue properly, understand the scope, and check the repo before applying. Make sure it’s something you can realistically deliver well.

**A strong application doesn’t need to be long**, but it should be specific. A couple of sentences explaining how you’d approach the task or why you’re a good fit is usually enough.

**Generic applications** (or obvious AI copy-paste jobs) **are easy to spot** and rarely get picked. A bit of effort here can make you immediately stand out.

efstajas · 2026-05-20T15:37:40Z

+
+When you submit work, make it easy to review. Keep things clean, follow existing patterns, and test where needed.
+
+One thing that really matters in Wave: **link your PR to the issue clearly**. If that connection isn’t obvious, your work may not be tracked properly. Not sure how? [More on that here](https://docs.drips.network/wave/contributors/faq#my-pr-got-merged-but-i-didnt-receive-points-why).


Suggested change

One thing that really matters in Wave: **link your PR to the issue clearly**. If that connection isn’t obvious, your work may not be tracked properly. Not sure how? [More on that here](https://docs.drips.network/wave/contributors/faq#my-pr-got-merged-but-i-didnt-receive-points-why).

One thing that really matters in Wave: **link your PR to the issue clearly**. If that connection isn’t obvious, your work may not be tracked properly. Not sure how? [More on that here.](https://docs.drips.network/wave/contributors/faq#my-pr-got-merged-but-i-didnt-receive-points-why).

efstajas · 2026-05-20T15:39:53Z

+- Read the docs before asking questions
+- Apply intentionally and where you’re a real fit
+- Stay in the loop once assigned - don’t disappear
+- Keep communication on GitHub and follow up respectfully
+- Link your PR to the issue clearly
+- Use tickets and the Support Hub for the right things
+- Be constructive, respectful, and easy to work with


Suggested change

- Read the docs before asking questions

- Apply intentionally and where you’re a real fit

- Stay in the loop once assigned - don’t disappear

- Keep communication on GitHub and follow up respectfully

- Link your PR to the issue clearly

- Use tickets and the Support Hub for the right things

- Be constructive, respectful, and easy to work with

- **Read the docs** before asking questions

- **Apply intentionally** and where you’re a real fit

- **Stay in the loop** once assigned - don’t disappear

- **Keep communication** on GitHub and follow up respectfully

- **Link your PR** to the issue clearly

- Use tickets and the Support Hub for the right things

- Be constructive, respectful, and easy to work with

efstajas · 2026-05-20T15:40:47Z

+
+When you get feedback, take it seriously. Don’t ignore it, improve the work and move it forward.
+
+And we all know AI can help when solving issues but it shouldn’t be doing all the thinking for you. If you can’t explain what you’ve submitted that usually becomes obvious pretty quickly and this may affect if maintainers want to work with you in the future.


Suggested change

And we all know AI can help when solving issues but it shouldn’t be doing all the thinking for you. If you can’t explain what you’ve submitted that usually becomes obvious pretty quickly and this may affect if maintainers want to work with you in the future.

Lastly: We all know that AI can help solve issues, but it shouldn’t be doing all the thinking for you. If you can’t explain what you’ve submitted, it becomes obvious pretty quickly, and this may affect whether maintainers want to work with you in the future.

efstajas · 2026-05-20T15:41:22Z

+
+## 5. Use the right channels
+
+Not everything belongs in general chat.


Suggested change

Not everything belongs in general chat.

Not everything belongs into `#general`.

efstajas · 2026-05-20T15:48:20Z

+
+But contributing well isn’t just about writing code. It’s how you apply, how you communicate, how you handle feedback and how you follow through. The contributors who get the most out of Wave (and the ones maintainers want to work with again) tend to get these basics right.
+
+This guide is here to help you do exactly that.


Suggested change

This guide is here to help you do exactly that.

This guide is here to help you do exactly that ✨

efstajas · 2026-05-20T15:49:20Z

+
+## 1. Start with the docs
+
+Before you apply to anything, take a few minutes to read the docs on Drips Network.


Suggested change

Before you apply to anything, take a few minutes to read the docs on Drips Network.

Before you apply to your first issue, take a few minutes to read the [Drips Wave docs](https://docs.drips.network/wave/contributors/solving-issues-and-earning-rewards)!

efstajas · 2026-05-20T15:50:13Z

+
+## 3. Communicate clearly (and don’t disappear)
+
+Once you’re assigned, stay in the loop.


Suggested change

Once you’re assigned, stay in the loop.

Once you’re assigned, stay in the loop 🔁

efstajas · 2026-05-20T15:50:44Z

+Keep communication on the GitHub issue or PR as much as possible. That’s where the work lives, and it helps everyone stay aligned. Ask questions there, share progress there and respond to feedback there.
+
+If you get stuck or can’t continue, say so. Don’t go quiet! Issues may be reassigned if there’s no activity, a quick update is always better than silence.
+
+Also worth saying: be patient. Maintainers are juggling a lot and reviews can take time. Follow up if you need to but don’t spam or demand instant replies. We recommend waiting 24 - 48 hours, pinging after 3 hours is unlikely to get a positive response.


Suggested change

Keep communication on the GitHub issue or PR as much as possible. That’s where the work lives, and it helps everyone stay aligned. Ask questions there, share progress there and respond to feedback there.

If you get stuck or can’t continue, say so. Don’t go quiet! Issues may be reassigned if there’s no activity, a quick update is always better than silence.

Also worth saying: be patient. Maintainers are juggling a lot and reviews can take time. Follow up if you need to but don’t spam or demand instant replies. We recommend waiting 24 - 48 hours, pinging after 3 hours is unlikely to get a positive response.

**Keep communication on the GitHub issue or PR** as much as possible. That’s where the work lives, and it helps everyone stay aligned. Ask questions there, share progress there and respond to feedback there.

**If you get stuck or can’t continue, say so.** Don’t go quiet! Issues may be reassigned if there’s no activity, a quick update is always better than silence.

Also worth saying: **Be patient.** Maintainers are juggling a lot and reviews can take time. Follow up if you need to but don’t spam or demand instant replies. We recommend waiting 24 - 48 hours, pinging after 3 hours is unlikely to get a positive response.

efstajas · 2026-05-20T15:52:17Z

+Not everything belongs in general chat.
+
+- For Wave questions or contribution-related issues → use 🎫 tickets
+- For KYC, wallets, rewards or feedback → use the [Support Hub](https://www.drips.network/wave/support)


Suggested change

- For KYC, wallets, rewards or feedback → use the [Support Hub](https://www.drips.network/wave/support)

- For KYC, rewards, or other sensitive topics → use the chat widget or send us an email through our [Support Hub](https://www.drips.network/wave/support)

bcccrmr added 2 commits May 20, 2026 17:17

Update src/blog-posts/your-guide-to-contributing-well-in-wave

4a0cf96

Update src/blog-posts/your-guide-to-contributing-well-in-wave

5278f5b

efstajas requested changes May 20, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update src/blog-posts/your-guide-to-contributing-well-in-wave#1905

Update src/blog-posts/your-guide-to-contributing-well-in-wave#1905
bcccrmr wants to merge 2 commits into
mainfrom
cms/top_tips_contributors

bcccrmr commented May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

efstajas May 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants


		When you submit work, make it easy to review. Keep things clean, follow existing patterns, and test where needed.

		One thing that really matters in Wave: link your PR to the issue clearly. If that connection isn’t obvious, your work may not be tracked properly. Not sure how? [More on that here](https://docs.drips.network/wave/contributors/faq#my-pr-got-merged-but-i-didnt-receive-points-why).


		When you get feedback, take it seriously. Don’t ignore it, improve the work and move it forward.

		And we all know AI can help when solving issues but it shouldn’t be doing all the thinking for you. If you can’t explain what you’ve submitted that usually becomes obvious pretty quickly and this may affect if maintainers want to work with you in the future.

	And we all know AI can help when solving issues but it shouldn’t be doing all the thinking for you. If you can’t explain what you’ve submitted that usually becomes obvious pretty quickly and this may affect if maintainers want to work with you in the future.
	Lastly: We all know that AI can help solve issues, but it shouldn’t be doing all the thinking for you. If you can’t explain what you’ve submitted, it becomes obvious pretty quickly, and this may affect whether maintainers want to work with you in the future.


		## 5. Use the right channels

		Not everything belongs in general chat.

	Not everything belongs in general chat.
	Not everything belongs into `#general`.


		But contributing well isn’t just about writing code. It’s how you apply, how you communicate, how you handle feedback and how you follow through. The contributors who get the most out of Wave (and the ones maintainers want to work with again) tend to get these basics right.

		This guide is here to help you do exactly that.


		## 1. Start with the docs

		Before you apply to anything, take a few minutes to read the docs on Drips Network.

	Before you apply to anything, take a few minutes to read the docs on Drips Network.
	Before you apply to your first issue, take a few minutes to read the [Drips Wave docs](https://docs.drips.network/wave/contributors/solving-issues-and-earning-rewards)!


		## 3. Communicate clearly (and don’t disappear)

		Once you’re assigned, stay in the loop.

	Once you’re assigned, stay in the loop.
	Once you’re assigned, stay in the loop 🔁

	- For KYC, wallets, rewards or feedback → use the [Support Hub](https://www.drips.network/wave/support)
	- For KYC, rewards, or other sensitive topics → use the chat widget or send us an email through our [Support Hub](https://www.drips.network/wave/support)

Conversation

bcccrmr commented May 20, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants