Ben, On So, 13 Aug 2023, Ben Fritz wrote:
> Thanks for the CC and I'm certainly very sad to have seen the news about Bram. > > And thank you Christian for taking on this leadership role. Yegappan, > Dominique, mattn, and zeertzjq: thanks to you guys too. It's comforting > to see Vim remains in good hands. We'll try our best. > You're right, I have gone mostly inactive on the project and it probably > makes sense to take me off the mailing list managers group. You don't > *need* to take me off it, but I will probably not become active enough > to be an effective moderator/list manager in the near-term. In the > longer term, if I do end up finding time to become more active, I work > in InfoSec so I might be able to contribute to the huntr.dev project. I > wasn't aware that existed! I'll reach out on that at some other time. Sounds good. It's always sad, to see some long-time contributors missing, so if you ever want to become more active, you are certainly welcomed back ;) > Something I don't see mentioned in this email is the scan.coverity.com > project for Vim at https://scan.coverity.com/projects/vim. It looks like > you and Dominique are currently the project admins there, do we need to > add a few more (probably everyone in the GitHub organization)? I wonder > if it is possible to set the organization as admin over there, since > there is a "login with GitHub" feature. Yeah, I did not mention this because I forgot. Anyhow, Dominique and me are also admins, so we should be good here. > I am still interested in maintaining the TOhtml plugin for which I am > the official maintainer, if Vim's development model continues to have > separate maintainers for the distributed plugins. However I will > understand if it is given over to someone more active (or if project > leadership wants a co-maintainer) as I have not been able to contribute > more than a couple bugfixes for the last few years. I have not sent any > unreleased updates to Bram. I haven't seen any complaints/issues for the TOhtml plugin, so I think we are good here, even so it may need some love to e.g. support popups or virtual text. Not sure if this would be easily addable to a plugin (or even makes sense). > If Vim development moves away from separate maintainers for the various > plugins, or if someone ends up taking over, I have been maintaining > TOhtml over at SourceForge where there is still free Mercurial hosting. > This project contains some automated testing (using Vim's own test > framework) which I have been slowly building with each feature addition > and bugfix, and should be part of however the script is maintained in > the future: https://sourceforge.net/projects/vim-tohtml/ > > If we continue with individual developers, how does the project want to > continue receiving updates? In the past, I would email a zip file > directly to Bram containing whole files. Sometimes I would CC the vim_dev > list. I believe this is how most plugin maintainers were contributing > updates. For now, is it best to just email whole files to vim_dev in the > same way? My apologies if this has already been addressed in another > thread. I didn't see anything while browsing through the list to check, > but as noted above I haven't been very active of late so I may have > missed something. I don't want to change the current runtime maintainership at all. I think it is fine. The only thing I am considering is to make bulk-updates easier, even so this adds a bit of burden to the individual runtime files maintainers. But I hope that is okay. In any case, if you want to send updates, I'd recommend to send PR at the github organization, but sending complete files to vim-dev or me will also work. Thanks Ben and hope to hear back from you ;) Christian -- The human race is a race of cowards; and I am not only marching in that procession but carrying a banner. -- Mark Twain -- -- 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/ZNkMusLr%2BPur6V6b%40256bit.org.
