Hi, I plan to clean a bit ... ergh, clean almost whole yast2-devtools. At first I would like to mention why I think it is important and what is benefits and then how I would like to do it.
Benefit from such cleaning is that for new yast developers is easier to orient what is useful for him and what makes his life easier. Also if we reduce number of tools, we can improve it to be really usefull to all developers. And last but not least, it allows us to identify where tools are just work-arounds that is no longer needed. So how to do it? I start[1] with a cleaning of tools related to ycp or tools that is not touched for years ( there is files not touched for more then 11 years! ). Then I would like to identify what tools are already used by other developers and what is their use case for such tool ( maybe we can enhance different tool to allow it ). I also would like to make logic structure in devtools to tools not intended for humans like rpm macros, generators used by other tools etc, for tools intended for developers that operate on one repo and third category should be current yast-meta project to operate on all yast repos. I also would like to improve README so new developers have easy starting point to introduce which tools we use to make our life easier. So please write which tools from yast2-devtools you use for current master development and how you use it. If you don't write it, there is quite big chance that such tool will be removed. Josef [1] https://github.com/yast/yast-devtools/pull/29 -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
