Period between 2023-07-15 and 2023-08-15 inclusive
- These reports: https://github.com/rphair/cip-editing
- GitHub activity overview: https://github.com/rphair
- Cardano Forum overview: https://forum.cardano.org/u/COSDpool
- Discord invite to CIP Editors Meetings: https://discord.gg/kyaTyzkBqd
CIP pull requests @rphair involved in, by last update time = 42 in this period
CIP issues @rphair involved in, by last update time = 4 in this period
Cardano Forum CIP topics @COSDpool posted in since beginning of period = 1 addressed in this period
Open pull requests (https://github.com/cardano-foundation/CIPs/pulls) = 63 (about same as last month)
Open issues (https://github.com/cardano-foundation/CIPs/issues) = 35 (increased due to governance feedback through IOG)
Still had 2 meetings this month despite workshops & individual editor's unavailability.
- Meeting 2023-07-18 postponed due to time off of other CIP editors after Edinburgh workshops last week.
- Then postponed again on 2023-07-25 because not having confirmation any more than Ryan and I would be there (generally we've done all our reviews on GitHub already & still need review and consensus from other editors).
On Matrix I answered a question about regularity of the meetings and how advocates & observers could be more assured of the schedule in advance. Excerpt of that message, with our resolution going forward:
- We had a convenor from the CF that was handling meeting agendas & scheduling, but recently Ryan from IOG and I have been doing most of this ourselves. My hope is that editors themselves creating the meeting schedule & agenda items will allow the meetings always to proceed without any dependence on centralised administration.
- (in fact this proved to be true for the rest of the month)
NOTE to Catalyst administrators: In the next & future monthly cycles I will be keeping a new monthly report format outline which will shorten the reports, make them easier to write and read, and avoid duplication between GitHub work and our group review at meetings. From now I'll be recording each action taken only once in one of these 5 headings to include in each report:
- Qualitative progress (hand written summaries)
- Community discussions (with social links)
- Work on pull requests (by each PR number)
- Work on issues ([if any] by each issue number)
- Meetings held (agenda links & notes not already made in PRs above)
Continuing language standardisation (in this case, best effort old proposal CIP-50) (cardano-foundation/CIPs#582)
- Agreement at CIP meeting to date translated documents as posted in PR branches to identify them uniquely.
- Robert will update the specification for CIP-0001 as agreed at CIP meeting.
Major rewrite of CIP-0013 (cardano-foundation/CIPs#559) ... enabling new "proof of onboarding" protocol to be the first developer-defined extension to this scheme. Reviewed over last month & merged at 01 August meeting... and is already being used to consider other Cardano URI forms.
New standard for draft review... instead of internal comments (seen by author only, or people reading GitHub source), use tick-boxes to call attention to unanswered questions inline, rather than hiding them.
- Case in point, "Governance Metadata standards" highlighted on the Cardano Forum for open review this month, with a test of this idea (cardano-foundation/CIPs#556 (review))
CIP versioning: finally we have a proper framework to make immediate changes AND get community / developer feedback about what they want:
- Closed issue for long timer versioning discussion & moved onto practical changes to CIP-1 (cardano-foundation/CIPs#520 (comment))
- Particular drafts & edits for new versioning requirements for CIPs; my review & some more detailed language if needed (cardano-foundation/CIPs#563 (review))
- Preliminary (private) review of CIP versioning & categorisation CPS from Adam Dean who has tendered himself as a CIP editor (https://github.com/Crypto2099/CIPs/tree/versionioning-cps/CPS-XXXX)
- Agreeing to keep discussion of "alternative" versioning schemes & requirements open in the long term: the issue "Versioning alternatives" (cardano-foundation/CIPs#520 (comment))
- Potentially adding a "versioning update" to our planned remediation process for ALL old CIPs (cardano-foundation/CIPs#563 (comment))
New token standard for royalties; I did a detailed review... regarding support for different token types, how to separate them, and how to version the CIP68 protocol to indicate support for them... ultimately deciding that new token types will need separate CIPs beyond what's defined in CIP68 through the 444 token type:
Helped clean up very old proposal for web-based interprocess communication, mainly stalled since Dec 2022:
NFT standards cleanup (CIP-0068 "image types") - documented versioning issue & discussion of whether to further clarify usage or remove it:
New standard for expanded NFTs, separating individual tokens from common presentation & functional elements. Reviewed to compare with other proposals still in the works or deprecated:
Meeting Merged long awaited "Authenticated Web3 HTTP requests" after multiple rounds of view.
CIP-0381 | Adapt to Plutus bindings merged from meeting agenda... followed up by other editors after meeting & I merged it:
Detailed review of new NFT clarification about use of images, with possible new version about which to coordinate with developers (e.g. pool.pm)
AGENDA (https://hackmd.io/@cip-editors/71)
CIP-0030 | Stipulate namespaced extension endpoints (cardano-foundation/CIPs#577) - handled between author Ryan and Matthias.
CIP-0050 | Translations: fix Spanish metadata, remove Chinese (cardano-foundation/CIPs#582)
- Only item worth discussing: How much maintenance should we put into these "one-off", gratis, probably unmaintained translations?
- That turned out not to be the issue, but rather that we should use a date when a commit hash isn't available for translations, i.e. when the source for the translation hadn't already been (and in CIP 50's case, never will be) a merged document in the repository.
CIP-???? | Royalty Datum Metadata Standard (cardano-foundation/CIPs#551)
- Confirmed recently promosed co-editor will update CIP-0068 as agreed to do at las biweekly meeting.
- Also relates to stalled PR#523 because CIP-0068 should include process for making changes to CIP-0067. If only required & admissible for new token types, the "Ada SubHandle" request should be dropped... this item is still pending.
- Reminded author after meeting he also still needs a Path to Active based on expectaions of coordination with NFT businesses especially those processing royalties (cardano-foundation/CIPs#551 (comment))
CIP-1694 | Semantic changes after the Edinburgh workshop (cardano-foundation/CIPs#576) - handled between author Ryan and Matthias.
CIP-0093 | Update cross-CIP links to absolute paths (cardano-foundation/CIPs#565)
- I made a compatibility error with this one & have submitted it with required ./ prefix on CIP document pathnames for re-review (cardano-foundation/CIPs#565 (comment))
Items very quickly merged:
- CIP-0068 | Improve image types and URI descriptions (cardano-foundation/CIPs#562)
- CIP-0030 | A few small fixes](cardano-foundation/CIPs#570)
- CIP-0050 | Fix relative links](cardano-foundation/CIPs#574)
- Fix or rationalise Adrestia links](cardano-foundation/CIPs#575)
Postponed in 2 weekly jumps from 18 July (I was in attendance without any other editors) and then 25 July due to continued absences.
AGENDA (https://hackmd.io/@cip-editors/70)
CIP-???? | Distributed Artifact Tokens Metadata Standard (cardano-foundation/CIPs#530) from "Wout"
- My review above was discussed a meeting, and we agreed to assign it as candidate with a number.
CIP-???? | Proof of Onboarding (cardano-foundation/CIPs#546)
- From Adam Dean recently promoted at co-editor.
- I have updated CIP-0013 to make it compatible with this new addition to the URI scheme.
- Also suggested it could be generalised to link to dApps in general.. I countered that this would require a longer URI string to generalise more functions; and therefore should be kept as-is.
- Agreed to promote to candidate with a number, which I did the next day.
CIP-0068 Update | Add Royalty Support (cardano-foundation/CIPs#551) - Sam Delaney
- Author responsive on GitHub & review progressing well there; I invited him to Discord and the meeting.
- Challenging review by Adam Dean (at a higher level than my own experience) - needs addressing.
- Feedback to fork into separate CIP (outside of CIP-0068) was followed before end of this month.
- Will be ready to promote to candidate as soon as author provides Path to Active, as requested after meeting # 71.
CIP-???? | Governance Metadata (cardano-foundation/CIPs#556)
- Excellent discussion & assigned CIP number in my updates after the meeting.
CIP-0013 | Generalise for further protocols (cardano-foundation/CIPs#559)
- As I already posted, suggestions to revise existing protocols should be dismissed.
- "Onboarding" (
//claim
) depends upon this being accepted. - Also CIP-0045 might use the generalised URI standard (e.g. //connect)
- Merged at meeting.
CIP-0068 | Improve image types and URI descriptions (cardano-foundation/CIPs#562) - Smaug
- Preliminary review, leading to be merged after Meeting # 71.
CIP-0045? | Decentralized WebRTC dApp-Wallet Communication (cardano-foundation/CIPs#395) - Fabian Bormann
- I suggested potential inclusion of CIP-0013 URIs, so not ready to move along yet (author indicated he might change it accordingly).
- I asked for clarification if we wants to do that (we're ready to move this ahead if not): (cardano-foundation/CIPs#395 (comment))... still pending at the end of this monthly report cycle.
CIP-0095? | Cardano dApp-Wallet Web Bridge Governance Extension (cardano-foundation/CIPs#509) - still in progress led by Ryan & all documented on GitHub.
CIP-0025 | Restrict to minting (positive amounts) (cardano-foundation/CIPs#527) - simple merge.
CIP-0050? | Pledge Leverage-Based Staking Rewards (cardano-foundation/CIPs#242) - merged.
- Author no longer involved... I'll take over (or coordinate) maintenance (Matthias did a comprehensive update it looks like?)
- So far I've been handling metadata & translations in this monthly cycle & now it stands as the most rigorously reviewed candidate out of all the RSS proposals.