Re: [gentoo-dev] turck-mmcache ebuild

[foser <foser@foser.dyn.warande.net>]

On Thu, 2003-06-26 at 10:57, Klavs Klavsen wrote:
> It's on bugs.gentoo.org.

Thats where it should go.

> I was wondering how these ebuilds go about getting added? as of now,
> it's in a Works For Me State (and works - fine I've just upgraded the
> ebuild so the newest version is there too) - and I would very much like
> to see it included in the three. I'm certain there are many people who
> could use this - and it's a very simple ebuild, and I'd gladly support
> and continuously update it.

I'm not sure this is documented anywhere, but this is not really the
place for your question if it is. Or it should be documented somewhere.

The bug will get assigned to a group or individual who takes care of
similar ebuilds and will get audited and added if no problems arise in
any way. This process may take some time, depends on how high profile
the application is and how bug loaded the developer is.

The herds system is a proposed way to improve ensured maintenance of
ebuilds, where groups of developers are directly responsible for certain
ebuilds (unlike the situation currently where everyone can touch
everything to a certain degree (hey you, stay off the gnome ebuilds ;)).
There is currently no formal way to have non-official devs maintain
directly their submitted ebuilds, you are of course free to keep the
relevant developers up-to-date with improved ebuilds and version notices
via bugzilla or maybe use IRC or email to interact with the responsible
developer(s) directly.

- foser


--
gentoo-dev@gentoo.org mailing list