From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: =?utf-8?Q?=E2=80=9CFuture?= of =?utf-8?Q?Guix=E2=80=9D?= panel Date: Fri, 03 Feb 2017 00:11:15 +0100 Message-ID: <878tpo89yk.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41396) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZQXS-0000A3-6N for guix-devel@gnu.org; Thu, 02 Feb 2017 18:11:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZQXP-00010q-0i for guix-devel@gnu.org; Thu, 02 Feb 2017 18:11:38 -0500 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: Guix-devel Cc: Pjotr Prins --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello Guix! We=E2=80=99ll close FOSDEM with a discussion on the future of Guix and Guix= SD: https://fosdem.org/2017/schedule/event/futureofguix/ Attached is a semi-structured list of topics that came to mind. Please feel free to bring your own, either at the event (this Sunday), or on this list, or on IRC during the event maybe? Ludo=E2=80=99. --=-=-= Content-Type: text/x-org; charset=utf-8 Content-Disposition: inline; filename=future-of-guix.org Content-Transfer-Encoding: quoted-printable Content-Description: topics #+TITLE: Future of Guix (panel) #+STARTUP: content hidestars https://fosdem.org/2017/schedule/event/futureofguix/ Sunday, 16:30, K.4.601 * Organization ** sharing the work load *** security updates *** build farm *** web site, posts, videos, etc. *** handling branches: starting & merging =E2=80=98core-updates=E2=80=99, = =E2=80=98staging=E2=80=99 *** release management: setting a date, choosing what goes in, publishing *** GSoC mentoring ** review *** getting more reviewers *** facilitating the process *** encouraging newcomers ** funding *** development - how do we get core & maintenance work funded? - how do we get funding for new areas (like =E2=80=98guix deploy=E2=80=99= )? *** infrastructure (build farm) - sustaining infrastructure growth and maintenance - Jan. 2016 crowdfunding was enough for a start * Publicity, outreach ** high-performance computing (HPC) *** competition: EasyBuild, Spack, Singularity, Shifter *** stories: MDC, Utrecht, Brisbane *** possible cooperation in the near future ** reproducible science *** how to help projects such as [[https://rescience.github.io/][ReScience]= ]? *** make reproducible free software stacks the obvious choice ** containers, deployment *** competition: Docker, Kubernetes, NixOps *** stories: gov.uk (Chris Baines), bayfront.guixsd.org ** hold Guix User Gatherings (GUGs)? * Code ** 1.0 in 2017! (see roadmap in [[https://www.gnu.org/software/guix/guix-gh= m-20160818.pdf][GHM 2016 talk]]) *** =E2=80=98guix pull=E2=80=99 and channels *** Git checkout authentication *** performance & usability improvements *** GuixSD graphical installer (John) *** self-hosted infrastructure **** Cuirass **** =E2=80=98guix publish=E2=80=99 improvements **** build machines running GuixSD *** bug fixes ** next big thing: =E2=80=98guix deploy=E2=80=99 ** scalability *** better importers & updaters *** better =E2=80=98guix lint -c cve=E2=80=99 ** reproducibility: reach 90% or so, and measure ** bootstrapping *** reduce the size of our bootstrap binaries (Bournish? Mes? =E2=80=A6) *** =E2=80=9Cdo something=E2=80=9D about compilers that cannot be bootstrap= ped --=-=-=--