Re: Next Steps For the Software Heritage Problem

2024-06-28 Thread Juliana Sims
Hey y'all, I've avoided weighing in on this topic because I'm of two minds about it. Still, when members of the community raise concerns, it's important to take those concerns seriously. We must be careful how we address them because the opinions and concerns of any community member are as le

Re: Next Steps For the Software Heritage Problem

2024-06-27 Thread Ludovic Courtès
Hi, Ian Eure skribis: > While this is what their paper claims[1], it doesn’t appear to be > true, since I can see my own GPL’d code in the training set. I’ve > since moved nearly all of my code off GitHub, but if you visit their > "Am I in The Stack?" page[2] and enter my old username ("ieure")

Re: Next Steps For the Software Heritage Problem

2024-06-27 Thread Development of GNU Guix and the GNU System distribution.
Hi Ian, On Thu, Jun 27 2024, Ian Eure wrote: > I’ve [...] moved nearly all of my code off GitHub Me too. I think closed it off from search crawlers. No one should be using Github anymore except for merge requests. I left many years ago. > if you visit their "Am I in The Stack?" page Thank y

Re: Next Steps For the Software Heritage Problem

2024-06-27 Thread Ian Eure
Hi Ludo, Ludovic Courtès writes: Ian Eure skribis: Guix sends archive requests to SWH. SWH gives that source code to HuggingFace. HuggingFace demonstrably violates the licenses. Which licenses? As has been said previously, and you can verify for yourself, it does not ingest code und

Re: Next Steps For the Software Heritage Problem

2024-06-27 Thread Ludovic Courtès
Ian Eure skribis: > Guix sends archive requests to SWH. SWH gives that source code to > HuggingFace. HuggingFace demonstrably violates the licenses. Which licenses? As has been said previously, and you can verify for yourself, it does not ingest code under copyleft licenses. Ludo’.

Re: Next Steps For the Software Heritage Problem

2024-06-21 Thread Luis Felipe
Hi, El 21/06/24 a las 9:19, MSavoritias escribió: On Fri, 21 Jun 2024 09:41:10 +0100 Dale Mellor wrote: `-x archival` does it, but it is too easy to forget and once the cat is out of the bag privacy is lost. I really think this should be default behaviour, or at least there should be a

Re: Next Steps For the Software Heritage Problem

2024-06-21 Thread MSavoritias
On Fri, 21 Jun 2024 09:41:10 +0100 Dale Mellor wrote: > On Thu, 2024-06-20 at 22:59 +0200, Ekaitz Zarraga wrote: > > Hi, > > > > On 2024-06-20 22:54, Andreas Enge wrote: > > > Am Thu, Jun 20, 2024 at 07:42:44PM +0100 schrieb Dale Mellor: > > > > I'm sure guix lint tried to push my code out t

Re: Next Steps For the Software Heritage Problem

2024-06-21 Thread MSavoritias
On Thu, 20 Jun 2024 16:40:57 +0200 Simon Tournier wrote: > Being concrete and explicit, could you please share: > > 1. Which part of your code is included in the pretraining dataset? > > It’s easy, you can copy/paste a snippet and it returns the location > from where it comes from. >

Re: Next Steps For the Software Heritage Problem

2024-06-21 Thread MSavoritias
On Thu, 20 Jun 2024 16:35:10 +0200 Ekaitz Zarraga wrote: > > 2. You seem to imply that Free Software or code is apolitical. (in the > > sense of social or state politics not) Which it is not. Nothing is. > > For example Free Software is explicitly pro-capitalist and > > pro-Google/big companies.

Re: Next Steps For the Software Heritage Problem

2024-06-21 Thread Dale Mellor
On Thu, 2024-06-20 at 22:59 +0200, Ekaitz Zarraga wrote: > Hi, > > On 2024-06-20 22:54, Andreas Enge wrote: > > Am Thu, Jun 20, 2024 at 07:42:44PM +0100 schrieb Dale Mellor: > > > I'm sure guix lint tried to push my code out to them the last time I > > > tried. > > > > Ah indeed, there is this in

