Is it possible to return to development with traditional P5P mailing lists?
Is it possible to return to development with traditional P5P mailing lists?
I still think the traditional method is suitable for advancing Perl development.
why?
We're used to it, and Perl development has been done that way.
We tend to think of it as a poor method, but it's actually a good one.
The first is that it will be developed with backward compatibility in mind.
The second is that we will not proceed unless there is a lot of consensus on the important points.
Some people say that Perl development can't proceed because of opposition.
I think there is no need to proceed with development with a lot of opposition.
I think it's important to find a way that as many people as possible can agree.
The culture of being able to decide everything because we have a majority is not good.
Make everything public and discuss about important decisions.
Small decisions are made by good P5P leaders.
On the other hand, big decisions will be disclosed and discussed to all users.
If the opposite happens, it's a normal reaction.
Is it possible to adjust features and modifications to the point where an agreement can be reached?
Is it possible to return to development with traditional P5P mailing lists?
What problem should moving to a mailing list solve? The mailing list was public, anyway, so apart from security issues, there was no "secret room" for the elite to discuss stuff before disclosing it. GitHub just makes participation easier for most people, but it doesn't mean anyone can get their proposals accepted or merged.
This is a comparison with the Perl committee, which is held by a small number of people.
It's a suggestion that p5p can go back to the mailing list conversation for big decisions.
I believe that big decisions should always be publicly and carefully discussed, even if some people disagree.
We can look for suggestions that are better for both sides.
If we can't find better way, the decision is something wrong.