Re: Please help evaluation Fineract's readiness for graduation

2017-01-06 Thread Roman Shaposhnik 
On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable  wrote:
> Could our Apache Fineract mentors please provide some guidance on a couple
> of the areas we need to improve upon:
>
> QU10 "*The project is open and honest about the quality of its code.
> Various levels of quality and maturity for various modules are natural and
> acceptable as long as they are clearly communicated." -*
>
> Do you have any other projects you could point to that have strong
> transparent measures of quality and maturity clearly available We want to
> follow best practices and adopt similar to display at
> http://fineract.incubator.apache.org

Regular deployment of tools like Findbugs is a good indication that you take
this requirement seriously.

> *QU30: The project provides a well-documented channel to report security
> issues, along with a documented way of responding to them.*
>
> Currently we just link to: http://www.apache.org/security/ Are we able to
> do as other projects at http://www.apache.org/security/projects.html or is
> a private channel not something we can set up till we're out of
> incubation.  If we can move forwarde, I'd suggest we have a security page
> on our site, document and fix known vulnerabilities and then provide clear
> instruction on reporting vulnerabilities to a private channel like
> secur...@fineract.incubator..apache.org

This is less about security@fineract vs.  http://www.apache.org/security/
and more about the community being ready for when the first 0 day
hits either of those. Being ready is a combination of tribal knowledge,
wiki recommendations and a release policy that would allow you to patch
at a drop of a hat.

Thanks,
Roman.

Re: Please help evaluation Fineract's readiness for graduation

2017-01-06 Thread Ed Cable 
Could our Apache Fineract mentors please provide some guidance on a couple
of the areas we need to improve upon:

QU10 "*The project is open and honest about the quality of its code.
Various levels of quality and maturity for various modules are natural and
acceptable as long as they are clearly communicated." -*

Do you have any other projects you could point to that have strong
transparent measures of quality and maturity clearly available We want to
follow best practices and adopt similar to display at
http://fineract.incubator.apache.org

*QU30: The project provides a well-documented channel to report security
issues, along with a documented way of responding to them.*

Currently we just link to: http://www.apache.org/security/ Are we able to
do as other projects at http://www.apache.org/security/projects.html or is
a private channel not something we can set up till we're out of
incubation.  If we can move forwarde, I'd suggest we have a security page
on our site, document and fix known vulnerabilities and then provide clear
instruction on reporting vulnerabilities to a private channel like
secur...@fineract.incubator..apache.org



On Wed, Jan 4, 2017 at 12:11 AM, Sander van der Heyden <
sandervanderhey...@musonisystem.com> wrote:

> Hi Myrle,
>
> Thanks for doing the first round of this, I've added my name to a lot of
> your evaluations and extended a few as well. I've still left a few blank,
> as I am not 100% clear on them and would therefore prefer to wait for a few
> more opinions on them.
>
> Thanks,
> Sander
>
>
>
> Sander van der Heyden
>
> CTO Musoni Services
>
>
>
>
> Mobile (NL): +31 (0)6 14239505
> Skype: s.vdheyden
> Website: musonisystem.com
> Follow us on Twitter!  
> Postal address: Hillegomstraat 12-14, office 0.09, 1058 LS, Amsterdam,
> The Netherlands
>
> On 3 January 2017 at 12:21, Myrle Krantz  wrote:
>
> > Hi all,
> >
> > Apache has a project maturity model which can be used to evaluate
> readiness
> > for graduation.  It's a guide rather then a set of requirements, but I
> > believe we can use it.  I've used it to create a page evaluating *our*
> > readiness:
> >
> > https://cwiki.apache.org/confluence/display/FINERACT/Maturity+Evaluation
> >
> > The evaluation is not finished.  Apache Fineract needs the following from
> > you:
> > * Evaluate the criteria which I did not evaluate.  I've highlighted them
> in
> > blue.
> > * Check the evaluation of the criteria which already have one.  If your
> > evaluation differs, document your disagreement. If you agree with the
> > evaluation, add your committer id.
> > * On those criteria in which Apache Fineract still has work to do before
> > graduation (highlighted in red), check if you can do that work.  I've
> left
> > at least one low-hanging fruit in there.  Who will find it first?
> > * If you feel we need to add a criteria, add it, and explain why.
> >
> > Once we have met all criteria, we should propose ourselves for
> graduation.
> >
> > Looking at our current state, we've made tremendous progress since we
> > entered incubation in December 2015, and I'd like us to make the push for
> > those last few bits in 2017.  I believe that, if we as a community wish
> to,
> > we can achieve this in the first quarter of this year.
> >
> > Greets,
> > Myrle
> >
> >
> >
> > *Myrle Krantz*
> > Solutions Architect
> > RɅĐɅЯ, The Mifos Initiative
> > mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
> >   
> >
>



-- 
*Ed Cable*
Director of Community Programs, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
<(484)%20477-8649>

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org

RE: [Mifos-developer] APPROVE COLLECTION SHEET ERROR

2017-01-06 Thread Zayyad A. Said 
Hi Santosh,

 

I have noticed that you cannot approve any item in checker inbox and not just 
collection sheet.

 

Try approving these items:

 

https://demo.openmf.org/#/viewcheckerinbox/6755 

 

https://demo.openmf.org/#/viewcheckerinbox/4776

 

https://demo.openmf.org/#/viewcheckerinbox/6152 

 

This creates a very big problem that MFIs will have to completely disable Maker 
Checker functionality.

 

I strongly believe there is need for an IMMEDIATE fix.

 

Regards;

 

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email: zay...@intrasofttechnologies.com 

 

Email banner

 

From: Santosh Math [mailto:sant...@confluxtechnologies.com] 
Sent: 06 January 2017 13:09
To: dev@fineract.incubator.apache.org; Zayyad A. Said
Cc: Mifos software development
Subject: Re: [Mifos-developer] APPROVE COLLECTION SHEET ERROR

 

Hi Zayyad,

 

We noticed this is major  issue related to 'Maker-Checker' and have already 
raised the issue on Jira.

 

https://issues.apache.org/jira/browse/FINERACT-364 

 

Meanwhile, Is it possible, you can submit collection sheet disabling maker 
checker? 

 

OR

 

Right now, you are submitting collection sheet selecting the center but not 
selecting  the groups individually so that all groups collection sheet  can be 
submitted in one go.. Can you try with selecting center as well as group in 
collection sheet  and submit  it?  I think it should work..

 

On Wed, Jan 4, 2017 at 5:04 PM, Zayyad A. Said 
 wrote:

Hi Sampath,

 

Yes this is checker inbox.

 

Here are the steps:

 

1.   Enable maker checker tasks for SAVE COLLECTIONSHEET and also 
SAVEORUPDATEATTENDANCE MEETING.

2.   Book JLG loans for a group.

3.   Use collection sheet module to post repayments for this group (it will 
save successfully).

4.   Open the transaction in checker inbox and click on approve (this is 
where it throws the error).

 

Let me know if you are successful.

 

Regards;

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email: zay...@intrasofttechnologies.com 

 

 

From: Sampath Kumar G [mailto:samp...@confluxtechnologies.com] 
Sent: 04 January 2017 14:29
To: Mifos software development
Cc: dev@fineract.incubator.apache.org
Subject: Re: [Mifos-developer] APPROVE COLLECTION SHEET ERROR

 

Hi Zayyad,

 

The attached screenshot looks like checker inbox. Are you submitting the 
collection sheet by maker-checker task? If yes, can you give the steps which 
you had followed and also relevant screenshots?




Thanks and regards,

Sampath

 

 

​

  Conflux Technologies Pvt Ltd 

#304, 2nd Floor, 7th Main Road 

HRBR Layout 1st Block

Bengaluru, Karnataka, 560043 INDIA

  

 

 

Disclaimer: The information contained in this e-mail message and any 
files/attachment transmitted with it is confidential and for the sole use of 
the intended recipient(s) or entity identified. If you are not the intended 
recipient, please email:   
supp...@confluxtechnologies.com and destroy/delete all copies and attachment 
thereto along with the original message. Any unauthorised review, use, 
disclosure, dissemination, forwarding, printing or copying of this email or any 
action taken in reliance on this e-mail is strictly prohibited and is unlawful. 
The recipient acknowledges that Conflux Technologies Private Limited or its 
subsidiaries and associated companies are unable to exercise control or ensure 
or guarantee the integrity of/over the contents of the information contained in 
e-mail transmissions. Before opening any attachments, please check.

 

On Wed, Jan 4, 2017 at 4:18 PM, Zayyad A. Said 
 wrote:

Devs,

 

One of our MFI partners is getting an error when approving collection sheet.

 

Please find attached screenshot of the error.

 

Kindly advise if you are able to approved saved collection sheet in 16.12.01.

 

Regards;

 

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email: zay...@intrasofttechnologies.com 

 

 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Mifos-developer mailing list
mifos-develo...@lists.sourceforge.net
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer

 





 

-- 

Thanks  and Regards

Santosh 

QA Team

Conflux Technologies Pvt Ltd, Bengaluru

Skype:santoshmath99

Re: [Apache Fineract] Addressing review comments of 0.5.0-incubating release

2017-01-06 Thread Myrle Krantz 
Hey Nazeer,

*I'm* sorry for expressing myself in a confusing manner.  I didn't mean to
imply you had done something wrong.  You haven't.

When I said "We shouldn't automatically disregard [our mentors] advice", I
didn't mean to imply that you were.  I was just setting the context for the
suggestion that we *do* disregard their advice, but only on maven
artifacts, and top-level RAT checks for the upcoming version.

