clisp-devel

GSoC 2017: we have a slot

[Sam S. <sd...@gn...>]

Hi,

Looks like we got a slot:
https://lists.gnu.org/archive/html/summer-of-code/2017-04/msg00034.html

This means that Compro's proposal is good to go!
https://summerofcode.withgoogle.com/dashboard/organization/5029441722908672/proposal/6094141044817920/

Congratulations and let's get coding!


-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net
http://no2bds.org http://think-israel.org http://americancensorship.org
A language that does not change the way you think is not worth learning.

Re: GSoC 2017: we have a slot

[Compro P. <com...@gm...>]

Thank you so much for your reply. I had been eagerly waiting for this email.

And sorry for the incompleteness of my proposal because I wanted to convey
more things properly but couldn't get much time.
Will there be a specific mentor or I can get help from anybody or its both
the ways?

I see that you have reviewed my proposal and have assigned a slot.
But GSOC 2017 Timeline says that the announcement is on 4th May 2017. Will
they be announcing the names that you have selected or they would modify
the slots. Whatever may be the case. I am having exams till 5th May 2017
12:00pm GMT+5:30 . And on 6th May I may have to attend/travel to a wedding
ceremony. But I would confirm on this after the announcement.

If its positive then I may cancel the travel else I will try joining you
after 15th May or after my vacations(July).
https://developers.google.com/open-source/gsoc/timeline

Yours faithfully,
Compro Prasad

Re: GSoC 2017: we have a slot

[Sam S. <sd...@gn...>]

> * Compro Prasad <pbzcebcenfnq@tznvy.pbz> [2017-04-26 17:20:06 +0500]:
>
> Will there be a specific mentor or I can get help from anybody or its
> both the ways?

Vladimir is the primary mentor - he knows way more about MT.
Please keep all communication on this list (clisp-devel).

> If its positive then I may cancel the travel else I will try joining you
> after 15th May or after my vacations(July).
> https://developers.google.com/open-source/gsoc/timeline

I am not sure what you mean by "joining us", but the next critical date
on the timeline is June 26.
By this date you need to have most of the work either done or in a state
where we will be confident that you _will_ finish it on time.

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://honestreporting.com
https://jihadwatch.org http://www.dhimmitude.org http://jij.org
Marriage is the sole cause of divorce.

Re: GSoC 2017: we have a slot

[Sam S. <sd...@gn...>]

> * Sam Steingold <fq...@ta...t> [2017-04-26 10:38:10 -0400]:
>
> I am not sure what you mean by "joining us", but the next critical date
> on the timeline is June 26.
> By this date you need to have most of the work either done or in a state
> where we will be confident that you _will_ finish it on time.

Looks like this date is closer than it appeared just a few weeks ago.
In 10 days we will have to see most of the work done.

So far I have not seen any code.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://memri.org
http://americancensorship.org http://www.dhimmitude.org
Beliefs divide, doubts unite.

Re: GSoC 2017: we have a slot

[Compro P. <com...@gm...>]

Do I have to provide the full diff in email? If so, what options to
diff would be necessary?
Or is it good to go with hg? Should I start off by creating any branch
or something else?
Are you requesting a huge change or an xyz is good enough to start with?
Because the code seems a bit more involved than I thought. Too many
identifiers and tasks trying to do similar things in different ways.
Just studying threads won't suffice so was looking through stacks,
objects, etc. and their modifications using different functions
and macros.

Re: GSoC 2017: we have a slot

[Vladimir T. <vtz...@gm...>]

Compro, try to follow the items outlined in you proposal.

31-May to 11-Jun: Writing the lisp code to make simple threads and find out
where the hash table hits a corner case. Get ready with enough tests
09-Jun to 30-Jun: Write/Improve functions/macros to handle the thread
safety in the hash tables.

The preferred communication channel is this mailing list - feel free to
post code here.

At that stage I would expect to see tests hitting the problem and
ideas/plans/code trying to resolve the observed issues.



On Thu, Jun 15, 2017 at 11:00 PM, Sam Steingold <sd...@gn...> wrote:

> > * Sam Steingold <fq...@ta...t> [2017-04-26 10:38:10 -0400]:
> >
> > I am not sure what you mean by "joining us", but the next critical date
> > on the timeline is June 26.
> > By this date you need to have most of the work either done or in a state
> > where we will be confident that you _will_ finish it on time.
>
> Looks like this date is closer than it appeared just a few weeks ago.
> In 10 days we will have to see most of the work done.
>
> So far I have not seen any code.
>
> --
> Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
> http://steingoldpsychology.com http://www.childpsy.net http://memri.org
> http://americancensorship.org http://www.dhimmitude.org
> Beliefs divide, doubts unite.
>