As you have been hearing on the Tsugi developer list and in my public presentations, Tsugi is going to build a new approach for adding tools that uses web services rather than a shared database connection across libraries written in multiple languages.
This means that new environments will be easier to build and support over the long-term and Tsugi will be able to provide a tool environment that will meet and exceed the privacy requirements of GDPR and similar privacy oriented measures.
The following efforts that I have put together for Tsugi over the years are now deprecated:
https://github.com/tsugiprojec
https://github.com/tsugiprojec
https://github.com/tsugiprojec
https://github.com/tsugiprojec
https://github.com/tsugiprojec
I would also recommend that there be no further investment in Tsugi PHP tools that depend on the Silex framework as it has been deprecated and I don’t expect to upgrade it.
If you have built Tsugi PHP tools that are currently working within Tsugi-PHP – they won’t be broken – what is there currently will be maintained. But some of the deprecated bits will be frozen going forward. If you are building a new tool before the new development model is complete, simply build it in generic (non-framework) PHP like the tools in https://github.com/tsugitools
In time I expect to build new sample code in Laravel, Python, and Node that makes use of the Tsugi APIs and services in time.
These deprecations allow me to “clear the deck” to focus on the next generation and make sure no one starts new work in an Tsugi environment that will not continue to be supported.
Questions welcome.