From: sapientech@openmailbox.org
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: GSOC 2016 Application
Date: Sat, 26 Mar 2016 00:08:27 -0700 [thread overview]
Message-ID: <019cf8e089dec4781c854424433dddf4@openmailbox.org> (raw)
In-Reply-To: <87h9fuilz8.fsf@gmail.com>
Hi Chris thanks for the response!
On 2016-03-25 09:03, Chris Marusich wrote:
> I would be happy to share with you the hacky little shell scripts I use
> to do this today. They're simple automations of the manual procedure,
> really, but perhaps they could be useful. I am not familiar with the
> implementation details of installer wizards used by other distros, but
> I've seen and used my fair share of them.
I would definitely like to see the shell scripts you have -- just let me
know how you would like to share those files.
>> - Consider both a text-based and graphical application using
>> guile-ncurses/libRUIN
>
> While it's good to plan for both text and graphical UI, maybe it will
> be
> more efficient to pick one to focus on, and treat the other as a
> stretch
> goal?
I agree and should turn the GUI interface into a stretch goal.
>> - Design for portability for use in other software distributions that
>> lack a proper installer wizard
>
> Again, this is a nice idea, but it might be more efficient to focus on
> getting it to work with Guix first.
>
>> - An emphasis on rigorous test suites, with stability prioritized over
>> features
>
> GuixSD is still beta software. Is it a good idea to make one of your
> goals be "the installer is stable" when the system it's installing is
> not stable?
I also agree with your sentiments here that I should prioritize Guix
before considering other operating systems.
One reason I think stability is particularly important here though, is
that installs have to check for a lot of edge cases, and it's generally
difficult for users to solve the problem since the api is so limited. I
agree I shouldn't go overboard, as Guile itself is in beta, though :)
Best,
Dylan
next prev parent reply other threads:[~2016-03-26 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 22:06 GSOC 2016 Application sapientech
2016-03-25 2:35 ` sapientech
2016-03-25 15:01 ` Christopher Allan Webber
2016-03-25 16:03 ` Chris Marusich
2016-03-26 7:08 ` sapientech [this message]
2016-03-26 11:29 ` Ludovic Courtès
2016-03-25 20:11 ` myglc2
2016-03-26 7:21 ` sapientech
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=019cf8e089dec4781c854424433dddf4@openmailbox.org \
--to=sapientech@openmailbox.org \
--cc=cmmarusich@gmail.com \
--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).