I appreciate your suggestions and decide to enable checkstyle first to get familiar with code style of storm and building storm.
At the same time, I will try reading some Clojure code in storm-core. Thanks, On Fri, Oct 13, 2017 at 3:29 AM, Stig Rohde Døssing <stigdoess...@gmail.com> wrote: > Hi Shawn, > > Welcome. I don't believe we have a mentoring program, but someone else can > correct me on that. I have a few suggestions for places to start. > > * On the master branch we've enabled checkstyle, and most modules currently > have a large number of violations. Fixing some of these violations > (disregarding those that cannot be fixed in a backwards-compatible manner, > e.g. public method renames) might be a good way to get familiar with > building Storm. Please refer to > https://issues.apache.org/jira/browse/STORM-2565. > > * We still have some Clojure code in storm-core. It's my impression that we > want to eventually port all of it to Java. Picking a file and translating > it to Java (as close to a verbatim translation as possible) is an option. > https://issues.apache.org/jira/issues/?jql=resolution% > 20%3D%20Unresolved%20AND%20labels%20%3D%20java-migration > > * We have several connectors for other systems in /external. Generally > fixing issues on these is a fairly self contained task that doesn't require > touching the storm core code. You might see if you can find unresolved (and > unassigned) issues for one of these components. > > * There's some ideas for improvements to the core parts of Storm here > https://issues.apache.org/jira/browse/STORM-2284. Solving any of these is > probably harder than the other suggestions, but I wanted to mention them. > > * If you have ideas for improvements, create your own issues on Jira. Since > you work with Storm professionally you might have suggestions for improving > the components your company uses. You might also consider joining the dev, > issues and user mailing lists. People with issues using Storm will tend to > either post to user or raise an issue on the issue tracker, and the dev and > issues lists will give you an idea of what's going on in the project. > > Helping to test open PRs on Github is also appreciated. > > 2017-10-11 17:22 GMT+02:00 yang xiao <shawnxiao...@gmail.com>: > > > Hi, > > > > My Name is Shawn XIAO, and I'm new to the Storm project. > > > > I'm very interested in Real Time Data processing and computation and want > > to become a contributor of Storm project. I have read Apache Mentoring > > Programme <https://community.apache.org/mentoringprogramme.html> and I > > want > > to know is it applied to Storm project? > > > > And I also read the Contributing to Storm > > <http://storm.apache.org/contribute/Contributing-to-Storm.html> and try > to > > find "Newbie" label issues and find three issues (STORM-487, STORM-2546, > > STORM-755) which seems two or three years ago and I don't know whether it > > is suitable for me to begin with. > > > > And I also read Implementation docs > > <http://storm.apache.org/releases/current/Implementation-docs.html>to > > try to understand codebase more and begin to read the master source code. > > > > I am a software development engineer in a company using Kafka, Storm, > Spark > > and Streamline to process and analyze telecom xDR data. > > > > I am willing to spend part of my spare time to learning and contribute > this > > great Open Source project. I wish someone could give me some suggestions > > that how to become a contributor of Storm project? > > > > Regards, > > Shawn > > >
