From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Jul 15 10:23:35 2014 Return-Path: Delivered-To: freebsd-ports-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B32D774 for ; Tue, 15 Jul 2014 10:23:35 +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 69370260A for ; Tue, 15 Jul 2014 10:23:35 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6FANZ5o020838 for ; Tue, 15 Jul 2014 10:23:35 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 10:23:35 +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: dreamcat4@gmail.com 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 10:23:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191873 --- Comment #2 from dreamcat4@gmail.com --- (In reply to Kurt Jaeger from comment #1) > dreamcat4@gmail.com: if you agree, I'll move universal-media-server I would say; If a user has no previous knowledge (or assumptions) whatsoever. They will look for uPNP / DLNA Media servers in the multimedia category. Because these are programs that ONLY provide entertainment services to the users. They do not also provide some purely 'network service'. Many programs have networked features but are not put in the 'net' category. 'www' is just one example of that. (heck almost all programs these days have some form of networked communications in them). Personally, I regard the 'net' category as something that offers network-level services (e.g. not as high as the top-tier 'application gateway' slice that is described in the OSI reference model). And 'net' also infers 'inet' - which alludes to suggests something that can also possibly be WAN-based. Also: gupnp says - GUPnP does not include helpers for construction or control of specific standardized resources (e.g. MediaServer); So the port 'gupnp' definitely ISNT a media server does not provide 'entertainment services'. It is providing a lower layer on the OSI model which is not application level, but network level. So is justified to remain in 'net' category. This also seems to be the situation for 'miniupnpc', that it isn't actually a DLNA Compliant Media server. Rather it provides networking features for other application level programs to make use of. So I imagine it should be best to remain in the net category too. In the end, I believe that: * The 'net' category is inherently vague, just by the fact that almost everything these days has some network features. * For 'DLNA Media Servers' not to be split around (bad idea), if each port maintainer get one vote. Then my vote, as maintainer of 'universal-media-server', is that they should all be moved into 'multimedia' category. * If no consensus can be agreed upon, then (personally) I would prefer 'universal-media-server' to remain in then multimedia category. -- You are receiving this mail because: You are the assignee for the bug.