Date: Thu, 28 Mar 2024 20:50:49 +0000 (UTC) Message-ID: <766588761.3351.1711659049262@aws-us-west-2-tungsten-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3350_1819386130.1711659049261" ------=_Part_3350_1819386130.1711659049261 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The election process occurs in two phases; the Nomination phase, and the= Election phase.
Individuals interested in running for this position must update this wik= i page with their biography and statement of intent on why you would be a g= ood person to hold this position.
The nomination phase begins and will conclude on 17:00 PDT. = ; Two calendar weeks from the time of the announcement.
If there are multiple nominees: A Condorcet election will be initia= ted by the LF using the CIVS voting system. All TSC members will rece= ive an invitation to vote. In the case of multiple candidates the timing is= as follows:
The Tungsten Fabric Community Release Manager guides the Project to the = timely delivery of regular software releases, follow-on stable releases, an= d manage any ad-hoc releases as required. The Release Manager works directl= y with the community to formulate a release plan (currently under developme= nt) from inception through approval by the TSC. Once approved, the Release = Manager then guides the Tungsten Fabric development community through the p= rocess and procedures needed to execute against that plan. A passion for re= lease planning, cross-project coordination, automation, and release deliver= y, as well as the ability to effectively partner with contributors from aro= und the globe, are required to be effective in this position. The t= erm of this role will last for 1 year and there will be no restrictions on = the number of terms served.
Primary Responsibilities
Short Biography:&nbs= p;I am currently Software E= ngineer at CodiLime. For over 2.5 year I've been working with Tungsten Fabr= ic. First developing SDWAN/multicloud with deployed TF on the top of that. = There I had opportunity to learn how Tungsten Fabric cooperates with = all three major cloud providers (AWS, GCP, Azure) and all nuances of TF dep= ending on environment, operating system et al.
Afterward, I was developing for almost a year TF operator (kn=
own as contrail-operator at that time) for Openshift 4.x deployments.
There I was one of key engineers in development of vRouter and Kubemanager =
part to support multiple business scenarios (like standard CNI usage of TF,=
a well as Nested Deployment mode where Openstack together with Openshift a=
re involved).
Currently, as TF Operator was officially released to Linux Fo=
undation, I actively contribute writing documentation for TF Operator, but =
also writing code to make TF Operator even better (all in all I'm probably =
one of a few that knows all the nuances and secrets of this code). I'm eage=
r to work with the community to make it easier and intuitive for others to =
use Tungsten Fabric.
I also actively take part in the community meetings, slack discussions or g=
iving presentations at LFN events.
I also wrote multiple blog posts about different aspects of Tungsten Fabric=
published on CodiLime's website: https://codilime.com/blog/