You can start from the below link http://apex.incubator.apache.org/contributing.html
If the documents are not clear, file a jira for that. To scale the community our documents needs to explanatory. Thanks Sandesh On Tue, Mar 15, 2016 at 2:11 PM Jayaradha Natarajan <[email protected]> wrote: > Hi Sandesh, > > Could please walk me through the steps from creating Jira tickets to > committing? > Please let me know if there is any URLs that I can follow. > > Thanks, > Jayaradha > > On Tue, Mar 15, 2016 at 2:03 PM, Sandesh Hegde <[email protected]> > wrote: > > > Hello Jayaradha, > > > > Please feel free to file jiras for the tasks that needs to be done to > > improve Apex. You can pick up any jiras unless nobody is working on it > and > > for the bigger items do initiate the discussion in the mailing list. > > > > Thanks > > Sandesh > > > > On Mon, Mar 14, 2016 at 11:09 AM Jayaradha Natarajan < > [email protected] > > > > > wrote: > > > > > Hi Pradeep, > > > > > > Thank you for detailed information on jUnit. I checked out the sample > as > > > well as Apex and Malhar project. I am getting error in pom.xml file, I > > took > > > myapexapp and fixed it by adding "<pluginmanagement>" tag. > > > > > > I can add more jUnits to sample. Also to start with I can add few best > > > practices in the existing sample. > > > Eg :The RandomNumberGenerator.java file has few values hardcoded. I can > > > move it to configuration details. > > > > > > private int numTuples = 100; > > > > > > private transient int count = 0; > > > > > > Do let me know if I can create jira tickets and assign it to myself and > > fix > > > and send it for code review. > > > Otherwise, I can take some of the existing tickets as well based on > > > priority. Do let me know if you have any tickets related to jUnit. > > > > > > Also, > > > I am getting errors in almost all .pom files with Apex and Malhar > > project. > > > > > > I have java version 1.8.0_60-b27, Maven verion 3.3.3 and using Eclipse > > > IDE. > > > > > > My Apache Apex project showed below error > > > > > > Plugin execution not covered by lifecycle configuration: > > > org.apache.maven.plugins:maven- > > > > > > dependency-plugin:2.1:build-classpath (execution: > > > create-client-mvn-generated- > > > > > > classpath-no-hadoop, phase: generate-resources) > > > > > > > > > Do let me know if you want me to create Jira ticket for the above > error. > > > > > > Thanks, > > > Jayaradha > > > > > > > > > On Tue, Mar 8, 2016 at 10:54 PM, Pradeep Kumbhar < > > [email protected]> > > > wrote: > > > > > > > Hi Jayaradha, > > > > > > > > First of all, Welcome to the Apex-Dev community! > > > > > > > > Happy to see that you want to contribute to testing down the line. > I'll > > > > talk about the "*testing part*" and others in the community can > comment > > > on > > > > the process for release management/automation. > > > > > > > > To start with you can have a look at > > > > http://apex.incubator.apache.org/docs/apex-3.3/ for making yourself > > > > familiar with the Apex. If you have done so already, please visit > these > > > > docs to understand more on testing: > > > > > > > > Apache Apex Development Environment Setup > > > > < > > > > > > > > > > http://apex.incubator.apache.org/docs/apex-3.3/apex_development_setup/#apache-apex-development-environment-setup > > > > > > > > > Testing > > > > < > > > > > > > > > > http://apex.incubator.apache.org/docs/apex-3.3/application_development/#testing > > > > > > > > > > > > > Testing your Operator > > > > < > > > > > > > > > > http://apex.incubator.apache.org/docs/apex-3.3/operator_development/#testing-your-operator > > > > > > > > > > > > > CLI commands <http://apex.incubator.apache.org/docs/apex-3.3/dtcli/ > > > > > > > > > > > > > > Currently apex has junit tests in place for each operator in Apex > > Malhar > > > > library > > > > < > > > > > > > > > > http://apex.incubator.apache.org/docs/apex-3.3/operator_development/#malhar-operator-library > > > > >. > > > > You can extend those tests and submit to the corresponding > repository. > > > > > > > > On the other hand, if you want to test the overall apex platform > > without > > > > writing/using junit tests, there is a command-line utility > > > > <http://apex.incubator.apache.org/docs/apex-3.3/dtcli/> (named as > > > "dtcli"; > > > > soon will be renamed to "apex") which is used to handle all the > > > operations > > > > (e.g. launch, kill-app, list-operators etc.) for an apex application. > > You > > > > can get your hands on this utility and test the platform by > automating > > > > testcases for the commands. > > > > > > > > If you have any more ideas on testing/automation, please share with > us. > > > > > > > > p.s. For more information on documentation, you can visit this link > > > > <http://docs.datatorrent.com/> as the Apex documentation is > currently > > in > > > > process of migrating from this site. > > > > > > > > > > > > On Wed, Mar 9, 2016 at 3:35 AM, Jayaradha Natarajan < > > > [email protected]> > > > > wrote: > > > > > > > > > I am Jayaradha. I would like to contribute to Apache Apex release > > > > > management, release automation and testing to start with. > Eventually > > I > > > > will > > > > > start contributing to development. Please let me know the steps to > > > > > contribute to Release management and testing. > > > > > > > > > > Thanks, > > > > > Jayaradha > > > > > > > > > > > > > > > > > > > > > -- > > > > *regards,* > > > > *~pradeep* > > > > > > > > > >
