Discussion: Repository maintenance and future plans

# Discussion: repository maintenance.

This issue has been made to discuss the maintenance of the `fluttercommunity/community` repository, and potentially also what the aim of the organisation still is as of mid 2022.

## Summary
Issues in this repository have generally speaking not been processed since the second half of 2020. Apart from a few exceptions, they have not been answered, and their statuses were changed only by those who created them.

While it isn't critical for package proposals (since packages can still live elsewhere), it becomes more problematic when dealing with packages already owned by the organisation: for example when [we need to add a new maintainer to a repository](https://github.com/fluttercommunity/community/issues/102).

[From what I gather](https://twitter.com/devangelslondon/status/1554589493583388673), the core founders of the organisations have now other responsibilities and cannot dedicate time to ensure that the repository is maintained.

What solution could we find to address this? Is it a matter of adding new maintainers? If we do so, should we also clarify what the scope of the packages owned by the organisation is? I see that https://github.com/fluttercommunity/community/issues/99 was created to discuss this more specifically.

Maybe @jeroen-meijer @slightfoot and @mhadaily would like to comment?