Re: Next Steps For the Software Heritage Problem (Dale Mellor)

2024-06-21 Thread MSavoritias
On Thu, 20 Jun 2024 14:43:30 -0700 Andy Tai wrote: > > Date: Wed, 19 Jun 2024 09:36:29 +0100 > > From: Dale Mellor > > I use Guix as a tool to develop my own projects, private and > > personal for reasons I'm keeping to myself. As part of that I write package > > definitions for them, and use t

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Simon Tournier
Hi, On Thu, 20 Jun 2024 at 19:42, Dale Mellor wrote: > I'm sure guix lint tried to push my code out to them the last time I > tried. Yes, it’s the checker ’archival’. Therefore, running “guix lint -x archival” does not send any request to SWH. Cheers, simon

Re: Next Steps For the Software Heritage Problem (Dale Mellor)

2024-06-20 Thread Andy Tai
> Date: Wed, 19 Jun 2024 09:36:29 +0100 > From: Dale Mellor > I use Guix as a tool to develop my own projects, private and > personal for reasons I'm keeping to myself. As part of that I write package > definitions for them, and use the Guix machinery to build and test. I > *cannot* > have Guix

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Andreas Enge
Am Thu, Jun 20, 2024 at 10:59:41PM +0200 schrieb Ekaitz Zarraga: > For this specific case we could add some flag to the command line like > `--do-not-archive` or something like that. guix lint -x archival if I understand "guix lint --help" correctly. Andreas

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Ekaitz Zarraga
Hi, On 2024-06-20 22:54, Andreas Enge wrote: Am Thu, Jun 20, 2024 at 07:42:44PM +0100 schrieb Dale Mellor: I'm sure guix lint tried to push my code out to them the last time I tried. Ah indeed, there is this in guix/lint.scm: (define (check-archival package) "Check whether PACKAGE's sourc

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Andreas Enge
Am Thu, Jun 20, 2024 at 07:42:44PM +0100 schrieb Dale Mellor: > I'm sure guix lint tried to push my code out to them the last time I tried. Ah indeed, there is this in guix/lint.scm: (define (check-archival package) "Check whether PACKAGE's source code is archived on Software Heritage. If it's

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Dale Mellor
On Thu, 2024-06-20 at 19:00 +0200, Andreas Enge wrote: > Am Wed, Jun 19, 2024 at 09:36:29AM +0100 schrieb Dale Mellor: > >   No, it's not.  I use Guix as a tool to develop my own projects, private > > and > > personal for reasons I'm keeping to myself.  As part of that I write package > > definitio

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Andreas Enge
Am Wed, Jun 19, 2024 at 09:36:29AM +0100 schrieb Dale Mellor: > No, it's not. I use Guix as a tool to develop my own projects, private and > personal for reasons I'm keeping to myself. As part of that I write package > definitions for them, and use the Guix machinery to build and test. I > *c

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Dale Mellor
On Tue, 2024-06-18 at 07:19 -0700, Ian Eure wrote: > Hi MSavoritias, > > Thank you for the email. > > I’m going to lay out this situation as clearly as I can, in the > hope that others will better understand, and hopefully treat it > with the seriousness it deserves. > > 1. Guix requests SWH t

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Simon Tournier
Hi MSavoritias, all, On Thu, 20 Jun 2024 at 09:51, MSavoritias wrote: >> Not to avoid the question but from a pragmatic point of view, one >> might ask if the source code you write and do not want to be included >> in the training dataset, if this source code is concretely part of >> that traini

Re: Next Steps For the Software Heritage Problem

