Marc Weber wrote: > Bram was so kind adding me to the list of contributors to the Vim > project which means that I can propose Vim web page changes by sending > Bram patches. If you have any urgent feature requests its the time to > start talking about them. > > I'd like to implement: > > A:a way to change the script type afterwards (because Bram had to do this > manually using SQL) > > > B:a "repository" field. This way you can register a > git/mercurial/whatsoever repository along with your plugin.
More general: a link to where the plugin is maintained. Could be a sourceforge or Google code project. There you can have a bugtracker and everything. > C:an opt-in collaboration feature: You can add other users as collaborators > to > your scripts which means that they can change the description and upload > new > versions as well (This is similar to what can be done on github) > > I'm not sure whether a collaborator should be able to add/drop other > collaborators. > > There was a request on the mailinglist for transfering > maintainership to someone else. If this should be possible a > collaborator should be able to add drop collaborators? > > I think yes because you have to trust collaborators anyway. > > > D:change the voting system this way: > > 1) votings should be tight to a specific versions. If a plugin fixed bugs > there is no reason why bad ratings of version 0.0 should still affect > the > latest version ( which might be 10.0 ) > > Because you can delete specific version archives later there may be > votings > for versions which can longe be downloaded > > I'm not sure which voting to show by default. Maybe the current figures > should be kept but an optional "detailed" few should be added? > > 2) force users to give a reason if they vote something down. This will be > kind of dialog and it'll help devs to understand user requirements We can't allow users to add arbitrary text and especially links. This will soon result in spamming, as what happened with Tips and forced us to take it down. It might be OK if we filter out anything that looks like a URL. > 3) create a new page returning a list of all scripts and achives as JSON > format > which can be used by tools like vim-addon-manager or similar. > > FUTURE (?) > PHP docs contain a feature: You can add comments below each documentation > page. > Someone (Bram) already added link to a per script id wiki page. However I > feel > that showing user comments in the same page could be a nice idea (?) > Do you have a strong opinion on this? > We should add a note that comments "are not maintained" by script authors. > We don't want to put an additional burden on them. Like above, spamming may become a problem. That's why there is a link to the tips page. > Maybe there should a way for users to subscribe to comment changes (?) > > This is not a top priority for me so only comment about this if you > feel strong about it and if you think I should change something here. > > Provide feedback about these ideas, please -- hundred-and-one symptoms of being an internet addict: 79. All of your most erotic dreams have a scrollbar at the right side. /// 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_use" 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
