Replace post install script with GTK UI or metapackage in software selection about tigeros HOT 14 CLOSED

After the meeting today, we have decided not to include the GTK UI in the Maker Faire. Tentative release for a fully working product is during winter break.

Current progress: ironing out the design layout. I also need to figure out the best way to include the GTK UI within the tigeros repository.

Current thought process:

1. Create design layout
2. Implement design
3. Add functionality
4. Merge final binary into tigeros project

Thoughts?

from tigeros.

from tigeros.

For ref in case we go the route of a custom comps.xml file: https://github.com/manatools/dnfdragora/blob/master/tools/gen-comps-category-list.sh

from tigeros.

@axk4545 @jflory @Tjzabel21 @josh1147582
While some of this will end up in another issue, this is where the process/discussion is happening right now, so forwarding this from Aidan to here (see below). I think we should discuss Week 8 and then Week 9 we should make a milestone for this and then break into issues based on the discussions and subsequent research.

1. Keep our "script-based" RPMs out of the iso, namely the major-specific ones. If we keep them just in a repository that TigerOS can grab from through dnf install, it'll be less we have to build each time. Also, not every user will need them. Ideally, our "first run" script would just be a bunch of `dnf install`s.
2. Add metapackages to our repo: packages that point to other packages. So installing the "CS" metapackage would install all the tools that a CS student might need.

from tigeros.

I have a base design for the UI completed. However, this will not be able to be finished by this Saturday for the Maker Faire. I may remove this issue from the milestone. Thoughts?

from tigeros.

from tigeros.

@ct-martin @axk4545 @jflory7 I agree. I am going to be working on this until completion, but we won't be able to get a model ready for the Maker Faire.

We are going to need to set up a model on how to incorporate the code of the GUI into this repository. There are dependencies needed, and so I'm trying to figure out the best way to set this up so if others want to contribute, they are able to pull the code, and compile/test on their own machine.

from tigeros.

from tigeros.

Discussed in our weekly meeting.

GTK implementation for repo

• Will we have other sources?
• What package name to use? (tigeros-setup-wizard, tigeros-software-selection, etc.)
• Do we want to make it more than a manager and tie all of our customizations to a single package with sane defaults? Or the meta-package approach?

The initial steps are to create the implementation first. There are concerns about GTK being more complicated than anticipated. We may focus more on GNOME-specific changes. We'll revisit this sometime after break, and @Tjzabel will add new announcements to the next meeting agenda on any progress.

from tigeros.

UX suggestion from kinri: show commands as they are being executed

from tigeros.

Reference metapackage: https://src.fedoraproject.org/rpms/qt5/blob/master/f/qt5.spec
And how to do package groups: https://pagure.io/fedora-comps

from tigeros.

comps.txt
How do do comps in more detail

from tigeros.

Update

The repo to house the code for the software manager will live here

from tigeros.

Closing as not being worked on now. Current goal is integrating with GNOME Software. If this is not possible, I would like to look at adding a patch to allow the capability before we fully decide to go off on our own.

from tigeros.