Folks,
our next meeting is scheduled for tomorrow, Wednesday, December 12, 17:00 UTC at #fedora-meeting. At the last meetings I was either alone with zodbot or we were too few participants or members were late because of the daylight saving time change.
(1)
These problems used to occur whenever there was a time change. The first thing we are to decide is whether to keep the time of our meeting. Due to the time difference, the date is now one hour earlier as used to be. And that may cause a problem for some of us. Many teams have therefore moved their meeting to an hour later.
(2)
In the meantime, some things have settled, so presumably:
= Server critical path definition proposal =
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or…
But perhaps there is still a need for discussion on this.
(3)
It is time to define and organize our work program for the upcoming year. See:
https://pagure.io/fedora-server/boards/Works%20in%20progress
Among others we have 5 „big“ topics to do:
1. Review quality and release criteria (#61, #63)
That is „naturally“ the next step after the update of our technical specification.
2. Systematization of our release testing
We had some discussion to create a „test week“ und use a public program as e.g. https://testdays.fedoraproject.org/events/131 or https://testdays.fedoraproject.org/events/132
We would have to decide what manual tests we need, which tests may run automatically, and for each test we need a test description.
3. Review installation media (#32, #48, #51, #55, #54, #65, #88)
This is a collection of several long standing tickets and tasks.
4. Ansible support (#60)
We are already working on this.
5. Upcomming Web page revamp (#66)
The revamp project makes progress. The pages for Workstation, CoreOS and IoT are ready or nearly ready. So it’s our turn now.
As an example: https://design.penpot.app/#/view/d0c3eb90-430d-11ed-9050-cf2300df1f4f?page-…
And then we have a number of not so urgent or not so extensive projects:
6. SW Raid EFI systems (#89)
7. Expansion of the documentation
8. Creation of a SBC reference (#52)
9. Cockpit File Sharing module (#86)
10. Improvement of our team pages, moving the wiki pages (#57)
But we can also define our program independently of the professional list and ask which of us would like to realize what in the coming year.
So folks, who is planning what?
peter
Peter
