RISC-V port for GSoC?

[ludo@gnu.org (Ludovic Courtès)]

Hello ng0,

ng0@n0.is skribis:

> On second thoughts I think it's okay to have all of this in
> public, there are no stupid questions.

In general it’s not OK to quote private messages on a public list
without the author’s consent.

No big deal in this case, but please keep that in mind in the future.

> On Mon, 05 Feb 2018, ludo@gnu.org (Ludovic Courtès) wrote:
>> Heya,
>>
>> ng0@n0.is skribis:
>>
>>> Sorry for the offlist message, but I thought since you list
>>> yourself as possible mentor for the item I'd ask.
>>
>> What?  I didn’t add myself there I think, we should find out where that
>> comes from.  :-)
>
> So.. who added Ludovic to the RISC-V item? And if not Ludovic,
> who'd be a good mentor for this item (and has time to spend on
> it)? Manolis has worked on porting to a different kernel, Efraim
> has worked on porting to another architecture.

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.

What do people think?  Should we remove it from the list of GSoC ideas?

(RISC-V porting in itself does sound useful to me, just somewhat
unsuitable for GSoC.)

Ludo’.