Re: Vim homepage - improvements I'd like to implement. Comment please

On Fri, Dec 31, 2010 at 08:44:02AM +0100, Marc Weber wrote:
> I'd like to implement:
> ...
> 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.

I agree with that. I suggest that not only the owner, but a "Vim site
manager" (one of a few people) should be able to add collaborators, to
enable script adoption even if the original maintainer can't be reached.

> 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 )

Keep also download count.

> 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

Yes, make it hard to be a troll.

> 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.
>
> Maybe there should a way for users to subscribe to comment changes (?)
>

At first I thought: "hey, comments would be great", but then I thought
that a comment system will become a rather unstructured area for user
support for that script, and that kind of needs should be fulfilled
providing decent documentation for the script.

IMHO, the ideal contact channel is a bug tracking system for each
script. But I do know that implementing that is: 1) a huge burden 2)
reinventing the wheel.

Maybe an optional "bugtracker" field to be filled by the author, which
is the URL of the bugtracking system the author uses, if any.

--
Javier Rojas

GPG Key ID: 0x24E00D68