Re: [RESULT] [VOTE] Apache Fineract podling graduation

[Roman Shaposhnik]

Congrats and best of luck!

Thanks,
Roman.

On Mon, Mar 27, 2017 at 3:33 AM, Myrle Krantz  wrote:
> Hello Incubator,
>
> The vote to graduate Apache Fineract from the incubator passes with 8
> binding votes,  2 non-binding votes, and no down-votes
>
> +1 binding: John D. Ament, Daniel Gruno, Bertrand Delacretaz, Roman
> Shaposhnik, Niclas Hedhman, Jim Jagielski, Justin Mclean, Tom Barber
> +1 non-binding: Pierre Smits, Markus Geiß
>
> (+1 binding votes not carried over from the pre-proposal-correction
> vote thread: Jean-Baptiste Onofré, Ross Gardler)
>
> We at Apache Fineract deeply appreciate the expressions of good will
> that came together with your votes.
>
> Thank you,
> Myrle
>
>
> On Wed, Mar 22, 2017 at 3:11 PM, Myrle Krantz  wrote:
>> Greetings Incubator,
>>
>> I propose that we graduate Apache Fineract from the Incubator.  The
>> full text of the proposal is below.
>>
>> This is a restarted VOTE thread to correct an error in the resolution
>> from the original thread. Here's the previous VOTE thread:
>>
>> [https://lists.apache.org/thread.html/1cbc738bbb4083e50b7772d5226b88d3fe321b91451303a69dbc4fa8@%3Cgeneral.incubator.apache.org%3E]
>>
>> And here's the DISCUSS thread:
>>
>> [https://lists.apache.org/thread.html/630d3ec22b4f72f827cd817a0a4da5c3c52dee4f96f47a1369f5dc50@%3Cgeneral.incubator.apache.org%3E]
>>
>>
>> Thank you,
>> Myrle Krantz
>>
>>
>> Resolution:
>>
>> Establish the Apache Fineract Project
>>
>> WHEREAS, the Board of Directors deems it to be in the best
>> interests of the Foundation and consistent with the
>> Foundation's purpose to establish a Project Management
>> Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the
>> public, related to a core banking platform that provides a reliable,
>> robust, and affordable solution for entrepreneurs, financial
>> institutions, and service providers to offer financial
>> services to the world's underbanked and unbanked.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Fineract Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>>
>> RESOLVED, that the Apache Fineract Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to a core banking platform that provides a reliable,
>> robust, and affordable solution for entrepreneurs, financial
>> institutions, and service providers to offer financial
>> services to the world's underbanked and unbanked.
>>
>> RESOLVED, that the office of "Vice President, Apache Fineract" be
>> and hereby is created, the person holding such office to
>> serve at the direction of the Board of Directors as the chair
>> of the Apache Fineract Project, and to have primary responsibility
>> for management of the projects within the scope of
>> responsibility of the Apache Fineract Project; and be it further
>>
>> RESOLVED, that the persons listed immediately below be and
>> hereby are appointed to serve as the initial members of the
>> Apache Fineract Project:
>>
>> * Vishwas Babu AJ 
>> * Edward Cable 
>> * Markus Geiss 
>> * Sander van der Heijden 
>> * Ishan Khanna 
>> * Myrle Krantz 
>> * Terence Monteiro 
>> * Adi Nayaran Raju 
>> * Gaurav Saini 
>> * Nazeer Hussain Shaik 
>> * Jim Jagielski 
>> * Michael Vorburger 
>>
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Myrle Krantz
>> be appointed to the office of Vice President, Apache Fineract, to
>> serve in accordance with and subject to the direction of the
>> Board of Directors and the Bylaws of the Foundation until
>> death, resignation, retirement, removal or disqualification,
>> or until a successor is appointed; and be it further
>>
>> RESOLVED, that the initial Apache Fineract PMC be and hereby is
>> tasked with the creation of a set of bylaws intended to
>> encourage open development and increased participation in the
>> Apache Fineract Project; and be it further
>>
>> RESOLVED, that the Apache Fineract Project be and hereby
>> is tasked with the migration and rationalization of the Apache
>> Incubator Fineract podling; and be it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache
>> Incubator Fineract podling encumbered upon the Apache Incubator
>> Project are hereafter discharged.

Re: Permissions to Share Filters in JIRA

[Roman Shaposhnik]

This is weird. You're actually in the committer group as far as JIRA
is concerned.

You sure you were logged in when you did this?

If yes -- your next option is to file and INFRA jira.

Thanks,
Roman.



On Wed, Mar 1, 2017 at 8:28 AM, Ed Cable  wrote:
> Markus or others,
>
> I'm trying to share a saved filter in JIRA to post a public link to issues
> that volunteers can work on but I can't share a filter (neither making it
> public nor sharing with individual users). Is this a permission I can be
> granted or a global setting we can change on our JIRA instance?
>
> Thanks,
>
> Ed
>
> --
> *Ed Cable*
> Director of Community Programs, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   

Re: [MENTORS] Preparing graduation

[Roman Shaposhnik]

I've updated  http://incubator.apache.org/projects/fineract.html

Thanks,
Roman.

On Thu, Feb 23, 2017 at 3:01 PM, Roman Shaposhnik  wrote:
> On Thu, Feb 23, 2017 at 9:48 AM, Myrle Krantz  wrote:
>> Hi Greg, Jim, Roman, and Ross,
>>
>> We of the Apache Fineract community, have reached a consensus that we are
>> ready for graduation.  I've put together a proposal (
>> https://cwiki.apache.org/confluence/display/FINERACT/Graduation+Resolution)
>> to send to the incubator.  Would you please review it and make/suggest any
>> changes you believe still need to be made?
>
> It looks fine, my biggest concerns are:
>* you are not articulating PMC growth during the incubation period
>* looking at 11 PMC vs 12 commiters makes me wonder why single
>  out that one person
>
> Also, I'll update http://incubator.apache.org/projects/fineract.html shortly
>
>> Which one of you would like to submit it to incubator general?
>
> The process is for you to send it first as a [DISCUSS] thread within your own
> community. Give it 5 days or so to stew and unless somebody objects I can
> then open up an IPMC [DISCUSS] and then a [VOTE]
>
>> Thank you all four for getting us this far.
>
> Thanks for listening.
>
> Thanks,
> Roman.

Re: [MENTORS] Preparing graduation

[Roman Shaposhnik]

On Fri, Feb 24, 2017 at 2:13 AM, Myrle Krantz  wrote:
> Hey Roman,
>
> I'll start a thread labeled [DISCUSS].  Here's the most recent state of
> discussions among the community: http://markmail.org/thread/4vzjbopjeozrccka
>  In that thread seven people gave their +1, and there were no objections.

Right, but that's different from them actually reviewing a proposed resolution.

> Here's a log of what happened with respect to the community growth
> 12 committers at induction into incubation
> +1 committer: Jim Jagielski
> -1 committer: Michael Vorburger (couldn't find an apache id for him, when
> assembling the proposal.  Please correct me if I'm wrong.)
> -1 committer: Andrew Dzakpasu (received no response in public or in private
> from him to the above referenced thread.)
> > 11 PMC members
>
> I'd like to keep Andrew on the committer list, and I'd like to add him to
> the PMC, but I don't feel comfortable doing the latter without his
> permission.  The same goes for Michael, except that I don't even know how
> to keep him on the committer list without an apache id.
>
> This all brings me to a question: is the list of initial committers in the
> graduation proposal also the PMC? Or is it possible to start with a
> difference in the list of committers and PMC?

The resolution (and board by extension) doesn't really care that much about
committers -- they care about PMC members.

Now, given the size of your community -- I'd really suggest committers == PMC
(unless you have a strong reason not to).

Thanks,
Roman.

Re: [MENTORS] Preparing graduation

[Roman Shaposhnik]

On Thu, Feb 23, 2017 at 9:48 AM, Myrle Krantz  wrote:
> Hi Greg, Jim, Roman, and Ross,
>
> We of the Apache Fineract community, have reached a consensus that we are
> ready for graduation.  I've put together a proposal (
> https://cwiki.apache.org/confluence/display/FINERACT/Graduation+Resolution)
> to send to the incubator.  Would you please review it and make/suggest any
> changes you believe still need to be made?

It looks fine, my biggest concerns are:
   * you are not articulating PMC growth during the incubation period
   * looking at 11 PMC vs 12 commiters makes me wonder why single
 out that one person

Also, I'll update http://incubator.apache.org/projects/fineract.html shortly

> Which one of you would like to submit it to incubator general?

The process is for you to send it first as a [DISCUSS] thread within your own
community. Give it 5 days or so to stew and unless somebody objects I can
then open up an IPMC [DISCUSS] and then a [VOTE]

> Thank you all four for getting us this far.

Thanks for listening.

Thanks,
Roman.

Re: Missing sign off on report

[Roman Shaposhnik]

I've just signed off. This one is doing super well actually. So it was
just a comination
of FOSDEM and being pretty sick on the way back that prevented me from signing
off on time.

Thanks,
Roman.

On Thu, Feb 9, 2017 at 5:39 PM, John D. Ament  wrote:
> Dear Fineract Podling,
>
> Your quarterly report is submitted and looks pretty good.  However, none of
> your mentors have signed off on it.  Any idea when that might come?
>
> John

Re: Please help evaluation Fineract's readiness for graduation

[Roman Shaposhnik]

On Thu, Jan 26, 2017 at 10:58 AM, Ed Cable  wrote:
> Nazeer,
>
> We do need to link to the latest download which in this case is 0.6.0 from
> https://dist.apache.org/repos/dist/release/incubator/fineract/
>
> Markus - is there a way in which to dynanmically link to the latest release
> or do we always have to manually update.

A lot of projects use semantic symlinks (stable/latest/etc.) to point to actual
release version folders. Of course, you have to update those as part of your
release process.

Thanks,
Roman.

Re: Please help evaluation Fineract's readiness for graduation

[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: [MENTORS] Managing non-Apache code from ASF resources?

[Roman Shaposhnik]

On Tue, Nov 22, 2016 at 4:53 AM, Myrle Krantz  wrote:
> Hi Mentors,
>
> As you know Apache Fineract has a UI project which Mifos did not donate to
> the ASF because it's not licensable in the way the ASF requires.  This has
> been a major communication challenge.  We've split the communication across
> two lists, even though newbies don't understand the difference between the
> UI and the backend code, and even though many discussions impact both.
>
> At the ApacheCon I was asked if we have any volunteer opportunites for
> non-techies.  Mifos does, and among those are translations or documentation
> which are definitely more prevalent in the UI.
>
> So here's the question (s): Is there any objection to us creating tickets
> for non-Apache code in the Apache's Jira, or moving documentation of the UI
> to Apache's Confluence? Is there any reason we should be careful about
> having discussions about the UI on the Apache mailing list?
>
> Because if we could move these kinds of communications into one channel,
> instead of the two it currently is split between, it might help alleviate
> some of the confusion...

Since what gets developed at ASF is basically the engine -- I'd assume that
multiple different UIs would be possible. Hence it seems to me that a more
natural relationship would be the other way around: folks working on Mifos
point at ASF JIRA, etc. Btw, does Mifos have a publicly available, developer
friendly tracker and wiki infrastructure?

Thanks,
Roman.

Re: Twitter account

[Roman Shaposhnik]

On Fri, Nov 4, 2016 at 11:12 AM, Myrle Krantz  wrote:
> FYI,
>
> I just claimed the twitter handle @ApacheFineract for us. If anyone wants to 
> tweet something as a community, let me know.

FWIW: I encourage all of my podlings to give Tweetdeck a try:
https://tweetdeck.twitter.com/

It has a very nice property of allowing other Tweeter accounts to
post tweets for a shared account without knowing said accounts
credentials.

Thanks,
Roman.

Re: Please welcome our newest Committer: Jim Jagielski

[Roman Shaposhnik]

Awesome news!

Roman.

On Thu, Nov 3, 2016 at 6:02 AM, Myrle Krantz  wrote:
> Hello Fineract Community,
>
> I am very pleased to announce that the Fineract PMC has asked Jim Jagielski
> to become a Committer, and he has accepted!
>
> Jim was a co-founder of the Apache Software Foundation and has been a
> member for nearly 22 years.  He has served as one of our mentors in
> incubation since May of this year.
>
> As a senior tech fellow at Capital One, he understands the domain we are
> working in. As a software architect on multiple related projects, he
> understands the technologies we are working with. As a dedicated
> open-source advocate, he understands the environment we are working
> together in.
>
> Congratulations to both Jim and the rest of the Fineract Community are in
> order.
>
> Greets,
> Myrle

Re: Interested in being a mentor for Google Code-In?

[Roman Shaposhnik]

FYI: I'm sure Mifos has its own legal council, but you may be interested
in ASF's legal council take on this program:
http://markmail.org/message/jrytcwoiaky5dny7

Thanks,
Roman.

On Tue, Nov 1, 2016 at 8:43 PM, Nayan Ambali  wrote:
> Sure Ed,
>
> Please use the label "GCI" to tag Google Code-In tasks, refer this link
> 
> for
> reference.
>
> As Ed said, tasks need to me simple, introductory and can be doable within
> 1 to 2 days and need not restrict to only coding, it could be cleaning of
> user manuals, installation guides or other training materials, please refer
> example tasks given by GCI at  "bite-sized tasks
> "
>
> -
> Nayan Ambali
>
>
>
>
> On Wed, 2 Nov 2016 at 05:02 Ed Cable  wrote:
>
>> Hi all,
>>
>> Based on the level of interest in acting as mentors from across the
>> community, I will be applying for GCI as the Mifos Initiative.
>>
>> For all those who've expressed an interest in mentoring, I want to
>> emphasize once more how involved you must be - we need to have hundreds of
>> tasks and be extremely prompt in reviewing completed tasks. If we are able
>> to get accepted, we will be notified on November 7 and will have 3 weeks to
>> build out our initial list of tasks which should be 200+ to start.
>>
>> Ed
>>
>> On Mon, Oct 24, 2016 at 2:25 PM, Ed Cable  wrote:
>>
>> > Hello community,
>> >
>> > We are considering applying to be a mentoring organization for Google
>> > Code-In . Google
>> > Code-In is a program run by Google aimed towards pre-university students
>> > where students compete to complete as many bite-sized tasks (3 to 5
>> hours)
>> > as possible across the following buckets: Code, Documentation/Training,
>> > Outreach/Research, Quality Assurance, or User Interface.
>> >
>> > The GCI timeline can be found at: https://developers.google.
>> > com/open-source/gci/timeline
>> >
>> > Important dates include:
>> > - Mentoring Org Application Deadline: Oct 24
>> > - Accepted Orgs Announced: Nov 7 - this is when we begin listing out all
>> > our tasks
>> > - Students begin working: Nov 28 - this is when students start working
>> and
>> > we must be quick to mentor, and review and close off tasks as completed.
>> > - last date to submit tasks - Jan 16 - students must complete all work on
>> > competing tasks.
>> >
>> > We last participated in 2014 and were very pleased and impressed withe
>> > output of our students who contributed more than 650 hours. However, this
>> > program is very intensive and requires the strong and active commitment
>> of
>> > mentors. Unlike Google Summer of Code where the mentorship is heaviest up
>> > front and then the students work somewhat independently throughout the
>> > summer, Google Code-In is intensive with hands-on engagement the entire
>> > time since we must keep a steady pool of hundreds of open tasks and
>> review
>> > and mentor students as they complete their tasks.
>> >
>> > Before we even consider applying, I want to put a call out to all members
>> > of the community to see if they're interested in mentoring - this would
>> > both involve coming up with tasks, mentoring students as they complete
>> > tasks, and reviewing the completed tasks.
>> >
>> > You don't need to be a developer to participate as the tasks are
>> technical
>> > and non-technical in nature.
>> >
>> > If interested in mentoring, please email me within the next two days or
>> > fill out this quick Google Form - https://goo.gl/forms/V7NDMbbCaHx2VFHI3
>> >
>> > Based on interest level, we'll determine if we apply.
>> >
>> > --
>> > *Ed Cable*
>> > Director of Community Programs, Mifos Initiative
>> > edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>> <+1%20484-477-8649>
>> >
>> > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>> >   
>> >
>> >
>>
>>
>> --
>> *Ed Cable*
>> Director of Community Programs, Mifos Initiative
>> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>> <+1%20484-477-8649>
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>   
>>

Re: Fineract Board Report for November

[Roman Shaposhnik]

On Thu, Oct 27, 2016 at 10:22 AM, Ed Cable  wrote:
> Hi all,
>
> I've started the Board Report for November:
>
> *https://cwiki.apache.org/confluence/display/FINERACT/2016-11+November+Report
> *
>
> Adi will be adding in technical details regarding the release and OpenJPA
> integration. Please review and add any comments/additions that you may
> have. The report is due on November 2 so I will be submitting it at the end
> of my work day on November 1 (PDT)

LGTM!

Thanks,
Roman.

Re: Fineract Board Report for November

[Roman Shaposhnik]

On Thu, Oct 27, 2016 at 10:27 AM, Jim Jagielski  wrote:
> Thx for the report!
>
> I would like to raise the possibility of calling for Graduation
> of Fineract. What does everyone think?

Personally I think having one more clean release would make me feel
more comfortable about casting a +1 graduation vote. Also, sine I remember
this community wanted to produce binary convenience artifacts at some
point, I'd like to see that happen first.

All in all: -0.

Thanks,
Roman.

Re: Interested in being a mentor for Google Code-In?

[Roman Shaposhnik]

On Wed, Oct 26, 2016 at 6:37 AM, Ed Cable  wrote:
> Nayan,
>
> Thank you for making the clarification.
>
> Roman, you were only talking about GSOC correct?

Correct.

> I haven't seen Apache
> participate in GCI before which is Google's program for pre-university
> students.
>
> Is Apache planning to participate in GCI this year? It's of a whole
> different nature than GSOC so I think it would be rather difficult for an
> umbrella organization of Apache's size to coordinate all the small tasks.

If I could find out more about it I can pass that info to ASF
Community Development folks.

Can you please tell me more about GCI?

Thanks,
Roman.

Re: Interested in being a mentor for Google Code-In?

[Roman Shaposhnik]

While having Mifos participate in GSoC would be great,
it doesn't really matter than much for Fineract sine ASF
always participates as well.

Just wanted to let y'all know.

Thanks,
Roman.

On Mon, Oct 24, 2016 at 2:25 PM, Ed Cable  wrote:
> Hello community,
>
> We are considering applying to be a mentoring organization for Google
> Code-In . Google
> Code-In is a program run by Google aimed towards pre-university students
> where students compete to complete as many bite-sized tasks (3 to 5 hours)
> as possible across the following buckets: Code, Documentation/Training,
> Outreach/Research, Quality Assurance, or User Interface.
>
> The GCI timeline can be found at:
> https://developers.google.com/open-source/gci/timeline
>
> Important dates include:
> - Mentoring Org Application Deadline: Oct 24
> - Accepted Orgs Announced: Nov 7 - this is when we begin listing out all
> our tasks
> - Students begin working: Nov 28 - this is when students start working and
> we must be quick to mentor, and review and close off tasks as completed.
> - last date to submit tasks - Jan 16 - students must complete all work on
> competing tasks.
>
> We last participated in 2014 and were very pleased and impressed withe
> output of our students who contributed more than 650 hours. However, this
> program is very intensive and requires the strong and active commitment of
> mentors. Unlike Google Summer of Code where the mentorship is heaviest up
> front and then the students work somewhat independently throughout the
> summer, Google Code-In is intensive with hands-on engagement the entire
> time since we must keep a steady pool of hundreds of open tasks and review
> and mentor students as they complete their tasks.
>
> Before we even consider applying, I want to put a call out to all members
> of the community to see if they're interested in mentoring - this would
> both involve coming up with tasks, mentoring students as they complete
> tasks, and reviewing the completed tasks.
>
> You don't need to be a developer to participate as the tasks are technical
> and non-technical in nature.
>
> If interested in mentoring, please email me within the next two days or
> fill out this quick Google Form - https://goo.gl/forms/V7NDMbbCaHx2VFHI3
>
> Based on interest level, we'll determine if we apply.
>
> --
> *Ed Cable*
> Director of Community Programs, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   

Re: [MENTORS] ApacheCon EU 2016

[Roman Shaposhnik]

On Thu, Sep 29, 2016 at 1:51 AM, Myrle Krantz  wrote:
> FYI: I've gotten my answer. One of my proposals was accepted.

Awesome! See you in Seville!

Thanks,
Roman.

Re: Are incubator mailing list archives indexed and searchable?

[Roman Shaposhnik]

You've got a few options listed here:
   http://apache.org/foundation/mailinglists.html#archives

On top of which there's a new beta UI:
   https://lists.apache.org/list.html?fineract.apache.org

Thanks,
Roman.


On Thu, Sep 29, 2016 at 4:45 PM, Ed Cable  wrote:
> Hi all,
>
> Are they any additional settings that must be configured to enable our
> mailing list archives to be publicly searchable via Google? I have trouble
> having the list archives pop up even if I search for content that's
> verbatim in a thread from the list.
>
> As you know, it's incredibly important that people find these mailing list
> conversations when searching for solutions on Google but I can't seem to.
>
> Thanks,
>
> Ed
>
> --
> *Ed Cable*
> Director of Community Programs, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   

Re: How to Unsubscribe

[Roman Shaposhnik]

On Thu, Jun 9, 2016 at 2:32 PM, Myrle Krantz  wrote:
> Hi Cole,
>
> Either unsubscribe from dev@fineract.incubator.apache.org or set up a
> filter based on the subject line of the e-mail.
>
> If your question is actually: "Why do these mails have to be sent to the
> dev list?" Presumably it's because people subscribed to the dev list are
> typically those who can merge pull requests.

Help is on the way ;-)
https://issues.apache.org/jira/browse/INFRA-12090

Thanks,
Roman.

Re: Read up on Cloud Foundry

[Roman Shaposhnik]

Myrle, quick question: are you saying that CF will be the preferred
runtime for Fineract?

Thanks,
Roman.

On Thu, Jun 2, 2016 at 9:19 AM, Myrle Krantz  wrote:
> Hi all,
>
> Here's an overview of the architecture of CloudFoundry Diego:
>
> https://docs.cloudfoundry.org/concepts/diego/diego-architecture.html
>
> This should help the detail-oriented reader understand how services are
> deployed and balanced within a cloud deployment.  This understanding, in
> turn, should give you a framework for understanding how scalability and
> availability are achieved within a cloud deployment.
>
> Greets,
> Myrle
>
>
> *Myrle Krantz*
> Solutions Architect
> RɅĐɅЯ, The Mifos Initiative
> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
>   

Re: Microservices release question

[Roman Shaposhnik]

On Tue, May 31, 2016 at 6:51 AM, Adi Raju
 wrote:
> My thought would be to keep core microservices as single repo and single 
> release.

FWIW: that'd be my preference as well.

Thanks,
Roman.

Re: [MENTORS] multiple repos for one Apache Product?

[Roman Shaposhnik]

On Thu, May 26, 2016 at 8:42 AM, Markus Geiß  wrote:
>
> 
>> Date: Thu, 26 May 2016 08:38:53 -0700
>> Subject: Re: [MENTORS] multiple repos for one Apache Product?
>> From: ro...@shaposhnik.org
>> To: dev@fineract.incubator.apache.org
>>
>> On Thu, May 26, 2016 at 5:03 AM, Markus Geiß  wrote:
>>> Hey Roman,
>>>
>>> Given that every micro service is implemented as a standalone artifact that
>>> can be replaced, and for this it utilizes its own versioning, I believe it 
>>> would
>>> be more in line with ASF if every service is a repo.
>>>
>>> We will release these independently from each other running their own 
>>> versions.
>>
>> What are you planning as far as compatibility matrix? Will you guarantee that
>> any combination of versions will work together?
>>
>> Thanks,
>> Roman.
>
> We are planing to allow the parallel usage of 2 major versions. Every micro 
> service
> will come with a versioned API and a versioned REST endpoint.
>
> Minor version will be backwards compatible by 'contract'.

I think this could be a good case for separate repos then. Next
question: how many of
these would you consider requesting? Do you see the # growing over time? If yes
by how much?

Thanks,
Roman.

Re: [MENTORS] multiple repos for one Apache Product?

[Roman Shaposhnik]

On Thu, May 26, 2016 at 5:03 AM, Markus Geiß  wrote:
> Hey Roman,
>
> Given that every micro service is implemented as a standalone artifact that
> can be replaced, and for this it utilizes its own versioning, I believe it 
> would
> be more in line with ASF if every service is a repo.
>
> We will release these independently from each other running their own 
> versions.

What are you planning as far as compatibility matrix? Will you guarantee that
any combination of versions will work together?

Thanks,
Roman.

Re: [MENTORS] multiple repos for one Apache Product?

[Roman Shaposhnik]

On Wed, May 25, 2016 at 12:29 AM, Markus Geiß  wrote:
> 
>> Date: Tue, 24 May 2016 20:33:06 -0700
>> Subject: Re: [MENTORS] multiple repos for one Apache Product?
>> From: ro...@shaposhnik.org
>> To: dev@fineract.incubator.apache.org
>>
>> On Tue, May 24, 2016 at 5:27 AM, Myrle Krantz  wrote:
>>> Hi Mentors,
>>>
>>> I asked this question in the thread on microservices, but the e-mail was
>>> long and most of the content was not relevant for you guys so you may have
>>> missed it:
>>>
>>> As far as I can tell the current mode of operation at Apache is one
>>> repository to one product. I would prefer to work with one repository per
>>> service. I believe that would help programmers remain strict about
>>> division of labor between the services, and think more carefully about
>>> interface breaking changes. Is there any reason a product can’t have
>>> multiple repositories?
>>
>> Multiple repos are, of course, permissible. However, the question you should
>> be asking your self are more along the lines of how much of a de-couple
>> release policy AND community participation do you want to have between
>> these projects. Because the thing is, if your repos are independent enough
>> wrt. release schedules AND independent enough regarding who commits
>> to them ASF will be asking a question of breaking you into a set of projects.
>>
>> Does this answer you question?
>>
>> Thanks,
>> Roman.
>
> Hey Roman,
>
> thanks for the answer. ; o)
>
> To provide a little more context. We are currently working on a per-service
> repository approach to reduce unwanted cross service usage of internal
> classes and implementations.
>
> Every business domain will become a micro service and a single repository
> with multiple modules.

The real question you should be asking yourself is how are you going to
release those things. The "contract" that ASF has with the rest of the normal
world is that we release software as tarballs/zips/etc. Source code
repo(s) is an
implementation details. With that in mind, please tell us about your release
strategy for these multiple repos and then we may be able to help refine
this.

Thanks,
Roman.

Re: [MENTORS] multiple repos for one Apache Product?

[Roman Shaposhnik]

On Tue, May 24, 2016 at 5:27 AM, Myrle Krantz  wrote:
> Hi Mentors,
>
> I asked this question in the thread on microservices, but the e-mail was
> long and most of the content was not relevant for you guys so you may have
> missed it:
>
> As far as I can tell the current mode of operation at Apache is one
> repository to one product.  I would prefer to work with one repository per
> service.  I believe that would help programmers remain strict about
> division of labor between the services, and think more carefully about
> interface breaking changes.  Is there any reason a product can’t have
> multiple repositories?

Multiple repos are, of course, permissible. However, the question you should
be asking your self are more along the lines of how much of a de-couple
release policy AND community participation do you want to have between
these projects. Because the thing is, if your repos are independent enough
wrt. release schedules AND independent enough regarding who commits
to them ASF will be asking a question of breaking you into a set of projects.

Does this answer you question?

Thanks,
Roman.

Re: HEADS UP: JIRA email patterns are changing over the weekend

[Roman Shaposhnik]

Unfortunately ASF INFRA is overwhelmed right now. I'll ping them today
and see when we can finalize this
transition.

Thanks for your patience.

Thanks,
Roman.

On Mon, May 23, 2016 at 10:20 PM, Adi Raju
 wrote:
> Is this enabled already?
> I am getting mailer daemon failure notice for email id 
> issues-subscr...@fineract.incubator.apache.org.
>
> Regards,
> Adi
>
> -Original Message-
> From: Myrle Krantz [mailto:mkra...@mifos.org]
> Sent: 23 May 2016 20:15
> To: dev@fineract.incubator.apache.org
> Subject: Re: HEADS UP: JIRA email patterns are changing over the weekend
>
> Thank you very very very much Roman!
>
> Greets from the Voreifel, Germany,
> Myrle
>
>
> *Myrle Krantz*
> Solutions Architect
> RɅĐɅЯ, The Mifos Initiative
> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org 
> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>
>
> On Sat, May 21, 2016 at 5:24 AM, Roman Shaposhnik 
> wrote:
>
>> Hi!
>>
>> to alleviate some of the chattiness concerns of dev@fineract I'll be
>> changing JIRA setup in such a way that the first email for every issue
>> will go to dev@fineract but all the future ones will go to
>> issues@fineract.
>>
>> May sure to subscribe to that other mailing list if you still want the
>> emails.
>>
>> Thanks,
>> Roman.
>>
>

HEADS UP: JIRA email patterns are changing over the weekend

[Roman Shaposhnik]

Hi!

to alleviate some of the chattiness concerns of dev@fineract
I'll be changing JIRA setup in such a way that the first email
for every issue will go to dev@fineract but all the future ones
will go to issues@fineract.

May sure to subscribe to that other mailing list if you still want
the emails.

Thanks,
Roman.

Re: Microservices

[Roman Shaposhnik]

Hi Myrle,

microservices are indeed a nice architectural pattern with an exponentially
growing adoption in the enterprise. It typically leverages some kind of a PaaS
solution to be available for deployment. My current understanding is that your
deployment model today is a traditional appserver. Are you going to change that?
If so, what will be the deployment requirements for the project?

Thanks,
Roman.

On Wed, May 18, 2016 at 2:35 AM, Myrle Krantz  wrote:
> Hi all,
>
> As many of you know Markus and I are thinking through a rearchitecting of
> Fineract into microservices. Markus gave some of you a preview into our
> work at the Mifos tech conference in Amsterdam in March (those of you who
> are interested and weren’t able to attend can check it out on Youtube here:
> https://www.youtube.com/watch?v=iIrnZpoNZ9A -- my apologies for the poor
> video quality)
>
> If you want to get an introductory understanding of what a microservice is,
> this is a good place to go:
>
> http://martinfowler.com/articles/microservices.html
>
> If there is interest, (and I have time), I’ll try to send you more
> information about my ideas as they take shape.
>
> Greets,
>
> Myrle
>
> P.S.  Here’s Spring’s take on this:
> https://spring.io/blog/2015/07/14/microservices-with-spring
>
>
> *Myrle Krantz*
> Solutions Architect
> RɅĐɅЯ, The Mifos Initiative
> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
>   

[jira] [Commented] (FINERACT-3) Move MIFOS issues to FINERACT

[Roman Shaposhnik (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283616#comment-15283616
 ] 

Roman Shaposhnik commented on FINERACT-3:
-

[~mgeiss] I am also curious as to how this migration is going and what help do 
you need. Questions like the one from [~meta-coder] show exactly what the 
problem with this split set up. 

> Move MIFOS issues to FINERACT
> -
>
> Key: FINERACT-3
> URL: https://issues.apache.org/jira/browse/FINERACT-3
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Pierre Smits
>Assignee: Markus Geiss
>
> Currently all open issues reside at https://mifosforge.jira.com.
> In order to draw the contributors into the Fineract project all open issues 
> should be migrated to the JIRA of the project.



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

Re: [VOTE] [FINERACT] 0.1.2-incubating for release

[Roman Shaposhnik]

Hi Nazeer,

thanks for working on the release. VOTE threads on ASF releases
typically follow a particular pattern of what information they communicate
to make the voting process easier. Here's a good example:
 
http://mail-archives.apache.org/mod_mbox/incubator-madlib-dev/201602.mbox/%3CCAKBQfzT6fn1Mzhs9gtEBC6m_pe=U1qzaRLF2rV5=7wpgv-s...@mail.gmail.com%3E

Also, I would highly encourage you to start a wiki page documenting
the process of releases to make next RM's job easier. Once again,
here's a good (if only exhaustive!) example:
 https://cwiki.apache.org/confluence/display/GEODE/Release+proccess

Thanks,
Roman.

On Fri, May 6, 2016 at 5:03 AM, Nazeer Shaik
 wrote:
> Hi all,
>
> We have resolved windows line feeds issue and prepared 0.1.2-incubating
> release for FINERACT. The files are hosted at
>
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.2-incubating/
>
> The git repository is located at
> https://github.com/apache/incubator-fineract/tree/0.1.2-incubating
>
> Again, this is source only release with no binaries, with instructions on
> how to build/test the application.
>
> I call for VOTING for this release and this voting closes by Wednesday
> (11-May-2016) evening.
>
> Thanks,
> Nazeer

Re: [VOTE] [FINERACT] 0.1.1-incubating for release

[Roman Shaposhnik]

One question: are you bumping the version # to 0.1.2-incubating just
because of that?

It is fine to do so, but I wonder whether RC# will help achieve the same without
version # proliferation.

Thanks,
Roman.

On Fri, May 6, 2016 at 5:09 AM, Nazeer Shaik
 wrote:
> Hi Jim,
>
> We have used tar for 0.1.2-incubating release.
>
>
>
> On Fri, May 6, 2016 at 5:31 PM, Jim Jagielski  wrote:
>
>> Would it make sense to consider using tar instead of zip ??
>>
>>
>> > On May 6, 2016, at 1:49 AM, Nazeer Shaik <
>> nazeer.sh...@confluxtechnologies.com> wrote:
>> >
>> > Hi all,
>> >
>> > You are seeing the mentioned issues because we have prepared the release
>> on
>> > windows machine. But we don't see any issues if we prepare same release
>> on
>> > Linux machine. Even the mentioned test case passes without any code
>> change.
>> >
>> > *So we are withdrawing the current release from voting.*
>> >
>> > We will work on 0.1.2-incubating release.
>> >
>> > Thanks,
>> > Nazeer
>> >
>> >
>> > On Wed, May 4, 2016 at 5:26 PM, Jim Jagielski  wrote:
>> >
>> >> Same on OSX. During the unzip the EOL chars are not translated
>> >> to native. According to zipinfo, text files lack the 't'
>> >> flag but are, instead, 'bx'
>> >>
>> >> eg:
>> >>
>> >> -rw-a-- 3.1 fat 1642 bx defN  2-May-16 18:03
>> >> apache-fineract-0.1.1-incubating-src/licenses/jQuery.txt
>> >> -rw-a-- 3.1 fat34388 bx defN  2-May-16 18:03
>> >> apache-fineract-0.1.1-incubating-src/licenses/jszip.txt
>> >> -rw-a-- 3.1 fat 1065 bx defN  2-May-16 18:03
>> >> apache-fineract-0.1.1-incubating-src/licenses/modernizr.txt
>> >> -rw-a-- 3.1 fat 1116 bx defN  2-May-16 18:03
>> >> apache-fineract-0.1.1-incubating-src/licenses/normalize.txt
>> >>
>> >>> On May 4, 2016, at 6:02 AM, Myrle Krantz  wrote:
>> >>>
>> >>> -1
>> >>>
>> >>> I checked the license and notifications.  They look good to me, so I
>> >> tried
>> >>> to build:
>> >>>
>> >>> I'm building on ubuntu, and the instruction wouldn't work for me
>> because
>> >>> gradlew has windows line feeds.
>> >>>
>> >>> Going around that by calling gradle directly I can build with "clean
>> >> war",
>> >>> but if I call just "gradle build" I get a build failure because of a
>> unit
>> >>> test failure.
>> >>>
>> >>> I know that unit test has been failing for a very long time.  If it's
>> not
>> >>> important we need to disable it, so that it doesn't distract from
>> >> important
>> >>> problems.  If it is important than we need to fix it before we release.
>> >>>
>> >>> To get my +1, we need to fix gradlew so that it can build on linux
>> >> machines
>> >>> and we need to have all of our unit tests green.
>> >>>
>> >>> Greets from the Voreifel, Germany,
>> >>> Myrle
>> >>>
>> >>>
>> >>> *Myrle Krantz*
>> >>> Solutions Architect
>> >>> RɅĐɅЯ, The Mifos Initiative
>> >>> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
>> >>>   
>> >>>
>> >>>
>> >>> On Wed, May 4, 2016 at 5:02 AM, Nayan Ambali 
>> >> wrote:
>> >>>
>>  +1
>> 
>>  On Wed, May 4, 2016, 12:43 AM Ed Cable  wrote:
>> 
>> > +1
>> > On May 3, 2016 4:09 AM, "Nazeer Shaik" <
>> > nazeer.sh...@confluxtechnologies.com>
>> > wrote:
>> >
>> >> Hello All
>> >>
>> >> We have addressed issues with Notice & License files and prepared
>> >> 0.1.1-incubating release for FINERACT.
>> >> The files are hosted at
>> >> 
>> >>
>> >
>> 
>> >>
>> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.1-incubating/
>> >>
>> >> This is a source only release with no binaries, with instructions on
>>  how
>> > to
>> >> build/test the application.
>> >>
>> >> We couldn't migrate to Open JPA to avoid dependency on
>> > Hibernate(LGPLv2.1).
>> >> We are referring Hibernate Entity Manager, MySQLDialect,
>> >> annotations(LazyCollection, LazyCollectionOption)
>> >> at run time only and it doesn't include any source or binary from
>> >> Hibernate. We know that we have to get Legal VP approval on the same
>>  and
>> > a
>> >> separate mail thread will be initiated.
>> >>
>> >> I call for VOTING for this release and this voting closes by Friday
>> >> (06-May-2015).
>> >>
>> >> Thanks,
>> >> Nazeer
>> >>
>> >
>> 
>> >>
>> >>
>>
>>

Re: New contributor introduction

[Roman Shaposhnik]

On Mon, May 2, 2016 at 1:34 AM, Daniel Carlson  wrote:
> Hi Roman,
> The easy issues are marked introductory.
> On Jira just search for introductory.

Great!

Thanks,
Roman.

Re: New contributor introduction

[Roman Shaposhnik]

Markus,

great suggestion on biting on the small issues. Quick question
for you (and the rest of the community): do you guys mark beginner
issues in your JIRA? A lot of projects do use a certain label
(like... "beginner" ;-)) which make it super easy for the new comers
to look at the list of what they can tackle.

Thanks,
Roman.

On Fri, Apr 29, 2016 at 7:40 AM, Markus Geiß  wrote:
> Hey Aditya,
>
> welcome to our family. ; o)
>
> You should get started making yourself comfortable with our codebase and try
> to solve some small issues to get a feeling for it.
>
> Don't hesitate to drop us a line if you are stuck or need support in 
> understanding
> what the hack we are doing.
>
> Looking forward to hear and see more from you. ; o)
>
> Best,
>
> Markus
>
> .::YAGNI likes a DRY KISS::.
>
>
> 
>> From: meta1...@gmail.com
>> Subject: New contributor introduction
>> To: dev@fineract.incubator.apache.org
>> Date: Fri, 29 Apr 2016 18:53:29 +0530
>>
>> Hello all,
>>
>> I am an M.Sc. student at Chennai Mathematical Institute, India.
>> As part of Google Summer of Code, I'll be working on integrating UPI[1] 
>> support into Fineract. I am being mentored by Markus Geiß on this project.
>>
>> The NPCI (National Payment Corporation of India) has launched the Unified 
>> Payment Interface which comprises a new protocol. Banks, Payment Banks, 
>> Prepaid Payment Instrument Issuers, and other participating entities, 
>> collectively termed as Payment System Players (PSP) will use this protocol 
>> to interface with the NPCI for Direct Pay, Collect Pay transactions. You can 
>> find the technical specification of UPI on NPCI website[1].
>>
>> [1] UPI technical specification: http://www.npci.org.in/UPI_Documents.aspx
>>
>> Right now, I am only getting started studying Fineract, UPI and how UPI can 
>> fit into Fineract, but on successful completion, Fineract users should be 
>> able to use the services of NPCI such as IMPS (Immediate Payment System), 
>> AEPS (Aadhaar Enabled Payment System), NFS (National Financial Switch) etc. 
>> In other words, they will be able to acquire customers, provide payment 
>> (credit/debit) services to individuals or entities, in India.
>>
>> I found the following pages very useful in understanding Fineract:
>>
>> [2] Platform Software Architecture Document 
>> https://demo.openmf.org/architecture/
>> [3] Mifos X API documentation https://demo.openmf.org/api-docs/apiLive.htm
>> [4] The public demo instance itself at https://demo.openmf.org/
>> [5] Fineract confluence wiki 
>> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
>> [6] Mifos Developer Zone 
>> https://mifosforge.jira.com/wiki/display/MDZ/Welcome+to+the+Zone
>>
>> Other GSoC contributors will also find the above documents useful.
>>
>> It would be nice to have a list of Fineract users in India with their 
>> contact information. Do we have such a list?
>>
>> This Fineract proposal[6] document on the Incubator Wiki explains the 
>> relation between Mifos X and Fineract.
>>
>> [7] https://wiki.apache.org/incubator/FineractProposal
>>
>> Feel free to suggest pointers for this project.
>>
>> --
>> Regards,
>> Aditya Hendre
>

