feat(devtools) Adding a command to create file from templates when we…

[Grummfy]

If we create a new library we need to initalize a series of files. This is the begining of that part.

I see a lot of potential improvements, but the idea is to have a base to build on.

vendor/bin/hoa devtools:project -n NewLibrary

Will create the base of the readme file, based on the common template. If the file exist, it will ask about it and offer the possibility to ovveride it.

[Pierozi]

That's good idea, even if we do not add new lib every day, (but extension more often, like you did)

We could integrate also some of Kitab block, to make it easier for the contributor to write doc.

[Grummfy]

yes, for me it's a base to built on.

In my previous job I got a template for project : a series of file I copy inside a new project and a tools to init some configuration on our repository and tools (like CI, deployment, ...) and even if it was times to times it help us to win a lot of time and overall in quality (global cohesion).

[Hywan]

What about a Skeleton.git repository? I mean, this is an alternative. It has pros and cons. I'm just raising new ideas.

[Grummfy]

Don't know the Skeleton poject where it is?

[Hywan]

It does not exist. In the past, a Skeleton.git repository was a thing but to start a full project based on Hoa. Here, you want a skeleton to start a new library. This is different.

[Pierozi]

Skeleton.git sounds like how to bootstrap an application with Hoa libraries.
This wording could be miss interpreted by a lot of peoples.
Besides, a line command seems to be much useful for creating new library instead of clone or copy content from another repository.

[Hywan]

So, let's go for a command-line I guess… :-).