[ccan] CCAN Summer of Code

[Adam Kennedy]

With regards to languages, I would suggest that "C if possible, 
otherwise Perl" would be the best policy for languages, as it lets us 
leverage existing CPAN elements (such as the TAP parser and test 
harness) while ultimately having everything written in C.

The ideal case though, would be everything written in C so we can 
leverage all this C code in other contexts.

Adam K

Luis Araujo wrote:
> Hello Rusty and everyone :-)
>
> How are you?
>
> I was looking at the CCAN project , and the list of ideas for the GSoC 
> , and some of them look interesting for me, I would like to work on 
> the following ones:
>
> - Judging code: This is supposed to be like a parser/checker right?
> - Publishing code: these all are very related tasks , and probably a 
> successful project would involve a little bit of each of them to get 
> something started.
>
> I have experience using several programming languages, among them C 
> and Perl , which as I can see, are needed for these projects, unless 
> some other language is recommended , this is pretty much a project 
> involving scripting tasks , so probably we could even consider 
> languages like CSL and Ch? , that would help us a lot, and we'll keep 
> loyal to the C language :-)
>
> I also have some experience with different packaging systems , I am 
> currently a Gentoo developer and successfully participated in the last 
> year SoC implementing a whole GUI framework for packages on Gentoo.
>
> I would be really interested on getting these ideas done for the CCAN 
> project, so, if you have any recommendation or advice, please let me 
> know.
>
> Thank you very much and Regards,
>
>
> Luis F. Araujo
> _______________________________________________
> ccan mailing list
> ccan at ozlabs.org
> https://ozlabs.org/mailman/listinfo/ccan