LILACS is a little different from core view, i dont think this will be merged and a hard-fork doesnt seem the way to go, we want to ensure core work stays compatible with us, and that LILACS stays compatible with core
LILACS should:
be contained as a single mycroft skill, we dont need to follow a normal skill structure, just ensure loading as a normal skill is compatible
msm compatible, so any user can install LILACS vocally in any mycroft unit
a hack for this can be made using converse method whatever way we go, we make timer to always keep LILACS in top active skill and mycroft will always use LILACS instead of parsing intent, this allows us to use core as a fallback
but do we want LILACS being used first (it will learn what to do eventually #13 ) or as a fallback for when wolphram alpha doesnt have an aswer?
LILACS is a little different from core view, i dont think this will be merged and a hard-fork doesnt seem the way to go, we want to ensure core work stays compatible with us, and that LILACS stays compatible with core
LILACS should:
a hack for this can be made using converse method whatever way we go, we make timer to always keep LILACS in top active skill and mycroft will always use LILACS instead of parsing intent, this allows us to use core as a fallback
but do we want LILACS being used first (it will learn what to do eventually #13 ) or as a fallback for when wolphram alpha doesnt have an aswer?