From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: RISC-V port for GSoC? Date: Thu, 08 Feb 2018 19:34:42 +0000 Message-ID: <87vaf7nulp.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> References: <87bmh4qrf5.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> <87bmh3kbd9.fsf@gnu.org> <87k1vqv23v.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> <87lgg3vb1y.fsf_-_@gnu.org> <87k1vn727y.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:32837) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejry0-00048H-Tz for guix-devel@gnu.org; Thu, 08 Feb 2018 14:34:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ejrxy-0000ND-3d for guix-devel@gnu.org; Thu, 08 Feb 2018 14:34:44 -0500 Received: from aibo.runbox.com ([91.220.196.211]:53914) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ejrxx-0000Mk-Sg for guix-devel@gnu.org; Thu, 08 Feb 2018 14:34:42 -0500 Received: from [10.9.9.212] (helo=mailfront12.runbox.com) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1ejrxw-0003KG-8W for guix-devel@gnu.org; Thu, 08 Feb 2018 20:34:40 +0100 Received: from dslb-088-078-026-213.088.078.pools.vodafone-ip.de ([88.78.26.213] helo=localhost) by mailfront12.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1ejrxt-0001pp-Gl for guix-devel@gnu.org; Thu, 08 Feb 2018 20:34:37 +0100 In-Reply-To: <87k1vn727y.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 08 Feb 2018 19:42:09 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org On Thu, 08 Feb 2018, Ricardo Wurmus wrote: > Ludovic Courtès writes: > >> To give some context, the issue is about the RISC-V port item at >> . >> >> 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/