Hopefully I haven't made things even more confusing...

Greets,
Myrle


*Myrle Krantz*
Solutions Architect
RɅĐɅЯ, The Mifos Initiative
mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
  


On Fri, Jan 6, 2017 at 8:22 AM, Nazeer Shaik <
nazeer.sh...@confluxtechnologies.com> wrote:

> Thank you Myrle. Sorry I was not disregarding mentors review comments
> rather I was trying to get some help/opinion from all of you for the next
> release.
> I will go ahead with releasing 0.6.0-incubating today by mentioning the
> same.
>
> Thanks,
> Nazeer
>
> *Principal Architect, **Conflux Technologies Pvt Ltd
> *
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>
>
> Disclaimer: The information contained in this e-mail message and any
> files/attachment transmitted with it is confidential and for the sole use
> of the intended recipient(s) or entity identified. If you are not the
> intended recipient, please email: supp...@confluxtechnologies.com and
> destroy/delete all copies and attachment thereto along with the original
> message. Any unauthorized review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies are unable to exercise control or
> ensure or guarantee the integrity of/over the contents of the information
> contained in e-mail transmissions. Before opening any attachments, please
> check.
>
> On Wed, Jan 4, 2017 at 6:32 PM, Myrle Krantz  wrote:
>
> > Hey Nazeer,
> >
> > Keep in mind, that, if it's not about the license, you can usually treat
> > what our mentors and reviewers says as advice that we can follow or not.
> > We shouldn't automatically disregard their advice, because that would
> > impact their willingness to review our releases.  But if the effort is
> > large, and the benefit small, no one is going to be offended if we say
> > "no", or "later".  If our mentors aren't responding on this issue, it's
> > likely because it's not very important to them.
> >
> > So we shouldn't let those points block our next release, but rather treat
> > them like any other ticket.
> >
> > Greets,
> > Myrle
> >
> >
> >
> > *Myrle Krantz*
> > Solutions Architect
> > RɅĐɅЯ, The Mifos Initiative
> > mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
> >   
> >
> >
> > On Fri, Dec 30, 2016 at 11:12 AM, Shaik Nazeer <
> > nazeer.sh...@confluxtechnologies.com> wrote:
> >
> > > Hi Fineract mentors,
> > >
> > >
> > >
> > > After analysing a bit, integrating RAT to top level directory is
> > difficult
> > > as our complete build scripts are under sub directory.
> > >
> > > Either we need to add Gradle scripts to top level directory also or
> move
> > > the
> > > complete source tree from Fineract-provider to top level directory.
> > >
> > > I feel above two approaches area not good. So do you have any
> suggestions
> > > on
> > > this or shall I try to proceed with next release by adding "How to run
> > RAT"
> > > in readme without integrating RAT to top level directory?
> > >
> > >
> > >
> > > And I don't understand how maven is going to help here as we are giving
> > > complete deployable war file.
> > >
> > >
> > >
> > > Can you let me know your opinion on this please.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Nazeer
> > >
> > > From: Shaik Nazeer [mailto:nazeer.sh...@confluxtechnologies.com]
> > > Sent: 29 December 2016 18:27
> > > To: dev@fineract.incubator.apache.org
> > > Subject: [Apache Fineract] Addressing review comments of
> 0.5.0-incubating
> > > release
> > >
> > >
> > >
> > > Hi all,
> > >
> > >
> > >
> > > I have created a JIRA task to address all review comments of
> > > 0.5.0-incubating release.
> > >
> > > https://issues.apache.org/jira/browse/FINERACT-357
> > >
> > >
> > >
> > > I can handle all review comments except maven related. Does anybody
> know
> > > how
> > > to include maven repo as part of Fineract release?
> > >
> > >
> > >
> > > Thanks
> > >
> > > Nazeer
> > >
> > >
> >
>

[jira] [Created] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error

2017-01-06 Thread Santosh Math (JIRA) 
Santosh Math created FINERACT-364:
-

 Summary: Submitting Collection Sheet through Maker Checker 
Throwing Error
 Key: FINERACT-364
 URL: https://issues.apache.org/jira/browse/FINERACT-364
 Project: Apache Fineract
  Issue Type: Bug
  Components: Loan
Reporter: Santosh Math
Assignee: Markus Geiss
Priority: Blocker
 Attachments: 1.png, 2.png

1. Enable Maker Checker in System>>Configuration.
2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select the 
center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
3. Disburse JLG Loan to a client.
4. Go to collection sheet and fill the details and select the center name but 
don't select the group name.
5. Click  on Submit button, which goes to Checker Inbox. 
6. When you try to approve it , it throws the error,

"The parameter `loanTransactions` has been passed and is not supported for this 
request.
The parameter `SavingsTransactions` has been passed and is not supported for 
this request."  
Check the attached file/screenshots. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)