From: ng0 <ng0@infotropique.org>
To: guix-devel@gnu.org
Subject: binary substitutes distribution via gnunet-fs - quick update
Date: Sun, 3 Sep 2017 13:24:11 +0000 [thread overview]
Message-ID: <20170903132411.aaosldtdmbwwn2rw@abyayala> (raw)
[-- Attachment #1: Type: text/plain, Size: 2750 bytes --]
The original GSoCs on this topic are a long way back now, and my
last message on this topic when I started to pick it up was more
than one year ago.
So where am I, with all of this? Obviously at the very least I had
the reality check that it takes a long time when it's done right.
I can't give an update on how our (infotropique collective) approach
differs from the past attempts, I should be able to do so over the
course of this semester (financial worries and soon university and
other things keep me busy).
Some people have joined me since I documented the efforts under a
collective name (infotropique), and it also developed beyond just this:
- 1. gnunet-fs binary substitutes distribution
- 2. gnunet-fs as a a secure data storage (in early design)
- 3. reusable blueprint of a system based on GuixSD
- 4. exploration of liquidfeedback integration
- and more (integration of GNUnet, etc, etc (I'm not a fan of
bullet points and good summaries right now)).
I had the logical development from "one goal" to "many goals"
because of the social and political implications which are
attached to the many branches of this project.
In spoken word I know how to describe the goals and intentions
of infotropique and how it's attached to GNUnet, Guix, etc.
Written words are fixed, so I'm still working on the best
presentation.
So where are we right now?
- 1: The December '16 - now has been rough to me, so I'm now
assembling from physical papers (bad habbits die hard..)
and emails the way forward. At least one person has joined
me with explicit wish to work on this.
Some work has been done in debugging GNUnet and contributing
towards the next release. Guix service needs to be debugged.
We will very likely only test against HEAD as having almost
4 years difference and the fixed bugs is just too much to
justify support of 0.10.1 with the work on a gnunet service
for GuixSD. At least that's my personal opinion, in general
the service should have no opinion on the version of
GNUnet.
- 3: Mostly the base and theory + roadmap/goals is done and it is
simply stuck at autotools and documentation right now (which
in turn need time).
Recently some ideas have been introduced to me which could
be solved in Guix.
Furthermore one basic idea related to the way of final
distribution has to be addressed within Guix once we
are at the point where "make dist" produces enough
material to justify a release candidate.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2017-09-03 13:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170903132411.aaosldtdmbwwn2rw@abyayala \
--to=ng0@infotropique.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).