Different libs -> different projects about arsenal HOT 8 CLOSED

• Other problem: Arsenal's index.js can only have one default export (if we export multiple libs in it, they'll no longer be default). This has consequences (for instance, I don't see how we can have our .eslintrc referencing Arsenal as the linting rule).

from arsenal.

Having a kinetic-node repo could be great to avoid unnecessary install steps for some modules, and I don't think having a public repo for the linter could be a problem either.

Overall I think this is a good idea. What do the other members of @scality/team-ironman think about that?

from arsenal.

Seen with Adrien with his poc for an independent Guidelines repository for
the contributing guidelines, as well as the eslitn config.

I agreed with his proposal, as it seems more modular, and better suited for
the npm use.

David Pineau
Scality R&D Developer

On Wed, Oct 14, 2015 at 3:29 PM, Michael Zapata [email protected]
wrote:

Having a kinetic-node could be great to avoid unnecessary install steps,
and I don't think having a public repo for the linter could be a problem
either.

Overall I think this is a good idea. What do the other members of
@scality/team-ironman https://github.com/orgs/scality/teams/team-ironman
think about that?

—
Reply to this email directly or view it on GitHub
#12 (comment)
.

from arsenal.

What about renaming IronMan-Arsenal to IronMan-Kinetic (cf. the versioning concerns)?

from arsenal.

Will we really only have kinetic inside this repository ? I'm not really
sure that it's what's gonna happen. Also, we need to decide with the whole
team whether we actually try to explode the number of repositories or not.
I know some of us are not too fond of this strategy; although I understand
the appeal of it.

David Pineau
Scality R&D Developer

On Mon, Oct 19, 2015 at 5:04 PM, Adrien Vergé [email protected]
wrote:

What about renaming IronMan-Arsenal to IronMan-Kinetic (cf. the
versioning concerns)?

—
Reply to this email directly or view it on GitHub
#12 (comment)
.

from arsenal.

The versioning problem (post #1) is a real problem. :/

What other libs do we plan to put in Arsenal?

from arsenal.

I've been bouncing the ops code and docs from repo to repo since FanOut. My understanding is that the general things (base Dockerfile, Ansible playbooks) go here, while the CI-specific things (test Dockerfile) go in IronMan-CI. If that's not the case, just let me know and I'll move things (Ansible, Docker, etc.) wherever they need to go.

from arsenal.

Done.

from arsenal.