On 8/10/20 4:07 PM, Stefan Hundhammer wrote:
On 2020-08-10 15:51, Lukas Ocilka wrote:
Hopefully (anything we'll do) we'll use as much upstream as possible. NIH syndrome should not apply here.
When I look at our current YaST modules, I see an awful lot of NIH: So many of them are just a thin wrapper around existing tools. So if we are taking this seriously, we should get rid of YaST modules that are really just duplicating functionality that is already available in some other form.
This is quite off-topic, please start another thread if necessary.
yast-printer, anyone? Or yast-apparmor? To name just a few.
Side note 1: Both actually have valid use-case: AutoInstallation. Side note 2: Neither of them were written by YaST developers. -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data ⚠ IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org