Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Aleks, Could you givean update to everybody on where we stand with this and if you're blocked, what assistance you need to get unblocked. This demo server infrastructure is critical for several of our interns and the work they're doing so the sooner we can have it in place, the better. Thanks for

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Ok, will keep you posted On Mon, May 21, 2018 at 4:19 PM Ed Cable wrote: > Aleks, > > The VM is now up as you probably saw from the ticket in on Infra. Chris > provided this link for getting sudo access: > https://reference.apache.org/committer/opie > > Please update community on your progress a

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Aleks, The VM is now up as you probably saw from the ticket in on Infra. Chris provided this link for getting sudo access: https://reference.apache.org/committer/opie Please update community on your progress as a number of interns are eager to have this available in order to test out the work the

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Thanks Isaac... I'll have a look at it tonight On Mon, May 7, 2018, 1:02 PM Isaac Kamga wrote: > Hi Alexsandar Vikakovic, > > Kindly take a look at this request for the Apache Fineract CN Ubuntu VM >

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hi Alexsandar Vikakovic, Kindly take a look at this request for the Apache Fineract CN Ubuntu VM so you polish it to provide more concrete specifications to the Apache Infrastructure team as requi

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Ok. Thanks Myrle. I will look into those links On Thu, Apr 5, 2018, 1:48 PM Myrle Krantz wrote: > Hi Courage, > > On Thu, Mar 29, 2018 at 4:11 PM, Courage Angeh > wrote: > > The domain microservices rely on Lang microservice to generate RSA keys. > > Lang microservice serves a library like Cass

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hi Courage, On Thu, Mar 29, 2018 at 4:11 PM, Courage Angeh wrote: > The domain microservices rely on Lang microservice to generate RSA keys. > Lang microservice serves a library like Cassandra and Async microservices. > I understand why relying on another program to start is not good but that's >

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hi Viswa, The domain microservices rely on Lang microservice to generate RSA keys. Lang microservice serves a library like Cassandra and Async microservices. I understand why relying on another program to start is not good but that's not the only dependency here. Nevertheless my proposal is we up

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Okay. Thanks On Wed, Mar 28, 2018 at 7:59 PM, Ed Cable wrote: > Thanks Courage for sharing that proposal. We'll keep you posted as GSOC > proposals get evaluated. > > Ed > > On Mon, Mar 26, 2018 at 3:27 AM, Courage Angeh > wrote: > > > Hi Viswa, > > > > I agree with you about Demo Server being

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

I was commenting on a bare minimum spec that Ed was alluding to. With minimum spec (4/16/100), current services (looks like about 12) and 4 infrastructure can be deployed. Typically service start up contributes to higher cpu use. After that really usage and data flow drives cpu usage/memory. I

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Anyone interested in updating the Request to ASF can sign into confluence and use the edit button on the top right hand corner. Am I right about this Myrle ? On Thu, Mar 29, 2018 at 8:12 AM, Isaac

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Thanks for the reminder Myrle. I just moved the content to confluence here . On Thu, Mar 29, 2018 at 7:59 AM, Myrle Krantz wrote: > Hey Isaac, > > Can you move that content into confluence pleas

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hey Isaac, Can you move that content into confluence please? That's our place for documentation collaboration. If you need additional guidance, just ask. Best Regards, Myrle On Thu, Mar 29, 2018 at 7:38 AM, Awasum Yannick wrote: > Hey Isaac, > > I don't have permission to comment on your Fine

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hey Isaac, I don't have permission to comment on your Fineract Infra doc above. On Thu, Mar 29, 2018 at 6:35 AM, Awasum Yannick wrote: > Hello All, > > Isaac and Viswa, I agree with all what you say. > > I use an i7 Processor with 32 GB RAM and 250 GB SSD for testing. Given we > might be runn

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hello All, Isaac and Viswa, I agree with all what you say. I use an i7 Processor with 32 GB RAM and 250 GB SSD for testing. Given we might be running ActiveMQ, Cassandra and MySQL/Mariadb. Nginx will likely be running fims-web-app. And given there will be instances when demo server is running alo

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hello Ed, On Thu, Mar 29, 2018 at 12:27 AM Viswa Ramamoorthy < viswaramamoor...@yahoo.com> wrote: > For the services currently available (as started by demo server), I > estimate 4 core/16 GB/100 GB would be minimum needed. > Viswa, I agree with most of these specifications but I think 4 Cores w

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

For the services currently available (as started by demo server), I estimate 4 core/16 GB/100 GB would be minimum needed. On ‎Wednesday‎, ‎March‎ ‎28‎, ‎2018‎ ‎03‎:‎05‎:‎12‎ ‎PM‎ ‎EDT, Ed Cable wrote: As we discussed earlier, the work to set up and configure the demo server on the Apa

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

