Hello Thilo, Thilo Six wrote: > Hello Thomas and Benjamin, > Excerpt from Thomas Köhler: > -- <snip> -- > >> I think you're misinterpreting what "team maintenance" would mean. It > >> wouldn't be a team per language, but rather a single team to handle > >> changes (maintenance) to all syntax files. (Which doesn't preclude > >> active maintainers from continuing to actively maintain their current > >> files.) > > > > I didn't think of "a team per language", but "the team should > > have two people who understand the language", as the goal seems > > to have been "if one is not available, then another one should be > > able to handle the issues". > > When i think of this team i count each current maintainer as a member already. > The idea is to use a mailinglist where anyone who likes can subscribe (think > of > vim-dev). All communication about runtimefiles happens openly. Not 99% via > private email where no one can learn from each other and reviewing changes is > left to Bram alone. > > So basically the only change for now would then be this line: > " Maintainer: Thilo Six <T Dot Six At gmx dot de> > > would change to > " Maintainer: Thilo Six <vimruntime-maintainers at foo dot org> > > Still i am the main-maintainer but not the only one. Questions, fixes, > additions > would *NOT* go lost just because my mailprovider has changed, or because i > lost > interest in it 4 years ago. > > No one is anyone blocking to take care of their peeve pets. > > I hope that makes my intention of this team a bight easier to understand.
OK, now things are clearer for me. That's basically a good idea, but: - URL would also need to change: http://gott-gehabt.de/800_wer_wir_sind/thomas/Homepage/Computer/vim/syntax/uil.vim would need to become something different, for example http://www.vim.org/runtimefiles/syntax/uil.vim - all the vim runtime file maintainers would need to have read/write access below http://www.vim.org/runtimefiles/ (or whereever that is) The reason is that if another maintainer changes a file, the file also should be changed at the URL given in the file. Of course there could be a git repository with all runtime files included, and all maintainers just send patches to a group of git maintainers, and the URL would point to where the central git repository would show the file, which would put down the number of people that need read/write access from a few hundred to just a few. What do you think? Ciao, Thomas -- Thomas Köhler Email: [email protected] <>< WWW: http://gott-gehabt.de IRC: tkoehler Freenode: thkoehler PGP public key available from Homepage!
signature.asc
Description: Digital signature
