Nadishka,

I'm glad that you're interested in contributing to an open source project.
That's great!

There are many ways to help.  I think there are so many ways to help that
you can choose one that you find most interesting and try it for a while.
If you find that is not working well enough for you, you can try other ways
to help.

Some of the ways you might assist the Jenkins git-client-plugin and the
git-plugin projects include:

   - Help other users on the Jenkins users mailing list, specifically with
   git client and git plugin questions
   - Compile and experiment with the git plugin
   <https://github.com/jenkinsci/git-plugin> or the git client plugin
   <https://github.com/jenkinsci/git-client-plugin> code
   - Exploratory test git client plugin 2.0.0-beta1 and git plugin
   3.0.0-beta1, from the experimental update center
   <https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/>,
   specifically as it relates to authentication (https, ssh, etc.).  Those
   beta versions have changed the authentication techniques and need deep
   verification before release.  The specific changes are related to
   authentication of submodules, but the changes are large enough that all
   authentication use cases need to be verified
   - Review and verify bug reports (git plugin
   <https://issues.jenkins-ci.org/issues/?filter=14040> and git client
   plugin <https://issues.jenkins-ci.org/issues/?filter=14041>).  When you
   verify a bug report and provide detailed steps to show that the problem is
   repeatable, you save time for others as they can reuse your steps
   - Create automated tests to duplicate bug reports, submit them as pull
   requests to the git plugin <https://github.com/jenkinsci/git-plugin> or
   the git client plugin
<https://github.com/jenkinsci/git-client-plugin> repos.
   An automated test to duplicate a bug report is often the first step to
   understand and fix a bug
   - Improve the javadoc in the git plugin
   <https://github.com/jenkinsci/git-plugin> or the git client plugin
   <https://github.com/jenkinsci/git-client-plugin> and submit the
   improvements as pull requests.  Specifically, the git plugin javadoc has
   many warnings when built with JDK 8.  It would be nice to fix those
   - Write automated tests for interesting statements in the javadoc, after
   checking if those statements are already covered by an existing test
   - Create automated acceptance tests and submit as pull requests to
the acceptance
   test harness <https://github.com/jenkinsci/acceptance-test-harness>.
   This may be especially interesting if you'd like to learn more about
   Jenkins, Selenium (web test automation) and Docker (Linux containers)
   - Create automated tests to verify less used features (like submodules)
   and submit them as pull requests to the git plugin
   <https://github.com/jenkinsci/git-plugin> or the git client plugin
   <https://github.com/jenkinsci/git-client-plugin> repos
   - Create portable Jenkins jobs in docker which verify interesting
   Jenkins use cases, submit them to my collection of Jenkins bug check jobs
   <https://github.com/MarkEWaite/docker/tree/lts-with-plugins> in a Docker
   instance.  This may be interesting if you want to learn more about Docker
   and rapid exploratory testing of Jenkins and its plugins
   - Explore and document the different ways that authentication can fail
   in a Jenkins git project, document those failure modes and the diagnostic
   steps someone might take to identify and resolve problems

I'm sure that is only a small beginning of the ways you can help.  The
Jenkins project is an especially nice place to help because your help can
benefit many people.

Thanks,
Mark Waite

On Mon, Jul 4, 2016 at 11:37 PM nadishka prabhashani <
nadishkaprabhashani...@gmail.com> wrote:

> Hi,
> I am new to open source contribution. I like to contribute Jenkins
> git-client-plugin-master project. But I don't understand from where to
> start.
> So I need your help.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPX603tMk%3DUN2R3Ov29RWOMa4x8M-i-_gdRwnQ3N8Jas0MTOzg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAPX603tMk%3DUN2R3Ov29RWOMa4x8M-i-_gdRwnQ3N8Jas0MTOzg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGLbZb_FKgxRBnrLjMJ5mHCr%3D7vzE2ZwdMijkgmTBX24w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to