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+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org

Reply via email to