( CC'ing Matt Miller, Josh Boyer, and Kalev Lember so that we may
avail ourselves of their sagacious insight. )
On Mon, Aug 28, 2017 at 10:31 AM, Alexander Ploumistos
On Mon, Aug 28, 2017 at 4:34 PM, Jeff Backus
> Hi All,
> Not sure if anyone else is aware, but it looks like FESCo voted to give us
> until September 8th to get organized or i686 is being pulled from kernels
> for F28. The good news is that they are letting us define what "organized"
> means. The bad news is that the clocks ticking.
> So, thoughts?
Do other SIGs have specific criteria about being "functional"?
I don't know what criteria other SIGs are having to meet, but I
expectation is that some degree of regular progress towards filling a
community need would be sufficient. My understanding is that there is
a specific need for:
* Testing on actual hardware, especially boot components, live images,
* Triaging i686-related bugs
* Helping organize resources to address the above (i.e. helping people
who are looking for something to work on find an issue to work on)
* Recruiting people interested in Fedora's continued support for i686.
Additionally, I suspect that we would need some form of regular
meeting. IRC meetings are difficult for me to attend, so my preference
would be a regular discussion via e-mail, but we should choose a forum
that works for the most people.
As for the group's responsibilities, I do not understand what
could/should be done when e.g. an upstream project stops supporting
CPUs without specific instruction sets or x86 altogether.
Good question. I think the SIG could help with triage, but I don't
think we should sign up for taking on supplementing upstream when they
choose to drop support. I think we should approach this in a fashion
similar to SIGs for architectures such as s390 and ARM.
Would it be feasible to schedule a meeting sometime next week, so
we may have the input of those attending Flock? Should we also ask
someone from the kernel team and perhaps infrastructure to attend as
well or should we leave that for a next meeting?
I think it would be great to drum up support at Flock. Unfortunately,
I won't be attending this year. A meeting next week would be a good
idea. If we can't work it in due to conflicts with Flock, should at
least getting a meeting on the schedule would help us make a case for
an extension with FESCo. I think it would be good to include someone
from the kernel and infrastructure teams so that we can figure out the
rules of the road. I think it would also be good to include Josh
Boyer, who is undoubtedly ready to wash his hands of i686 altogether,
but I believe has quite a bit of insight into what specific needs the
SIG might fill and where to start.