From 8648e2fc4c715f8d32fbf967c048fad006fb67e0 Mon Sep 17 00:00:00 2001 From: Viacheslav Turovskyi Date: Wed, 4 Dec 2024 11:31:20 +0200 Subject: [PATCH] docs: add Bounty Program Rules --- BOUNTY_PROGRAM.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/BOUNTY_PROGRAM.md b/BOUNTY_PROGRAM.md index a8afb0aa7..983a54f1e 100644 --- a/BOUNTY_PROGRAM.md +++ b/BOUNTY_PROGRAM.md @@ -143,7 +143,7 @@ In case the Bounty Program Participant has not provided critical fixes during th ## Extension Of Bounty Issue's Timeline -In case a response critical for the technical resolution of the Bounty Issue is delayed in [GitHub](https://github.com) and/or [Slack](https://asyncapi.slack.com) for a period of more than three consecutive working days, all remaining target dates of the Bounty Issue's Timeline are increased by one calendar week per each of the three consecutive working days the critically important response was delayed, plus one calendar week in case of two and more periods of the three consecutive working days. 'Plus one calendar week' period is required because after the critically important response that was delayed for a significant amount of time has been given, the Bounty Program Participant would have to spend time getting back to the insides of the issue and nearly unfamiliar at that time their own code. 'Working days' are weekdays, from Monday through Friday. Friday and Monday may be considered consecutive in the sequences 'Thursday-Friday-Monday' and 'Friday-Monday-Tuesday.' +In case a response critical for the technical resolution of the Bounty Issue is delayed in [GitHub](https://github.com) and/or [Slack](https://asyncapi.slack.com) for a period of more than three consecutive working days, all remaining target dates of the Bounty Issue's Timeline are increased by one calendar week per each of the three consecutive working days the critically important response was delayed, plus one calendar week in case of three and more periods of the three consecutive working days. 'Plus one calendar week' period is required because after the critically important response that was delayed for a significant amount of time has been given, the Bounty Program Participant would have to spend time getting back to the insides of the issue and nearly unfamiliar at that time their own code. 'Working days' are weekdays, from Monday through Friday. Friday and Monday may be considered consecutive in the sequences 'Thursday-Friday-Monday' and 'Friday-Monday-Tuesday.' In case of unpredicted [force majeure](https://iccwbo.org/wp-content/uploads/sites/3/2020/03/icc-forcemajeure-hardship-clauses-march2020.pdf) and/or circumstances that could not be foreseen and/or that are beyond the control of both the Bounty Program Participant and the AsyncAPI Maintainer, the Bounty Issue Timeline can be increased by a fixed or indefinite amount of time, with a fair explanation in the Bounty Issue's or Pull Request's comments.