Hi all, I am listing the tasks that Bram used to do for developing and maintaining Vim below (as far I can remember):
1. Developing fixes for Vim crash reports including the analysis of fuzzy test files. 2. Addressing reported security vulnerabilities including those reported in https://huntr.dev/repos/vim/vim. I think various Linux distribution maintainers report these issues directly to Bram. 3. Fixing Coverity warnings reported in https://scan.coverity.com/projects/vim 4. Fixing CI build breakages including ASAN errors. 5. Create patches based on pull requests from Vim contributors (including updating the patches to match the Vim coding style and perform minor refactoring). 6. Developing major new features (e.g. Vim9 script, virtual text, etc.) 7. Reproducing the reported issues and developing fixes for those issues. 8. Improving the test infrastructure. For example, he recently incorporated coding style checks and the support for syntax highlighting checks. 9. Incorporating the runtime file updates (e.g. syntax files, file types, etc.) 10. Updating the Vim documentation based on discussions and pull requests. 11. Maintaining the todo.txt file to track the roadmap for features and fixes. 12. Responding to questions and discussions in the Vim-dev mailing list. 13. Updating the vim.org website with news. 14. Preparing and making Vim releases (maybe once a year). Regards, Yegappan On Mon, Aug 7, 2023 at 7:53 AM Christian Brabandt <cbli...@256bit.org> wrote: > > Hi all, > thanks for all this. As Dominique mentioned, please send future > contributions (in the order of my preference): > - create a PR in the Vim github repo > - Send patches (or full files) to the vim-dev mailinglist > - continue sending the files to me (I'll handle it as Bram did) > > I appreciate all your help suggestions. > > Thanks, > Chris > -- -- 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 vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3DBPfZ3%2Bgi6NPrjPWdFxeM7pnCB94%3DCWrK5iP-ygsWa-Q%40mail.gmail.com.
