[Starlingx-discuss] Input needed - split starlingx/tools git repo into multiple

[Bruno Drugowick Muniz]

I too +1 on moving the "deployment" directory into its own repo.

Everything there is related to deployment in virtualized (via libvirt or VirtualBox) environments.

--
Bruno
________________________________
From: Church, Robert <Robert.Church at windriver.com>
Sent: Wednesday, May 31, 2023 14:08
To: Panech, Davlet <Davlet.Panech at windriver.com>; starlingx-discuss at lists.starlingx.io <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Input needed - split starlingx/tools git repo into multiple

You don't often get email from robert.church at windriver.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe.

+1 for moving “deployment” out of tools and into its own repo with a set of core reviewers that use the scripts.



As a core reviewer that does not use the scripts provided here, I don’t have the bandwidth to review these.



Bob



From: Panech, Davlet <Davlet.Panech at windriver.com>
Date: Wednesday, May 31, 2023 at 10:09 AM
To: starlingx-discuss at lists.starlingx.io <starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] Input needed - split starlingx/tools git repo into multiple

Good day,



We are considering splitting the git repository starlingx/tools into multiple. Reason: it contains files & scripts from unrelated domains and it is difficult to find Git reviewers whose expertise covers all of them.



At a minimum, I suggest we separate out the "deployment" directory in its own repository.



Would it make sense to separate out any other directories?



D.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20230601/e3b99b82/attachment.htm>