Completely, what needs to be done is to add types of extractors (we are currently able to extract the rooms in Gladys, the houses, and the times, we would need to add the places, etc…) + new sentences. The engine itself works well, just need to add data 
By the way, the sentence database, like all of Gladys, is 100% open-source, and modifiable by everyone, it’s not code, just a config file that can be found here →
https://github.com/GladysProject/gladys-data/blob/master/sentences/v2/fr.json
No excuses! Everyone can help! 
I disagree on that, I would really like to develop the conversational aspect of Gladys
But through questions about the schedule, ordering an Uber, more specific questions: what temperature is it in my living room? More than the age of Emmanuel Macron or other ^^ (that will clearly come but in a second step)
Yes, as I already said in another topic, I am really not for Blockly, for me it’s like programming but visual, and in addition, visually ugly. Result it combines the disadvantages of both: it’s not for the general public (it’s still a programmer’s logic that few people understand) and it’s ugly! 
My opinion on this, it would be to develop more and improve the scenario editor, by adding as many triggers/conditions/actions as possible. Because currently there are very few and it’s a shame! Given the amount of things possible in Gladys, we are limited in scenarios stupidly 
Yet to add triggers/conditions/actions it’s very simple, it’s like the sentences, it’s config files available on Github editable by everyone!
The triggers:
https://github.com/GladysProject/gladys-data/blob/master/events/fr.json
The conditions:
https://github.com/GladysProject/gladys-data/blob/master/states/fr.json
The actions:
https://github.com/GladysProject/gladys-data/blob/master/actions/fr.json
I think that the next live coding session, the next weekend where I am available I work only on that full time 