I see. Thanks for the direction. I’ll try to start heading that direction over 
the next two days. Need to also release commons-parent and 
commons-release-plugin, but those should be fairly easy.

Cheers,
-Rob

> On Sep 29, 2020, at 1:35 PM, Aleksandar Vidakovic <[email protected]> 
> wrote:
> 
> ... just my 2 cents: I think we can always use more tests... in terms of 
> specific features: we were a little bit short on time to fix a couple of 
> issues related to OAuth in the last release. There's e. g. 
> https://issues.apache.org/jira/browse/FINERACT-1012 
> <https://issues.apache.org/jira/browse/FINERACT-1012> which is related to 
> recent deprecations on the side of Spring Security.
> 
> I think we will soon(-ish) start preparing for release 1.5.0... there are a 
> couple of feedbacks about certain features that are broken ("notes")... so 
> you could just jump on that wagon.
> 
> And then finally: there's our security report page that could use some help 
> https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+Security+Report.
>  
> <https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+Security+Report.>..
>  either by addressing/fixing one of the issues listed there... or you could 
> integrate e. g. this Gradle plugin 
> https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/index.html
>  
> <https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/index.html>
>  so that we can get a better and more recent view on this front.
> 
> On Tue, Sep 29, 2020 at 7:09 PM Rob Tompkins <[email protected] 
> <mailto:[email protected]>> wrote:
> Curious where you guys think the best place to start contributing might be. I 
> heard that you could stand to have more documentation. I’ve found that either 
> documentation or unit tests are the best places to start contributing. That 
> said, I figure that you guys, knowing the codebase better than I do, might 
> have a specific place that you want help.
> 
> Cheers,
> -Rob

Reply via email to