Replies: 1 comment
-
#2956 was created to reach more or less the same on issue-level. 😉 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In these times it seems to me that the number of active users in the community who contribute issues/discussions and code with pr's/plugins.
However, we are still under the judgment of just one person who decides what goes in and what doesn't go in.
There are many questions for just one person to look at and it may happen that there are pr's like 1897 that motivated this discussion, or like pr which adds a 2018 plugin that remains untouched by the person responsible even when called for an opinion. There are plugins that cannot be used because they depend on a new implementation, such as the nav and search plugins.
I believe that these ignored pr's will only make the people who made them build the micro from the branch with this functionality/improvement.
I'm not going to individualize the issue and say that the solution is for each person to build and run their computer with a different code than others, update their pr with the master branch in the hope of one day being accepted and merged (I'm not criticizing this, that's not the point).
The issue I'm trying to address here is that this can no longer be left to just one person.
There must be people who want to join to help the project grow, these people are responding and creating issues, reviewing and creating pr's every day.
If there is already someone who does this besides the creator, where is the credit to them? where is their title? "This person responds to me in the issue, is he a user or a maintainer?"
My suggestion is:
I want to make it clear that my objective is not to be able to approve my own pr's.
The objective of this discussion is to highlight the problem of maintaining the community because, for me, these attitudes only weaken it.
Seeing plugins ignored by the official plugin-channel made me create a fork of it to list these plugins.
Will the community have to create a fork of the editor too so that it can be heard?
Beta Was this translation helpful? Give feedback.
All reactions