On 2022-12-31 at 18:11:17, Filip Lipien wrote: > There are more than one million questions on Stackoverflow related to the usage of Git. > This is not normal. > > Git is in its current state not a tool that's made for humans. There are also many questions related to Windows and Linux. It is unsurprising that software that is flexible is also very complicated and that many people may have questions about how it works or the best way to work with it. Git is also extremely portable and popular and as such there are many people who use it or want to use it, and therefore people asking many questions. As I mentioned above, many people have questions about the best way to accomplish a task on Linux, which is also very popular. We should not force Linus Torvalds to step down because Linux is complex or because people have many questions about it because it may differ from other software they've used. > It's realistic to assume, that millions of working hours were wasted due to his ignorance of developer experience. > The financial damage goes into the billions. Do I think Git could benefit from improved developer experience? Certainly. I think there would be substantial value in doing that, and such topics have been discussed at contributor summits in the past. I was left with the impression that most contributors would like to see this kind of work done. However, I think you misunderstand how Junio acts as the maintainer here. This is not a corporation where Junio tells people what to do and how to do it. Instead, this is an open-source project, and it's my impression that Junio spends most of his time shepherding other people's patches and making sure that the project and contributions are in a good state. He sends relatively few patches himself, and while he might make a suggestion on what he'd like to see out of a series or project, he doesn't really tell people what to do because people don't have to do what he says. As a result, it's not really fair to blame him for a poor developer experience. If that's valuable to someone, then someone will send patches to work on it, and I'm confident that Junio would accept those once they were suitable for merging. If nobody has sent such patches, then the presumption is that nobody is interested in doing the work for that at this point, and Junio isn't going to be able to just tell people to work on it, since people work on what they want or what their employers want (if they're working on Git in their professional capacity). In my role as a contributor, I've sent and reviewed patches that correspond to my areas of interests and expertise. While I think a better developer experience would be valuable, I lack the experience to contribute meaningfully in this regard, and as a consequence, I've sent no patches here. I welcome contributions from others in this area who are more familiar with the work that needs to be done. > I hereby request the removal of Junio C Hamano 濱野純 as the Git Maintainer. I think, given my explanation above, that this is completely unwarranted. The maintainer of this project has no authority over participants to force them to address developer experience here. While I don't always agree with him on everything, I think Junio is doing a fine job as maintainer, and assuming things stay as they are, I would be happy with him remaining as maintainer for the indefinite future. -- brian m. carlson (he/him or they/them) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
