From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Re: Seeking Outreachy internship project proposals Date: Sun, 08 Sep 2019 11:05:58 +0200 Message-ID: <875zm3b1jd.fsf@cbaines.net> References: <87imq8ffo9.fsf@cbaines.net> <87ftlc5f2h.fsf@cbaines.net> <87ftl9c3ry.fsf@cbaines.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38712) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i6t92-00021l-OY for guix-devel@gnu.org; Sun, 08 Sep 2019 05:06:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i6t91-0007S9-6p for guix-devel@gnu.org; Sun, 08 Sep 2019 05:06:04 -0400 Received: from mira.cbaines.net ([212.71.252.8]:50644) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1i6t90-0007Rg-Uf for guix-devel@gnu.org; Sun, 08 Sep 2019 05:06:03 -0400 In-reply-to: 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: =?utf-8?Q?G=C3=A1bor?= Boskovits Cc: Guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable G=C3=A1bor Boskovits writes: > Christopher Baines ezt =C3=ADrta (id=C5=91pont: 2019. = szept. 6., > P, 8:55): > >> >> G=C3=A1bor Boskovits writes: >> >> >> >> >> >> >> > After discussing this with Ricardo and Ludo, it seems that the way >> forward >> > would be to >> > get the project under the Guix umbrella, like it was done for cuirass.= If >> > you do not oppose, >> > I would like to ask Ludo to file a request for a sub-repository to >> > savannah-hackers, so that >> > we could move the code there. Wdyt? >> >> That works for me :) >> >> I guess this kind of thing relates to the "Project Contribution >> Information" part of the proposal. I think there's some other bits of >> preparation to do for this, like: >> >> - Making sure the service is actually running publicly somewhere (maybe >> milano-guix-1 if that's back working, maybe somewhere else if not) >> >> - Generating a small sample database that can be used for local >> development >> >> - Writing some step-by-step instructions for running the service >> locally >> >> I'm guessing that it would be ideal to have all this done by the 24th of >> September, but it would be good to clarify that? >> >> > It would be nice to have it by the 24th. > I guess we can skip the publicly running instance, if we must. Since my last email, milano-guix-1 is back online, so for now there is a public instance at [1]. I'm looking at setting up DNS and other things so that it's available at data.guix.gnu.org. 1: http://milano-guix-1.di.unimi.it:8765/ >> > Also, should you need any help in finding out what to do with the TODO >> > sections, we could arrange >> > an appointment on IRC. How does that sound? >> >> Regarding the "Internship Tasks", I have some ideas here that I haven't >> written up yet, I also just need to do some more thinking and >> investigating. I'm sure if I spend some time looking, I can find some >> rough edges in the functionality that would make good small tasks. >> >> I'm not particularly clear on the timeline for this though, does this >> need to be done by the 24th of September, or sooner? >> > > The proposal is just a rough project outline, which can be refined later, > but should be in its final form by the 24, so that applicants reading it > can have a rough estimate of the timeline, and of the milestones. Ok, that sounds fine. > Having starter tasks defined is actually outside the scope of Outreachy, = but > an applicant must have a valid contribution to the project by the time of > intern > selection. These are also very helpful for you to know what it would be > like to with > a given intern. I would say there is no strict timeline on this, but very > much reduces > the communication overhead at the beginning, thus it is easier for you, a= nd > more > attractive to the applicants. Wdyt? That all sounds fine to me, I've updated the application with some tasks which I think would make good initial contributions. I'm not sure how relevant I can make them to the project (without making them too complicated), so I've just been looking for small improvements to the exisiting functionality (mostly specifying JSON responses, where I haven't). >> > Also, Ricardo brought to my attention the following things, that could ... >> Some beginning, and sub-tasks need outlining, and once that is more >> understood, hopefully we'll be in a better place to check if the above >> is a reasonable goal. I think it would be also good to add some stretch >> goals as well. >> > > Yes, stretch tasks also make sense. Later the applicants will also be ask= ed > to > a timeline. It is nice if they plan some spare time in their schedule, so > that they > can stay on deadline, and be less stressed about it. Sounds good :) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl10xHZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9Xf7wxAApl4Taof5QL9vvN0hbKQ/UUf6itpGP3MSsyPi4mZHkTiTxhAgvuuAnd5/ EUBpzTx0FXMLqplISdGu5PeqnelUx61af4cJ7CvoK2McVumq0txJ2rY8cj9ruJ5W H1To8o6d7R7s/Hjy4OCNFyJg7K0WhvQ++EGv5Yl2ydtr4pCRzBUf265wYpr5CKJj IWIGQ1kFNPRlxQM87dSOSR3VPO4XB91frJMBLp/1IyLtwemWWjxtDNE3vlKzevSf KobpbtrIi7ZP69cYYo5dUHEpYyO1oncTb5DSm8LCKb+cyDqT9Vgi8qwVZ79801xU TkeEhXksWuXjo/XxlUsmPJmQFrxIsboBtXwCfn3yTACx8402lVdTdE5LSdjqrmGm OUpzFcERe4UQmqJJ7gRGc8z0dlFnfTsopp6JWEYqu3jfi9rvSOPANHo7fncQtFs/ aNAPVD75HiSNrR9EWQPMvjh3zMLW+QPrp9F0LgFSLWsYur2cRc/Q3DRJi91qExlM b3fw6HHWQT5SGmIJPs5tL0eXfHPd/RrukeeReoH6KA8+3+NboDRD7ScQ1mWRu6pQ Hk/r5Hf60fxQXmP8a5oC0rc2FV3ulz4mpP3+egMIu1AEZnn0Voz7GM2Wf1RUkSiK zK3v8Graiwr1ZiQWNurLbrQe7nxMXPzCgYZTdusQ2XGQKMOFWaU= =VFBp -----END PGP SIGNATURE----- --=-=-=--