Not trying to be difficult , but I am missing the point of the organization. I like the idea of a registry of plugins (ala wbonds json file) but I do not see the benefit in having 19 admins (that do not know each other) for these 20 odd repos.

slestak989 wrote:Might be a need for another plugin here. We might need something to display all the current keybindings and where they are sourced from. I can see where conflicts can arise by chance.

An example that I like is gnu screen, if you remap keybindings in your .screenrc, the help screen reflect the default + your mods.

I could not agree more, I've no clue how to pull it off though. There is no automatic way of doing this as far as I know, you could do it manually but somebody has to keep looking for new bindings in that case.

I have just joined this organization and I do not want to be a Robin Williams in Vietnam but wouldn't it be nice if we created a repo just for communication? We could ask things via Issues and people have the option to opt out. We could use a mailing group (which I can volunteer to set up on my web server) however Issues on github would be public and have the option to be referred to and flagged as closed or tagged and what not.

I could provide a opt-out-able mailing system too, however since we are already on github we could use the system there and grow the organization into a little knowledge base...

All of this comes from me looking for a way to ask others on github and to be able to attach code on github or even link issues from our plugin repos.

I must say I do not dislike this idea. Issues on github are well-conneted with other issues on github by cross-linking other repos and stuff and all in all this seems like the place where "SublimeText" coders can communicate and discuss on problems or something.

I'd also like to mention the #sublimetext IRC channel on freenode where I and several others are helping people with being sublime. You should check there too and you can also discuss small or urgent things there.

I'm new to github, python and sublime plugins, so this may be a silly question, buuutt: if I switch my plugin over to this sublimetext packaged github, is it no longer mine? What all am I transferring over? What happens to all my existing issues for the plugin? who can edit my repository after the switch?