Showcase your project at ApacheCON: consider Podling Shark Tank

[Roman Shaposhnik]

Hi!

I apologize for the wide distribution, but since my email to general@
didn't seem to have reached all of the podling communities, I took
the liberty of direct email. Here's the deal:

If you are (or anybody you know who's passionate about your project is)
going to travel to Vancouver for ApacheCON we've got an awesome
opportunity for you to showcase your project. Even if you don't have
talks scheduled in the regular program, consider doing a lighting talk
at Podling Shark Tank:
 https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank

You've got nothing to lose (in fact, the opposite: you're likely to get
a prize!) and you will get a chance to receive feedback that might
actually help you grow your community and ultimately graduate to the
TLP status. Given our awesome panel of judges:
 * Jim Jagielski
 * Shane Curcuru
 * Milind Bhandarkar
We guarantee this to be a fun and useful event for your community!

Please sign up on the wiki ASAP. The time is running out!

Thanks,
Roman.

P.S. If you have *any* questions whatsoever, but especially if you have
questions on logistics please email me directly.

Fwd: Google Summer of Code 2016 is coming

[Roman Shaposhnik]

FYI.  Please make sure to follow Ulrich's instructions and label the ideas
in JIRA as he's askit to.

It is extremely important for us since GSOC has been a really great
way to grow (and retain!) new members of the community!

I would really encourage at least 2 volunteers from every podling
community to consider mentoring for GSoC. Please reply to me
personally (IN ADDITION TO FOLLOWING THE INSTRUCTIONS
BELLOW) if you are offering to be a mentor.

Really hoping for your help!

Thanks,
Roman.


-- Forwarded message --
From: Ulrich Stärk 
Date: Wed, Feb 10, 2016 at 12:16 PM
Subject: Google Summer of Code 2016 is coming
To: ment...@community.apache.org


Hello PMCs (incubator Mentors, please forward this email to your podlings),

Google Summer of Code [1] is a program sponsored by Google allowing
students to spend their summer
working on open source software. Students will receive stipends for
developing open source software
full-time for three months. Projects will provide mentoring and
project ideas, and in return have
the chance to get new code developed and - most importantly - to
identify and bring in new committers.

The ASF will apply as a participating organization meaning individual
projects don't have to apply
separately.

If you want to participate with your project we ask you to do the
following things as soon as
possible but by no later than 2016-02-19:

1. understand what it means to be a mentor [2].

2. record your project ideas.

Just create issues in JIRA, label them with gsoc2016, and they will
show up at [3]. Please be as
specific as possible when describing your idea. Include the
programming language, the tools and
skills required, but try not to scare potential students away. They
are supposed to learn what's
required before the program starts.

Use labels, e.g. for the programming language (java, c, c++, erlang,
python, brainfuck, ...) or
technology area (cloud, xml, web, foo, bar, ...) and record them at [5].

Please use the COMDEV JIRA project for recording your ideas if your
project doesn't use JIRA (e.g.
httpd, ooo). Contact d...@community.apache.org if you need assistance.

[4] contains some additional information (will be updated for 2016 shortly).

3. subscribe to ment...@community.apache.org; restricted to potential
mentors, meant to be used as a
private list - general discussions on the public
d...@community.apache.org list as much as possible
please). Use a recognized address when subscribing (@apache.org or one
of your alias addresses on
record).

Note that the ASF isn't accepted as a participating organization yet,
nevertheless you *have to*
start recording your ideas now or we will not get accepted.

Over the years we were able to complete hundreds of projects
successfully. Some of our prior
students are active contributors now! Let's make this year a success again!

Cheers,

Uli

P.S.: Except for the private parts (label spreadsheet mostly), this
email is free to be shared
publicly if you want to.

[1] https://summerofcode.withgoogle.com/
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] http://s.apache.org/gsoc2016ideas
[4] http://community.apache.org/gsoc.html
[5] http://s.apache.org/gsoclabels

Re: FW: [DISCUSSION] How to deal with runtime dependencies