2024-06-20 Thread Ekaitz Zarraga
Hi, On 2024-06-20 08:36, MSavoritias wrote: On Wed, 19 Jun 2024 17:46:08 +0200 Ekaitz Zarraga wrote: On 2024-06-19 12:25, raingl...@riseup.net wrote: On 2024-06-19 11:54, Efraim Flashner wrote: On Wed, Jun 19, 2024 at 12:13:38PM +0300, MSavoritias wrote: ... One of our packages, dbxfs, lef

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread MSavoritias
issues with LLMs or code harvesting without consent. - Efraim seemed to have suggested that there hasn't been any communication and its even offtopic. - Nothing has been written from Guix or SWH publicly about it and there are no mechanisms in place in the short term even to mitigate some of these things. (Which my next steps try to fix when I make the patches in a few weeks) Regards, MSavoritias > Cheers, > simon

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread MSavoritias
On Wed, 19 Jun 2024 17:46:08 +0200 Ekaitz Zarraga wrote: > On 2024-06-19 12:25, raingl...@riseup.net wrote: > > On 2024-06-19 11:54, Efraim Flashner wrote: > >> On Wed, Jun 19, 2024 at 12:13:38PM +0300, MSavoritias wrote: > >> ... > >> One of our packages, dbxfs, left Github a while ago and con

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread MSavoritias
On Wed, 19 Jun 2024 19:56:26 -0700 Felix Lechner wrote: > Hi MSavoritias, > > On Wed, Jun 19 2024, MSavoritias wrote: > > > I am not interested what the states or licenses/copyrights allow or > > don't allow in this case. What I care about is what we expect as a > > community when we submit a p

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread Development of GNU Guix and the GNU System distribution.
Hi MSavoritias, On Wed, Jun 19 2024, MSavoritias wrote: > I am not interested what the states or licenses/copyrights allow or > don't allow in this case. What I care about is what we expect as a > community when we submit a package/code to guix and if that violates > our social rules and expectat

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread Ekaitz Zarraga
On 2024-06-19 12:25, raingl...@riseup.net wrote: On 2024-06-19 11:54, Efraim Flashner wrote: On Wed, Jun 19, 2024 at 12:13:38PM +0300, MSavoritias wrote: ... One of our packages, dbxfs, left Github a while ago and continued development on a different forge. They adjusted their README to disallow

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread Simon Tournier
Hi MSavoritias, all, Let me provide more context. The concern started couple of months ago, to my knowledge. And discussion is still on going. So I think that’s incorrect to say “any result for over 6 months”. Moreover, I feel you have a misunderstanding about HuggingFace and SWH partnership.

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread MSavoritias
On Wed, 19 Jun 2024 12:54:30 +0300 Efraim Flashner wrote: > On Wed, Jun 19, 2024 at 12:13:38PM +0300, MSavoritias wrote: > > On Wed, 19 Jun 2024 09:52:36 +0200 > > Simon Tournier wrote: > > > > > Hi Ian, all, > > > > > > On Tue, 18 Jun 2024 at 10:57, Ian Eure wrote: > > > > I think that LLM

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread raingloom
On 2024-06-18 20:08, Ian Eure wrote: > Andy Tai writes: > >> What is the role of GNU Guix in this? If Guix is mainly a referral >> mechanism like web page links to the actual contents, the real problem >> is not Guix but the use of free software which can be obtained via >> other mechanisms direc

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread raingloom
On 2024-06-19 11:54, Efraim Flashner wrote: > On Wed, Jun 19, 2024 at 12:13:38PM +0300, MSavoritias wrote: > ... > One of our packages, dbxfs, left Github a while ago and continued > development on a different forge. They adjusted their README to disallow > hosting of their code on Github. Based on

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread Efraim Flashner
On Tue, Jun 18, 2024 at 11:37:17AM +0300, MSavoritias wrote: > Hello, > So with that said I urge anybody who has been in contact with them in > an official Guix capacity to come forward, otherwise I can volunteer to > be that. Idk if we have a community outreach thing I need to be in also > for th

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread Efraim Flashner
On Wed, Jun 19, 2024 at 10:01:43AM +0300, MSavoritias wrote: > On Tue, 18 Jun 2024 13:31:02 -0400 > Greg Hogan wrote: > > > On Tue, Jun 18, 2024 at 12:33 PM MSavoritias > > wrote: > > > > > > > If you feel that LLMs/AI are violating the terms of a license, then > > feel free to pursue that thr

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread Efraim Flashner
On Wed, Jun 19, 2024 at 12:13:38PM +0300, MSavoritias wrote: > On Wed, 19 Jun 2024 09:52:36 +0200 > Simon Tournier wrote: > > > Hi Ian, all, > > > > On Tue, 18 Jun 2024 at 10:57, Ian Eure wrote: > > > > > Guix is continuing to partner with SWH in spite of their continued > > > support of thes

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread MSavoritias
On Wed, 19 Jun 2024 09:52:36 +0200 Simon Tournier wrote: > Hi Ian, all, > > On Tue, 18 Jun 2024 at 10:57, Ian Eure wrote: > > > Guix is continuing to partner with SWH in spite of their continued > > support of these violations. > > Quickly because I am in the middle of a busy day. :-) Hey

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread Simon Tournier
Hi Ian, all, On Tue, 18 Jun 2024 at 10:57, Ian Eure wrote: > Guix is continuing to partner with SWH in spite of their continued > support of these violations. Quickly because I am in the middle of a busy day. :-) I think that LLM asks ethical and legal question that even FSF or EFF or SFC doe

