From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: Call for project proposals: Guix and Outreachy Date: Sat, 10 Feb 2018 08:08:42 +0100 Message-ID: References: <87fu6y27re.fsf@elephly.net> <87zi4lg4ep.fsf@elephly.net> <20180207105721.GB2876@jurong> <87zi4jvbgg.fsf@gnu.org> <87mv0j78mc.fsf@elephly.net> <87inb76yp1.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a113f8c2ab1a8fb0564d650a2" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ekPHD-0006Ie-DX for guix-devel@gnu.org; Sat, 10 Feb 2018 02:08:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ekPHC-0007SW-59 for guix-devel@gnu.org; Sat, 10 Feb 2018 02:08:47 -0500 In-Reply-To: <87inb76yp1.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 --001a113f8c2ab1a8fb0564d650a2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2018-02-08 20:58 GMT+01:00 Ricardo Wurmus : > > G=C3=A1bor Boskovits writes: > > >> The project idea sounds good, but we really need a mentor who feels > >> responsible for this project and who will be able to guide an intern > >> throughout the application phase and the three-month internship betwee= n > >> from May to August. > [=E2=80=A6] > > > If we could draft the specifics of this, what we expect as a outcome > > at least, then I am willing to help in mentoring, if that suits you. I > > might drop some parts of the draft if I don't feel comfortable with > > some parts of the draft proposed. > > Thank you. > > > However I feel, that the expectations about this should be discussed > > publicly, to have a tool that is really useful for the community, > > WDYT? > > Yes, we should discuss this here, but we don=E2=80=99t have all that much= time > left before the intern application process begins. During that period > interns get to pick a project they are interested in and start getting > to know the community. At the end of the application period we need to > pick one of the applicants. > > So even though the internships won=E2=80=99t start before May, we really = need to > submit our proposals this week or early next week. > > Ok, I've thought about what my personal needs would be at first. I currently see three main aspects of this user interface: 1. statistics overall a. percentage of packages failing on a branch (with links) b. percentage of packages not reproducible (also with links) (can be interesting in the face of the content addressable store idea, but would be useful in general) 2. packages, that we tried to build: a. build status on achitectures b. build logs c. related bugs - can this be done easily? d. related build jobs 3. packages, that we would like to build a. estimated effort to do so b. privilege system to do it c. notification when a build completes d. some way to make this useful for collaborations - (for example if a bunch of developers is working on a feature branch, and the feel, that it is ok to build it, then somehow sum the resources allowable?) I am not very familiar with our current frontend yet, so if I have something, that is already done, please note me. If you have any other suggestions, that would be fine. > -- > Ricardo > > GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC > https://elephly.net > > > --001a113f8c2ab1a8fb0564d650a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2018= -02-08 20:58 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:=

G=C3=A1bor Boskovits <boskovits@g= mail.com> writes:

>> The project idea sounds good, but we really need a mentor who feel= s
>> responsible for this project and who will be able to guide an inte= rn
>> throughout the application phase and the three-month internship be= tween
>> from May to August.
[=E2=80=A6]

> If we could draft the specifics of this, what we expect as a outcome > at least, then I am willing to help in mentoring, if that suits you. I=
> might drop some parts of the draft if I don't feel comfortable wit= h
> some parts of the draft proposed.

Thank you.

> However I feel, that the expectations about this should be discussed > publicly, to have a tool that is really useful for the community,
> WDYT?

Yes, we should discuss this here, but we don=E2=80=99t have all that= much time
left before the intern application process begins.=C2=A0 During that period=
interns get to pick a project they are interested in and start getting
to know the community.=C2=A0 At the end of the application period we need t= o
pick one of the applicants.

So even though the internships won=E2=80=99t start before May, we really ne= ed to
submit our proposals this week or early next week.

<= br>
Ok, I've thought about what my personal needs would be at= first.
I currently see three main aspects of this user interface= :

1. statistics overall
a. percentage of= packages failing on a branch (with links)
b. percentage of packa= ges not reproducible (also with links) (can be interesting in the face of t= he content addressable store idea, but would be useful in general)

2. packages, that we tried to build:
a. build st= atus on achitectures
b. build logs
c. related bugs - ca= n this be done easily?
d. related build jobs

=
3. packages, that we would like to build
a. estimated effort= to do so
b. privilege system to do it
c. notification = when a build completes
d. some way to make this useful for collab= orations - (for example if a bunch of developers is working on a feature br= anch, and the feel, that it is ok to build it, then somehow sum the resourc= es allowable?)

I am not very familiar with our cur= rent frontend yet, so if I have something, that is already done, please not= e me.

If you have any other suggestions, that woul= d be fine.

=C2=A0
--
Ricardo

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



--001a113f8c2ab1a8fb0564d650a2--