You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Namespaces orga: Should each namespace be a folder, not a file? that would allow per-CAIP statuses and an auto-generating table of contents that looks like this:
CAIPS
2
10
19
eip155
F
D
D
polkadot
F
P
where
F = Final
D = Draft
P = PR open
_ = help wanted
Orga Topics (cont.)
free up old CAIPs - re-use rather than leave huge gaps?
stick to PR-based automatic numbering
shoud we remove attendees from the AMS page?
delete attendees.md file
filling more spots in the AMS event
open up rsvps not to require vouchers when?
consensus: April 2? DM-invites before then; invite EIP magicians list after that
CASA 10Mar Agenda
TO BE MERGED TODAY, LAST CALL
namespaces/eip155.md
Organization/non-GitHub Topics
where
Orga Topics (cont.)
Standing GitHub Agenda
CASA/
PRsnamespaces/
PRsCAIPs/
issuesCAIPs/
PRsThe text was updated successfully, but these errors were encountered: