Hi,

To be honest, it was kind of a coincidence, I showed up there. I started to
look a bit deeper into Storm in the last few days, but I still don't know
much about it. I started to check the project (clone the repository and
tried to build) with some errors, because I use windows and Storm is not so
windows friendly. :D
Anyway, I did not think I could make a huge impact in it (especially as I
am unfortunately not the most active member of the community :( ).
But I don't want to let Storm die. If I can help, I want to. In the last
few days I read lots about Storm's history and it deserves to live.
I am going on a long vacation from 24. May to 8. June, but after that I am
happy to discuss how I can help.

Regards,
Sigee

Richard Zowalla <[email protected]> ezt írta (időpont: 2026. máj. 18., H,
16:35):

>
> Hi all,
>
> I wanted to raise something that's been on my mind for a while regarding
> the sustainability of Apache Storm itself. From what I've observed, getting
> the 3 votes required for releases and decisions has become quite cumbersome
> - sometimes really hard - and that makes me worry about how viable Storm is
> as a foundation for us going forward.
>
> On a more positive note, I noticed that Dávid recently showed up in one of
> the Storm issues. I think it would be a good idea to try to get a few more
> people from the StormCrawler side involved in Storm directly. One thing
> that helps here: Storm doesn't differentiate between Committer and PMC -
> they vote new people straight into the PMC. So it could be a relatively
> clean way to inject some fresh contributors and voting power into the
> project.
>
> If we don't manage to do something along those lines, I'm afraid we'll
> have to seriously consider re-inventing or migrating our underlying cluster
> technology to another stream processing framework sooner rather than later,
> and let Storm die (in the attic).
> I'd rather avoid that if we can since the technology has a proven record
> in web crawling projects.
>
> Any thoughts?
>
> Gruß
> Richard

Reply via email to