I've sent this email some days ago to vim_use, didn't get any replies,
so I does anybody mind me implementing those small changes?
--- Begin forwarded message from Marc Weber ---
From: Marc Weber <marco-owe...@gmx.de>
To: vim_use <vim_...@googlegroups.com>
Date: Mon, 10 Feb 2014 16:04:06 +0000
Subject: website / wikis - important links / proposal
You may have learned about a recent case:
VAM vs Vundle vs NeoBundle etc.
One of the things which I feel very sorry about is that Shougo that time
did miss VAM - so we have two plugin managers. Diversity is fine (if
there are known reasons) - I feel that "I missed the other solution"
is not a nice reason.
I'd like to improve this. And I think the way to go is improve the
visibility of the wikis at vim.sf.net because I think wikis are closest
to "self organization" and delegating repsonsibility to the community,
too.
Right now we have at least two wikis:
vim.wikia.com:
+ much content
+ most tips
- ads
+ payed by ads
vim-wiki.mawercer.de:
+ minimal set of features
+ based on git (thus editable by Vim on disk)
+ you can edit without logging in.
+ custom code allowing to add custom features (such as feature
matrixes).
I don't want to judge which one is better (either is better than missing
both or having none being visible enough).
At vim.sf net the keyword "wiki" is easy to miss - and you'll find
broken links such as
community -> Another wiki is at wikibooks: learning the vi editor/Vim.
which is dead since 2010 (?) Anybody knows what happened?
While discussing hosting would be worthwhile (Bram?? - would you accept
a different solution if it was guaranteed to exist for a couple of
years?) I think that discussing the most visible links is most
important.
I'd sugggest:
1) What is Vim
2) Get Vim
3)
Additional resources
Documentation
wikia Wiki
vim-wiki
Tips
Plugins (and managers) (overview) [1] [X]
4) Community/getting Help [2] [X]
5) Sponsoring
6) My Account
7) humor (all those nice graphics etc)
This would be a small enhancement without changing too much.
[X]
Some of the pages should be "community-driven" thus hosted on wikis.
The contents on vim.sf.net could be updated once a day to reflect the
wiki contents.
Projects /ideas such as "monthly/weekly" tips could be added easily
then.
[2]
help: vimtutor, :help, mailinglist, irc, stackoverflow (less recommended),
github issues (or similar)
For plugins:
doc/* (best viewed in Vim - yes I got a mail telling me that < > signs
at github views are hard to understand (those indicate code blocks
but they are only visible inside of Vim)
and nowabays README.*, too as well as the install instructions at
the plugin page at vim.sf.net (which get harder to mantain now that
github is standard)
[1] and here its important that ratings can be a guide, but can also
be missleading. We had cases where massive downvotings happened on a
couple of plugins within 1-3 days for no apparent reason.
Here its also important to talk about "best practises" about how to
report bugs etc.
I really think it does make sense to state
1) look for existing plugins
2) talk to those maintainers (eg by github issues)
3) if you still need to write something new document your goals
Recommending some feedback workflows will help all parties a lot.
Does this make sense?
I cannot rewrite the website - but I will take enough time to add the
important bits -and maybe remove the outdated ones such as the "what is
this site still talking about it hosting the tips".
Which additional do you think are important and missing?
Most of the changes are trivial, but important for "newbies" IMHO.
Please reply to this thread what you think - thanks.
If you want to make changes to the suggestion, you can just edit the
titanpad [T] (and reply briefly describing your changes here on the
mailinglist)
[T]: http://titanpad.com/ZilTT7O6wZ
Marc Weber
--- End forwarded message ---
--
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
