Next Meeting Agenda

This page is used as a meeting agenda for the weekly TigerOS contributor meeting. Every week, this wiki page is updated with weekly announcements or discussion topics for the next meeting. The template always stays the same, but the content changes based on what we're doing during the week. You can find past revisions / versions of this page here.

TigerOS contributors are encouraged to add any announcements or tickets they'd like to discuss to the agenda before the meeting.

Agenda

Topic	Time
Arrival / welcome	5 min.
Announcements	5 min.
Action items from last meeting	10-20 min.
Tickets	30 min.
Open floor	Any time left

Announcements

Announcements are anything the rest of the team should know about, but doesn't need discussion. These should be read off by the meeting chair or project lead at the beginning of the meeting and should take about five minutes. Anything that needs to be discussed deeper should wait for tickets.

New TigerOS ISO!
3/28: Ditched normal agenda and did trial run of current progress

Action Items

During a meeting, action items might be assigned to team members for the next week. Anything that needs follow up from a previous meeting should be discussed here. Depending on how many previous action items there are, this could take 10-20 minutes.

@axk4545

Work with @CoffeeFrame on stuff
~~Work on separating packages~~
Compartmentalize build machine?
- Look at environment file @kst123abc

@ct-martin

(Unimportant) Work on personal dev instance of TigerOS CI, move from LAN to DMZ
~~Roadmap page based on meeting discussions~~
~~UX analysis writeup~~

@Tjzabel

Work on fixing default placement of dash
Create rpm for Logisim

@gen1e

Working on survey questions and how to distribute it

@kst123abc

Ansible Environment File

Tickets

Tickets are where most of the meeting time is devoted to. This is when we discuss things that are easier with everyone in the same room. This takes around 30 minutes. Items can be ticket numbers or they can have some details.

See all meeting tickets here

Open floor

Anything that doesn't belong anywhere else fits into open floor.

Add wiki blurb for adding tigeros.repo if users wish to install our packages through dnf?
First Release Milestone; What constitutes a first, working release?
- This will be a beta release since we're not as far as we'd like
  - F27, GNOME (done)
  - Scripts broken up
    - What already exists working, more not needed
  - Valid RPMs
  - Nothing blatantly broken
  - GTK GUI nice, but not required
- Formal first release
  - GTK GUI needs to work
  - Proper UX analysis done
    - Changes made as needed based on analysis
  - All metapackages and repackaging that we want are done
How has the package movement gone? Have repos, otherwise slow
Do we want to remove RPMfusion? Do we still need it? move to non-foss section of manager
- Call this 3rd party tools (similar to Ubuntu and others)?
where do we want external contributors to focus their efforts? make a list or use labelling. did this get resolved? defer until first release-ish
Maybe move Wiki to TigerOS website to host more content? discuss when doing beta release