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
Timeslot: 14:15-15:00
Convener: N/A
In attendance: (comment if desired)
Minutes:
Open question: when should you submit something to a CAIP process, and if there's an explicit place where CAIP doesn't want things, that would be helpful.
-- Good example, we made namespaces to prevent CAIP spam.
Problem: we have blockchain namespaces but now need to support things like gpg?
-- We are just the fertile ground at CASA, people can put seeds in but need to make sure seeds are watered. We would love to be extremely inclusive but also we have limited resourcing.
We had the doing-first, and now need to govern.
Who is funding this? (ongoing question)
-- The main groups that are pushing this forward. As part of this, we're all contributing organizing energy.
How do we determine who can use the CASA logo? (ongoing question)
What defines the border of this type of organization versus some headless brand? (ongoing question) -- Could be the rule, if you want to use the logo, you need to merge yourself in as an organization. We would need more reviewers, maybe two reviewers - rough consensus.
We need IPR for CASA (ongoing question) - include in the GitHub form [Boris to add context]
How do we establish a process for CASA (participation / contributing) (ongoing question)
-- Create a basic listserv for CASA
Note: everyone should not be involved in the CAIP review process
-- Need a number of implementers to be able to be the reviewers on something like this
-- Question: should things be merged if they follow a structure or should there be a barrier (no)
-- Possibility: use 2-3 organizations to be the signal mechanism to get something over the first barrier
-- Can't call something a standard too soon
-- Possibility: use additional stages for nuance of where a CAIP is in the process
Next steps:
Membership process, PR your organization (done)
Funding - voluntary for now until a future date (done)
Determining usage of the CASA logo for things (open question - member organizations)
IPR for CASA (open question - important - Boris - GitHub)
CAIP review process (structuring - automating some things @ligi )
Reach out to L1s to get involved (ongoing)
The text was updated successfully, but these errors were encountered:
obstropolos
changed the title
CASA Governance & CAIP Process
Workshop: CASA Governance & CAIP Process
Apr 25, 2022
I'd like "two reviewers - rough consensus" on all uses of the CASA logo; I'd prefer no event at a conference be called a CASA event unless someone who's gotten a PR merged is there to MC/rep and the above.
Timeslot: 14:15-15:00
Convener: N/A
In attendance: (comment if desired)
Minutes:
-- Good example, we made namespaces to prevent CAIP spam.
-- We are just the fertile ground at CASA, people can put seeds in but need to make sure seeds are watered. We would love to be extremely inclusive but also we have limited resourcing.
-- The main groups that are pushing this forward. As part of this, we're all contributing organizing energy.
-- Could be the rule, if you want to use the logo, you need to merge yourself in as an organization. We would need more reviewers, maybe two reviewers - rough consensus.
-- Create a basic listserv for CASA
-- Need a number of implementers to be able to be the reviewers on something like this
-- Question: should things be merged if they follow a structure or should there be a barrier (no)
-- Possibility: use 2-3 organizations to be the signal mechanism to get something over the first barrier
-- Can't call something a standard too soon
-- Possibility: use additional stages for nuance of where a CAIP is in the process
Next steps:
The text was updated successfully, but these errors were encountered: