> > That's not an issue. We could introduce a version field in addon-info.txt.
> For me it is fine.
No, seriously: If you're going to break things you should use a "topic"
branch. If your VCS makes this hard you're using the wrong VCS :)
But I agree that it should not me forcing working styles on others.
So "version" will be one of the supported fields for that reason even
though I'm very unlikely to maintain it myself.
Thus I'd also suggest a setting which tells whether the latest stable
version should be preferred.
I just don't to give this version field a high priority at the
beginning because it requires visiting each commit.
If your code is still unstable users will tell you and you'll reach a
new stable state much faster.
fields I'd use in addon-info.txt:
tags: ["C++",".."] # to group plugins by language, feature, ...
name: # name used to resolve dependencies. If there are multiple matches ask user which one to use
# if there are obvious reasons to prefer one
# vim-addon-manager-known-repositories will reflect this in some
# way
dependencies: {
# VAM style list of dependencies by name
}
maintainer : "email"
version: "0.3" # if this changes assume new stable version
preferred: true # for your style of development. Indicates whether the latest stable version should be used
relations: ... relations to other plugins.
> No, it is not. I don't trust this and relations are defined by tags.
Of course you neither trust any VimL code unless you've written it
yourself. But hey, don't you think that this will give you an idea about
what could be important? Nobody prevents you from verifying the
statements yourself.
And of course I'd rather propagate "join and improve existing projects"
rather than "fork and tell everybody your code is better" even though it
may not.
So this is meant to place hints at "unmaintained" projects so that you
can get users attention. Of course the user still has to decide what to
install and use.
Eg visit this: http://www.vim.org/scripts/script.php?script_id=2540
The first impression says: "Hey, great plugin". Then you fix something.
Then you sent a patch. Then you don't get a reply. Then on irc you're
told: upstream is at github.com/garbas/... Then you can rewrite your
patch cause all the code has changed?
What is left ? A bad feeling about wasted time on all sides.
Its ok to have different ideas about how things should be.
I'd like to introduce a soft force that those differences get documented
and pointed out. That's the idea.
Marc Weber
--
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
No comments:
Post a Comment