Re: Next Steps For the Software Heritage Problem

2024-06-19 Thread MSavoritias
On Tue, 18 Jun 2024 13:31:02 -0400 Greg Hogan wrote: > On Tue, Jun 18, 2024 at 12:33 PM MSavoritias > wrote: > > > > Ah it seems I wasn't clear enough. > > I meant write something like: > > > > By packaging a software project for Guix you are exposing said > > software to a code harvesting proje

Re: Next Steps For the Software Heritage Problem

2024-06-18 Thread Ian Eure
Guix sends archive requests to SWH. SWH gives that source code to HuggingFace. HuggingFace demonstrably violates the licenses. Guix could stop sending archive requests to SWH. This wouldn’t *stop* the bad things from happening, but it would *stop condoning* them. The same as how Guix not a

Re: Next Steps For the Software Heritage Problem

2024-06-18 Thread Ian Eure
Hi Greg, Please read my earlier reply in this thread[1]. HuggingFace is demonstrably violating the licenses of the Free Software used to train its StarCoder2 LLM. Software Heritage is continuing to partner with HuggingFace in spite of these violations. Guix is continuing to partner with SW

Re: Next Steps For the Software Heritage Problem

2024-06-18 Thread Greg Hogan
On Tue, Jun 18, 2024 at 12:33 PM MSavoritias wrote: > > Ah it seems I wasn't clear enough. > I meant write something like: > > By packaging a software project for Guix you are exposing said software > to a code harvesting project (also known as LLMs or "AI") run by > Software Heritage and/or their

Re: Next Steps For the Software Heritage Problem

2024-06-18 Thread Andy Tai
What is the role of GNU Guix in this? If Guix is mainly a referral mechanism like web page links to the actual contents, the real problem is not Guix but the use of free software which can be obtained via other mechanisms directly anyway to train LLMs if Guix is not in the loop?

Re: Next Steps For the Software Heritage Problem

2024-06-18 Thread MSavoritias
On Tue, 18 Jun 2024 12:21:33 -0400 Greg Hogan wrote: > On Tue, Jun 18, 2024 at 4:37 AM MSavoritias > wrote: > > > > 1. Add a clear disclaimer/requirment that any new package that is > > added in Guix, the person has to give consent or get consent from > > the person that the package is written i

Re: Next Steps For the Software Heritage Problem

2024-06-18 Thread Greg Hogan
On Tue, Jun 18, 2024 at 4:37 AM MSavoritias wrote: > > 1. Add a clear disclaimer/requirment that any new package that is added > in Guix, the person has to give consent or get consent from the person > that the package is written in. This needs to be added in the docs and > in the email procedures

Re: Next Steps For the Software Heritage Problem

2024-06-18 Thread Ian Eure
ppens when they submit packages to Guix. So it is all done without consent. Next Steps: So what can we do as a Guix community from here? Communication/Writing wise: 1. Add a clear disclaimer/requirment that any new package that is added in Guix, the person has to give consent or get consent from t

