Advertisement
olegtikhonov

DRAFT - September 2013 S4 ASF board report

Sep 2nd, 2013
172
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.29 KB | None | 0 0
  1. S4 is a general-purpose, distributed, scalable, fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous unbounded streams of data.
  2.  
  3. S4 has been incubating since 2011-09-26.
  4.  
  5. Three most important issues to address in the move towards graduation:
  6.  1. The frequency of releases has been low in the past. Working to put out more releases.
  7.  2. The community rise, to be more active and flourish.
  8.  
  9. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
  10. There also was discussion related to “retirement”. Currently people of the community stepped up and decided continue the project. As result, came up with building community, providing more patches, implementing new features. Moreover, Kurtt Lin wrote:
  11. “Cheer up, guys. I'm seeing opportunities in this stream processing field as well as in S4. What I haven’t mentioned is that, S4 had found successful applications in our research group even back in the 0.3.0 days and now in our start-up. We have built scalable real time search over microblogs with some S4 features enhanced (the paper appears in 2013’s EDBT proceedings, link is http://www.edbt.org/Proceedings/2013-Genova/papers/edbt/a31-lin.pdf); we also built a platform on top of S4 for detecting and analyzing real-time traffic conditions, processing over hundreds of millions of records every day. Now we plan to contribute to the community. I personally have created and responded to some JIRAs, but I would like to do more. Actually, I am ongoing proposing a design documentation of integrating S4 with Helix along the roadmap; this would help enhancing the elasticity feature for S4. So, I suppose we could put the "retirement" discussion aside? Give us the new comers some time perhaps a couple of months to see what we can do to make the community healthier. Of course, some of us are new; we shall ask for your help and guidance occasionally, please be responsive (as what you are doing now), :) You all have done brilliant jobs! :) “
  12.  
  13. One particular problem we have been having is with growth of the community. Having said that in a recent e-mail thread, we have received very positive feedback from some developers, so we would like to remain in incubation for a little longer so that we can get some traction.
  14.  
  15. When were the last committers or PMC members elected?
  16. Was reported by March 2013 (Daniel Gómez Ferro).
  17.  
  18. When did the project last make any releases?
  19. June 2013: S4 0.6.0 released.
  20. Two patches are available now, due to 0.7 release 3 of 18 issues was solved, the rest in progress.
  21.  
  22. How has the community developed since the last report?
  23. In March, the dev mailing list was reasonably busy (132 messages) and then that's dwindled to less than 35 per month since March. There was no activity in git on August at all. A little in July, more in June. There has been no change in the community. We have been seeing some traffic on the mailing lists, mostly questions about how to use S4, but the code contributions have been fairly minimal. However, some developers have expressed interested in contributing so we expect to start receiving more contributions in the near future. To grow the community, we plan to have a closer interaction with other Apache projects like Gora and Helix.
  24.  
  25. Signed-off-by:
  26.  
  27.  
  28. Shepherd notes:
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement