-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Town hall meeting or general public call #68
Comments
Great idea! 1 x per quarter sounds about right - my 0.2 cents |
Quarterly sounds good to me too. Blockstack PBC usually does quarterly town hall, we can try to make it staggered a bit from theirs.
|
Yes, this all sounds good! An open call could be marketed via newsletter mentioned etc. Granted they're all open, this would be different format. |
From #99:
|
In #118 it was discussed that this may fit better into the main Stacks Ecosystem / Town Hall calls with a representative from the group. Definitely still open to feedback. @paradigma-cl Phillip made the point that as the community takes over, it will be our responsibility to decide how we want to share this information with the general public. |
This could be brought in to the Stacks Ecosystem Calls at 10EST for the mid-month calls. If the governance committee wanted to give an update on the work going on, the next call would be on the Thursday the 21st of January. Thoughts? |
@HaroldDavis3 @jennymith suggested Dr. Ron Eglash as a speaker at our most recent governance group mtg on Jan 21, 2021. Harold is working with Dr. Eglash on his TRW project. More info: https://csdt.org/ |
We are starting by using the general Stacks townhalls as a place to represent governance, and can revisit this as a separate issue if needed. |
Per Phillip's recommendation on call 17 #61, we should add in a general public-facing call and invite a larger audience outside of the working group.
It could include a briefing of what's been done, some pointers to get people involved, and help advertise/market the resources the group has developed.
Open Questions:
The text was updated successfully, but these errors were encountered: