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