Decide the name and packaging structure of the library

[Hombre-x]

We are at the final stretch of the G🧦and at the end of the first part of the library, so congrats to all 🎉❤️

So, I think it's time to start deciding how we should name this library and how we should structure it so other users can start importing it (whenever the Maven issue for publishing is solved 😅).

These are some of the suggestions so far:

• Cats OS: Not pretty awesome, but integrates nicely with the naming of the Cats projects and you could import it very nicely by doing import cats.os.*

• Shellfish: The good ol' name, but as we discussed this library isn't any more about shells. The advantage is that not much more refactoring is needed.

• Purrcess: Funny, but the library does not have processes implemented just yet.

• Gatos: This one's my favorite, it is the Spanish and Italian translation for cats but has the os name at the end of it. Also, really easy to import by doing something like import gat.os.* or simply import gatos.*.

Also, more names and suggestions are very welcome!

[mpilquist]

+1 for sticking with shellfish or picking a name that directly acknowledges the library is aimed at simplifying shell scripting and isn't a general purpose replacement for fs2-io. Though I do like the fun names. :)

[TonioGela]

I don't like very much shellfish as a name nor I feel that any of the proposed ones really indicates very clearly that we're talking about scripting.

How about names that contain script/ing somehow? Importing cats.scripting.* might be cool.

Here's some completely random ideas/suggestions:

• catscript
• catnip (as it makes things more "fun")
• catly
• kits (an even shorter form of kittens)

[Hombre-x]

feel that any of the proposed ones really indicates very clearly that we're talking about scripting.

I thought you liked the Gatos one 😭

Catscript also sounds really cool to me, I'll +1 to it