I was asked if MauiKit and Maui applications are being packaged for Fedora.
As far as I know, nobody has done it yet, is this something someone wants to do?
Metadata Update from @ngompa: - Issue tagged with: meeting
@ngompa assign to me (I already started working way before and we even have packages in RPM and I will rest soon enough since plamo series over and I can work on this series as well)
Also I can refresh current bugzilla reviews If any left and bring others and ask for review in here from you guys and move on.
maui-mauikit is already in Fedora - https://koji.fedoraproject.org/koji/packageinfo?packageID=33739
These are all the review requests for the apps: maui-mauikit-filebrowsing https://bugzilla.redhat.com/show_bug.cgi?id=1968204 maui-mauikit-accounts https://bugzilla.redhat.com/show_bug.cgi?id=2056243 maui-mauikit-texteditor https://bugzilla.redhat.com/show_bug.cgi?id=2056245 maui-buho https://bugzilla.redhat.com/show_bug.cgi?id=2056268 - Why does this have a different name structure? station - Convergent terminal emulator, based on MauiKit - https://bugzilla.redhat.com/show_bug.cgi?id=2056269
I'm putting these links here so I and others can easily find them. It looks like maui-mauikit-filebrowsing is the most critical one, and it looks like thunderbirdtr has already updated the spec, so it should be an easy review is someone wants to take it.
Metadata Update from @ngompa: - Issue untagged with: meeting - Issue assigned to thunderbirdtr
Because for some reason we're using different names as upstream. Can we not change names unless necessary?
maui-buho is just buho, maui-mauikit-texteditor is just mauikit-texteditor, etc.
@justinz I did that because for grouping and easier for me to follow. I can change apps but libs ones I prefer to use it. That is all. I even asked long ago with to team and we were all fine with it.
I find it strange I ever agreed to change upstream name for no reason, so please don't count me in that statement.
I personally strongly disagree with using a package name which is not the same as upstream unless there is a good reason for it (like an already existing package with that name).
So, for this case, extracted from invent:
bonsai booth buho clip communicator index-fm maui-libdavclient mauikit mauikit-accounts mauikit-filebrowsing mauikit-imagetools mauikit-texteditor mauiman nomad-style nota pix shelf sol station strike vvav
Those should be the package names
I agree with @marcdeop. The package naming guidelines also recommend using the upstream name when possible. Booth will be a problem, as that name is already taken in dist-git (and well known enough to be in RHEL also). There is also already a pix dist-git repo, but it's retired and I guess could be unretired and converted to this software instead.
What is the status on this? I'm looking for something to do in my downtime (Considering plasma-welcome-fedora can't really be worked on yet). I see mauikit is already in Fedora, so what's the packaging tree for this? In what order do we need to bring those?
Nobody is actively working on this. This should be evaluated to identify what we have and what we're missing.
Metadata Update from @ngompa: - Assignee reset
Metadata Update from @timaeos: - Issue set to the milestone: Future Release
Log in to comment on this ticket.