From: Chris Marusich <cmmarusich@gmail.com>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel@gnu.org
Subject: Re: Please review blog post draft: powerpc64le-linux support
Date: Wed, 07 Apr 2021 23:04:37 -0700 [thread overview]
Message-ID: <87v98xnwga.fsf@gmail.com> (raw)
In-Reply-To: <e05a61642ee0c6a59f122b5727f427289eab1c19.camel@zaclys.net> ("Léo Le Bouter"'s message of "Wed, 07 Apr 2021 01:13:31 +0200")
[-- Attachment #1: Type: text/plain, Size: 2478 bytes --]
Hi Léo,
Léo Le Bouter <lle-bout@zaclys.net> writes:
> It's been mostly you here Chris, thank you so much for writing it, as
> others said, it is really beautifully written! Unfortunately I havent
> felt enough peace of mind to write like you did :-(
You've been busy! It's totally understandable. The encouragement from
you and others has been very useful and motivating for me, so thank you.
> I would've liked to write about the early days where I met some
> problems with the core-updates branch having to rebase several times
> and learning GNU Guix at the same time since my first ever project
> related to GNU Guix was porting before even trying to use it elsewhere.
> Having to learn the GNU commit message guidelines, then learning git-
> send-email and GNU Emacs (since that's where all dev tools are), all
> that to contribute to GNU Guix and get this port in. Aaaahh very long
> story!
I agree. Those are interesting topics. I tried to include some
discussion about it, but the post became too lengthy. I just want it to
be about the new support, mainly, and why it's exciting.
I think that the following related topics would make good candidates for
future blog posts:
- An analysis of trust in Guix, with an eye towards bootstrapping. If
you use substitutes, what are you implicitly trusting? If you build
without substitutes, what are you implicitly trusting? If you build
Guix from source without using Guix, like you have to do when you
first port Guix to a new platform, what are you trusting? A
comparison of similar paths of trust when using other software. Make
a script to find out if there are any forgotten "bootstrap roots"
beyond the bootstrap binaries, like there apparently used to be for
some self-hosted compilers (see:
https://lists.gnu.org/archive/html/guix-devel/2015-02/msg00814.html).
Stuff like that. I think it is not obvious.
- An analysis of the hurdles / friction involved in contributing.
Preferably with suggestions for ways to remove the hurdles and reduce
friction. It is easy to complain or bikeshed, of course, but the
point is not to do that. The point is to discuss issues to try and
make things better.
Thank you again for your help! This is just the beginning - let's keep
hacking away at it and improving POWER9 support together! Hopefully
others will see the benefits of the platform and join us along the way.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-04-08 6:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 7:15 Please review blog post draft: powerpc64le-linux support Chris Marusich
2021-04-06 15:47 ` Joshua Branson
2021-04-08 5:46 ` Chris Marusich
2021-04-06 23:13 ` Léo Le Bouter
2021-04-08 6:04 ` Chris Marusich [this message]
2021-04-08 8:55 ` Chris Marusich
2021-04-08 10:49 ` Vincent Legoll
2021-04-08 16:37 ` Chris Marusich
2021-04-08 17:15 ` Vincent Legoll
2021-04-08 22:59 ` Léo Le Bouter
2021-04-10 9:59 ` Tobias Platen
2021-04-11 7:34 ` Chris Marusich
2021-04-11 7:37 ` Chris Marusich
2021-04-12 19:46 ` Chris Marusich
2021-04-15 22:06 ` Léo Le Bouter
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=87v98xnwga.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
/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).