Google Summer of Code: Proposals and Mentors

[Andoni Morales]

2015-02-18 20:21 GMT+01:00 Nirbheek Chauhan <nirbheek.chauhan at gmail.com>:
> On Wed, Feb 18, 2015 at 5:23 PM, Sebastian Dröge
> <sebastian at centricular.com> wrote:
>> On Di, 2015-02-17 at 16:59 +0000, Luis de Bethencourt wrote:
>>> GStreamer is going to apply for Google Summer of Code 2015. But we need
>>> your help!
>>>
>>> We would really appreciate if you suggested proposals, volunteered for
>>> mentoring, or added content to the proposals.
>>>
>>> Current list of proposals is here:
>>> http://gstreamer.freedesktop.org/GSOC/socprojects.html
>>
>> Does anybody have any other ideas, or would like to be added as a
>> potential mentor for any of these projects? Would be great to get some
>> more ideas and potential mentors so we can properly handle all
>> projects :)
>>
>
> It might be useful to have a project to improve Cerbero.
>
> Cerbero's main use-case right now is to build binaries
> tarballs/packages from upstream sources. It's quite difficult to use
> it for other uses such as local development; which is a shame because
> it's currently our best way of doing cross-compilation.
>
> List of deficiencies (Incomplete):
> ==================================
> 1) Local development is hard; current best way is to push to a custom
> remote/branch
> 2) Difficult to maintain multiple checkouts of Cerbero (gst 1.4,
> master, custom, etc)
> 3) Downloaded-sources management is suboptimal (no checksums, etc)
> 4) Built-sources management is supoptimal (mtime is compared, which is
> often misleading)
> 5) No way to "uninstall"/"wipeone" a recipe; need to wipe everything
> 6) Essentially no documentation about how to use it
> 7) More![1]

Other improvements:

   8) Deterministic buids.
   9) Integration with OSTree in combiation with the build bots for
the final binaries. This could be helpful for having the latest
binaries without having to reinstall the latest package created by the
build bots.
 10) glibc minimum requirements, to package apps that can run in older
glibc's than the one from the build machine.
 11) templating system for debian and rpm packages like the OS X and
Windows ones, which make it easier to add custom changes to packages.
 12) Packaging summaries, listing the files included in the package
and other information that could be used to compare the results of the
output packages between 2 releases.
 13) Diagnostic tool that rebuilds a recipe and collects information
to debug build issues producing a single log file that can be easilly
attached to a bug report.
 14) Packaging of sources used to created the packages, to fully
comply with the GPL and other licenses that require it.

Cheers,
Andoni

>
> A subset or a superset of these problems can be turned into a GSoC
> project. The aim is not to turn Cerbero into a full-fledged package
> management system, but something that at least fulfills basic
> development requirements such as "don't arbitrarily rebuild everything
> ffs". :)
>
> I volunteer myself to mentor/co-mentor this project[2] if we think
> it's worth doing.
>
> Cheers,
> Nirbheek
>
> 1. I'm sure Alessandro has many choice expletives he would love to
> share with us on the matter
> 2. I have experience being a GSoC student and a mentor with the Gentoo project
>
> --
> ~Nirbheek Chauhan
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel



-- 
Andoni Morales Alastruey

LongoMatch:The Digital Coach
http://www.longomatch.ylatuya.es