Picture of the author
Topic :
Welcome Iffort
Thread Created at Aug 26th 2021, 12:03:11 am | Started by Brent_Allsop
Number of Post in this thread: 5
Please Sign In to comment on this Thread
Iffort replied 2 years ago (Aug 26th 2021, 3:37:44 am)

Absolutely. Please go ahead and make changes to the statement. I was also thinking if I could edit the statement and make the formatting right but I did not get any option.

Iffort replied 2 years ago (Aug 26th 2021, 3:35:17 am)

Thank you Brent. Yes, I am receiving the notifications now. Also, I am getting to learn more and more about canonizer as I am using it.

It's a pleasure to know that you are liking my proposal. Yes, we are on same page as far as our understanding of "Service oriented architecture" is concerned. To detail it out a bit more - Firstly, we will need to break our code architecture from Monolithic design to a design which is more service based. Secondly, we need to distribute these services into "Micro Services" so that they can work independently. 

Regarding "$15 Design Sprint or Discovery", yes, I noticed that a camp is created for that. However, I am not able to see that camp right now now I am able to change the parent camp. Could you please provide more details about collaborative design process?

Brent_Allsop replied 2 years ago (Aug 26th 2021, 2:57:27 am)

Sorry, the link to our wiki markup is in that post is broken, and the ability to edit posts is still on our to do list.

You can get to the wiki markup from the "help" button on the side bar.

Or, here is a working link to the wiki markup help page.


Brent_Allsop replied 2 years ago (Aug 26th 2021, 2:51:02 am)

Hi Sunny,

I’m studying your proposal in more detail, and it is very exciting, exactly the design I’ve been dreaming about, with Kubernetes microservices and all.  In our item #6, we mention “services-oriented architecture” which I think of as what you are calling microservices.  I would think the first one we would create would be the core “canonizer” service, as described there?  Later on we would have one to manage identity, and a very secure micro service core to that, to handle anonymous nick name identities and passwords (everything else but this one being open), and stuff like that.  Does that sound correct?

 

Do you mind if I wiki propose some formatting to your camp statement, like a title, hotlinks, and stuff?  I’m familiar with our wiki markup, so that would be easy for me to do.  If you don’t like what I submit, as a supporter, you can object, then we can fix it to be what you agree with, then submit it again?

Brent_Allsop replied 2 years ago (Aug 26th 2021, 12:10:27 am)

Welcome Sunny Jindal, and thanks for supporting your camp.  This is a post to the forum for the Iffort camp.  As a supporter, you should now receive notifications when posts are made to this forum, and the parent agreement camp forum.


We are meeting with other companies, and showing them your great camp example of what they need to do.  Thank you for making our job easier by stepping up to do this.  As you can see, I (and people delegating to me) are already supporting your camp.  But this is just my current support, so things may change in the future.  but you are the first out of the block, so have a good head start.

 

You might have noticed, we created a “$15K Design Sprint or Discovery” phase super camp.  We are offering $15K to all companies to participate in a one-month collaborative design process, before we make any decisions.  We also may select multiple companies.  Your company certainly meets the requirement for receiving this initial $15K payment.  You already have my e-mail, so feel free to send me instructions for how we might send this $15K to you, to get this started.  Also, if you could go to the “Manage/Edict Camp” button in the camp record at the bottom of your “Iffort Camp”, then you could change the parent camp to your camp, from the current agreement camp, to be the $15K Design Sprint” super camp.  This would put your camp into a supporting sub camp position to that super camp, indicating Iffort's participation in this $15K seeding process.


Thanks, Brent Allsop