<p dir="ltr"><br>
On Dec 9, 2014 11:54 AM, "Brian Wheeler" <<a href="mailto:bdwheele@indiana.edu">bdwheele@indiana.edu</a>> wrote:<br>
><br>
> On 12/09/2014 01:45 PM, Bastien Nocera wrote:<br>
>><br>
>><br>
>> ----- Original Message -----<br>
>>><br>
>>> Richard Hughes wrote:<br>
>>>><br>
>>>> So do I! I'm a developer, which spin do I use so that the firewall<br>
>>>> doesn't get in my way? We can't develop a *product* based around what<br>
>>>> you specifically want, not me, nor anyone else on this list.<br>
>>><br>
>>> If you're a developer, surely you know what a port is and can make a few<br>
>>> clicks in firewall-config or system-config-firewall to open it! A<br>
>>> "developer" who can't even figure that out is a HORRIBLE developer!<br>
>><br>
>> Still waiting for that answer about the rygel use case. You'll see how<br>
>> much of a HORRIBLE setup this can be...<br>
><br>
><br>
> How, exactly, is a home media solution a key requirement for the "Developer oriented" firewall touted by the release notes?<br>
><br>
> This is the problem I've got with this feature. It has nothing to do with developers and everything to do with making a gnome feature work without having to click a "I really want to open everything because I'm on a trusted network" box.<br>
><br>
></p>
<p dir="ltr">This is one sentence fragment based on my impression of the Workstation working group's intent to use this feature to create their ideal development environment. I recall dev servers being cited as use cases as well. If the only problem you have with the firewall config is the way it is described in the RNs, I'm tempted to change it just to end the stop energy put into what *could be* a productive discussion.</p>
<p dir="ltr">--Pete</p>