📝 v6.0 will go into effect on the 15th of October
We start with a 16-day evaluation, prepare the scores for the new format, and then shift to the new timeframe.
From the 11th of November onward, we will be in the bi-weekly evaluation schedule for contributions. In combination with the infrastructure Evaluations, this means we will have a score update every friday.
| Submission cut-off |
15/10/2024 EOD Tuesday 23:59:59 UTC |
| Appeals Begin |
29/10/2024 EOD Tuesday 2024 12:00:00 UTC |
| Appeals End |
31/10/2024 EOD Thursday 2024 23:59:59 UTC |
| Report publication |
01/11/2024 Friday 18:00:00 UTC |
📆 Upcoming Tech Reviews
| Eval |
Snapshot |
Period |
Voting |
| v5.10T3 |
20/10/2024 EOD |
07/10/2024 - 20/10/2024 |
23/10/2024 |
| v6T1 |
05/11/2024 EOD |
21/10/2024 - 05/11/2024 |
08/11/2024 |
| v6T2 |
19/11/2024 EOD |
06/11/2024 - 19/11/2024 |
22/11/2024 |
Green text represents additions / modifications.
Re-phrased for clarity.
Blue text highlights passages that have been moved.
Red text with strikethrough represents removals.
Orange text represents proposed changes that have not reached consensus yet.
Major Changes in v6.0
Removed HaaS from the guidelines.
Adjusted minimum and penalty SLRs for Round and Block availability.
Key Changes:
- Bi-weekly Evaluations:
- Guilds will be able to submit individual contributions for evaluation on an ongoing basis.
The OIG will roll the submissions of two weeks into one bi-weekly evaluation.
- Technical evaluations will remain on a two-week schedule, alternating with the review of contributions.
- This change aims to allow the OIG to spend more time on each contribution and communicate more ****with guilds throughout the review process, giving direct feedback ****and increasing transparency.
- Submission of Reports:
- Report submission remains optional, not mandatory. Guilds are encouraged to submit reports only when their products or contributions undergo new updates or changes.
- Guilds may submit a report at any time; we encourage guilds to submit reports on a per-contribution basis within the established ‘latest.md’ through Git Hub.
- A 6-week evaluation cycle will remain in place as a shell structure. This means that products will be rolled into every third evaluation if no update is submitted in between. This will be captured by a new timestamp on every contribution, displaying when we will re-evaluate a specific contribution at the latest If no update is provided.
- Decay
- In addition to the current ‘Decay Rate’ and ‘Decay Target’, each contribution will receive a timestamp determining when the decay rate will be applied for the first time if no significant updates are provided or related requirements are not met.
- ‘Decay Rate’, ‘Decay Target’, and the date will be revised with every evaluation.