Hi Akshay, Thank you for reaching out to me. We welcome community contributions. In terms of the next steps, I recommend that you join an upcoming TSC/Community meeting (Wednesdays at 10am Eastern time) to provide an overview of what you are proposing to gauge interest. If there is sufficient interest, then you would follow the contributor/development process for StarlingX: https://docs.starlingx.io/contributor/development_process.html The first step in the development process would be to post a spec for review by TSC members. I think we also need the test teams to review as they have a number of automation tools as well and they may benefit from your contributions. The more specific pointer to the spec process is: https://docs.starlingx.io/contributor/development_process.html#specification... Regards, Ghada From: Akshay 346 <Akshay.346@hsc.com> Sent: Friday, September 04, 2020 4:26 AM To: Khalil, Ghada <Ghada.Khalil@windriver.com> Subject: Interested in Contributing back to community Hello Ghada, I hope you are doing good and keeping safe.

From around last 1 year I am using StarlingX , deployed many modes of it many-many times, played around it, tested it and reported issues if I had any. From all this I came to one point to automate these various deployments to save time and efforts. I was thinking to automate all these deployments and contribute it to the community. In addition, I can also give a GUI on top of this automation. Please let me know if it is a acceptable idea or not.

Regards Akshay DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.