new home, I see... about primus HOT 3 CLOSED

@jcw

Your project looks great, but I haven't fully decided yet what I wanted to do with the new Primus organisation. I mostly created it to bundle all of Primus's code, dependencies, parsers, transformers, examples and website in one single location. This makes contribution to the project a lot easier.

I was thinking of creating a couple of plugins for Primus that would be added to the organisation as they would receive support from me (and hopefully the rest of the community as well).

We can add community contributed modules to the organisation but I don't know if the addition management overhead is worth it as restrictions has to be setup for every plugin/repo. But this is my personal opinion, I don't know what the of the community and contributors think of this.

from primus.

Well, I'll let you ponder on what you want to do with your new repository structure, then :)

(I tend to open up my repo's more and more, it simplifies life, and rotten apples can always be kicked out again)

Cheers & Groetjes,
Jean-Claude Wippler

from primus.

@jcw I do open the organisation to contributors, if a couple of high quality patches are contributed the user would gain full administrator access for Primus and it's related projects. The only problem I foresee if that add contributed plugins to the primus organisation I give those an unfair advantage over plugins that implement the same functionality.

So I'm going to close this issue for now. I always add the plugins to the README.md and in the future, on the website as well.

Thanks again for bringing this issue up.

from primus.