On 05/18/2016 08:45 AM, Ancor Gonzalez Sosa wrote:

On 05/18/2016 02:19 PM, Ancor Gonzalez Sosa wrote:

...

Another three weeks, another update from the YaST Team.

https://lizards.opensuse.org/?p=11822

A note for the impatient.

Just in case you jumped into the link as soon as we announced it, we have just added a small paragraph that was originally missing (titled "paying our debts: much better cleanup rules in Snapper") with a link to this other article http://snapper.io/2016/05/18/space-aware-cleanup.html

Enjoy your extra dose of reading.

Maybe this has been brought up before but I don’t see these published on news.opensuse.org, do you guys do that? I think it would be useful for having these updates on there too. PS: Love the progress being made with yast, it looks even more cool than when I started using it, keep up the great work! -- Regards, Uzair Shamim -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On 18.5.2016 19:45, Yamaban wrote:

Thanks for clarifying the ssh-key behavior!

On the SSH config options:

IMHO the text for the option "None" option should be extendend to "None, create new keys and fresh config" to remove any doubts about what will happen.

Kudos for the interface bonding config, really nice!

Thanks for your feedback, I'll consult your idea with our designer today and hopefully make it more understandable in next sprint. Thanks! Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux https://en.wikipedia.org/wiki/Scout_Promise#Czech_Republic http://www.scouting.org/Visitor/WhyScouting/ServingOthers.aspx -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On Thu, 19 May 2016 11:31, Kenneth Wimer wrote:

...

...

...

On 05/19/2016 at 09:46, Lukas Ocilka wrote: On 18.5.2016 19:45, Yamaban wrote: Thanks for clarifying the ssh-key behaviour!

On the SSH config options:

IMHO the text for the option "None" option should be extended to "None, create new keys and fresh config" to remove any doubts about what will happen.

Kudos for the interface bonding config, really nice!

Thanks for your feedback, I'll consult your idea with our designer today and hopefully make it more understandable in next sprint.

How about "Do not import from previous system"?

Also worth to consider. My first impression was: "What will happen if I select the 'none' option?" If you add a ", start fresh with defaults" to your proposal, it would be equivalent. It's all about to remove ambiguity and give clarity from the get-go of a new interface. To remove any newbie / DAU ammunition before it (the new interface) is introduced to the public. Better get it right before the strings get translated the first time, saves work in the long run Thanks for the consideration. - Yamaban -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org