Felipe Contreras wrote:
> I didn't contact the maintainer, it should be responsibility of > him/her to be responsive to patches. The way Vim runtime file maintenance works is that you report any problems or possible improvements directly to the maintainer. If the maintainer does not respond we may look at other ways. > His address on the syntax file is wrong anyway. There are instructions how to fix that. But many people don't spot that, there are better ways to avoid spam these days. > He eventually replied, years later, not looking at my patches, and he > didn't reply to me so I never got that response. He said he didn't > read every mail in the mailing list (even though all he needed to do > is read the sh syntax mails), presumably implying that he wanted to be > CC'ed, but then he doesn't CC me, so the only way I could have read > his response is to be constantly checking the mailing list for two > years. That's very slow indeed. > And the comment I made was not about the content of the code, > certainly not about the content of the sh syntax file, it was about > the development **PROCESS**. > > The current content of the code is almost irrelevant, as the project > with the better development **process** will eventually have better > code. Every maintainer has the freedom to use his choice of process. Some have a github project where you can file an issue or pull request, some just use email. Enforcing a certain way of working will increase the bureden on maintainers, which for some people is already a bit much. > So my comment was true, it's just that you are not listening to what > I'm actually saying. > > And BTW it was a miracle I saw this mail, as I saw it from the web > interface. I'm a member of this group but I don't receive mail from > it. I guess there isn't a habit of replying to the person you are > actually replying. I'm actually CC'ing the sender (and some people don't like getting the message twice). > I'm not trying to be snarky, I'm just trying to to illuminate the fact > that my experience as a random patch contributor has been anything but > smooth. I contribute to many projects and rarely do I experience such > issues. Everbody here is volunteering and we'll have to live with slow responses and various ways of mainaining runtime files. -- hundred-and-one symptoms of being an internet addict: 177. You log off of your system because it's time to go to work. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201906142125.x5ELPBUB024907%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
