From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Allan Webber Subject: Re: =?utf-8?Q?=E2=80=9CFuture?= of =?utf-8?Q?Guix=E2=80=9D?= panel Date: Fri, 03 Feb 2017 05:44:25 -0600 Message-ID: <87a8a3pkh2.fsf@dustycloud.org> References: <878tpo89yk.fsf@gnu.org> <20170203061603.GA12952@mail.thebird.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42604) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZcI4-0002p1-1A for guix-devel@gnu.org; Fri, 03 Feb 2017 06:44:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZcI0-0002ku-RN for guix-devel@gnu.org; Fri, 03 Feb 2017 06:44:32 -0500 In-reply-to: <20170203061603.GA12952@mail.thebird.nl> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Pjotr Prins Cc: Guix-devel It looks good. We won't run out of topics for sure. :) Pjotr Prins writes: > Heh. Long list. > > On Fri, Feb 03, 2017 at 12:11:15AM +0100, Ludovic Court=C3=A8s wrote: >> Hello Guix! >>=20 >> We=E2=80=99ll close FOSDEM with a discussion on the future of Guix and= GuixSD: >>=20 >> https://fosdem.org/2017/schedule/event/futureofguix/ >>=20 >> Attached is a semi-structured list of topics that came to mind. Pleas= e >> feel free to bring your own, either at the event (this Sunday), or on >> this list, or on IRC during the event maybe? >>=20 >> Ludo=E2=80=99. >>=20 > >> #+TITLE: Future of Guix (panel) >> #+STARTUP: content hidestars >>=20 >> https://fosdem.org/2017/schedule/event/futureofguix/ >> Sunday, 16:30, K.4.601 >>=20 >> * Organization >>=20 >> ** sharing the work load >>=20 >> *** security updates >>=20 >> *** build farm >>=20 >> *** web site, posts, videos, etc. >>=20 >> *** handling branches: starting & merging =E2=80=98core-updates=E2=80=99= , =E2=80=98staging=E2=80=99 >>=20 >> *** release management: setting a date, choosing what goes in, publish= ing >>=20 >> *** GSoC mentoring >>=20 >> ** review >>=20 >> *** getting more reviewers >>=20 >> *** facilitating the process >>=20 >> *** encouraging newcomers >>=20 >> ** funding >>=20 >> *** development >>=20 >> - how do we get core & maintenance work funded? >> - how do we get funding for new areas (like =E2=80=98guix deploy=E2=80= =99)? >>=20 >> *** infrastructure (build farm) >>=20 >> - sustaining infrastructure growth and maintenance >> - Jan. 2016 crowdfunding was enough for a start >>=20 >> * Publicity, outreach >>=20 >> ** high-performance computing (HPC) >>=20 >> *** competition: EasyBuild, Spack, Singularity, Shifter >>=20 >> *** stories: MDC, Utrecht, Brisbane >>=20 >> *** possible cooperation in the near future >>=20 >> ** reproducible science >>=20 >> *** how to help projects such as [[https://rescience.github.io/][ReSci= ence]]? >>=20 >> *** make reproducible free software stacks the obvious choice >>=20 >> ** containers, deployment >>=20 >> *** competition: Docker, Kubernetes, NixOps >>=20 >> *** stories: gov.uk (Chris Baines), bayfront.guixsd.org >>=20 >> ** hold Guix User Gatherings (GUGs)? >>=20 >> * Code >>=20 >> ** 1.0 in 2017! (see roadmap in [[https://www.gnu.org/software/guix/gu= ix-ghm-20160818.pdf][GHM 2016 talk]]) >>=20 >> *** =E2=80=98guix pull=E2=80=99 and channels >>=20 >> *** Git checkout authentication >>=20 >> *** performance & usability improvements >>=20 >> *** GuixSD graphical installer (John) >>=20 >> *** self-hosted infrastructure >>=20 >> **** Cuirass >>=20 >> **** =E2=80=98guix publish=E2=80=99 improvements >>=20 >> **** build machines running GuixSD >>=20 >> *** bug fixes >>=20 >> ** next big thing: =E2=80=98guix deploy=E2=80=99 >>=20 >> ** scalability >>=20 >> *** better importers & updaters >>=20 >> *** better =E2=80=98guix lint -c cve=E2=80=99 >>=20 >> ** reproducibility: reach 90% or so, and measure >>=20 >> ** bootstrapping >>=20 >> *** reduce the size of our bootstrap binaries (Bournish? Mes? =E2=80=A6= ) >>=20 >> *** =E2=80=9Cdo something=E2=80=9D about compilers that cannot be boot= strapped