Next Steps For the Software Heritage Problem

2024-06-18 Thread MSavoritias
on of course :) This is against our desire to make it a welcoming space and also against the spirit of our CoC. Specifically because authors do not know this happens when they submit packages to Guix. So it is all done without consent. Next Steps: So what can we do as a Guix community from

Re: Hurd substitute availability (27.5%) and next steps?

2021-03-09 Thread Svante Signell
On Mon, 2021-03-08 at 22:47 +, Christopher Baines wrote: > Vincent Legoll writes: > > > often I'll be unable to SSH in > > > > Couldn't you get a console from a virtual serial port from the VM ? > > Maybe, I also want to look at getting the serial port output logged > to a file (if that's e

Re: Hurd substitute availability (27.5%) and next steps?

2021-03-09 Thread Efraim Flashner
On Tue, Mar 09, 2021 at 07:57:33AM +, Christopher Baines wrote: > > jbra...@dismail.de writes: > > > I'd be happy to reformat this as a guix blog post, unless you'd rather > > I not. > > I think another blog post on the Hurd would be nice, although I'm not > sure what the main takeaway shoul

Re: Hurd substitute availability (27.5%) and next steps?

2021-03-08 Thread Christopher Baines
jbra...@dismail.de writes: > I'd be happy to reformat this as a guix blog post, unless you'd rather > I not. I think another blog post on the Hurd would be nice, although I'm not sure what the main takeaway should be. The substitute availability stat I led this email thread with doesn't really c

Re: Hurd substitute availability (27.5%) and next steps?

2021-03-08 Thread jbranso
one&limit_results=50 > > The util-linux and tcl failures are both test related, and I believe > building without the tests works. With this data, given a package which > isn't build for the Hurd, say git as an example, it's possible to find > out which relevant builds are

Re: Hurd substitute availability (27.5%) and next steps?

2021-03-08 Thread Christopher Baines
Vincent Legoll writes: > Hello, > > On Mon, Mar 8, 2021 at 10:57 PM Christopher Baines wrote: >> In terms of getting more packages building, and substitute availability, >> personally I think it would be useful to disable tests for packages for >> i586-gnu if that gets packages building. It's n

Re: Hurd substitute availability (27.5%) and next steps?

2021-03-08 Thread Vincent Legoll
Hello, On Mon, Mar 8, 2021 at 10:57 PM Christopher Baines wrote: > In terms of getting more packages building, and substitute availability, > personally I think it would be useful to disable tests for packages for > i586-gnu if that gets packages building. It's not ideal to not run the > tests, b

Hurd substitute availability (27.5%) and next steps?

2021-03-08 Thread Christopher Baines
s works. With this data, given a package which isn't build for the Hurd, say git as an example, it's possible to find out which relevant builds are failing [4]. 4: https://data.guix-patches.cbaines.net/build-server/3/build?build_server_build_id=4ebf32a7-5b1e-425f-89e9-cd3933875da3 So

Re: [gnu-soc] [IMPORTANT] Next steps for participating projects and mentors

2020-04-14 Thread Gábor Boskovits
Hello Danny, Danny Milosavljevic ezt írta (időpont: 2020. ápr. 14., Ke 19:45): > Hi Gabor, > > when I try to log in at https://summerofcode.withgoogle.com I get: > > >403 > >Ruh roh. Something went wrong here. > >Current Google account: danny.m...@gmail.com > > > >You don't have a GSoC account.

Re: [gnu-soc] [IMPORTANT] Next steps for participating projects and mentors

2020-04-14 Thread Danny Milosavljevic
Hi Gabor, when I try to log in at https://summerofcode.withgoogle.com I get: >403 >Ruh roh. Something went wrong here. >Current Google account: danny.m...@gmail.com > >You don't have a GSoC account. >[Get Started] When I try to create an account using [Get Started], there are only the choices "o

Fwd: [gnu-soc] [IMPORTANT] Next steps for participating projects and mentors

2020-04-14 Thread Gábor Boskovits
To GSoC mentors: I have received the following communication from the GNU coordinators: -- Forwarded message - Feladó: Jose E. Marchesi Date: 2020. ápr. 14., Ke 9:54 Subject: [gnu-soc] [IMPORTANT] Next steps for participating projects and mentors To: Hi people! At this

Next Steps for Application

2020-03-22 Thread Naga Malleswari
Hi I have completed writing package description and 2 of my patches were merged successfully with help of Danny. I am looking for Next steps for my Outreachy Application Process -- Regards NagaMalli

Re: Review of my patch and Suggestions for Next Steps

2020-03-17 Thread Gábor Boskovits
Hello, Naga Malleswari ezt írta (időpont: 2020. márc. 17., Ke 4:12): > Hi > > I am introducing myself as Outreachy Applicant for May 2020. I have been > in touch with my Mentor Danny and working on R Packages. > > I received a reply that #40064 and #40040 are merged. I am waiting for > response

Review of my patch and Suggestions for Next Steps

2020-03-16 Thread Naga Malleswari
Hi I am introducing myself as Outreachy Applicant for May 2020. I have been in touch with my Mentor Danny and working on R Packages. I received a reply that #40064 and #40040 are merged. I am waiting for response and the next task to go ahead. -- Regards NagaMalli

Re: Guix Wikidata module - next steps

2019-01-08 Thread swedebugia
"Ludovic Courtès" skrev: (8 januari 2019 18:25:05 CET) >Hello! > >Interesting work! > >swedebugia skribis: > >> First thing to add is the procedures from guile-wikidata that enables >us to get a label for a given Qid and the output of queries like the >one below. >> >> The second thing to add is

Re: Guix Wikidata module - next steps

2019-01-08 Thread Ludovic Courtès
Hello! Interesting work! swedebugia skribis: > First thing to add is the procedures from guile-wikidata that enables us to > get a label for a given Qid and the output of queries like the one below. > > The second thing to add is fold procedures to guess the right qid according > to the upstr

Guix Wikidata module - next steps

2019-01-08 Thread swedebugia
Hi I started today writing a new module and would like to share my ideas with you. Feel free to add your ideas too! I imagine it as an utils collection for a wd importer (correlate the two) and a wd exporter that can push e.g. version updates, synopsis and descriptions and whole new entries to

Re: [GWL] (random) next steps?

2019-01-04 Thread zimoun
Hi Ricardo, Happy New Year !! > We can connect a graph by joining the inputs of one process with the > outputs of another. > > With a content addressed store we would run processes in isolation and > map the declared data inputs into the environment. Instead of working > on the global namespace

Re: [GWL] (random) next steps?

2018-12-21 Thread Ricardo Wurmus
Hi simon, >> > 6. >> > The graph of dependencies between the processes/units/rules is written >> > by hand. What should be the best strategy to capture it ? By files "à >> > la" Snakemake ? Other ? >> >> The GWL currently does not use the input information provided by the >> user in the data-inp

Re: [GWL] (random) next steps?

2018-12-17 Thread zimoun
Dear, > I’m working on updating the GWL manual to show a simple wispy example. Nice! I am also giving a deeper look at the manual. :-) > > Some GWL scripts are already there. > I only know of Roel’s ATACseq workflow[1], but we could add a few more > independent process definitions for simple ta

