Hey guys, happy new year. Launched the Ara, a social media layer on top of the open-source projects, that adds maintainer-led community building. Once its build, turns the open-source to the community-based project. Even though, I got early replies that's still UX needs lots of improvements, I would still encourage to try it, and your feedback will be really helpful. First, check out the youtube walkthrough Then, try it yourself on https://ara.foundation (better to use Dark Mode, Laptop Browser, mobile screen or light mode have some bugs). And Happy New Year!

Feedback on the video: • It uses quite a lot of terms the viewer has to grasp. • Not always clear which actions/concepts are internal to Ara vs. have a "reality" on GitHub... • Does Ara interface to GitHub Issues, or does it have its own? • In particular, "create a version" is that a Git tag or something? Or is it a new Ara concept? • And "release it" does it just mark it released on Ara or did something external happen (e.g. new GitHub release created)? I started from the video, and felt it has little to do with how I think about open-source "community". Is this monetization? Karma? Assigning issues is something I mainly saw on corporate repos; a maintainer != a manager... 😕 Only at the very end I started to get a glimpse of the goals. But then I read the web page — that clicked much better 👍 I don't feel I need it (or expect any funding) for my projects, but I can see how the "2 rules" resonate with things maintainers complain about.