On Tue, Jul 10, 2018, 5:44 PM Ken Moffat <[email protected]> wrote:
> On Tue, Jul 10, 2018 at 02:23:38PM -0700, Jalus Bilieyich wrote: > > Having multiple parts of the book being split up and teams working on > > each part is a good idea in my opinion. > > > > Except at the moment we have one small team and in general people > pick things they think they can handle. In my case, a lot of the > things I care about are spread throughout the 'Basic' and 'Advanced' > parts, and I'm sure the other editors will say the same. So I'm not > convinced that separate teams is going to work. > > For the moment I'm mostly stepping aside, as previously noted. > > I hope to keep an eye on firefox (past experience suggests that > trying to pick up the new version only when it is released is too > painful), and almost every release has CVE fiexes, even 61.0 did > (although those were not initially in the Release Notes). > > Eventually I hope to be able to devote a bit more time to this, but > for the next few months that is now less likely. > > But the big problems as I see them are: > > · lack of people building the development book and finding issues > > · lack of people willing and able to edit > > And of those, the second is the greater problem. > > So, since we are now hopefully looking at longer-term changes, > anybody else got other suggestions for changed format/process ? > > Please ? > > ĸen > -- > Keyboard not found, Press F1 to continue > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > Would this be the time to suggest a change in policy on tickets? I'd like to see tickets have the changelog for the package and security updates marked as such. It would make people's lives a lot easier. >
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
