-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/01/2015 04:23 AM, Chris Murphy wrote: > On Wed, Oct 28, 2015 at 5:11 PM, Dan Mossor <danofsatx@xxxxxxxxx> > wrote: > >> I'm with Simo. I *DO NOT* want to place a burden on a FOSS >> operating system to be 100% compatible with non-FOSS software. > > OK well seeing as we even have some issues with FOSS software A > not getting along with FOSS software B and there's no burden... > > The question is: should Cockpit have a bug that prevents it from > being functional with OSX+Chrome, should it be blocking? What if > it's OSX+Firefox? > > I would say a more practical, and permissive policy would be: > should Cockpit have a bug that prevents it from being functional > with OSX or Windows using any (Chrome, FireFox, or OS default) then > it's a blocking bug. The point is to make sure a Cockpit bug > doesn't prevent people on other OS's from using Cockpit and thus > benefiting. > That's a fairly reasonable statement. So something like: * All Cockpit functional criteria must be satisfied when the user is running any of the following blocking browsers: - Mozilla Firefox as shipped in the same Fedora release - At least one of a) Mozilla Firefox or b) Google Chrome of the latest available version on Windows at compose time. - At least one of a) Mozilla Firefox or b) Google Chrome of the latest available version on OSX at compose time. Would that be satisfactory to everyone? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlY3ZbIACgkQeiVVYja6o6PLkgCeOfnUZJGNktuo/bUPZQoJlGEP AV0AoKVF6C71LqLMaH/fAnXimRaL/vv5 =X7+d -----END PGP SIGNATURE----- -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
