# Idea: Hanami community organization on Github

**URL:** <https://discourse.hanakai.org/t/idea-hanami-community-organization-on-github/483>\
**Category:** proposals\
**Created:** [January 17, 2019, 9:39am UTC](https://discourse.hanakai.org/t/idea-hanami-community-organization-on-github/483 "2019-01-17T09:39:40Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![katafrakt](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.hanakai.org/katafrakt/32/735_2.png) [@katafrakt](https://discourse.hanakai.org/u/katafrakt)\
**Post date:** [March 20, 2019, 8:40am UTC](https://discourse.hanakai.org/t/idea-hanami-community-organization-on-github/483/7 "2019-03-20T08:40:30Z")

</div>

Coming back to old topic 😉 Yes, ruby-toolbox gives a nice overview of available gems (so does awesome-hanami). However it does not solve ownership issues.

I see a lot of [topics like this](https://github.com/aemadrid/orientdb-jruby/issues/19) on Github - someone loses interest in maintaining the repo, because he no longer uses the technology. In case the project brings a value and there is an interest in maintaining it, projects in Hanami community org could be handed over to someone else or at least minimal maintenance could be done for them.

---

_[View the full topic](https://discourse.hanakai.org/t/idea-hanami-community-organization-on-github/483)._