Community manager/interface/helper/or... wanted
Hi, I'm really sad since i have never thought to write this mail but we do need someone from SUSE who interacts with the community. When I started playing with libyui and especially with binding I was followed and we fixed a lot of things making this project growing and interesting for other people. When i wrote my first project manatools (formerly adminpanel) i didn't believe that could be of interest but for other people than in mageia, but the use of dnf made it possible! I started writing dnfdragora, a forntend to dnf first and to dnfdaemon later, in python and that attracted fedora attention... So now we do strongly need someone to interact, because i cannot afford a fork to manage my changes or any others required by fedora also. Thank you in advance for any feedbacks :) Cheers Angelo -- To unsubscribe, e-mail: libyui-devel+unsubscribe@opensuse.org To contact the owner, e-mail: libyui-devel+owner@opensuse.org
Hi, Sorry for being a lazy maintainer. Let's give you more power. This is a summary of yesterday's chat on #libyui on Freenode. I've omitted some details to keep the focus on the main points. Please fill in the details. Status ------ SUSE's use case for libyui is YaST, and for that purpose it is good enough as it is now. That means maintaining libyui sits low on the priority list and as a result we've been mostly ignoring your patches. Meanwhile, Mageia has been using libyui for: - manatools (perl bindings) - rpmdragora (perl bindings) - isodumper (python bindings) and there are plans to use it for - dnfdragora (a package manager frontend. DNF is the rewrite of Yum to use libsolv, which also powers Zypper) - possibly DrakX (the Mageia installer) DNF originated in Fedora and people from there are interested in libyui too. Direction --------- I think we need to give the new users the power to drive the project: develop features, make releases. For my team and our bosses to be comfortable with that, we need to have automated tests that will alert us if a change breaks YaST. We already have a huge testing machinery checking screenshots of the openSUSE installation process, at https://openqa.opensuse.org/ but the turnaround times are too long for the intended purpose: gating the GitHub pull requests. So one task for me and the YaST team for this scrum sprint is to hook up tests to GitHub PRs. We have a half-working libyui specific CI setup at https://ci.opensuse.org/view/libyui/ , powered by https://github.com/libyui/libyui-test . Either use that with Jenkins, or use Travis. Then we should resolve the long standing issues and pull requests, and integrate the Mageia extensions upstream. -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
Hi! Il 30/09/2016 10:10, Martin Vidner ha scritto:
Hi,
Sorry for being a lazy maintainer. Let's give you more power.
This is a summary of yesterday's chat on #libyui on Freenode. I've omitted some details to keep the focus on the main points. Please fill in the details. [...]
Thank you very much for your clarification! I'm glad to hear that there is interest on this project to go on with (and for) the community also not for YaST only.
From my side I'm ready to help and fix, in my spare time as usual :)
Cheers Angelo -- To unsubscribe, e-mail: libyui-devel+unsubscribe@opensuse.org To contact the owner, e-mail: libyui-devel+owner@opensuse.org
participants (2)
-
Angelo Naselli
-
Martin Vidner