Re: [GWL] (random) next steps?

2018-12-15 Thread Ricardo Wurmus
Hi simon, > Here, I would like to collect some discussions or ideas about the Guix > Workflow Language (GWL) and the next steps of this awesome tool! thanks for kicking off this discussion! > With wisp, the workflow description seems close to CWL, which is an argument > ;-) &g

[GWL] (random) next steps?

2018-12-14 Thread zimoun
Dear Guixers, ... or at least some of them :-) Here, I would like to collect some discussions or ideas about the Guix Workflow Language (GWL) and the next steps of this awesome tool! For those who do not know. About workflow language, Wikipedia says: https://en.wikipedia.org/wiki

Re: Next steps

2018-07-02 Thread Sahithi Yarlagadda
Hi Please review the patch and assign me the what to do next. On Saturday 30 June 2018 04:21 AM, Sahithi Yarlagadda wrote: > Hi > > >>> a spinning animation. For each line the animation could be advanced by >>> one (so it will spin really fast). >>> >>> Danny previously suggested this implement

Re: Next steps

2018-06-29 Thread Sahithi Yarlagadda
Hi >> a spinning animation. For each line the animation could be advanced by >> one (so it will spin really fast). >> >> Danny previously suggested this implementation: >> >>https://lists.gnu.org/archive/html/guix-patches/2017-07/msg00068.html I have tried the Spinner code and it worked fine

