On Tue, 19 May 2020 09:44:25 -0600 "David Benjamin" <[email protected]> wrote:
> Good evening to most of you on this list. Hi David, welcome to the list. > > I have worked on a new > https://github.com/dwbenjamin/yast-devtools/tree/create-new-package script, > it is not complete. I would like to know some thoughts on continuing to put > time into this, here is a little more information: > > I am not a professional developer, so I will need some help with > Licensing and such. Well, licensing is a bit tricky. What we usually do in YaST is using GPLv2 or GPLv3. This way you can use code under both, it is your pick. SUSE discourages for code that it develops ( which is not external contribution ) using "or later" as you never know what can be in next version of license and somethinng like GPLv55 - "Owner of code has to buy a beer to every user." which is not something SUSE would like to do :) > Is there any real value to this? For me it would shorten the learning > curve as the script would build the minimum directory and file structure. > The idea is to reduce the time to start actually hacking in Yast, it might > help external contributors. Well, there was something called skeletons which was quite similar in old YCP times. And I drop it [1] when we start using ruby with idea that all glue should be shared and not hard copied in skeleton. We succeed in some areas, but failed in others. So now for new modules it still need to create non trivial amount of files that is mainly for helpers and related services like travis, yardoc config, rake build or rubocop config. So I see some value. And I comment your pull request with some notes. But I am not sure about general approach. I worry then script can quickly grow and become serious mess. I think better approach is to have github.com/yast/yast-hello-world that is that minimal starting module and then having script like create-new-package that checkout that hello world and adapt it here and there to fit e.g. new module name. This way it will be also easier to verify that test runs, documentation is built, travis pass, code follows rubocop conventions and so on. Ideally this hello world should also follow the latest "best practices" which was issue with original skeletons, which was not updated, so it became obsolete and module that uses it was sub optimal. I hope that having it as common yast module helps with keeping it more up to date. > > There currently isn't any docs for this tool but I will continue to work on > that if this is something you think is of value. See above. And maybe it can be also interesting feature if it can add missing parts as we have some old modules that do not use rubocop, travis, coveralls, rspec tests, etc. And for that modules it can be good to create that initial parts for that recommended tools, which can speed up getting module in shape. > > Thank you for any and all of your time, > David. > Thanks also for your time and interest. Also if you miss any information or something is not clear from current one, feel free to write us and we try to improve it ( or you can try to do it yourself ). Josef -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
