paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-09 08:26:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

contributor docs: Rename section and update references.

Browse Source 
Remove unnecessary reference from questions doc.
This commit is contained in:
Alya Abbott
2025-10-27 15:02:37 -07:00
committed by Tim Abbott
parent c6a60fd533
commit 459cd87bd4
3 changed files with 4 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@@ -69,7 +69,7 @@ This page will guide you through the following steps:
1. [Getting started](#getting-started) 1. [Getting started](#getting-started)
1. [Finding an issue to work on](#finding-an-issue-to-work-on) 1. [Finding an issue to work on](#finding-an-issue-to-work-on)
1. [Getting help](#getting-help) as you work on your first pull request 1. [Getting help](#getting-help) as you work on your first pull request
1. Learning [what makes a great Zulip contributor](#what-makes-a-great-zulip-contributor) 1. Learning [best practices](#best-practices)
1. [Submitting a pull request](#submitting-a-pull-request) 1. [Submitting a pull request](#submitting-a-pull-request)
1. [Going beyond the first issue](#beyond-the-first-issue) 1. [Going beyond the first issue](#beyond-the-first-issue)
@@ -304,7 +304,7 @@ Well-posed questions will generally get a response within 1-2 business days.
There is no need to @-mention anyone when you ask a question, as maintainers There is no need to @-mention anyone when you ask a question, as maintainers
keep a close eye on all the ongoing discussions. keep a close eye on all the ongoing discussions.
## What makes a great Zulip contributor? ## Best practices
As you're working on your first code contribution, here are some best practices As you're working on your first code contribution, here are some best practices
to keep in mind. to keep in mind.

3
docs/contributing/asking-great-questions.md
View File

@@ -43,9 +43,6 @@ When your question is answered, follow through on the advice you receive, and (w
appropriate) summarize the resolution of your problem so that others can learn appropriate) summarize the resolution of your problem so that others can learn
from your experience. from your experience.
You can find additional helpful tips in our guide to [what makes a great Zulip
contributor](contributing.md#what-makes-a-great-zulip-contributor).
## Follow the community guidelines ## Follow the community guidelines
As always, be sure to follow the [Zulip community As always, be sure to follow the [Zulip community

4
docs/outreach/apply.md
View File

@@ -104,8 +104,8 @@ As you are getting started on your first pull request:
review. Catching mistakes yourself will help your PRs be merged faster, and review. Catching mistakes yourself will help your PRs be merged faster, and
folks will appreciate the quality and professionalism of your work. folks will appreciate the quality and professionalism of your work.
Our documentation on [what makes a great Zulip Our documentation on [how to be a successful
contributor](../contributing/contributing.md#what-makes-a-great-zulip-contributor) contributor](../contributing/contributing.md#how-to-be-a-successful-contributor)
offers some additional advice. offers some additional advice.
## Putting together your application ## Putting together your application