From: Yagnesh Raghava Yakkala <hi@yagnesh.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Emacs UI for Guix (GSOC)
Date: Fri, 21 Mar 2014 23:04:00 +0900 [thread overview]
Message-ID: <877g7n1wdr.fsf@sealion.lowtem.hokudai.ac.jp> (raw)
In-Reply-To: <87ior71x0b.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 21 Mar 2014 14:50:28 +0100")
Hello Ludovic,
On Mar 21 2014, ludo@gnu.org (Ludovic Courtès) wrote:
> Hi!
>
> Yagnesh Raghava Yakkala <hi@yagnesh.org> skribis:
>
>> I know its too late and few hours before the dead line of GSOC
>> application. Anyway I wrote a proposal based on previously discussed by Xue¹
>
> Heh, we can thank him. ;-)
Yes. Big thanks to him.
>
>> in the list. I am attaching that here. I would like to work on this whether
>> or not I will get selected for GSOC. I seek your comments (especially
>> Ludovic.)
>
> I don’t see significant differences compared to what we originally
> discussed with Xue, and I like the proposal.
>
> One thing the proposal doesn’t mention is the possibility to have an
> additional mode to browse the generation history. I think it’d be nice
> to keep it as a “bonus item”.
Yes, you raised that in a reply to Xue's mail. I will include that as well.
>> * Timeline of the development.
>> ** Before April 21:
>> - Getting familiar with guix concepts and code base
>> - Study Emacs Package.el implementation.
>> - Adding new package to guix.
>>
>> ** April 20 – May 23:
>> - Start on guix.el coding.
>> - Initial work on Elisp interface of guix function calls.
>> - Finalizing on guix.el implementation concepts that includes how to interact
>> with guix from Emacs.
>
> An open question is whether to rely on Geiser for communication between
> Emacs and Guix. I suggest discussing it with jao, the author of Geiser.
I will mail him, before so I will look into Geiser code.
>
>> ** May 24 – July 15:
>> - Implementation of glue code between Elisp and Guix.
>> - Work towards primary usable implementation of guix.el.
>>
>> ** July 16 – July 24:
>> - Code cleanup
>> - Fixing initial reported bugs.
>> - Preparing for submission of mid term evaluation
>>
>> ** June 27th Mid term evaluation
>>
>> ** June 28 – July 15:
>> - Further changes to improve code functionality.
>> - Refactoring code if required.
>> - Writing tests
>>
>> ** July 15 – July 25:
>> - Start working on documentation to meet GNU documentation standards.
>> - Fixing remaining bugs.
>> - Code cleanup
>>
>> ** July 26 - August 11
>> - reserved time left for unexpected delays.
>> - During whole period I will be communicating with mentor in guix IRC channel.
>
> Looks good to me!
Thanks.
>
> Also, an important part of GSoC, IMO, is communication. So I’d expect
> that we keep in touch on IRC and the mailing list during GSoC, so we can
> share our thoughts, problems, experience, etc.
Sure, I will. I will have lot of question as I am very new working with
scheme.
I will submit the proposal and will send you the final copy.
Thanks.
--
ఎందరో మహానుభావులు అందరికి వందనములు.
YYR
next prev parent reply other threads:[~2014-03-21 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 10:55 Emacs UI for Guix (GSOC) Yagnesh Raghava Yakkala
2014-03-21 13:50 ` Ludovic Courtès
2014-03-21 14:04 ` Yagnesh Raghava Yakkala [this message]
2014-03-22 18:29 ` Ludovic Courtès
2014-03-23 20:29 ` Yagnesh Raghava Yakkala
2014-03-23 20:45 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877g7n1wdr.fsf@sealion.lowtem.hokudai.ac.jp \
--to=hi@yagnesh.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).