> 1. Should the project be focused on reference/most common > implementations, or maybe more of them? Say, giflib vs libnsgif. > I think the latter library is specific to a few programs right now but > if it gets more popular, it would fit.
It's mostly a question of critical mass. To give an example from a different corner of Gentoo... Initially net-libs/libtirpc was more of an obscurity, a more feature-complete replacement for code within glibc. Back then it didn't matter so much who maintained it. In the meantime, the corresponding part of glibc has been phased out, and everyone is relying on libtirpc. So now it's important that it is well- maintained, and it's taken care of by base@. > 2. How many kinds of media should the project accept? Audio, graphics, > video seem pretty obvious. Containers too. libass makes sense as it is > specifically for video subtitles. Anything else? Again, critical mass should be the main criterion. Things that are used by many different packages, with many different maintainers. If a library is only used by LibreOffice, it makes more sence that it is maintained by office@. If a library is used exclusively via kde-frameworks, the same for kde@. I wouldn't be too restrictive regarding the type of media. > 3. What about libraries implementing media-specific streaming protocols? > E.g. libshout, live... I suppose the ones specific to voip would fall > into voip project's domain instead. Same arguments... > > >  > https://archives.gentoo.org/gentoo-dev/message/79073ab9c7cebd79fc12e897e110 > bc3c  https://wiki.gentoo.org/wiki/Project:Codec_project -- Andreas K. Hüttel dilfri...@gentoo.org Gentoo Linux developer (council, qa, toolchain, base-system, perl, libreoffice)
Description: This is a digitally signed message part.