I don't really have any skin in the game as far as which components stay vs 
which go, however, I want to make sure we're not alienating the community. I 
see this as a great opportunity for the wider community to step up. I wouldn't 
want to simply trash the work that was done. That sends the wrong message. I 
think something akin to the Apache Attic would be good. Components we're no 
longer maintaining can live in the "attic" and if someone comes along who's 
willing to pick it up and run with it, maintain it (for however long), and 
really work on it, I don't see that as being a bad thing at all.

On 2023/12/17 17:48:11 Alex Porcelli wrote:
> As we gear up for the much-anticipated 10.0.0 release, I invite
> everyone to a crucial discussion about refining our codebase. This is
> not just about what we're adding but also about what we might consider
> removing or changing for the better.
> 
> The following are initial suggestions for components we might deprecate:
> 
> - Infinispan
> - MongoDB
> - Redis
> - Elastic
> 
> However, this list is just a starting point. I encourage each of you
> to contribute your thoughts. If there are other components you believe
> should be on this list, please bring them forward. Likewise, if any of
> the listed components should remain, your input is equally valuable.
> Explain your reasons so we can all understand the benefits of keeping
> them.
> 
> The TrustyAI codebase is also up for discussion. It hasn't been a
> primary focus for a while, and while I see some potential in it,
> setting it aside might be more practical for now. But remember, no
> decision here is permanent. We can always revisit any component,
> especially if there's a collective interest in its maintenance and
> development.
> 
> Your opinions and expertise are vital in this process. Let's work
> together to make these decisions unanimously, ensuring our project's
> long-term success and manageability.
> 
> -
> Alex
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to