[Roman Shaposhnik]

On Wed, Feb 10, 2016 at 12:56 AM, Markus Geiß  wrote:
> Hey all,
>
> We've started a thread at our dev list and forgot to send it to the
> general incubator list too.
> Any opinion is appreciated, you can find the original message below.
>
> Best,
>
> Markus
>
> .::YAGNI likes a DRY KISS::.
>
>> From: markus.ge...@live.de
>> To: dev@fineract.incubator.apache.org
>> Subject: [DISCUSSION] How to deal with runtime dependencies
>> Date: Mon, 8 Feb 2016 14:12:04 +0100
>>
>> Hey all,
>>
>> hope this finds you well.
>>
>> I thought instead of discussing this on top of pull request, because it is 
>> more
>> than just the JDBC driver, it is the right time to create a new thread.
>>
>> We are currently using MySQL's Connector/J and Hibernate's EntityManager at
>> runtime as the JDBC driver and JPA implementation. Our source code is not
>> depending on both.
>>
>> It would create a huge effort to replace both for test and production 
>> environments.
>>
>> The questions is:
>>
>> Would it be compliant with the license policies if we omit them for our 
>> source
>> release, but keeping them for our own integration tests.
>>
>> If somebody is creating a deployable distribution, the expectation is that 
>> whomever
>> is creating the distribution can decide what he wants to use.

The devil is in the details. Can you show a branch with this solution to the
problem prototyped?

Thanks,
Roman.

Re: FOSDEM 2016

[Roman Shaposhnik]

I am. Meet me at either ASF booth or Big Data/Data Sci/HPC devroom

On Thu, Jan 28, 2016 at 12:49 PM, Pierre Smits  wrote:
> Hi all,
>
> Just out of curiosity: is anyone attending the FOSDEM event coming weekend?
>
> Best regards,
> Pierre Smits
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/

Re: January 2016 Report

[Roman Shaposhnik]

On Fri, Jan 1, 2016 at 9:04 AM, Greg Stein  wrote:
> On Fri, Jan 1, 2016 at 10:33 AM,  wrote:
>>...
>
>> How should we deal with the required sign-off? Should we assume consensus
>> if we don't here something and simply add a mentor to the sign-off list?
>>
>
> Prep the report on-list, as you've already done. I gave some feedback, and
> others also had a chance for feedback. ... and as Ross notes: pushing to a
> list/inbox is best, rather than a pull to a website.
>
> Y'all are doing great! The report is very good. ("dude, we just started.
> get off our back" :-P )
>
> As Ross said, don't be overly concerned with sign-off. If us Mentors don't
> sign off, then we're doing it Wrong. (and if that persists, then raise a
> flag)

