The herds have been deprecated by the Council and are being replaced by projects. For this reason, please decide on the fate of the herd stated in the summary and update [1] or state the request here. The common choices are: 1. Map the herd to an existing project (in this case all packages in the herd will be maintained by the project) -- let us know which project to use. 2. Create a new project for the herd -- create the wiki page, let us know the new mail alias name to be created, create the wiki page and let us know about it. 3. Decide to disband the herd -- just let us know (but keep it for now in herds.xml!), we'll replace it with individual maintainers when herds are removed. [1]:https://wiki.gentoo.org/wiki/Project:Metastructure/Herd_to_project_mapping
The address is also used in <maintainer>s.
As per the recent Council decision[1], the final deadline for herd -> project migration is 24th January 2016. If no action is taken for this herd by that time, any packages that do not have another maintainer will be reassigned to maintainer-needed. Common options include: mapping the herd to a new project, mapping it to an existing project, reassigning the packages to the herd maintainers, and reassigning to maintainer-needed. Please let me know ASAP about your intentions for this herd and I'll be happy to take care of it. 1: https://projects.gentoo.org/council/meeting-logs/20160110-summary.txt
app-eselect/eselect-vdr : vdr@ app-misc/activylircd : proxy-maintainers, vdr@helmutauer.de app-misc/iguanaIR : hd_brummy@ app-misc/inputlircd : app-misc/lirc : app-misc/usbirboy : dev-libs/cxxtools : vdr@ dev-libs/tntnet : hd_brummy@ dev-perl/HTML-TableContentParser : perl, vdr@ dev-perl/Lirc-Client : perl dev-perl/Video-Frequencies : dev-perl/Video-ivtv : dev-perl/XML-Simple-DTDReader : perl, vdr@ dev-perl/X-Osd : perl dev-python/pylirc : python media-fonts/vdrsymbols-ttf : vdr@ media-libs/libdvb : media-libs/libdvbpsi : lordvan@ media-libs/libv4l : tetromino@ media-libs/zvbi : media-plugins/vdr-actuator : vdr@ media-plugins/vdr-admin : vdr@ media-plugins/vdr-alcd : proxy-maintainers, vdr@, vdr@helmutauer.de media-plugins/vdr-arghdirector : vdr@ media-plugins/vdr-atscepg : vdr@ media-plugins/vdr-audiorecorder : vdr@ media-plugins/vdr-autosort : vdr@ media-plugins/vdr-avards : vdr@ media-plugins/vdr-beep : vdr@ media-plugins/vdr-bgprocess : vdr@ media-plugins/vdr-browse : vdr@ media-plugins/vdr-burn : vdr@ media-plugins/vdr-burn-templates : vdr@ media-plugins/vdr-calc : vdr@ media-plugins/vdr-cdplayer : vdr@ media-plugins/vdr-chanman : proxy-maintainers, christian.gmeiner@gmail.com, vdr@ media-plugins/vdr-channelblocker : vdr@ media-plugins/vdr-cinebars : vdr@ media-plugins/vdr-clock : vdr@ media-plugins/vdr-console : vdr@ media-plugins/vdr-coverviewer : vdr@ media-plugins/vdr-cpumon : vdr@ media-plugins/vdr-decruft : vdr@ media-plugins/vdr-devstatus : vdr@ media-plugins/vdr-dummydevice : vdr@ media-plugins/vdr-duplicates : vdr@ media-plugins/vdr-dvbapi : hd_brummy@ media-plugins/vdr-dvbhddevice : vdr@ media-plugins/vdr-dvbsddevice : vdr@ media-plugins/vdr-dvd : vdr@ media-plugins/vdr-dvdswitch : vdr@ media-plugins/vdr-epgsearch : vdr@ media-plugins/vdr-epgsync : vdr@ media-plugins/vdr-exec : vdr@ media-plugins/vdr-extb : vdr@ media-plugins/vdr-extrecmenu : vdr@ media-plugins/vdr-femon : vdr@ media-plugins/vdr-fepg : vdr@ media-plugins/vdr-ffnetdev : vdr@ media-plugins/vdr-filebrowser : vdr@ media-plugins/vdr-freecell : vdr@ media-plugins/vdr-fritzbox : vdr@ media-plugins/vdr-graphlcd : vdr@ media-plugins/vdr-graphtft : vdr@ media-plugins/vdr-image : vdr@ media-plugins/vdr-imonlcd : media-plugins/vdr-infosatepg : vdr@ media-plugins/vdr-iptv : vdr@ media-plugins/vdr-joystick : vdr@ media-plugins/vdr-kvdrmon : proxy-maintainers, gentoo@bjusystems.de, vdr@ media-plugins/vdr-launcher : vdr@ media-plugins/vdr-lcdproc : vdr@ media-plugins/vdr-lcr : vdr@ media-plugins/vdr-live : vdr@ media-plugins/vdr-loadepg : vdr@ media-plugins/vdr-mailbox : vdr@ media-plugins/vdr-markad : vdr@ media-plugins/vdr-menuorg : vdr@ media-plugins/vdr-mlist : vdr@ media-plugins/vdr-mount : vdr@ media-plugins/vdr-mp3ng : vdr@ media-plugins/vdr-mplayer : vdr@ media-plugins/vdr-music : vdr@ media-plugins/vdr-newsticker : vdr@ media-plugins/vdr-noepg : vdr@ media-plugins/vdr-nordlichtsepg : vdr@ media-plugins/vdr-osdpip : vdr@ media-plugins/vdr-osdserver : vdr@ media-plugins/vdr-osdteletext : vdr@ media-plugins/vdr-peer : vdr@ media-plugins/vdr-permashift : vdr@ media-plugins/vdr-picselshow : vdr@ media-plugins/vdr-pilot : vdr@ media-plugins/vdr-pilotskin : vdr@ media-plugins/vdr-pin : vdr@ media-plugins/vdr-powermate : vdr@ media-plugins/vdr-prefermenu : vdr@ media-plugins/vdr-proxy : vdr@ media-plugins/vdr-pvr350 : vdr@ media-plugins/vdr-pvrinput : vdr@ media-plugins/vdr-quicktimer : vdr@ media-plugins/vdr-radio : vdr@ media-plugins/vdr-radiolist : vdr@ media-plugins/vdr-rcu : vdr@ media-plugins/vdr-recsearch : vdr@ media-plugins/vdr-recstatus : vdr@ media-plugins/vdr-remote : vdr@ media-plugins/vdr-remoteosd : vdr@ media-plugins/vdr-remotetimers : vdr@ media-plugins/vdr-rotor : vdr@ media-plugins/vdr-rpihddevice : vdr@ media-plugins/vdr-rssreader : vdr@ media-plugins/vdr-satip : vdr@ media-plugins/vdr-scheduler : vdr@ media-plugins/vdr-screenshot : vdr@ media-plugins/vdr-serial : vdr@ media-plugins/vdr-skincurses : vdr@ media-plugins/vdr-skinelchi : vdr@ media-plugins/vdr-skinenigmang : vdr@ media-plugins/vdr-skinnopacity : idl0r@ media-plugins/vdr-skinsoppalusikka : vdr@ media-plugins/vdr-sleeptimer : vdr@ media-plugins/vdr-sndctl : vdr@ media-plugins/vdr-solitaire : vdr@ media-plugins/vdr-span : vdr@ media-plugins/vdr-spider : vdr@ media-plugins/vdr-streamdev : vdr@ media-plugins/vdr-sudoku : vdr@ media-plugins/vdr-suspendoutput : vdr@ media-plugins/vdr-svdrposd : vdr@ media-plugins/vdr-svdrpservice : vdr@ media-plugins/vdr-systeminfo : vdr@ media-plugins/vdr-text2skin : vdr@ media-plugins/vdr-ttxtsubs : vdr@ media-plugins/vdr-tvguide : idl0r@ media-plugins/vdr-undelete : vdr@ media-plugins/vdr-vcd : vdr@ media-plugins/vdr-vdrmanager : vdr@ media-plugins/vdr-videosystem : vdr@ media-plugins/vdr-vodcatcher : vdr@ media-plugins/vdr-vompserver : proxy-maintainers, pfrank@gmx.de, vdr@ media-plugins/vdr-wapd : vdr@ media-plugins/vdr-weatherng : vdr@ media-plugins/vdr-wirbelscan : vdr@ media-plugins/vdr-xine : media-plugins/vdr-xineliboutput : idl0r@ media-plugins/vdr-xvdr : vdr@ media-plugins/vdr-zaphistory : vdr@ media-plugins/vdr-zappilot : vdr@ media-plugins/xbmc-addon-xvdr : vdr@ media-sound/vdramgw : vdr@ media-tv/channeleditor : billie@ media-tv/dvbstream : media-tv/dvbstreamer : media-tv/dvbtune : media-tv/freevo : media-tv/gentoo-vdr-scripts : vdr@ media-tv/gtk-v4l : ssuominen@ media-tv/ivtvplayer : media-tv/ivtv-utils : cardoe@ media-tv/linuxtv-dvb-apps : media-tv/linuxtv-dvb-firmware : media-tv/me-tv : lordvan@ media-tv/nvtv : media-tv/shoutcast2vdr : vdr@ media-tv/tvmovie2vdr : vdr@ media-tv/v4l-dvb-saa716x : proxy-maintainers, martin.dummer@gmx.net, hd_brummy@ media-tv/v4l-utils : tetromino@ media-tv/wis-go7007 : media-tv/w_scan : hd_brummy@ media-tv/xawtv : media-tv/xmltv : media-video/alevt : media-video/dvbsnoop : media-video/matroxset : video media-video/maven-poke : video media-video/mjpegtools : video, billie@ media-video/mplayer-sh : vdr@ media-video/mplay-sh : vdr@ media-video/vdr : vdr@ sys-firmware/tt-s2-6400-firmware : vdr@ virtual/linuxtv-dvb-headers : www-misc/vdradmin-am : vdr@ x11-themes/skinenigmang-logos : vdr@ x11-themes/vdr-channel-logos : vdr@ x11-themes/vdrgraphtft-avp : vdr@ x11-themes/vdrgraphtft-deepblue : vdr@ x11-themes/vdrgraphtft-deeppurple : vdr@ x11-themes/vdrgraphtft-poetter : vdr@ x11-themes/xxv-skins : vdr@
I think vdr@ packages can stay within vdr project only, the rest can be assigned to video project. These days, the distinction between tv and digital video isn't as it used to be.
I think video is not fully suitable here. I think the point of distinction was that people in media-tv had some kind of tv hardware.
(In reply to Michał Górny from comment #5) > I think video is not fully suitable here. I think the point of distinction > was that people in media-tv had some kind of tv hardware. (In reply to Alexis Ballier from comment #4) > These days, the distinction between tv and > digital video isn't as it used to be. ? do you have any particular example in mind to motivate your disagreement ?
Didn't I already mention one? For example, I could myself maintain a random video player like mpv or vlc. But I wouldn't consider myself good maintainer for xawtv without proper V4L hardware like analog tv or DVB card.
(In reply to Michał Górny from comment #7) > Didn't I already mention one? No. > For example, I could myself maintain a random > video player like mpv or vlc. But I wouldn't consider myself good maintainer > for xawtv without proper V4L hardware like analog tv or DVB card. funnily enough, both mpv & vlc support both v4l & dvb... v4l is more used for webcams than tv tuners these days; v4l also includes some hw codec interface. dvb is mostly mpeg2/h264(/hevc) into mpegts. dvb shares *a lot* with iptv. the only "tv" part remaining is the kernel driver and the userspace code controlling this driver and telling it to tune to some frequency. nothing worth being treated special. and I'm not even talking about xawtv going away because it is dead upstream and never got a release with dvb support, making it completely useless in most countries these days... finally, there already are some "tv" (in your sense) packages under video herd (media-video/kaffeine comes to mind) but anyway, if you wish to create a tv project, go ahead; mass m-n'ing those packages like you advertised on -dev is simply wrong.
Maybe you are right. If you feel like the video team is actually going to maintain those packages, feel free to take them over. Just let me know if you believe all of them should land in video, or only some of them.
The herd has been disbanded. I will be announcing resulting maintainer-needed packages shortly.
(In reply to Alexis Ballier from comment #4) > I think vdr@ packages can stay within vdr project only, the rest can be > assigned to video project. These days, the distinction between tv and > digital video isn't as it used to be. (In reply to Michał Górny from comment #9) > Maybe you are right. If you feel like the video team is actually going to > maintain those packages, feel free to take them over. Just let me know if > you believe all of them should land in video, or only some of them. (In reply to Michał Górny from comment #10) > The herd has been disbanded. I will be announcing resulting > maintainer-needed packages shortly. Something doesn't sound right here.
GLEP67 work is done. I didn't get a clear reply if you want all the packages, and I've waited a week for it. Now you can take those you want.
(In reply to Michał Górny from comment #12) > GLEP67 work is done. I didn't get a clear reply if you want all the > packages, and I've waited a week for it. Now you can take those you want. You didn't get a reply because the initial statement was clear and you seemed to understand that. I don't intend to fight against your scripts. I could use your same logic and revert your commit and let you fix that, but I think you could just use your scripts to correct your mistake and everyone would be happy. CC'ing comrel in case some mediation is needed.
As I already explained multiple times, the scripts are all-or-none. I've asked people more than once that if they want to split stuff, they gotta do it before or after this.
(In reply to Michał Górny from comment #14) > As I already explained multiple times, the scripts are all-or-none. I've > asked people more than once that if they want to split stuff, they gotta do > it before or after this. As I see it, your scripts set maintainer to maintainer-needed for what matched my description (which I intentionally left simple for this purpose). How hard must it be to change that ? I don't know. Better let those packages rot indeed.
The script only did 1:1 herd->project replacement. Your statement suggested that only some packages are supposed to have the replacement (e.g. VDR should have not). This they can't do.
(In reply to Michał Górny from comment #16) > The script only did 1:1 herd->project replacement. Your statement suggested > that only some packages are supposed to have the replacement (e.g. VDR > should have not). This they can't do. I was under the impression that stuff left without herd were m-n'ed, as you announced. Looking more carefuly at logs, it seems I was wrong. Anyway, your script for comment #3 can easily generate a list of such packages ( use "script | grep ':[ ]*$' | cut -f 1 -d ' '" if you need help with this), and then feed that to your metadata.xml mangler. But hey, why don't I do that manually ? I wonder, really.
