![](https://seccdn.libravatar.org/avatar/654c5b4f0d657240edff9440a901839b.jpg?s=120&d=mm&r=g)
Dne 19. 05. 20 v 17:44 David Benjamin napsal(a):
Good evening to most of you on this 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:
As I wrote in the other thread, a GitHub template repository might work better than a script...
I am not a professional developer, so I will need some help with Licensing and such.
I'm not a lawyer but for a template I'd use as permissive license as possible. We usually use GPLv2 for our modules but the template should allow creating a module with any license (or allow changing it later). So maybe MIT/BSD or even Public Domain would be better. But again, we should ask some expert about this...
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.
I think it would be nice to have a minimal skeleton with documentation, unit tests, Travis CI, etc... The question is how more value it can bring than the already existing https://github.com/yast/yast-journalctl-tutorial tutorial module. Maybe it would be better (and easier) to change the tutorial module into a template, I do not know. I'm too long in the YaST team, for me it's quite difficult to imagine what the newcomers would like to have... -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org