On Di, 05 Mär 2019, Jón Arnar Briem wrote:
> Hello everyone, > > My name is Jón Arnar Briem and I am a part of a group of students at > TU Delft who are taking part in a course which focuses on open > software project and the cooperation within these projects. For our > assignment we are supposed to pick an open source software project and > monitor and analyze different aspects of the project, furthermore we > are also expected to make our own contributions to the project. Our > group chose Vim as our project, we have started on our analysis (which > we'll be more than happy to share with you once it's complete, if > anyone is interested) and now we are starting to look at possible I think this would definitely be interesting. > contributions. Before diving in and suggesting features or changes > that we can think of we wanted to ask you if there were any specific > areas which are suitable for contributions from motivated developers > who might not have very intimate knowledge of Vim. I am not sure how skilled you are and how much time you want to spend on this, so some of the following might be too complex. However, please have a look at those wiki pages for some suggestions: https://vim.fandom.com/wiki/Vim_GSoC_2011_Ideas https://vim.fandom.com/wiki/Vim_contribution_Ideas Some of that is old or already implemented, but there are still some valid suggestions. Also you might want to skim through the todo.txt help file to find anything interested. Be warned though, Vim is a mature and old Open Source project. Developing anything for Vim might take considerable amount of time until it gets included. Also we are not very well-known for giving feedback for patches. You have to dig through the mailinglist archives and into the code mostly by yourself to find the answers :( A good test coverage for your newly contributed code certainly helps getting it included. However, that does not mean, that contribution is not welcomed or appreciated. So don't let those things scare you. Best, Christian -- -- 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]. For more options, visit https://groups.google.com/d/optout.
