Please stop top posting. On 07/02/2019 05:04, Jim E Bonfiglio wrote:
Hi Simon- as far as I'm aware I am not making assumptions, merely communicating my observations. It appears that the (open)SUSE community/corporation lacks any process to escalate such risks, suggestions, and/or recommendations upstream. As such, this simply is not the distribution for me to use for any use case in any domain.
Best, Jim
We actually have quite a simple policy: 1. File a bug report 2. The maintainer will then decide on the following. a. Its an openSUSE issue. i. Then they can decide to add it to there todo list ii. or mark it as wont fix because they don't have time to do it b. Its an upstream issue i. They can point you to the upstream location for suggesting features / enhancements (preferable) ii. Suggest the feature on your behalf (generally if they also agree its something they want to see). iii. If your extra lucky they might just implement it upstream. iv. They may say the idea is likely unfeasible or wont be accepted upstream because similar ideas in the past have been rejected. Bug reports are handled differently of course. Especially those related to security issues.
On Wed, 2019-02-06 at 11:57 +0100, Carlos E. R. wrote:
On 06/02/2019 04.36, Jim E Bonfiglio wrote:
Hi Simon- if the (open)SUSE community is just that impotent I'll take my leave.
I'm sorry to say that what you ask is simply impossible to do. Your assumptions about openSUSE are plain wrong.
If you want such a change to how filesystems are handled, you should convince Linus Torvalds and sufficient people of the kernel developers, not openSUSE.
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B