+1 to the above. On top of which -- I did the sign off thing ;-)

You guys are doing great!

Thanks,
Roman.

Re: How to get our processes bootstrapped

[Roman Shaposhnik]

On Thu, Dec 31, 2015 at 4:49 AM, Myrle Krantz  wrote:
> Hi Fins,
>
> We've been having discussions about what processes we want, but we haven't
> agreed yet on how to institute processes or how to change them once we've
> instituted them.  I've put my thoughts on the matter into a short document
> here:
>
> https://cwiki.apache.org/confluence/display/FINERACT/Changing+Processes
>
> I'd love to read your opinions on the matter too.

In general, my strong advise to any young community is to avoid formal votes
as a plague. At its core ASF runs on natural, not forced consensus. Any time
there's a natural consensus -- you really don't need a vote. Any time
there's a formal vote as a forcing function to a consensus -- you
inevitably end up
creating winners and losers. You really don't need that. At least not while the
community is still young (and even when it grows up -- you don't
*really* need it).

My second point is that documenting practices is good, but creating bylaws or
anything resembling a formal governance documents is typically a bad idea
for the same reasons I've outlined in the first paragraph.

Once again: ASF is a doocracy. You don't need permissions -- not much of them
anyway. You JFDI most of things around here and then if how you did it turns
to be a repeatable pattern you document it (or somebody else does).

Thanks,
Roman.

Re: It appears our infrastructure on-boarding is complete

[Roman Shaposhnik]

Ok, I made sure you have full admin rights. Please on-board others as needed,
but lets try not to proliferate admin rights without need.

Thanks,
Roman.

On Sun, Dec 27, 2015 at 12:05 PM,   wrote:
>
>
> mage ... I only needed to use a different one for JIRA ...
>
>
> Best,
>
>
> Markus
>
>
> Cheerio
>
>
> Markus
>
>
> ::: YAGNI likes a DRY KISS :::
>
>
>
>
>
>
> On Sun, Dec 27, 2015 at 11:43 AM -0800, "Roman Shaposhnik" 
>  wrote:
>
>
>
>
>
> On Sun, Dec 27, 2015 at 3:57 AM, Markus Geiß  wrote:
>> Hey,
>>
>> I've tried to edit the home page or add a new page to our Confluence page, 
>> but I'm lacking permissions.
>>
>> Could somebody provide me with proper permissions please. ; o)
>
> Hm. I thought you were given admin karma on wiki. What's your Confluence ID?
>
> Thanks,
> Roman.

Re: It appears our infrastructure on-boarding is complete

[Roman Shaposhnik]

On Sun, Dec 27, 2015 at 3:57 AM, Markus Geiß  wrote:
> Hey,
>
> I've tried to edit the home page or add a new page to our Confluence page, 
> but I'm lacking permissions.
>
> Could somebody provide me with proper permissions please. ; o)

Hm. I thought you were given admin karma on wiki. What's your Confluence ID?

Thanks,
Roman.

Re: It appears our infrastructure on-boarding is complete

[Roman Shaposhnik]

On Sat, Dec 26, 2015 at 10:27 PM, Markus Geiß  wrote:
> Hey Roman,
> I've tried to fetch your changes, but given that the asf-site branch triggers 
> the web site,
>  I only can fetch it if I'm at the master branch. Fetching it into asf-site 
> gives a non-bare error.

Huh? The following worked for me:
   $ git clone 
https://git-wip-us.apache.org/repos/asf/incubator-fineract-site.git
   $ git checkout asf-site
   $ curl -L https://github.com/apache/incubator-fineract-site/pull/1.patch
> /tmp/1.patch
   $ git am /tmp/1.patch
   $ git commit --amend (adding closes #1)
   $ git push -n
   To https://git-wip-us.apache.org/repos/asf/incubator-fineract-site.git
 03b4368..959288d  asf-site -> asf-site

Thanks,
Roman.

Re: Use of TM and a Powered by Logo

[Roman Shaposhnik]

On Sat, Dec 26, 2015 at 11:55 PM, Markus Geiß  wrote:
> Hey Mentors,
>
> hope this finds you well. : o)
> I have a few questions. ; o)
>
> When should we start to use TM behind our brand,

If you're looking to say Apache™ Fineract® I don't think you can
do that until  Apache Fineract gets registered. That can happen once
you've graduated to the TLP status.

I believe you can say  Apache Fineract (incubating)™ if you really
want that ™ qualification.

