Conversation
| - owner: cofson | ||
| - status: not started | ||
| - start-date: 2026/04/01 | ||
| - end-date: 2026/07/31 |
There was a problem hiding this comment.
Fixed in all the commitments.
|
|
||
| ### New RFCs | ||
|
|
||
| - fully qualified name: `ift-ts:rfc:anoncomms:2026q2-rfc-iteration:new-rfcs` |
There was a problem hiding this comment.
new-rfcs doesn't seem so accurate since we will mostly review/improve on the LIPs proposed by projects (in the form of a PR)
There was a problem hiding this comment.
Also I would replace rfc with lip
We can keep only the team name rfc
There was a problem hiding this comment.
new-rfcs doesn't seem so accurate since we will mostly review/improve on the LIPs proposed by projects (in the form of a PR)
Actuallly I see this task ift-ts:rfc:ift:2026q2-lip-index-maintenance:review-pipeline
But then what exactly are we expected to do here for the new-rfc track?
There was a problem hiding this comment.
The idea behind is to help support with the creation of new RFCs - not really write them, but through use of tools and the team support (i.e. adversarial spec) create new specs. Hence why I left it here as a (potential) pipeline.
There was a problem hiding this comment.
If there is a better name other than new-lips - I will change it - maybe new-lips-support?
fbarbu15
changed the title
|
|
||
| #### Description | ||
|
|
||
| Maintain lip.logos.co quality through routine review and cleanup tasks |
There was a problem hiding this comment.
I think you can fix this if you put at Deliverables:
- PRs
2 participants
No description provided.