<div dir="ltr"><div><div><div><div>Hello,<br><br></div>I think I did everything in time by 2 pm (utc) of the last Friday.<br><br></div>Today when I was going to review what I did to add some details to the project I realized that I forgot to add the link to my application and the project I proposed in the Debian wiki, I hope that is not a problem because I think I registered my proposal in melange in time.<br>
</div>Is there any way to verify that everything is OK? does anyone have to review the proposal submitted in melange website?<br></div><div><br></div>Thanks in advance.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2014-03-21 7:50 GMT+01:00 Daniel Pocock <span dir="ltr"><<a href="mailto:daniel@pocock.com.au" target="_blank">daniel@pocock.com.au</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Hi José,<br>
<br>
The most urgent thing to do now is to insert your proposal in the Google<br>
Melange site:<br>
<br>
<a href="http://www.google-melange.com" target="_blank">http://www.google-melange.com</a><br>
<br>
It is just 12 hours until the deadline. If your proposal is not<br>
registered on Melange at 19:00 UTC today, you can't participate.<br>
<br>
The proposal should also be uploaded to the wiki as soon as possible but<br>
for the purpose of the deadline, the Melange site is extremely strict<br>
<br>
Regards,<br>
<br>
Daniel<br>
<div class=""><br>
<br>
<br>
On 20/03/14 23:15, José Luis Sanroma Tato wrote:<br>
> Hello again,<br>
><br>
> I found a mentor and I have almost everything ready. Should the mentor<br>
> creates the project in the wiki or should be myself?<br>
><br>
> Regards,<br>
> José Luis<br>
><br>
><br>
> 2014-03-17 17:50 GMT+01:00 José Luis Sanroma Tato<br>
</div>> <<a href="mailto:josel.sanromatato@gmail.com">josel.sanromatato@gmail.com</a> <mailto:<a href="mailto:josel.sanromatato@gmail.com">josel.sanromatato@gmail.com</a>>>:<br>
<div class="">><br>
> Hi Daniel,<br>
><br>
> Thanks for your comments. The item number 4 describes one of the<br>
> uses of my project. :)<br>
><br>
> I will write then in the debian-devel list.<br>
><br>
> Regards,<br>
> José Luis Sanroma<br>
><br>
><br>
><br>
> 2014-03-17 14:52 GMT+01:00 Daniel Pocock <<a href="mailto:daniel@pocock.com.au">daniel@pocock.com.au</a><br>
</div>> <mailto:<a href="mailto:daniel@pocock.com.au">daniel@pocock.com.au</a>>>:<br>
<div><div class="h5">><br>
><br>
> Hi José,<br>
><br>
> Thanks for your email about this<br>
><br>
> The most critical thing for you now is to find a mentor - if the<br>
> Debian GSoC admins agree, the mentor could be somebody employed<br>
> in your campus. Every project proposed to Google needs to have<br>
> both a mentor and a student.<br>
><br>
> On the problem and solution you describe:<br>
><br>
> - one of my projects is remotely similar but not really the same<br>
> thing (recursively building Java dependencies from source)<br>
><br>
> - I've heard of big corporations using Ganglia (it is open<br>
> source) as part of a strategy to find spare CPU cycles where<br>
> they could run HPC tasks and also to measure the impact of those<br>
> tasks on the machines concerned. You may be able to use Ganglia<br>
> in a similar way to support your distributed builds. E.g. you<br>
> could create a "logged_in_users" metric and when it goes down to<br>
> 0, you use the person's machine.<br>
><br>
> - there is some interest in automated rebuilds of full<br>
> dependency hierarchies every time a dependency changes. The<br>
> existing buildd servers may not be able to cope with that extra<br>
> workload and a distributed solution may be helpful.<br>
><br>
> - there are issues of trust when building official packages for<br>
> the official Debian catalog - building on shared machines<br>
> increases risk. Then again, given that DDs are trusted to build<br>
> packages on their local machines, maybe spare clock cycles<br>
> volunteered by DDs could also be trusted for rebuilds of<br>
> official packages.<br>
><br>
> These are all good topics for discussion on debian-devel too -<br>
> you may also find a mentor there<br>
><br>
> Regards,<br>
><br>
> Daniel<br>
><br>
><br>
><br>
> On 17/03/14 14:29, José Luis Sanroma Tato wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> My name is José Luis Sanroma Tato and I am finishing my MSc in<br>
>> computer Engineering. I heard about the Google Summer of Code<br>
>> the last week.<br>
>><br>
>> I don't know if it is possible to propose a project and this<br>
>> is the reason I am writing to this mailing list.<br>
>><br>
>> Currently I am working on my Master thesis that I expect to<br>
>> present in June, and I think that maybe is a good starting<br>
>> point to develop a bigger project because there will be still<br>
>> problems to solve (adding architectures, issues with<br>
>> repositories,...).<br>
>><br>
>> I am working on a highly scalable and opportunistic<br>
>> architecture to build Debian packages for different<br>
>> architectures automatically taking care of the dependencies,<br>
>> this project also takes part of the VIII Free Software<br>
>> University Competition in Spain[1].<br>
>><br>
>> At first appearance it looks like “buildd” but it's different<br>
>> because it covers different needs.<br>
>><br>
>> I am part of the ARCO research group[2] where we use Debian<br>
>> and we have our own debian repository[3] where we build and<br>
>> serve our debian packages. We use the computer of the workers<br>
>> to build the packages. The problems that we have are:<br>
>><br>
>> *<br>
>><br>
>> We don't have a dedicated infrastructure to build software.<br>
>><br>
>> *<br>
>><br>
>> Furthermore, we don't know when a computer will be<br>
>> available to build the packages due to the employees schedule.<br>
>><br>
>> *<br>
>><br>
>> We have some special needs, for instance, we usually work<br>
>> with the Zeroc Ice middleware, which version 3.5[4] is not<br>
>> part of the debian “stable” distribution and we need to<br>
>> build it for “stable”.<br>
>><br>
>><br>
>> My project tries to solves all these points by setting up a<br>
>> distributed system in which each node is compound by computers<br>
>> with some virtual machines as isolated and updated<br>
>> environments. This isolated environments are used to build,<br>
>> sign and upload the packages to the repository. I can go more<br>
>> into details if you want.<br>
>><br>
>> There will be some work to do, solving problems with<br>
>> repositories, also adding more architectures (right now only<br>
>> amd64 and i386 are supported)...<br>
>><br>
>> I am not even a debian maintainer so I don't know if this<br>
>> project could be useful in Debian somehow or if someone would<br>
>> be interested in mentoring something like this to set new<br>
>> objectives.<br>
>><br>
>><br>
>> Regards,<br>
>> José Luis Sanroma<br>
>><br>
>> [1] <a href="http://www.concursosoftwarelibre.org/1314/proyectos/19" target="_blank">http://www.concursosoftwarelibre.org/1314/proyectos/19</a><br>
>><br>
>> [2] <a href="https://arco.esi.uclm.es/en" target="_blank">https://arco.esi.uclm.es/en</a><br>
>><br>
>> [3] <a href="http://babel.esi.uclm.es/debian/" target="_blank">http://babel.esi.uclm.es/debian/</a><br>
>><br>
>> [4] <a href="http://packages.qa.debian.org/z/zeroc-ice.html" target="_blank">http://packages.qa.debian.org/z/zeroc-ice.html</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Soc-coordination mailing list<br>
</div></div>>> <a href="mailto:Soc-coordination@lists.alioth.debian.org">Soc-coordination@lists.alioth.debian.org</a> <mailto:<a href="mailto:Soc-coordination@lists.alioth.debian.org">Soc-coordination@lists.alioth.debian.org</a>><br>
>> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination</a><br>
><br>
><br>
><br>
</blockquote></div><br></div>