From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Multimedia overlay
Date: Tue, 11 Aug 2009 02:06:21 +0200 [thread overview]
Message-ID: <4A80B5FD.1030904@gentoo.org> (raw)
In-Reply-To: <4A809EFA.4070801@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]
Ben de Groot schrieb:
> Hi,
>
> The qting-edge overlay (the official overlay for the Gentoo Qt team) is
> a great success as a place to develop new ebuilds, packages, eclasses,
> to prepare new releases, to maintain bleeding edge stuff like live
> ebuilds and especially as a training ground for new recruits. I thought
> it would be a good idea to do something similar for our multimedia
> related projects, and Steve "beandog" Dibb agreed.
>
> So hereby we announce the Gentoo Multimedia overlay. It is located at
> http://gitorious.org/gentoo-multimedia and any developers who want to
> join can let us know their gitorious account name, so they can be added.
> Administration of the overlay will be shared among the participating
> Gentoo devs, so new committers can quickly be added. Any users that want
> commit status can get access after their work is found to be of
> sufficient quality. We encourage this, as the overlay is also a training
> ground for new contributors to Gentoo.
>
> We would like to invite anyone interested in developing and maintaining
> ebuilds related to multimedia in the wider sense: video, sound, tv,
> graphics and fonts. If you have any live ebuilds or otherwise bleeding
> edge packages, you can move them to the overlay for testing and shared
> maintenance.
>
> Enjoy!
>
> Ben
>
>
Is there a special reason, why we need to split things even more? Why not invite those devs and
interested users to sunrise? Training ground for interested users is one of the main goals of our
project.
--
Thomas Sachau
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2009-08-11 0:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 22:28 [gentoo-dev] Multimedia overlay Ben de Groot
2009-08-10 22:53 ` Sebastian Pipping
2009-08-10 23:22 ` Ben de Groot
2009-08-11 0:06 ` Thomas Sachau [this message]
2009-08-11 0:26 ` [gentoo-dev] " Nikos Chantziaras
2009-08-11 8:34 ` [gentoo-dev] " Markos Chandras
2009-08-11 22:21 ` Ben de Groot
2009-08-11 0:10 ` Mark Loeser
2009-08-11 22:26 ` Ben de Groot
2009-08-21 5:48 ` Mike Frysinger
2009-08-11 1:21 ` Federico Ferri
2009-08-11 13:31 ` Sebastian Pipping
2009-08-11 4:02 ` Josh Saddler
2009-08-11 4:40 ` Jeremy Olexa
2009-08-11 6:28 ` Josh Saddler
2009-08-11 13:34 ` Sebastian Pipping
2009-08-11 15:07 ` Arun Raghavan
2009-08-11 16:12 ` Maciej Mrozowski
2009-08-11 16:30 ` Nirbheek Chauhan
2009-08-11 17:22 ` Markos Chandras
2009-08-11 17:38 ` Arun Raghavan
2009-08-11 17:52 ` Nirbheek Chauhan
2009-08-11 17:56 ` Arun Raghavan
2009-08-11 21:04 ` Robin H. Johnson
2009-08-11 20:46 ` Maciej Mrozowski
2009-08-11 22:37 ` Ben de Groot
2009-08-12 1:38 ` Arun Raghavan
2009-08-12 12:43 ` Ben de Groot
2009-08-11 9:08 ` Robert Buchholz
2009-08-11 10:40 ` Maciej Mrozowski
2009-08-11 12:57 ` Robert Buchholz
2009-09-03 18:42 ` [gentoo-dev] " Nikos Chantziaras
2009-09-03 18:47 ` Jeremy Olexa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A80B5FD.1030904@gentoo.org \
--to=tommy@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox