I've done my best to collate all of your feedback and asses the feedback thusly
For: 17.5 people
Against: 3 people (4 if I count Fabian's in person feedback)
Unclear (on the fence/both equally bad/talking about adding features
not on the table): 9 people
This obviously means there is a majority that support this change.
Due to the high number of unclear feedback though, I wanted to weight
people's responses to make sure I looked at this thread from more than
one point of view. As this would be a wide-ranging change, I felt a
lot of peoples responses weren't very helpful when they were only
talking about their own personal usecase and not considering the wider
users project.
Therefore went through everyone's responses and applied an additional
weight of +0.5 for all responders who demonstrated they had considered
an opinion beyond their own personal use cases.
In this case, the numbers become:
For: 20.5
Against: 4 (or 5 incl. Fabian)
Unclear: 11.5
Still showing a clear body of support for this change beyond those who
disagree or have a more nuanced view on the topic.
With these numbers in hand, I've just discussed this with Leap &
Tumbleweed's release managers and based on their feedback the current
plan is
- It'a almost certain that there will be no change on the current
behaviour for Leap 15.0; Although we could do it, any late change
bring risks. Many of the negative and unclear comments on this thread
helped identify the nature of those risks. Even if I am reasonably
confident that many of those risks will not apply, I concur that the
benefits of this change probably don't justify risking Leap 15 being a
smooth and happy release. We've lived for years without this behaviour
without major concerns.
- Tumbleweed will likely adopt this change in the coming weeks. I
won't be rushing my submission to the changes (I already have changes
the transactional server system role on the way and wait to wait for
them to land before proposing more).
openQA should be enough to ensure that nothing outright breaks, and
our ability to tweak, tune, or revert things quickly based on user
feedback will mean we can address peoples concerns as/when/if they
bear fruit.
- Assuming things go well in Tumbleweed, users can probably expect
this behaviour of NM by default for Desktop roles in Leap 15.1
Thanks all for your feedback
On 12 April 2018 at 13:22, Patrick Shanahan
* Mathias Homann
[04-12-18 04:46]: Am Donnerstag, 12. April 2018, 10:27:22 CEST schrieb Stefan Seyfried:
Executive summary: I support the default of NetworkManager by default for openSUSE.
#metoo
Cheers MH
I definitely do not.
-1
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org