@@ -203,6 +203,45 @@ should do to help ensure that your pull request is accepted.
203203
204204#. Proper :ref: `documentation <documenting >` additions/changes should be included.
205205
206+ Coordinating work on an issue
207+ -----------------------------
208+
209+ Before starting work on an issue, contributors should coordinate with
210+ others to avoid duplicating efforts and to make collaboration easier.
211+
212+ #. **Check for existing contributions. ** Before working on an issue,
213+ review its discussion and any linked pull requests. If another
214+ contributor is already working on a solution, consider offering
215+ assistance or discussing possible collaboration instead of
216+ submitting a competing pull request.
217+
218+ #. **Communicate your intentions. ** Contributors are encouraged to
219+ express their interest in an issue and describe their planned
220+ approach. Providing an approximate timeframe can help others
221+ understand when to expect progress, although these estimates
222+ should not be treated as strict deadlines.
223+
224+ #. **Share progress and ask for help. ** If difficulties arise or
225+ progress is delayed, contributors should communicate any blockers
226+ and seek assistance when appropriate. Opening a draft pull
227+ request can help others review work in progress and provide
228+ early feedback.
229+
230+ #. **Respect ongoing work. ** Contributors should avoid taking over
231+ an issue while someone else is actively working on it. If progress
232+ has stopped, discuss the situation with the original contributor
233+ and maintainers before proceeding.
234+
235+ #. **Allow others to continue unfinished work. ** Contributors who
236+ are unable to complete their work are encouraged to communicate
237+ this in the issue. This gives other interested contributors an
238+ opportunity to continue the effort.
239+
240+ #. **Coordinate before taking over inactive issues. ** If an issue
241+ has remained inactive beyond an estimated timeframe, contributors
242+ should discuss its status before starting a new solution. An
243+ expired estimate does not automatically transfer responsibility.
244+
206245.. _news-entry :
207246.. _what-s-new-and-news-entries :
208247
0 commit comments