From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tatiana Sholokhova Subject: Re: GSoC: Adding a web interface similar to the Hydra web interface Date: Fri, 18 May 2018 01:31:32 +0300 Message-ID: References: <87vac3twbe.fsf@gnu.org> <87o9hog2ye.fsf@elephly.net> <87d0xyn9zs.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000c6e499056c6e65e0" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44908) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fJRQv-00051G-Mt for guix-devel@gnu.org; Thu, 17 May 2018 18:31:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fJRQu-0004Kf-JP for guix-devel@gnu.org; Thu, 17 May 2018 18:31:37 -0400 In-Reply-To: <87d0xyn9zs.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 --000000000000c6e499056c6e65e0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello everyone, Thank you for the proposed ways of dealing with the problem I've faced. Eventually, I have managed to run Danny's application locally. I have learned all the queries to Cuirass web API which the application sends and the general workflow of the interface. I have started thinking about the type of web interface we want to have for 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 choose 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 options= ? Since I am a newcomer to the guix developers team, I have a question related to the interface development workflow. Once we choose the desired type of the web interface, I will start implementing it. 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. Best regards, Tatiana 2018-05-14 7:20 GMT+03:00 Ricardo Wurmus : > > Hi Tatiana, > > > Unfortunately, I have no experience of IRC usage and I'm not sure how t= o > do > > in a proper way. Of course, I would like to communicate with the > community, > > but I'm not sure which discussions are relevant in the IRC. For instanc= e, > > could I ask questions on building issues similar to ones I've > encountered? > > Yes, anything relating to the project that is easier discussed live is > appropriate for the IRC channel. > > If you don=E2=80=99t have an IRC client you can use > > https://webchat.freenode.net/ > > Input any nickname and #guix as the channel. > > -- > Ricardo > > > --000000000000c6e499056c6e65e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello everyone,

Thank you fo= r the proposed ways of dealing with the problem I've faced. Eventually,= I have managed to run Danny's application locally. I have learned all = the queries to Cuirass web API which the application sends and the general = workflow of the interface.

I have started thinking= about the type of web interface we want to have for Cuirass in this projec= t. As far as I see, there are two options:
  • a web applicat= ion served by Cuirass web server;
  • a=C2=A0standalone static site whi= ch sends queries to the Cuirass web API (this is similar to Danny's app= lication);
I suppose that the first option has more ben= efits since it allows to choose the exact type of information required to b= e extracted from the database by a specific part of the web interface. What= do think regarding these options?

Since I am a ne= wcomer to the guix developers team, I have a question related to the interf= ace development workflow. Once we choose the desired type of the web interf= ace, I will start implementing it. How will we organize the development pro= cess? 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.

Best regards,
Tatiana

2018-05-14 7:20 GMT+03:00 Ricardo Wurmus <rekado@elephly.net&= gt;:

Hi Tatiana,

> Unfortunately, I have no experience of IRC usage and I'm not sure = how to do
> in a proper way. Of course, I would like to communicate with the commu= nity,
> but I'm not sure which discussions are relevant in the IRC. For in= stance,
> could I ask questions on building issues similar to ones I've enco= untered?

Yes, anything relating to the project that is easier discussed live = is
appropriate for the IRC channel.

If you don=E2=80=99t have an IRC client you can use

=C2=A0 =C2=A0 https://webchat.freenode.net/

Input any nickname and #guix as the channel.

--
Ricardo



--000000000000c6e499056c6e65e0--