A consensus appears to have formed to split the project in half for management purposes, with the “Tsedei” (time series event data engine initiative) working group taking primary responsibility for all data definition and engine development, including API, efficiency, and data conversion, while the language/compiler/environment effort stays put. Tsedei is the closest to delivering anything at this point, and we don’t want to slow Tsedei down by tying it to the difficult requirements process for language/compiler/environment. It is hoped that a working prototype of Finili can be delivered faster by making Finili a client of Tsedei. In addition, this makes it easier to deliver more results from Tsedei that aren’t necessarily tied to Finili, and it should, we hope, lead to better energy efficiency in the products of both projects. Also, early errors may be avoided by having thorough formal documentation of the interface between (Finili) language and (Tsedei) engine.
This is a change in the management process only. At this point everyone is continuing to work on the same things, which means people are working on both Finili and Tsedei. However, the formal split does make it possible for people to focus on just one project or the other if they choose. It also paves the way for a possible future operational split, though no one foresees any need for that in the next couple of years.
