Hi Yasith, Thanks for your interest in contributing to OODT. With the technologies you are familiar with, you will definitely be able to help us improve a lot. At the moment, I don't have beginner level issues to point you to. So the best thing is to play around and get an idea on what is OODT. When you go through you may notice that there are a lot of problems in documentation in cwiki and readme files. It will be a great help for new comers if you can fix them as you go through.
Following is a response I sent to another student to introduce OODT. That will help you too. Thanks for your interest in contributing yo OODT. As you may already know, > we are planning to offer 2 GSoC projects [1] this year which we think are > the most important at the moment. > Since you have experience in React, Java and hopefully some knowledge on > containerization, you will be able to help one of those projects for sure. > The community will be really happy to see your contribution. Thanks for > your PR as well. I will look at it soon. > > On getting started, did you try running OODT? > > In brief, OODT have 3 main components, File Manager [2] (for information > integration), a Resource Manager [3] (managing resources and scheduling > jobs) and a workflow manager to execute workflows. In addition to that, > there are other components like crawler (for crawling and ingesting crawled > documents to file manager), OPSUI (the main dashboard of a OODT deployment > which shows status of each component and ingested files, workflows etc) and > a set of REST APIs. > > You can refer file manager user guide [5] to get an idea of file manager. > If you want to run all the components at once, you can use the docker > container [6]. If you prefer more hands on experience, try the RADiX [7] > build. Try to play around a bit to get an understanding of the usage of > OODT since it is more of a framework rather than a product. > > When you play around, if you encounter anything you don't understand, feel > free to ask. If you encounter any issue please create an issue in JIRA. If > you can, try to fix it yourself to get familiarized with the code base. The > above steps will be a good starting point as I don't see any newcomer type > issue in Jira to let you work on immediately. > > Thanks, > Imesha > > [1] > https://issues.apache.org/jira/browse/OODT-986?jql=project%20%3D%20OODT%20AND%20labels%20%3D%20GSoC2019%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > [2] https://github.com/apache/oodt/tree/master/filemgr > [3] https://github.com/apache/oodt/tree/master/resource > [4] https://github.com/apache/oodt/tree/master/workflow > [5] > https://cwiki.apache.org/confluence/display/OODT/OODT+Filemgr+User+Guide > [6] https://cwiki.apache.org/confluence/display/OODT/Docker+powered+OODT > [7] https://cwiki.apache.org/confluence/display/OODT/RADiX+Powered+By+OODT > Thanks, Imesha On Wed, 13 Mar 2019 at 03:12, Jayawardana, Yasith <yas...@cs.odu.edu> wrote: > Hey all, > > First of all, let me introduce myself. I'm currently a PhD student at > Old Dominion University, Norfolk VA, USA. I completed my bachelor's last > year at University of Moratuwa, Sri Lanka in Computer Science and > Engineering. I interned at WSO2 Lanka (PVT) Ltd, where I worked with > Docker and Docker Compose for creating deployment configurations. As my > Final year project, I have worked on Apache Kafka, Apache Zookeeper and > Apache Curator. > > I have experience in Java, Docker, Maven, Gradle, and also in C/C++, > Python and HTML/CSS/JS through working on university projects and > personal projects. I'm interested in contributing to Apache this summer > as I'm hoping to put my free time into good use to help out the > development community, and thought Apache would be the best place to > start as it means a lot to the community. > > Having said that, I would very much like to contribute to Apache OODT > this time around. These days I'm familiarizing with the components of > OODT, and I have some questions to ask. > > 1) Is there any beginner-level issues that you suggest me to look into > so that I could kick start contributing? > > 2) I read through some README files and found some points I could add to > improve them. Would it be fine to create PRs that contain such > improvements? > > 3) I see there are three main components in OODT. Do you think I should > familiarize with all, or do you have any specific areas that I should > focus on? > > > Best Regards, > > Yasith > > -- > Yasith Jayawardana > PhD Student, Department of Computer Science > Old Dominion University, Norfolk VA > +1 (757) 698-8978 > >
