Replies: 1 comment 1 reply
-
Definitely need to grant someone permission to merge/close duplicate issues. There are currently 281 open issues and 90% of them are either about JSON, or debug. Somehow need to convince people to search for existing issues/PRs and collaborate on those instead of opening new ones. What this project really needs is one of the Auto-GPT-GUI projects to become the repo for non-coders and simple users. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am truly grateful for the foundations that have been laid, but I think it would be super important if the maintainer let himself support additionally and provide people he trusts additional GitHub permissions (I'm not speaking about myself - but there are very capable people in the community). So that not everything weighs on his shoulders and the development can qualitatively and quantitatively pick up speed (I think the unlimited motivation/curiosity from plenty of people, including devs, is very obvious).
It can be negative for the project, if there are a ton PR's waiting and the problems they would solve pile up in the issue backlog. On the one hand, new releases often break a working version, on the other hand, atomic PRs come in faster than the maintainer himself can merge them with prepared pre-evaluated lists.
It's very important to me to say that I don't mean this disrespectfully, but the velocity in this area is too high for just one single person with limited time to handle. It would be a pity when getting rewarded with 25K+ stars on GH in less than 7 days isn't leveraged in a way, that a momentum can build up and glue an active community together.
Ultimately, of course, this is the decision of the maintainer, but from the outside it looks like that would be a good idea and is meant in a friendly way without any expectations.
Beta Was this translation helpful? Give feedback.
All reactions