Mailinglist Archive: opensuse-factory (602 mails)

< Previous Next >
Re: [opensuse-factory] Re: [PLEASE SPEAK UP] Disabling legacy file systems by default?


On 08/02/2019 03:21, Jim E Bonfiglio wrote:
On Thu, 2019-02-07 at 09:16 +1030, Simon Lees wrote:
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.

Hi Simon- per your request I have two questions for you:

1. Is this to-be-implemented blacklist a feature or a bug?

Personally i'd call it a bugfix, several of the filesystems listed have
open security bugs and this change fixes those bugs on default systems
by making it not possible to execute the buggy code

2. What is the purpose of this mailing list? I have observed
discussions related to the determination of bugs in this list.
Should this list be utilized for this purpose or for a different
purpose? As far as I'm aware bugs are fair game for discussion here,
though perhaps the openSUSE forum may be more appropriate?

This list is not for the general discussion of bugs or whether or not a
certain behavior is a bug those things should generally be discussed in
bugzilla with occasional exceptions i'll get to in a minute.

This list is designed for coordinating development between the various
teams / people developing openSUSE. So for discussing changes to tooling
that will effect all developers for giving notice / coordinating changes
that will effect multiple different teams or developers and occasionally
for if a developer wants a second opinion on something. Its also used if
you intend to package something new to avoid duplicate effort in case
someone else is also packaging it.

So the obvious exception for bugs that are worth discussing here are
ones that are likely to involve or affect a large number of people in
multiple areas of which this one counts.

--

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

< Previous Next >
List Navigation
This Thread
Follow Ups