Hi,
It would be easier to manage each packs/modules separately. Each in its own
repo.
They could evolve at different speed from core with ease.
I think it would decrease load on core dev team so that they can focus on
core dev :p
PS : There's a typo in your link : https://npmjs.org/
2013/5/14 nap <napar...@gmail.com>
> Hi all,
>
> now the 1.4 is on RC, it's time to talk about the next one, the 1.6.
>
> If we take a look back since the 1.0 version, there are more and more
> contributors, that's great, thanks to all of you :D
>
> If we take a closer look, we can see that the major part of the
> contributions are about bug fix and module/packs enhancements, and it's
> quite normal in fact. But there are fewer new packs or modules. I saw
> enhancements that were far more complex than creating a simple module or
> pack, so why no "new" things there?
>
> I think there is one main reason why there is no "new" things : it's in
> the core. First, it's not easy to find them. Ok for packs it's just
> etc/packs, but for modules it's inside the python lib. What if a user code
> a new one and upgrade? He will have to "reinstall" the module. That's not
> good.
>
> Packs are also hard to manage when updating. Currently, we just don't
> touch them as the other user configuration in fact. But maybe the user
> change a pack files, but want others packs to be updated.
>
> As it's on the core, modules and packs are seems to be managed by the core
> team (quite logic), and so don't see that they can also add new ones,
> especially if they need to ask us for inclusion on the core (if you are
> shy, it can be hard to ask for it).
>
> That's why I think we should "export" modules and packs from the shinken
> core repository, and give them their own, one repository by module/pack.
> This will make them look as they are : small if you take one by one. So
> eveyone will saw that it's quite easy to code a new module or a new pack.
>
> We only need to provide a simple tool for listing and installing the. I
> already get the shinken.io URL, so this can be the place of a new
> exchange place, a bit like what npm.org is for the nodejs tool.
>
> Every one will be able to send a pack or a module there, there won't be
> need to get my aproval for posting there (just moderation to remove things
> taht should not be there, like illegal things).
>
> What do you think of this? Do you think you wil be more attract by such a
> platform than commit in the core repository?
>
> If you got other ideas for the 1.6 release, it's time to share :)
>
>
> Jean
>
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
