RE: Please help evaluation Fineract's readiness for graduation

[sendoro]

+1
Will you have a link just adjacent to e.g. the latest stable link, that 
point to "change log" a.k.a "What new in this release"?


So that immediate one decide  why s/he should upgrade or not?



Regards
Sendoro

On 2017-01-26 03:52, Shaik Nazeer wrote:

Instead of modifying Fineract website on every Fineract releases, can
we link required details to Fineract wiki pages?
For example latest release details can be found at
https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders

Thanks,
Nazeer
-Original Message-
From: Markus Geiß [mailto:mge...@mifos.org]
Sent: 26 January 2017 01:55
To: Ed Cable
Cc: dev (dev@fineract.incubator.apache.org)
Subject: Re: Please help evaluation Fineract's readiness for graduation

Hey Ed,

the Apache Fineract website is a github repo you'll find at Apache's
github mirror.

Simply fork it, create a new branch, do the needed changes and send a 
PR.


Best wishes,

Markus Geiss
Chief Architect
RɅĐɅЯ, The Mifos Initiative

On Jan 24, 2017 15:58, "Ed Cable"  wrote:


Markus,

Nazeer is continuing to work on addressing the areas of concern
related to QU10, QU40, and RE50.

Could you provide me access to the Apache Fineract website to address
CO10 and then for CS10 do we want that on the Apache Fineract website
or the wiki?

Thanks,

Ed

On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski  
wrote:



Agreed.

> On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
wrote:
>
> 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.





--
*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
  

Podling Report Reminder - February 2017

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 22 February 2017, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, February 08).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/February2017

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Please help evaluation Fineract's readiness for graduation

[Markus Geiß]

Hey Ed,

the Apache Fineract website is a github repo you'll find at Apache's github
mirror.

Simply fork it, create a new branch, do the needed changes and send a PR.

Best wishes,

Markus Geiss
Chief Architect
RɅĐɅЯ, The Mifos Initiative

On Jan 24, 2017 15:58, "Ed Cable"  wrote:

> Markus,
>
> Nazeer is continuing to work on addressing the areas of concern related to
> QU10, QU40, and RE50.
>
> Could you provide me access to the Apache Fineract website to address CO10
> and then for CS10 do we want that on the Apache Fineract website or the
> wiki?
>
> Thanks,
>
> Ed
>
> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski  wrote:
>
>> Agreed.
>>
>> > On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
>> wrote:
>> >
>> > 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.
>>
>>
>
>
> --
> *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
>   
>
>

[jira] [Created] (FINERACT-382) In Data Import Tool, unable to download 'Loan Repayment History'

[Santosh Math (JIRA)]

Santosh Math created FINERACT-382:
-

 Summary: In Data Import Tool, unable to download 'Loan Repayment 
History' 
 Key: FINERACT-382
 URL: https://issues.apache.org/jira/browse/FINERACT-382
 Project: Apache Fineract
  Issue Type: Bug
Reporter: Santosh Math
Assignee: Markus Geiss


While trying to download Loan repayment history excel sheet, it is throwing 
following error:

"com.google.gson.stream.MalformedJsonException: Use JsonReader.setLenient(true) 
to accept malformed JSON at line 1 column 29"



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