As we discussed earlier, the work to set up and configure the demo server on the Apache infrastructure needs to be carried out by committers. Fortunately, Nikhil, Rajan, and Isaac, all committers, have graciously volunteered their time to assist. Can you all please provide your Apache IDs on the i

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Thanks Courage for sharing that proposal. We'll keep you posted as GSOC proposals get evaluated. Ed On Mon, Mar 26, 2018 at 3:27 AM, Courage Angeh wrote: > Hi Viswa, > > I agree with you about Demo Server being largely oriented towards a quick > use but it has a lot of useful data. I have gone

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hi, Spring boot applications should be starting by itself with configurations. Relying on another program to start is not good. My proposal to add RSA key creation from within services is pretty simple; we will reuse existing utility 'RsaKeyPairFactory' to create keys. It will not be intrusive

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hi Viswa, I agree with you about Demo Server being largely oriented towards a quick use but it has a lot of useful data. I have gone through demo server too and I see they introduce RSA keys through external properties so I was thinking changing all the microservices will be a little more stressfu

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hello, I think services need more work to get to deployable state. Demo server is largely oriented towards a quick use in laptops/desktops but using Junit to bootsrap services may result in inconsistencies. I have been reviewing for sometime now. Based on my review, below are the changes needed

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hi Ed, I am willing to assist in configuring the VM requested for Apache Fineract CN. I don't have all the required skills but with commitment and some mentorship, this up and running within a few weeks. At Your Service, Isaac Kamga. On Thu, Mar 22, 2018 at 10:17 PM, Ed Cable wrote: > Com

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Committers, We need a committer who can assist in configuring the VM we've requested for a public demo server for Apache Fineract CN. The massive hardware requirements to build locally have made this a huge barrier to prospective GSOC applicants. We were trying to get this infrastructure set up b

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Aleks, Apache IDs are only available to committers. The guide to becoming a committer is at https://cwiki.apache.org/confluence/display/FINERACT/Becoming+a+Committer I know that the major body of your work related to Fineract isn't yet something the customer was willing to contribute back yet so

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hi Ed, ... how do I get one of those Apache IDs? Anything you need from me? Cheers, Aleks On Mon, Mar 19, 2018 at 3:50 PM Ed Cable wrote: > Thanks Viswa. I will let Myrle and others reply to your input. Through > Apache for this demo infrastructure I think we only have access to one VM. > > M

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Thanks Viswa. I will let Myrle and others reply to your input. Through Apache for this demo infrastructure I think we only have access to one VM. Myrle, Robert, Aleks, Did you see Chris' comments on the Infra ticket? https://issues.apache.org/jira/browse/INFRA-16203 Permalink

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hello, My 2 cents... Assuming a) all of 30+ services (gtihub.com/apache/fineract-cn-*) to be deployed as individual micro servicesb) in a single VM (this is the quickest as more maturity needed for multi VM deployments) c) usage purpose is for integration environment for functional test & demo

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

I'm not sure the process as it's not well documented nor do I know the virtual machine requirements for Fineract CN but I created the ticket and would appreciate others from PMC to put in comments the specifics required for the instance: https://issues.apache.org/jira/browse/INFRA-16203 Thanks, E

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hey Ed, It’s just a matter of putting in an Infra ticket. Anyone on the PMC can do it. Regards, Myrle On Sat 17. Mar 2018 at 08:50 Ed Cable wrote: > Myrle, > > I know you are still slammed but wanted to see if you had the chance to > place this request or if it was something I could do as I wa

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Myrle, I know you are still slammed but wanted to see if you had the chance to place this request or if it was something I could do as I wanted to get Aleks up and going as it's proving problematic for a number of our GSOC aspirants to not be able to fully grok the functionality of Fineract CN wit

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Myrle, Robert Jakech and Aleksander Vidakovic have volunteered to assist. I'll let you move forward with the process and let you provide them the necessary information to allow them to get access to infrstructure and get continuous build process going for the community to have access to a publicly

Re: Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

On Wed, Mar 7, 2018 at 9:25 PM, Ed Cable wrote: > Hi all, I wanted to give this thread a new subject line as it's a valuable > discussion that had gone beyond the original topic. I'm especially thinking > about this in the context of new potential contributors that are coming > along for GSOC that

Reducing Barriers to Entry for New Contributors WAS [ Re: GSoC 2018: Fineract CN SMS & Email Notifications]

Hi all, I wanted to give this thread a new subject line as it's a valuable discussion that had gone beyond the original topic. I'm especially thinking about this in the context of new potential contributors that are coming along for GSOC that won't have the proper hardware to build and deploy. Whi