I agree with Julien.
Le mar. 3 oct. 2023 à 09:20, Julien Nioche <lists.digitalpeb...@gmail.com> a écrit : > > Hi > > Thanks Richard. There are some dubious votes indeed. > > My views is that we could keep only the modules with 4 votes or more : > cassandra, elasticsearch, hdfs-*, jms, kafka*, metrics, redis > > The rest can be removed. If people feel strongly about them, they can > always copy the code and maintain it in external repos (which can of course > be contributed back later on if they prove to be popular). > Given the low number of active committers on the project, any reduction on > the size of the code or number of dependencies to maintain is a good thing. > > Julien > > > > On Mon, 2 Oct 2023 at 07:04, Richard Zowalla <r...@apache.org> wrote: > > > Hi all, > > > > our survey is closed and here are the results. We only have a sample > > size of n=11, which isn't great but somehow represents the current > > state of Storm (just revived from the Attic). > > > > You find the results here: [1] (csv + image). User comments are also > > added to the gist. > > > > We had some votes from people, who aren't using Storm at the moment and > > just need a technical comparison between Storm, Flink and Spark to > > decide, which one to use. Therefore, it seems, that they marked every > > module as "must have" ;-) - as a take-a-way: it might be good to > > provide such comparison on our website. > > > > We should discuss, which modules are worth being kept in the main > > repository and which modules can be extracted (for example into a > > "storm-external" repository). > > > > Due to the tight coupling for security (in the UI), we need to keep the > > hadoop-related stuff. Kafka things are also a thing, it seems. > > > > Some of the moduels are used by (new) PMC members, so they might have > > the energy to start an update initiative on these modules. > > > > Happy to hear your thoughts! > > > > Gruß > > Richard > > > > > > > > [1] https://gist.github.com/rzo1/2a1d20acfc20da050ea515770c6606df > > > > > -- > > *Open Source Solutions for Text Engineering* > > http://www.digitalpebble.com > http://digitalpebble.blogspot.com/ > #digitalpebble <http://twitter.com/digitalpebble>
