From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0@we.make.ritual.n0.is Subject: gnunet-fs integration Date: Fri, 01 Jul 2016 11:12:41 +0000 Message-ID: <87lh1lk3x2.fsf@we.make.ritual.n0.is> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bIwNm-0006Na-5i for guix-devel@gnu.org; Fri, 01 Jul 2016 07:13:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bIwNg-00010a-H4 for guix-devel@gnu.org; Fri, 01 Jul 2016 07:13:13 -0400 Received: from 93-95-228-168.1984.is ([93.95.228.168]:40633 helo=beleriand.n0.is) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bIwNg-000104-2D for guix-devel@gnu.org; Fri, 01 Jul 2016 07:13:08 -0400 Received: by beleriand.n0.is (OpenSMTPD) with ESMTPSA id eb305c3b TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Fri, 1 Jul 2016 11:13:00 +0000 (UTC) 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@gnu.org Hi, While I'm still new to guile and guix, one of my main motivations since I started contributing to guix was an item on the end of the roadmap, using a decentralized system to distribute updates. I have started to read through the scripts and underlying parts of guix, and also our guix/gnunet.git repository where some work already happened in GsoC 2015. Because this is very likely short, not very explanatory in detail, incomprehendable, you can view this email as a short introduction of the task, longer emails will follow once I have worked out texts and completed phase 0. At the moment I assume that the following items and steps are what's left to get closer to this system: 1. an up to date GNUnet a. 0.10.1 of gnunet-fs is not compatible to 0.9, gnunet-svn of gnunet-fs is not compatible to 0.10.1 https://gnunet.org/bot/log/gnunet/2016-06-23#T1067897 2. GNUnet system service for shepherd a. it needs a basic service to start with, ideally we provide what gnunet-setup does through an extended system-service later on 3. stitching together the guile GNUnet bindings with additions to mechanisms which are at least guix {publish,pull,package}. 4. taking in consideration the current incompabilities of gnunet-fs versions. 5. -optional- construct `gnunetfs-download', similiar to git-download and others, for origins (of software) which are available in gnunet. I have concrete ideas for solutions, interactions and users consent and more, but those will end up in an dedicated document which can be viewed online and/or appended to an email later. I will split the work into different phases: Phase 0: - learning about system services - write the shepherd gnunet-service - finish packaging gnunet-svn pinned to a functional svn position - learn more guile (continously) - a first theoretic design Phase 1: - learn more about the current guix publish, guix pull, guix package functionality - solve design questions Phase 2: - writing a proto-type which can be used in a test setup Phase 3: - have a functional test setup which can (guix) publish, pull, and package from gnunet-fs in addition to the current methods I will publish Phase 1 and later in a checkout of guix with a branch `guix-gnunet', accessible once they are created on both of these git urls: git://git.far37qbrwiredyo5.onion:/guix.git git://s.n0.is:/guix.git optionally even a .gnu address when I had time to set it up on the server The current goal for Phase 3 is summer 2017, but I can't predict how much time I can invest in the future or how fast I will progress with learning. -- ♥Ⓐ ng0 For non-prism friendly talk find me on psyced.org / loupsycedyglgamf.onion