From Fedora Project Wiki

m (updates on how I could contribute to those willing to innovate using Fedora)
m (udpates in the presented content.)
Line 1: Line 1:


<h3>Ambassador - Henry Jurkauskas</H3>
As a Cloud architect with a ‘carte blanche’ authority to transform clients’ estates to benefit their strategic enterprise visions, I found that counterbalancing between innovations and a consequential risk, due to the little known market reaction to the ‘new thing’, has already paid off in multiple client engagement cases. Looking at what’s the next technological trade-off (known for unknown) in <b>Fedora </b>development acts as a navigator for me to make right technological decisions today knowing that the trade-off will eventually be reflect in the follow-up RHEL editions. I am Henry Jurkauskas  <b> an ambassador </b> to evangelise on why, where and how this platform can favour those who are willing to disrupt the ‘status quo’ or define the roadmap from ‘tabula rasa’ state to the target state implementation. Reach me out for the case study, advise, support in reasoning good choice. <b>Open source </b> is not just a product development model, its a mindset which was introduced to stop reinventing the wheel and build on what's already present.
As a Cloud architect with a ‘carte blanche’ authority to transform clients’ estates to benefit their strategic enterprise visions, I found that counterbalancing between innovations and a consequential risk, due to the little known market reaction to the ‘new thing’, has already paid off in multiple client engagement cases. Looking at what’s the next technological trade-off (known for unknown) in Fedora development acts as a navigator for me make right technological decisions today knowing that this will eventually reflect in the next RHEL edition as a follow up. I am Henry Jurkauskas  <H3>
an Ambassador </H3> to evangelise on why, where and how this platform can favour those who are willing to disrupt the ‘status quo’ or solution from ‘tabula rasa’ to the defining the future.


Should you need a case or success story example to define your DC transformation roadmap reach me out via below contact
== Contact ==
== Contact ==
* ergeneral[X]sdf.org where X stands for @.  
* ergeneral[X]sdf.org where X stands for @.  
Line 11: Line 8:
= Area of Interest =
= Area of Interest =
Stretched hybrid clouds, Big data, AI
Stretched hybrid clouds, Big data, AI
== RSA public key==
<pre>
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA4Tfp3lItA4dAeESaEhxXB33YQJD6/dvYYwL1aV1W/E5Pa1Cy0Lw9b9F2StstIQSKxYMQbFuqD7q5YmAcFJI5yLzCuJkBBEuv2HWacZjURI0JiezQFgFmAbyP7ffcjyaX5fesxE7zQ5PxYt8Afq102vBXGvoJqe1e/0cel0H0aT9PVPQQacq3CGcLSAc2xuxdShDjv+wK88ZoKfHgMsvf+TZW1lGUO48VyEIYnOg5xEPsWhT7UQUPeRVq6Vz1rWXcQh+S6Y0pTvEcko/CrjiiAqyE6DP7ot/68eqc577Q753jArhbxfvLuRz9+UHIlHx8qEVw8n8UPNSUOwPpzBQKw== sinonime@ppee
</pre>

Revision as of 20:10, 22 April 2018

As a Cloud architect with a ‘carte blanche’ authority to transform clients’ estates to benefit their strategic enterprise visions, I found that counterbalancing between innovations and a consequential risk, due to the little known market reaction to the ‘new thing’, has already paid off in multiple client engagement cases. Looking at what’s the next technological trade-off (known for unknown) in Fedora development acts as a navigator for me to make right technological decisions today knowing that the trade-off will eventually be reflect in the follow-up RHEL editions. I am Henry Jurkauskas an ambassador to evangelise on why, where and how this platform can favour those who are willing to disrupt the ‘status quo’ or define the roadmap from ‘tabula rasa’ state to the target state implementation. Reach me out for the case study, advise, support in reasoning good choice. Open source is not just a product development model, its a mindset which was introduced to stop reinventing the wheel and build on what's already present.

Contact

  • ergeneral[X]sdf.org where X stands for @.
  • 'PGP key' : [1]

Area of Interest

Stretched hybrid clouds, Big data, AI