[yast-devel] Time to decide on new priorities for next sprints
Hi guys, Me and Ancor have been maintaining a long list of big topics, such as features, refactoring, wishes, future needs etc., but this list reflects the current situation trying to address all the needs from various sources at the time. I'd like to ask for your personal view now: What do you feel is important to do, let's say mid to long-term, and also why? To spoil the fun a bit, I'll use an example... ~~~~~ We've been postponing some refactoring in Packages/Patterns/Extensions/Add-Ons/Registration because we always felt it was going to change once more and thus it's not wort the effort of the refactoring. We've created a technical debt there. In fact, we should have done the refactoring even earlier exactly because we knew it was going to change again and again. The refactoring in this area is utterly needed to, e.g., split classes into smaller ones to have a simple responsibility, to increase the test coverage, to implement some realy object-oriented code, ... to be more flexible - prepared for changes to come (this real example has been written with a huge help from Imo and Ancor :)) ~~~~~ Obviously we already have many topics, but it's never too late to learn that there are even some more and more important just behind the corner :) Please, share your opinion. Thanks in advance Lukas -- 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
On Wed, 11 Mar 2020 22:47:24 +0100
Lukas Ocilka
Hi guys,
Me and Ancor have been maintaining a long list of big topics, such as features, refactoring, wishes, future needs etc., but this list reflects the current situation trying to address all the needs from various sources at the time.
I'd like to ask for your personal view now: What do you feel is important to do, let's say mid to long-term, and also why?
To spoil the fun a bit, I'll use an example...
~~~~~ We've been postponing some refactoring in Packages/Patterns/Extensions/Add-Ons/Registration because we always felt it was going to change once more and thus it's not wort the effort of the refactoring. We've created a technical debt there. In fact, we should have done the refactoring even earlier exactly because we knew it was going to change again and again.
The refactoring in this area is utterly needed to, e.g., split classes into smaller ones to have a simple responsibility, to increase the test coverage, to implement some realy object-oriented code, ... to be more flexible - prepared for changes to come (this real example has been written with a huge help from Imo and Ancor :)) ~~~~~
Obviously we already have many topics, but it's never too late to learn that there are even some more and more important just behind the corner :) Please, share your opinion.
Other topics I have in mind is - unify and refactor license handling/showing - kill no longer used features in installation as it is already complex enough so any simplification is good - find if there is future and how it looks for command line interface Josef
Thanks in advance Lukas
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 3/11/20 10:47 PM, Lukas Ocilka wrote:
Hi guys,
Me and Ancor have been maintaining a long list of big topics, such as features, refactoring, wishes, future needs etc., but this list reflects the current situation trying to address all the needs from various sources at the time.
I'd like to ask for your personal view now: What do you feel is important to do, let's say mid to long-term, and also why?
To spoil the fun a bit, I'll use an example... In the storage area, for me the next big thing would be proper support for all the Btrfs features, specially subvolumes, snapshots and quotas.
Some (but not all) of the current problems are summarized at the corresponding section of the Btrfs&Partitioner document[1]. There is also a Trello card[2] (non public, sorry) for the same goal. This big change probably should come together with an important revamp of the Partitioner UI... which will likely need some new widgets or UX solutions. So this is something that needs a good master plan and that will keep us busy for months. Cheers. [1] https://github.com/yast/yast-storage-ng/blob/master/doc/btrfs_in_partitioner... [2] https://trello.com/c/fJ3Jpn8Q/ -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 3/11/20 9:47 PM, Lukas Ocilka wrote:
Hi guys,
Me and Ancor have been maintaining a long list of big topics, such as features, refactoring, wishes, future needs etc., but this list reflects the current situation trying to address all the needs from various sources at the time.
I'd like to ask for your personal view now: What do you feel is important to do, let's say mid to long-term, and also why?
To spoil the fun a bit, I'll use an example...
~~~~~ We've been postponing some refactoring in Packages/Patterns/Extensions/Add-Ons/Registration because we always felt it was going to change once more and thus it's not wort the effort of the refactoring. We've created a technical debt there. In fact, we should have done the refactoring even earlier exactly because we knew it was going to change again and again.
The refactoring in this area is utterly needed to, e.g., split classes into smaller ones to have a simple responsibility, to increase the test coverage, to implement some realy object-oriented code, ... to be more flexible - prepared for changes to come (this real example has been written with a huge help from Imo and Ancor :)) ~~~~~
Obviously we already have many topics, but it's never too late to learn that there are even some more and more important just behind the corner :) Please, share your opinion.
In network we have some topics that have been partially addressed and some not: In short term: - The current hostname setup (I could extend it, but basically it is about functional tests, update or remove out of date documentation and approval of current behavior by PM or PjM) In long term: - Split of proposal and current network configuration during the installation - Some research in vpn configuration. (would it be nice to have as a connection in network module as NM does? what about supporting wireguard?)
Thanks in advance Lukas
-- Knut Alejandro Anderssen González YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (4)
-
Ancor Gonzalez Sosa -
josef Reidinger -
Knut Alejandro Anderssen González -
Lukas Ocilka