community
community copied to clipboard
fluttercommunity
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.
From what I gather, 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?
Let's get back on this after FlutterVIkings please, I am so engaged at the moment.
On Fri, Aug 5, 2022 at 3:48 PM Vincent @.***> wrote:
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 #99 https://github.com/fluttercommunity/community/issues/99 was created to discuss this more specifically.
Maybe @jeroen-meijer https://github.com/jeroen-meijer @slightfoot https://github.com/slightfoot and @mhadaily https://github.com/mhadaily would like to comment?
— Reply to this email directly, view it on GitHub https://github.com/fluttercommunity/community/issues/106, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKDTC5DSO4Z4GZ7L53U36DVXULSLANCNFSM55WEWAKQ . You are receiving this because you were mentioned.Message ID: @.***>
Hi Vincent. We have been in discussions to resolve this. But its all having to wait atm until at least mid next month after Flutter Vikings. Once we have something to report i'll update this discussion.
