From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Jul 15 11:46:39 2014 Return-Path: Delivered-To: freebsd-ports-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 09DF6210 for ; Tue, 15 Jul 2014 11:46:39 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CC6BC2D3F for ; Tue, 15 Jul 2014 11:46:38 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6FBkcVq093439 for ; Tue, 15 Jul 2014 11:46:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 191873] Network ports in category "multimedia" Date: Tue, 15 Jul 2014 11:46:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: se@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2014 11:46:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191873 --- Comment #4 from Stefan Esser --- (In reply to Kubilay Kocak from comment #3) > I'm +1 on the primary motivator behind category selection being "Where would > our users reasonably expect to find it?" > > Considering multimedia as the 'service' provided to the user as distinct > from a softwares primary 'functional' class makes this easier to identify The problem is, that all DLNA servers have been in "net" for many years. AFAIK, the PlexMediaServer is not using UPnP/DLNA, but a protocol specific to their devices. UPnP is not only used for media streaming, but as a universal network access mechanism. Those UPnP/DLNA servers, that are primarily meant to stream media contents, should probably add multimedia as a secondary category, to make them appear in the package repository under that category. DLNA renderer ports do belong into the multimedia category, most do support other access methods (including local files). UPnP/DLNA controller without rendering functionality are media devices from a user's point of view. But UPnP/DLNA servers are more similar to web servers with addition of service announcements and media file introspection (to distinguish audio/photo/video formats). Therefore, I'd think that the following categories are most appropriate: UPnP/DLNA renderer: multimedia (secondary: net?) UPnP/DLNA controller: multimedia (secondary: net) UPnP/DLNA server: net (secondary: multimedia) But in fact, any other systematic assignment to categories might be OK, as long as it follow some concept. I'd expect to find the others in the same category if I installed one and find that it does not fit my requirements. And UMS is the outlier, right now, since all other DLNA servers are in "net" ... -- You are receiving this mail because: You are the assignee for the bug.