Re: community repositories? community and activities report? Who would be interested in joining?

On Wednesday, January 1, 2014 5:36:45 PM UTC+4, MarcWeber wrote:
> Maybe you've noticed the discussion on vim-dev about providing a single
> repository containing all vim plugin repository information.
>
> The goal is to allow multiple parties (VAM, NeoBundle, ..) to use this
> repository.
>
> Thinking about it I come up with:
> - my UltiSnips fork
> - Snipmate (and vim-snippets)
> - my vim-wiki.mawercer.de code
> - vim-dev-plugin
> - vim activities and community report web site (to be done)
>
> Those are maintained by a couple of people at the moment anyway.
> Note that I didn't talk to the repository owners yet.

I do not see why somebody cannot just grant commit access to this couple of people in their repositories.

>
> and many additional packages which I'd like to allow commnuity to
> contribute to even easier.

How does your proposal makes contribution easier (except for the vim main plugin set which would be easier only because we will have more then one man with commit access)?

>
> I even consider moving vim RUNTIEMPATH into its own community maintained
> repository could be a success - because a lot of things could be
> improved - and we could work on new standards such as "asynchronous task
> lists" etc.
>
> Who of you would be interested in joining such a community maintained
> project - even if its a piece only?
>
> I'd also like to start something which existed in Haskell for a long
> time: The community and activities report.
>
> So we need a new page collecting such updates - so that its harder to
> miss new plugins and how they compare to existing work.
>
> For vim-addon-manager-known-repositories (which is likely to be renamed)
> we're looking for a new home, thus discussion should take place now
> about whether we should create something like
>
> github/vim-community/<the projects>
>
> or just use
>
> github/vim-pi/vim-pi (pi = package index)

*Plugin* index. The farther we get from pypi the better.

>
> for that single project.
> I feel the more communication the better.
>
> Ideas, thoughts - comments?

I cannot have thoughts about this idea because it is not defined. First you need to have at least a draft of the proposed organization structure then any useful comments may appear. Not reverse.

I currently think that this thread may result in a huge discussion and in nothing else but a discussion. We still even do not have a definition of what should be hosted in vim-pi.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.