> and when is it allowed
> to provide a Powered by Apache logo? I guess we need to be TPL, right?

Correct.

In general, the following document is a pretty useful read around podling
branding requirements: http://incubator.apache.org/guides/branding.html

Thanks,
Roman.

It appears our infrastructure on-boarding is complete

[Roman Shaposhnik]

Hi!

with wiki and GH integration completed I believe
that our infrastructure on-boarding is complete. If
you think otherwise, please update the master ticket:
https://issues.apache.org/jira/browse/INFRA-10968

Now, speaking of GH integration, I wanted to take a
moment an explain what kind of a workflow it enables.

>From now on, anybody can fork our ASF GitHub
mirrors:
   https://github.com/apache/incubator-fineract
   https://github.com/apache/incubator-fineract-site
and send us PRs following the normal GH fokflow.

Those PRs will generate emails to our dev mailing
list and one of you guys will have to prodive feedback
or merge the code in by committing to the ASF Git
repo. That last point is only difference between a classical
GH workflow: there's no way to simply click a Merge
button on GH -- you actually have to commit the change
into the ASF Git.

Speaking of which, when committing don't forget to
include "Closes #xxx" (where xxx is the numeric ID
of the PR) in your commit message. This is the easies
way to tell GH to close the outstanding PR.

To test-drive this new workflow I've created our first
PR: https://github.com/apache/incubator-fineract-site/pull/1
As expected it generated an email to our dev@fineract.i.a.o
mailing list and is now waiting for your feedback. Please
don't let my contribution go to waste ;-)

Finally, I'd really encourage you to document various
ways of how folks can now contribute to Fineract on
the wiki. For a good example take a look at:
https://cwiki.apache.org/confluence/display/HAWQ/Contributing+to+HAWQ

Thanks,
Roman.

Making incubator disclaimer prominently visible

[Roman Shaposhnik]

Guys,

congrats on a nicely looking website! One think
that I've noticed is that the Incubator disclaimer
is now missing. You need to make sure it is
prominently displayed:
http://incubator.apache.org/guides/branding.html

Thanks,
Roman.

Re: Fineract Status Template

[Roman Shaposhnik]

Fixed.

On Sat, Dec 26, 2015 at 7:48 AM, Markus Geiß  wrote:
> Hey all,
>
> hope this finds you well. ; o)
>
> On our status template site 
> (http://incubator.apache.org/projects/fineract.html) the URL for the website 
> content points to an unavailable SVN repository, 
> https://svn.apache.org/repos/asf/incubator/fineract. I guess the correct 
> entry would be the Git repository 
> https://git-wip-us.apache.org/repos/asf/incubator-fineract-site.git.
>
> Best,
>
> Markus
>
> .::YAGNI likes a DRY KISS::.

Subscription to private@fineract

[Roman Shaposhnik]

Hi!

I see a bunch of folks trying to subscribe
to private@fineract with their corporate
email addresses. This is not a good idea.
When an individual leaves a corporation
their emails tends to get forwarded to
their managers who are likely not expected
to be subscribed to private@fineract.

Best thing to do is to subscribe using your
ASF email. Personal emails are ok too.

Please re-subscribe.

Thanks,
Roman.

Fineract has been provisioned on ASF JIRA

[Roman Shaposhnik]

Hi!

looks like we're now all set with the JIRA project
FINERACT. I've made all the mentors and Markus
admins.

Markus, please assign appropriate roles to other
folks via:
  https://issues.apache.org/jira/plugins/servlet/project-config/FINERACT/roles

Thanks,
Roman.

Re: Fineract website

[Roman Shaposhnik]

On Thu, Dec 24, 2015 at 8:26 AM, Greg Stein  wrote:
> Why create an issue? Just work on the site.

I think sometimes it makes sense to create JIRA. See my point in the
other thread.

> Further: don't "claim" the work. Many people should be working on the site,
> or able to work on it. If others want to work on it, then figure out a way
> to include them and work together. Please don't use an issue to claim the
> work and to exclude others from that work.

That's a great point though.

Thanks,
Roman.

Re: [DISCUSS] Git procedure and branching model

[Roman Shaposhnik]

On Thu, Dec 24, 2015 at 9:02 AM, Greg Stein  wrote:
>> Feature branches should be created using the name of the JIRA issue which
>> is to be solved.
>>
>
> If you discuss a feature on the dev@ list, then why create a JIRA issue?
> The community already knows a feature is going to be developed. No need to
> create an issue for it.

I disagree. I find JIRA a much more flexible tool for tracking on going work
on the project. JIRA allows me things like registering for
notifications, integration
with GH pull requests, etc. that are simply too tedious to do using pure mailing
list workflow.

Now, I agree with you that fixing a one liner probably shouldn't
require JIRA -- everything
else just use JIRA as your community TODO list.

In fact, enter *ideas* into JIRA, keep things marked for newbies, etc. etc.
This is, again, where JIRA shines over mailing list -- if somebody new
comes to the community and asks how she or he can help -- it is much
easier to point a JIRA query that would give you exact list of issues
than a pointer to mailing list discussions or wiki.

> Meta: JIRA is busy-work, if used for features.

Not always. I fine it useful, for example, to track evolution of a proposals
or blueprints. And yes, certain feaatures will require those documents
to get buy-in from the community.

>> I suggest to use the CTR[5] (commit then review) model for code
>> modifications, and RTC[6] (review then commit) for package releases. We
>> should not mismatch review with a code review. A code review should be done
>> based on the pull request and prior to commit the changes into the main
>> repository. Once this process has finished, a vote based on lazy consensus
>> is initiated with a message like "This solves issue FINERACT-1234, if
>> no-one objects within three days, I'll assume lazy consensus and commit it."
>>
>
> That is not CTR. Commit straight away. Don't wait. "This looks good to me.
> "
>
> You use the term "object", but that isn't quite right. Commit the change.
> Others can review. If they have *issues* with the change, then you begin a
> discussion. Not an objection.
>
> The goal is to *fix* what was committed. Not to object to it, and roll it
> back. When the commit lands in the repository, then review happens (CTR).
> And based on the review, further changes can be applied.
>
> Remember: this is version control. There is no reason to "object". There is
> no reason to vote. Everything goes into version control with the lowest
> barrier possible. Let people directly commit to a branch, or even to the
> "develop" main branch. Why not? If it breaks something, then fix it. Worst
> case, it can always be backed out.
>
> TRUST each other to commit working code, and fixes, and new features. Trust
> is a huge issue. Please don't erect barriers. Please don't control the
> repository via JIRA. Let people write and commit code. Give them room, and
> let them work. Contributions are *always* a bonus, and very rarely a harm.
> So optimize for the former.

Huge +1 to the above!

Thanks,
Roman.

Re: Fineract project page

[Roman Shaposhnik]

Pierre, thanks for spotting it -- I'll fix this shortly.

Thanks,
Roman.

On Tue, Dec 22, 2015 at 7:25 AM, Pierre Smits  wrote:
> My apologies, I accidentally didn't include the Fineract community.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> -- Forwarded message --
> From: Pierre Smits 
> Date: Tue, Dec 22, 2015 at 4:21 PM
> Subject: Fineract project page
> To: gene...@incubator.apache.org
>
>
> Hi all,
>
> The project page of the Fineract project (incubating) is showing a wrong
> name associated to the id of privileged contributor and mentor rgardler,
> see http://incubator.apache.org/projects/fineract.html
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/

SGA has been receieved

[Roman Shaposhnik]

Hi!

SGA for Fineract code base has been received.
Let me know if you need help importing the code
base into the ASF Git repo.

Thanks,
Roman.