From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: GSoC: Adding a web interface similar to the Hydra web interface Date: Fri, 18 May 2018 22:35:11 +0200 Message-ID: <87d0xswvls.fsf@elephly.net> References: <87vac3twbe.fsf@gnu.org> <87o9hog2ye.fsf@elephly.net> <87d0xyn9zs.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fJpcp-0005zy-0S for guix-devel@gnu.org; Fri, 18 May 2018 20:21:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fJpcj-0002wH-C8 for guix-devel@gnu.org; Fri, 18 May 2018 20:21:29 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21112) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fJpcj-0002vx-3y for guix-devel@gnu.org; Fri, 18 May 2018 20:21:25 -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: Tatiana Sholokhova Cc: guix-devel Hi Tatiana, > I have started thinking about the type of web interface we want to have f= or > Cuirass in this project. As far as I see, there are two options: > > - a web application served by Cuirass web server; > - a standalone static site which sends queries to the Cuirass web API > (this is similar to Danny's application); > > I suppose that the first option has more benefits since it allows to choo= se > the exact type of information required to be extracted from the database = by > a specific part of the web interface. What do think regarding these optio= ns? You are free to extend the Cuirass web API to suit your application=E2=80= =99s needs. Having a standalone site is a valid way of providing a web interface, but it doesn=E2=80=99t have to be the only way of accessing the information. Even if you go for the first route, the HTML you serve could talk to the API. These two options don=E2=80=99t have to be mutually exclusive. FWIW, I expect the first approach to be easier because you can use Scheme for the most part; the pages it serves could be progressively enhanced with JavaScript, if the client supports it. I=E2=80=99m sure ther= e are many users who would prefer a system that would work fine even without running JavaScript in the browser. > How will we organize the development process? More precisely, where > should I place the implemented code in order to provide access to it > for our team? In my experience, I have used to create the separate > branch in the git repository. I would like to know which way of doing > this you would prefer. I forgot how we did this for past GSoC, but my preference is to do this in a separate branch of the Cuirass git repository. Do you have an account on Savannah yet? Once you do we could give you permissions to push your work to a separate branch on the repository. (You are free to host the code elsewhere as long as we have read access via git.) -- Ricardo