Build a team

[kisst]

@jaime @tkh @vorlock @PeteJBooth @niceguydave are you interested ?

( aka test github notifications )

[vorlock]

yooo man, fine with me, how is live at the dark side? :-)

[tkh]

I might be able to help a bit on tooling and some lighter stuff but I have almost no free time at the moment.

[kisst]

Hi All,

For now as a first step I want to organize something to talk trough the structure of data, hosting, project timeline and the basics, I have some of the skeleton of the cli in a local branch but I'm ashamed to publish it, maybe will push it to a dev branch after a bit of tidy up.

So far I started to write it with python3 and the only external library I used is piera but I guess I will need something more when I reach the search functions,but I already I realized that more then one level of structure is needed in long term to accommodate different installation flavours.

One good example for the flavours is the aws cli, as that is available as a system package in more of the distro, but at the same time also on pip, but even in pip you can install it with root into system level, or user level, etc, so there must be an other of preference when I say glid install aws-cli then which instructions to parse, of course we can just get away with interactive select as well, and just let the user choose per install bases, and then maybe extend it with cli parameter for the non interactive options, but then we need something smarter local database to store for which package which flavour is preferred.

Anyway I can write about this a little book already, so what I suggest it to pick a date, grab a beer and maybe a pizza and just brainstorm. Just the data structure of the recipes can be challenging, that's why the #3 would good to crack.

ps.: I forgot to add @evenicoulddoit I already had a chat about this with him as well