Welcome to the OVAL list (I saw you joined recently). Thanks for submitting both an issuehttps://github.com/OVAL-Community/OVAL/issues/111 and a PRhttps://github.com/OVAL-Community/OVAL/pull/112 for your proposal. I haven’t looked at your PR directly, but I wanted to mention our Community Guidelineshttps://oval-community-guidelines.readthedocs.io/en/latest/, and specifically mention the language proposal processhttps://oval-community-guidelines.readthedocs.io/en/latest/proposal-process/index.html. At this point, the Unix/Linux Area Supervisor would be shepherding the proposal through the process. However, that Area Supervisor is somewhat in flux at the moment, though Matej (from RedHat) should opine soon enough.
I’m also hoping that others in the community will have a conversation about the proposal as part of the issuehttps://github.com/OVAL-Community/OVAL/issues/111.
From: BOUILLARD Esteban email@example.com
Date: Wednesday, February 10, 2021 at 9:46 AM
To: "firstname.lastname@example.org" email@example.com
Subject: [OVAL DEVELOPER] Pull request oval community github
Hi Oval dev team !
I am a French developer working for Sopra Steria France.
I recently made a pull request on OVAL to publish some adding to Unix and Linux schemas (https://github.com/OVAL-Community/OVAL/pull/112https://github.com/OVAL-Community/OVAL/pull/112).
As I am not very familiar with pull request process on your github, could anyone please give me some feedback on it, to see if everything is ok or if some modifications are required otherwise?
I am available if you have any question/request over this pull request !
Parc de la Conterie 2
13 rue Léo Lagrange
35131 Chartres-de-Bretagne - France
firstname.lastname@example.org:email@example.com - www.soprasteria.comhttp://www.soprasteria.com
This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments.