lib vs. library

Hey Ansiblers,

I’ve been using Ansible for the last couple of months. It’s great! I’m already up to speed with contributions/pull requests and I there has been times when I’ve had to read the source code to make sure I understand what an Ansible module has been doing.

That said, I’d say I’m through the beginner’s stage as of now and I thought I should report on a big annoyance that hits me every time I visit the Ansible source code; There is one ‘lib’ folder and another ‘library’. (Yes, ‘lib’ is an abbreviation for ‘library’ for those who don’t know it.) Every time I revisit the source code and I don’t know which one I should go into. I can’t be the only mixing them up.

I know I am dropping a bomb here but I suggest that at least one of them should be renamed. However, both of them has their own annoyances, so if you’d ask (naive) me I’d probably

  • move ‘/lib/ansible’ to ‘/ansible’ since ‘/lib’ doesn’t contain anything else than…ansible; and
  • rename ‘/library’ to ‘/modules’ because that’s what the folder actually contains. This change would would probably also lead to searching for ‘./modules’ relative to playbooks, possibly phasing out ./library.
    Comments on this? Has it been discussed before? Would you be willing to accept pull requests for anything of this kind?

Cheers from Sweden,
Jens

We’re not going to move anything at this time.

I think you can get used to it.

Hey,

We’re not going to move anything at this time.

Aight. It’s your call.

I think you can get used to it.

Sure, and the next thousand users can too. :wink: I’m not thinking of me, but more them.

Cheers,
Jens

No one else has had a problem.