On 27.01.20 13:42, Josef Reidinger wrote:
[5] Native Ruby interface for libYUI
https://github.com/openSUSE/mentoring/issues/11
I am all for doing that, but it's a vital piece of infrastructure, so we (!)
need to do this right. Outsourcing this to a GSoC student would be most
counterproductive IMHO.
>
Sadly, even if it is vital, we do not assign any resources to libyui in past.
Now situation is better, still I am not sure if we can finish it in reasonable
future. But I agree that this is a bit too much for GSoC and probably result
will be only some prototype how it can work, which can be start of discussion
and maybe even not used in final connection.
When we do something that is really important for us, we should get into the
habit of doing it the proper way, not doing something half-baked or, worse,
letting some outsider do something half-baked. We need to make use of our
expert knowledge in the area; otherwise somebody from the outside will repeat
mistakes that we already made in the past. If we do it, we have better
chances of keeping those past mistakes in the back of our head and avoiding
them in a new implementation.
This process starts with collecting requirements, thinking hard (which
requires a free head, i.e. not being interrupted by countless meetings and
unrelated things), coming up with a solid concept, maybe doing a feasibility
prototype, evaluating it, starting a skeleton, fleshing it out.
Yes, this can be done in an agile way (if that is what we want).
Agile does not have to mean doing minimalistic stuff that falls apart when
the first unexpected thing happens. ;-)
Kind regards
--
Stefan Hundhammer <[email protected]>
YaST Developer
SUSE Software Solutions Germany GmbH
Geschäftsführer: Felix Imendörffer HRB 36809 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
