-
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
Role: Meeting Secretary #80
Comments
Hi, folx, On a call with Dan, Juliet, and others, I accidentally volunteered for this Issue before I even knew it was an open item. Happy to discuss performing the role pro bono while we figure for fit and final details. While new to the community, I'm a quick study with ample free time. It sounds like this might be a small, helpful win on the road to transparent governance. Thoughts welcome; otherwise, I will catch everyone on Discord. |
@BaiHuLaoShi Thank you for your interest! Notes are really helpful for those that watch the video later or prefer to read over watching the videos. To give you some back story on this:
Right now I am working through stacksgov/grants-program#30 to update the repositories, standard operating procedures, and bring everything back up to date. Some things that would be really helpful in order of priority:
As far as the bounty, this did not fit in directly with the beta grants program but I am open to any ideas, suggestions, or proposals to what would make it fair, as well as with any of the items listed above. The goal is to keep things simple, but to provide as much info for the public as possible! |
Agreed re: accessible, maintainable transparency for the public. No ideas yet, don't know what I don't know, definitely more as we go. The context kickstart is super helpful, thank you! The low hanging fruit is easy for me and others to grab. Good stuff to get the ball rolling and get folx familiar. |
The above was ambiguous on my reread. I will shoot for by the next Thursday Governance meeting:
|
Hi All, |
I've cleaned up all the formatting of the notes from meetings 14-32 (13, 15 and 18 are not yet transcribed). I have them in RTF format. The next step would be to compare them to the videos for clean up: clearing out the paragraph breaks due to pauses, correcting transcription errors, and generral clean up. If there is somewhere I should post in the in progress files, please let me know. |
@Brexton017 Absolutely awesome work. Thank you! |
@Brexton017 I appreciate your help with this!! I am happy to review any of the content and get it into the correct format to include in the repo. Are you on the Stacks Discord? If so, dm me there, my username is also |
Closing in favor of #181 |
Per #62, this was agreed upon as a good idea among the group, so both of the roles that were "bounty candidates" for the future are now separated into its own issue for further discussion of responsibilities and tracking.
Meeting Secretary
This would be a new role similar to what I have done in the past with notes, but breaks up the tasks so that they are only required during the meeting and directly after.
Given the amount of work listed below and the goal of creating a consistent experience, I think this position would be eligible for a small bounty. We can add rules for rotation or anything else necessary to keep it fair between all participants.
The text was updated successfully, but these errors were encountered: