|
| 1 | +--- |
| 2 | +title: LIP Index Maintenance |
| 3 | +tags: |
| 4 | + - 2026q2 |
| 5 | + - rfc |
| 6 | + - ift |
| 7 | +draft: false |
| 8 | +description: Continuous maintenance of lip-index and related publication workflows. |
| 9 | +--- |
| 10 | + |
| 11 | +`ift-ts:rfc:ift:2026q2-lip-index-maintenance` |
| 12 | + |
| 13 | +## Description |
| 14 | + |
| 15 | +This commitment covers recurring maintenance for the LIP ecosystem: |
| 16 | +reviewing updates, keeping references consistent, and handling routine quality improvements. |
| 17 | + |
| 18 | +## Task List |
| 19 | + |
| 20 | +### Maintenance |
| 21 | + |
| 22 | +* fully qualified name: `ift-ts:rfc:ift:2026q2-lip-index-maintenance:maintenance` |
| 23 | +* owner: filip |
| 24 | +* status: not started |
| 25 | +* start-date: 2026/04/01 |
| 26 | +* end-date: 2026/06/30 |
| 27 | + |
| 28 | +#### Description |
| 29 | + |
| 30 | +Maintain lip.logos.co quality through routine review and cleanup tasks |
| 31 | +(such as new gitbook addons) |
| 32 | +including fixes to |
| 33 | +content consistency, metadata, and publication hygiene. |
| 34 | +This includes (and is not limited to) fixing any errors found, |
| 35 | +adding new rules and features to the website, |
| 36 | +as well as any potential improvements discussed by the team(s). |
| 37 | + |
| 38 | +#### Deliverables |
| 39 | + |
| 40 | +- Updates to the lip.logos.co |
| 41 | +- PRs |
| 42 | + |
| 43 | +### Review Pipeline |
| 44 | + |
| 45 | +- fully qualified name: `ift-ts:rfc:ift:2026q2-lip-index-maintenance:review-pipeline` |
| 46 | +- owner: cofson |
| 47 | +- status: not started |
| 48 | +- start-date: 2026/04/01 |
| 49 | +- end-date: 2026/06/30 |
| 50 | + |
| 51 | +#### Description |
| 52 | +This task revolves around |
| 53 | +the effort of reviews and support |
| 54 | +of all the teams that use the specifications, |
| 55 | +this includes (and not limited to) |
| 56 | +Blockchain, Storage, Anoncomms, ACZ. |
| 57 | + |
| 58 | +#### Deliverables |
| 59 | +- Reviews on existing written specifications, approvals |
| 60 | +and comments. |
| 61 | + |
| 62 | +### Adversarial Spec - IFT |
| 63 | + |
| 64 | +* fully qualified name: `ift-ts:rfc:ift:2026q2-lip-index-maintenance:adversarial-spec-ift` |
| 65 | +* owner: filip |
| 66 | +* status: not started |
| 67 | +* start-date: 2026/04/01 |
| 68 | +* end-date: 2026/06/30 |
| 69 | + |
| 70 | +#### Description |
| 71 | + |
| 72 | +Develop, educate the teams and support the creation |
| 73 | +of new specs based on https://github.com/vacp2p/adversarial-spec-ift |
| 74 | +while polishing the skill and engaging in relevant workshops in regards to it. |
| 75 | + |
| 76 | +#### Deliverables |
| 77 | + |
| 78 | +- New versions of adversarial spec. |
| 79 | + |
| 80 | +### COSS Update |
| 81 | + |
| 82 | +* fully qualified name: `ift-ts:rfc:ift:2026q2-lip-index-maintenance:coss-update` |
| 83 | +* owner: filip |
| 84 | +* status: not started |
| 85 | +* start-date: 2026/04/01 |
| 86 | +* end-date: 2026/05/01 |
| 87 | + |
| 88 | +#### Description |
| 89 | + |
| 90 | +Based on discussions from Lisbon, do updates of 1/COSS: |
| 91 | + |
| 92 | +- Make Track optional instead of mandatory (informational, core, etc.). |
| 93 | +- Introduce a new status: Approved |
| 94 | +meaning it has been verified by the internal dev team |
| 95 | +and is ready to be moved to the Index. |
| 96 | +- Introduce a new document type (in addition to RFC) - |
| 97 | +CFR (Change For Request): used to aggregate multiple LIPs |
| 98 | +and process their changes together. |
| 99 | +- Miscellaneous fields that are currently mandatory should become optional, |
| 100 | +at least temporarily. TBD |
| 101 | +- Introduce a new status: Verified |
| 102 | +when something has been implemented by a non-IFT entity. |
| 103 | + |
| 104 | +#### Deliverables |
| 105 | + |
| 106 | +- Updated 1/COSS |
| 107 | +- Any affected specs by these changes should be updated. |
| 108 | +Likely none. |
0 commit comments