As I was mentioning to @baldemo.to, I think Attestations is also a good way to start talking about membership and whether that is just a special case of that or (more likely) its own separate mechanism.
We haven’t formally discussed this, but “throwing out there a personal thought” this makes sense to me as an initial bundle of real value for communities:
- Attestations: What should communities use them for? What use cases where they’re tempting actually need different handling?
- Membership primitives: How is membership (likely its own case) represented? How is it assigned? What primitives are needed?
- The “Middle Entity”: How is community data (starting with the use cases above) written and accessed in practice?
(edit: to clarify, I don’t mean to expand the original scope. Just pointing out that “membership primitives” naturally slot with the topic, and will likely begin to take form alongside it.)
I’m happy to do specing work for Attestations, as I’ve already done some. The intention here is mostly to understand how they relate to communities—and obviously making sure that my initial spec does work for such an important use case.
As a more general question, I would love to hear people’s thoughts on what they’d like to get agreement on as a (working) group in the longer term. I’m going to make a different thread though, so this can stay focused on this specific discussion.