The currently active projects is a good question (and as I'm not that
active myself, let's see which are active).
When we were all using Subversion it was easier, but now some components
are on Git and some Subversion.
Looks like four are on Git (Math, Lang, Compress and SCXML). I would
assume, based on recentness of the migrations, that all four are active.
For the rest, you can see their most recent activity by sorting by Age on
this SVN directory (the top 20 would imply _possibly_ active to me):
https://svn.apache.org/viewvc/commons/proper/?sortby=date#dirlist
And for the Sandbox:
https://svn.apache.org/viewvc/commons/sandbox/?sortby=date#dirlist
There only the one (inject) looks like it might be active.
Unless you use one of the projects, the next issue you hit is what to work
on.
Each has a JIRA project. You can find the list of them here:
https://issues.apache.org/jira/secure/BrowseProjects.jspa#10260
Click on a project, click issues, click View Issues and browse the open
issues. There will be many that are open ended, and some will be that way
because there's no real good solution, so early on the recommendation is to
look for issues that are concretely described.
For example - Sebb and I worked on this one:
https://issues.apache.org/jira/browse/LANG-1143 - I think it's a case of
finishing the work (we're both stretched all over the place) and might be a
good one to work on. IMO Lang does tend to have the more easily
approachable first items (but I'm biased :) ).
Contribution process can be via GitHub (
https://github.com/apache/commons-lang) or via attachments to a JIRA issue
(generated using svn diff or git diff).
https://commons.apache.org/patches.html has more about patches, common
sense stuff, but the type of thing you might not think about while heads
down on a first contribution.
Lastly - ask questions. One of the hardest habits to lose when getting into
Open Source (imo; and I'm making an assumption that those interested in
participating are often fairly new to open source teams) is that feeling
that a question will lead to shame. A question, especially one that
mentions the web page you looked at and didn't find an answer on, often
identifies a need for better documentation. Having asked the question, make
your next step a contribution to make it so the next person doesn't need to
ask.
To that end - https://commons.apache.org/site-publish.html appears to be
the documentation for getting the site. Use this JIRA for patches/issues in
the site: https://issues.apache.org/jira/browse/COMMONSSITE
Hope some of that helps :)
Hen
On Wed, Sep 2, 2015 at 8:10 AM, Arsen Babakhanyan <arsen...@gmail.com>
wrote:
> Hi everybody,
> I am interested in participating in some projects, but need some help.
> I don't know how to find currently active projects that are in development
> or a project that needs help at all and the second problem help with
> getting started as i am new here. (going to be :) )
>