Re: Next steps

2018-06-26 Thread Gábor Boskovits
Ricardo Wurmus ezt írta (időpont: 2018. jún. 25., H 22:29): > > Hi Sahithi, > > > I think I am done with basic changes for 4th task. File is attached. As > > mentioned in IRC output is in escape code sequence when I tried in REPL. > > Great. Please change ui.scm directly and send a patch that ca

Re: Next steps

2018-06-25 Thread Ricardo Wurmus
Hi Sahithi, > I think I am done with basic changes for 4th task. File is attached. As > mentioned in IRC output is in escape code sequence when I tried in REPL. Great. Please change ui.scm directly and send a patch that can be applied to the wip-sahithi branch. Please also pay attention to th

Re: Next steps

2018-06-25 Thread Sahithi Yarlagadda
Hi Ricardo, I think I am done with basic changes for 4th task. File is attached. As mentioned in IRC output is in escape code sequence when I tried in REPL. > I am done with 2nd task out of given 4 tasks and that was included in my > previous patch. > I am currently working on 4th task. I am abl

Re: Next steps

2018-06-24 Thread Ricardo Wurmus
Hi Sahithi, I checked out the “wip-sahithi” branch and ran this command in a terminal (urxvt): ./pre-inst-env guix build --check --no-grafts hello I do see colours for phase start and end notices, so the code is fine. What terminal are you using? Did this not work for you before? What h

Re: Next steps

2018-06-24 Thread Sahithi Yarlagadda
Hi On Monday 25 June 2018 01:52 AM, Ricardo Wurmus wrote: > Hi Sahithi, > > I checked out the “wip-sahithi” branch and ran this command in a > terminal (urxvt): > > ./pre-inst-env guix build --check --no-grafts hello > > I do see colours for phase start and end notices, so the code is fine. I

Re: Next steps

2018-06-24 Thread Sahithi Yarlagadda
Hi all, The following are the changes that I made earlier and changes worked fine... This patch is pushed to my branch wip-sahithi But when I try executing it now I don't find its results not even soft-port is getting called... May I know the reason behind this --- Thanks!! Sahith

Re: Next steps

2018-06-21 Thread Ricardo Wurmus
Hi Sahithi, > Patch file is attached with the following changes. >> Excellent, this looks better. Unfortunately, your patch includes a >> couple of unrelated indentation changes. Please remove those. >> >> 2) Fixing the other soft port procedures > > As desc

Re: Next steps

2018-06-21 Thread Sahithi Yarlagadda
Hi Ricardo, Thank you. I felt merging to wip-sahithi will allow me to work from different machines and also reset back to the original branch to undo all changes. > as I previously informed you on IRC I have pushed your last patch to the > “wip-sahithi” branch. I am done with 2nd task out of given

Re: Next steps

2018-06-16 Thread Sahitihi
Hi Ricardo, Patch file is attached with the following changes. > Excellent, this looks better. Unfortunately, your patch includes a > couple of unrelated indentation changes. Please remove those. > > 2) Fixing the other soft port procedures As described I will proceed on with ne

Next steps

2018-06-15 Thread Ricardo Wurmus
Hi Sahithi, > I have fixed the errors mentioned bellow, Please do check and notify me > for further modifications. Excellent, this looks better. Unfortunately, your patch includes a couple of unrelated indentation changes. Please remove those. Let’s talk about the next steps. 1) En