-
Notifications
You must be signed in to change notification settings - Fork 11
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.
The remainder of the semester will be devoted to preparing for ImagineRIT. After ImagineRIT, we will focus on retrospective.
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 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.
- We need to plan for ImagineRIT
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
- Compartmentalize build machine?
- Set up Builder with Jenkins and Ansible (may not happen, but documenting)
@ct-martin
- (Unimportant) Work on personal dev instance of TigerOS CI, move from LAN to DMZ
@Tjzabel
- Create rpm for Logisim (CSCI250 Version, not upstream)
- Continue adding to TigerOS UI Tweaks
- Check for any packages that need to be turned into RPMs
- 12H time format probably needs to be RPM'ed
@gen1e
- Working on survey questions and how to distribute it
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.
Anything that doesn't belong anywhere else fits into open floor.
-
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
- This will be a beta release since we're not as far as we'd like
- 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
© CC-BY-SA 4.0 – 2018, RIT Linux Users Group