Move existing project definitions from projects/gsoc_2011/ to
projects/project/ .
The goal for this reorganization is to remove any knowledge of the projects
classification from the file hierarchy: the classification goes into tags,
and projects indexes automatically list projects based on such tags.
Also, the current gsoc_2011 name was wrong anyway, because GSoC 2011 has
already concluded and projects would have had to move to a gsoc_2012 directory
anyway.
Lastly, yes, "projects/project/*" is slightly redundant. But I want to keep
the project lists from the projects "database" clearly separated.
This is as proposed in www@.

[[!template id=project
title="Add other package format(s) to pkgsrc"
contact="""
[tech-pkg](mailto:tech-pkg@NetBSD.org)
"""
mentors="""
[Jeremy C. Reed](mailto:reed@NetBSD.org), [Aleksej Saushev](mailto:asau@NetBSD.org)
"""
duration="3 months"
description="""
In 2006 and 2007, the pkgsrc build system was abstracted to allow packaging for other package system packages. For details see [pkgsrc/mk/flavor/README](http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/mk/flavor/README) and the [original commit message](http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/mk/flavor/bsd.flavor.mk?rev=1.1&content-type=text/x-cvsweb-markup).
This means pkgsrc build infrastructure may be used to potentially create packages that may be installed using non-NetBSD packaging tools (i.e. not using NetBSD's pkg_add). Note: this is not about cross-builds; the packages may be built on an appropriate host system using the pkgsrc collection.
This project may include creating shell command wrappers to mimic pkgsrc build needs as documented in README. (The wrappers only needed for building packages and not for using packages.) Also the project may include implementing package-specific make targets as documented in README. Also see suggestions to do in the initial commit message.
The goals of this project include:
* Add support for RPM, dpkg, SVR4, PC-BSD PBI, and/or the Solaris native package system(s).
* Be able to build at least 100 packages and demonstrate that the packages can be installed and de-installed using the corresponding system's native package tools.
* Document support and interaction with existing packages.
"""
]]
[[!tag gsoc]]
[[!tag easy]]
[[!tag pkgsrc]]