So to recap whats left:
Our new hardware needs (HDD space, SSDs) : *Was this taken care of Fabio?* Bugzilla improvements: *Bug Bankruptcy may assist in removing complication of differentiating bugs. * - Too complicated, too many choices, not all correct:* Any ideas on how to simplify?* - *Testing team should be able to assist when launched by making sure bugs go to correct queues and teams* - *Possibility of bug bankruptcy: Currently looking at >6months age since last modified date * Communication with our community: *Needs documentation. Trying to merge a single blog has proven painful.* - Blog/PR team of 2-3 people?* (need more reviewers and appovers who can merge)* - Mudler has credentials/can invite. - https://github.com/Sabayon/sabayon-website-next/tree/master/content/article - https://github.com/Sabayon/w0h000/tree/master/content Libav vs ffmpeg:* Mudler, did you get any information on this topic?* *Are we upgrading to Libav 12.1 ?* ARM support: *Where are we on this?* - No ARM downloads link in download page (microchip icon from fontawesome 4.7) - Notice that ARM images are minimal (no GUI) might be useful GCC upgrade (status, branch, SLO?): *Any updates on this? Curious if we are branching or not?* - Branching may result in user unfriendly issues. - Hopping branches needs to be automated and somewhat noob friendly. - Chroot snapshot, then bump GCC and recompile all as opposed to branching? - Use of eit status to tell what is recompiled vs what is not. - Need to complete core updates before freezing for GCC Security team possibilities - *Is the team actually necessary since we are a downstream distro?* Last known issue was https://github.com/Sabayon/for-gentoo/commit/8858b6ce02931112fccd87e7819042df95f29d1f - U2F capabilities? (yubikey assisted login PAM etc) Entropy auto updater : *Who works on magneto/Rigo?* - Can we not release this to sabayonlinux.org repo? - Can it not include auto branch hopping upon branch completion? - Can we add auto-updater feature to magneto? - Keep as systemd service to allow compat with minimal distros. - Have Rigo remind users of updating config files. Entropy autoremove function:* In the works?* BTRFS Anaconda installer support? : *Any Updates?* - BTRFS is bootable from GRUB, snapshot support etc is nice. ZFS isn’t bootable yet. Virtualization and containers (dockers, OVMF, etc): *Any Updates?* - OVMF support needed. (virt-manager “UEFI not found”) - VMs should be more turnkey for server deploys - Docker simplification for administration? automatic install of kitematic docker? *http://www.tothenew.com/blog/docker-kitematic-for-linux/ <http://www.tothenew.com/blog/docker-kitematic-for-linux/>* On Tue, Jul 4, 2017 at 1:53 PM Jerrod Frost <piroisl...@gmail.com> wrote: > As long as people don't leave the bug untouched for 6 months, it won't be > considered abandoned. So this will enforce better bug wrangling. > > On Tue, Jul 4, 2017 at 12:33 PM Sławomir Nizio <slawomir.ni...@sabayon.org> > wrote: > >> > I agree with this, how long do we think is 'fair' before resolving a bug >> > due to abandonment? 6months? >> >> There are 409 bugs open. >> >> 73 have been changed within the last 6 months, >> 36 within the previous 6 months (that is, starting from July 4th, 2016), >> 31 since 2016-01-09, >> 44 since 2015-07-01, >> 36 since 2015-01-08, >> 34 since 2014-07-11, >> 59 since 2014-01-12, >> 57 since 2013-07-07, >> 37 since 2013-01-20, >> 2 since 2012-07-07. >> >> (I verified the sum with awk. :P) >> >> The are no older bugs because they were once closed. >> >> These figures alone don't form an answer but at least we could see what >> number of bugs would be affected. >> >> I think that 6 months would work just to have a smallish number of bugs >> to focus on, but then some would be reopened, and who knows, maybe the >> final number would be doubled meaning there would be 146 bugs to work on. >> >> >
