Currently, cadCAD is in a shift from blockscience to the community. To get towards a fully community-owned cadCAD, this needs work on the core dev side, in infrastructure/admin tasks, as well as outreach and education to get more people involved.
🎉 Subtasks
This sheet lists all tasks. The next milestone is the release of the blockscience labs, a collaborative modelling environment, simplifying the process around getting started with and coding cadCAD.
From those tasks, I started working on:
[X] Read and watch all the stuff on cadCAD
[ ] Outreach/Education: Help with Token Engineering workshop
[X] Infra/Admin: Convert spreadsheet issues to public github issues
[ ] Infra/Admin: Help with bridging chats and Twitter from and to the cadCAD Discord chat #18 #19
🤼♂️ Reviewer
@ Jeff-Emmett
🔗 Work doc - inspirational links
We coordinate in the cadCAD channels for Infra/Admin and for Outreach
📋 Anything to add?
Currently, cadCAD is in a shift from blockscience to the community. To get towards a fully community-owned cadCAD, this needs work on the core dev side, in infrastructure/admin tasks, as well as outreach and education to get more people involved.
🎉 Subtasks
This sheet lists all tasks. The next milestone is the release of the blockscience labs, a collaborative modelling environment, simplifying the process around getting started with and coding cadCAD.
From those tasks, I started working on:
[X] Read and watch all the stuff on cadCAD [ ] Outreach/Education: Help with Token Engineering workshop [X] Infra/Admin: Convert spreadsheet issues to public github issues [ ] Infra/Admin: Help with bridging chats and Twitter from and to the cadCAD Discord chat #18 #19
🤼♂️ Reviewer @ Jeff-Emmett
🔗 Work doc - inspirational links We coordinate in the cadCAD channels for Infra/Admin and for Outreach
Copied from CS repo issue 231