-
Notifications
You must be signed in to change notification settings - Fork 13
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
Create a April update for wider HOT community #113
Comments
Initial thoughts for an outline:
|
Input from the Tech WG meeting:
|
This is great. Newsletters are probably the best way to reach a wider audience with all the key bullet points. It would be really helpful if this brought in more user testing to our tools that are currently in development, so that the feedback can be integrated into the process. Having the links to the tools, as well as where to provide feedback would be helpful! |
I've started a draft here: https://docs.google.com/document/d/1LGSTVo-1cX7Ae-bjiutfpgH59mgeoo8BIVSwhtP6VWQ/edit?usp=sharing. Will look to have this complete before the end of April. |
We posted the update but April turned into June: https://docs.google.com/document/d/11q6ZeugJ8X3Fs5BoSKqPA40fT8KWqor6K7-OszEqLGo/edit?usp=sharing. To keep this moving each month, we'll use the template document as notes in the biweekly meeting and then clean up at the end of the month. |
It would be great for HOT to circulate a monthly update from the tech side of things to the wider community. This would allow people outside of the Tech Working Group to know what's happening and what's coming up. We don't always do the best at circulating updates and this could help expose new projects or ways to get involved to new community members.
Let's use this to track an update for April. If you have an idea to contribute that you want to include, post here. We'll discuss more in the Tech Working Group meeting on April 3.
The text was updated successfully, but these errors were encountered: