all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@crash.cx>
To: guix-devel@gnu.org
Subject: Re: RISC-V port for GSoC?
Date: Thu, 08 Feb 2018 19:34:42 +0000	[thread overview]
Message-ID: <87vaf7nulp.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87k1vn727y.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 08 Feb 2018 19:42:09 +0100")

On Thu, 08 Feb 2018, Ricardo Wurmus <rekado@elephly.net> wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> To give some context, the issue is about the RISC-V port item at
>> <https://libreplanet.org/wiki/Group:Guix/GSoC-2018>.
>>
>> I’m happy to help with Guix porting insight, but apart from that I’m not
>> the most qualified person and I’d rather have someone else mentor it, if
>> someone were to take this project.  Any takers?
>>
>> Actually I’m unsure how good of a project it is for GSoC.  GSoC is about
>> development, but this one is not so much development, as Ricardo wrote
>> in the context of Outreachy.
>
> It’s difficult to mentor a project like that; a consequence is that it
> doesn’t really fit into the framework of GSoC, where mentors need to
> have some way of deciding if the student is still on track (and fail the
> student if necessary).
>
> For a project that is “follow the instructions” in the best case and
> “wait for upstream to fix it” in the worst case, I really don’t feel
> comfortable having this as a GSoC project.  Problems encountered in the
> porting effort are unforeseeable and could be outside the student’s
> means to work around them — what do we do then?  Fail the student?  Pass
> them by default?  It doesn’t really make sense to me to have a project
> that has big unknowns as dependencies.
>
> My opinion is to remove it from the list of GSoC ideas.

Okay, sounds more than reasonable. I also vote for removal.

So we have 4 people agreeing on removal.. let's take it down then.

>> (RISC-V porting in itself does sound useful to me, just somewhat
>> unsuitable for GSoC.)
>
> Same here.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> https://elephly.net

Thanks for all your replies, Ludovic, Ricardo and Gàbor.
-- 
ng0 :: https://crash.cx
A88C8ADD129828D7EAC02E52E22F9BBFEE348588 :: https://crash.cx/keys/

  parent reply	other threads:[~2018-02-08 19:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87bmh4qrf5.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me>
     [not found] ` <87bmh3kbd9.fsf@gnu.org>
2018-02-06 10:33   ` GSoC ng0
2018-02-08 11:25     ` GSoC ng0
2018-02-08 12:09       ` GSoC Gábor Boskovits
2018-02-08 12:31         ` GSoC ng0
2018-02-08 12:41           ` GSoC ng0
2018-02-08 13:57     ` RISC-V port for GSoC? Ludovic Courtès
2018-02-08 14:42       ` ng0
2018-02-08 18:42       ` Ricardo Wurmus
2018-02-08 19:19         ` Gábor Boskovits
2018-02-08 19:34         ` ng0 [this message]
2018-02-08 22:25           ` Ludovic Courtès
2018-02-08 16:42     ` ARM compilation via qemu binfmt - Assertion failure Danny Milosavljevic
2018-02-10 23:45       ` Chris Marusich
2018-02-11  1:07         ` bug#30394: " Leo Famulari
2018-02-11  1:07         ` Leo Famulari
2018-02-11  9:53         ` Pjotr Prins
2018-02-16 10:35       ` bug#30394: " Ludovic Courtès
2018-02-16 10:35       ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vaf7nulp.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me \
    --to=ng0@crash.cx \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.