> This applies to both #10 and #11: > I think we should just write a guide (I could write such guide as I'm > planning to write my own custom spoke) how to write Anaconda spokes > and > then help other teams with the development of *their* spokes > maintained > by them (probably as separate packages installed by lorax?). > > And replacing firstboot with the second run of the Anaconda UI with > unfinished spokes would allow us to use such spokes in both > installation > and setting up the installed system during the first boot. > This is exactly what I would like to happen. IT will save us lot of code, but we need to decide fast as some partners already have firstboot plugins and those would need to be changed to support the new UI API. Martin _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
