First draft volunteer newsletter

[nabramow]

Please leave your feedback, suggest changes, and share any shoutouts I missed as I wasn't here most of the year and don't want to leave anyone out!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
couchers	✅ Ready (Inspect)	Visit Preview	Jan 8, 2025 5:48pm

[nabramow]

@spreeni I know you did the user survey and I'd love to include that here I just didn't know how to describe it so if you want to add a blip or send me a ticket that describes it please do!

[nabramow]

@Krishnag09 Don't want to leave you out! I think you did a lot before I started and I don't always get your updates in the meeting so send me a blurb of what you've done or the tickets you worked on and I'll add it!

[nabramow]

Also considering maybe a welcome to our new volunteers section and tagging everyone who has merged something in the last months, but trying to decide the boundary there is tricky haha.

[spreeni]

@spreeni I know you did the user survey and I'd love to include that here I just didn't know how to describe it so if you want to add a blip or send me a ticket that describes it please do!

Couchers 2024 User Survey
We conducted a survey among all Couchers.org users to gain an insight into the main issues and priorities of our users. Improvements to the map search and filtering of inactive/incomplete profiles were the most requested feautures in the survey.

[aapeliv]

As I briefly mentioned on the weekly call, I think trying to shape this to be more actionable would be good. We should reduce the hurdle to contribute as much as possible. So would be good to add a call to action with clear instructions: "pop back in to slack", "join our weekly meeting at [time] at [location]", etc. And where possible good to add links to github issues/PRs and/or define clearly the task and basically make it "go here and start on this" without any intervention from us.

[nabramow]

As I briefly mentioned on the weekly call, I think trying to shape this to be more actionable would be good. We should reduce the hurdle to contribute as much as possible. So would be good to add a call to action with clear instructions: "pop back in to slack", "join our weekly meeting at [time] at [location]", etc. And where possible good to add links to github issues/PRs and/or define clearly the task and basically make it "go here and start on this" without any intervention from us.

Okay @aapeliv I added a "How to get involved" section, added a table of contents and anchor links so it's easier to click around, linked the "how to get involved" after the help wanted sections, and made the engineering help wanted section more ticket focused.

Let me know what you think. If you want more edits let me know more specifically what you're thinking.

[Super-Programmer-Navi]

Looks good to me, very upbeat!