From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: RISC-V port for GSoC? Date: Thu, 8 Feb 2018 20:19:48 +0100 Message-ID: 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: multipart/alternative; boundary="94eb2c049e5c9d59770564b84b8e" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56506) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejrjc-0007ca-NM for guix-devel@gnu.org; Thu, 08 Feb 2018 14:19:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ejrjb-0006pv-B8 for guix-devel@gnu.org; Thu, 08 Feb 2018 14:19:52 -0500 In-Reply-To: <87k1vn727y.fsf@elephly.net> 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: Ricardo Wurmus Cc: Guix-devel , ng0@n0.is --94eb2c049e5c9d59770564b84b8e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2018-02-08 19:42 GMT+01:00 Ricardo Wurmus : > > Ludovic Court=C3=A8s writes: > > > To give some context, the issue is about the RISC-V port item at > > . > > > > I=E2=80=99m happy to help with Guix porting insight, but apart from tha= t I=E2=80=99m not > > the most qualified person and I=E2=80=99d rather have someone else ment= or it, if > > someone were to take this project. Any takers? > > > > Actually I=E2=80=99m 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=E2=80=99s difficult to mentor a project like that; a consequence is th= at it > doesn=E2=80=99t 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 =E2=80=9Cfollow the instructions=E2=80=9D in the be= st case and > =E2=80=9Cwait for upstream to fix it=E2=80=9D in the worst case, I really= don=E2=80=99t feel > comfortable having this as a GSoC project. Problems encountered in the > porting effort are unforeseeable and could be outside the student=E2=80= =99s > means to work around them =E2=80=94 what do we do then? Fail the student= ? Pass > them by default? It doesn=E2=80=99t really make sense to me to have a pr= oject > that has big unknowns as dependencies. > > My opinion is to remove it from the list of GSoC ideas. > > > (RISC-V porting in itself does sound useful to me, just somewhat > > unsuitable for GSoC.) > > Same here. > > Ok, remove it from the list then. It really seems, that this project does not suit GSoC. I am interested in getting this work, but GSoC does not seem to be th= e place for this. > -- > Ricardo > > GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC > https://elephly.net > > > > --94eb2c049e5c9d59770564b84b8e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2018= -02-08 19:42 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:=

Ludovic Court=C3=A8s <ludo@gnu.org&g= t; writes:

> To give some context, the issue is about the RISC-V port item at
> <https://libreplanet.org/wiki/Group:G= uix/GSoC-2018>.
>
> I=E2=80=99m happy to help with Guix porting insight, but apart from th= at I=E2=80=99m not
> the most qualified person and I=E2=80=99d rather have someone else men= tor it, if
> someone were to take this project.=C2=A0 Any takers?
>
> Actually I=E2=80=99m unsure how good of a project it is for GSoC.=C2= =A0 GSoC is about
> development, but this one is not so much development, as Ricardo wrote=
> in the context of Outreachy.

It=E2=80=99s difficult to mentor a project like that; a consequence = is that it
doesn=E2=80=99t really fit into the framework of GSoC, where mentors need t= o
have some way of deciding if the student is still on track (and fail the student if necessary).

For a project that is =E2=80=9Cfollow the instructions=E2=80=9D in the best= case and
=E2=80=9Cwait for upstream to fix it=E2=80=9D in the worst case, I really d= on=E2=80=99t feel
comfortable having this as a GSoC project.=C2=A0 Problems encountered in th= e
porting effort are unforeseeable and could be outside the student=E2=80=99s=
means to work around them =E2=80=94 what do we do then?=C2=A0 Fail the stud= ent?=C2=A0 Pass
them by default?=C2=A0 It doesn=E2=80=99t 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.

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

Same here.

Ok, remove it from the list then. It really seems, th= at this project does not suit
GSoC. I am interested in getting th= is work, but GSoC does not seem to be the
place for this.=C2=A0
--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6=C2=A0 2150 197A 5888 235F ACAC
https:= //elephly.net




--94eb2c049e5c9d59770564b84b8e--