[PureOS] Clarification of PureOS browser and browser policy

[Jeremiah C. Foster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

We have a rather sizable backlog of issues around the PureBrowser: 
https://tracker.pureos.net/project/board/1/

I point this out not as a criticism of Jonas, the PureBrowser
maintainer, but to highlight that we do not have a clear, distilled
policy document that might mitigate some of the issues in the backlog. 

One example is this issue: https://tracker.pureos.net/T699 That issue
comes from a video of PureOS which makes some inaccurate claims. The
video was linked in our bug tracker and I went through the video and
pulled out the claims so that they can be refuted, T699 tracks one such
claim of not having httpseverywhere enabled per default. 

Having a policy for an issue like this would allow someone to quickly
go to our policy, quote it in the issue tracker and/or demonstrate that
in fact we do have httpseverywhere installed, and then close the bug 
which I feel is a positive outcome. As it stands now, we have a lot of
issues that seem to attract a lot of commentary but little change is
effecutated. For me the point of an issue tracker is to track the
progress of the issue to the point where it is no longer an issue and
it is closed. Is this a shared view from folks on this list?

Regards,

jeremiah
-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxm9YQACgkQeFgrT+6R
sjnVagv+L0v1WkdLZ3jL2NoZbJr8ROE2/SPUyBe67chr1v1dOJIyyxcw9/Ol1FGU
dztk+/XwKri9SHlV9lP7lTim/RxPbZ5wxVPQf+S3n8KDNnOOBdpRbo0xRYd/qqTM
aIeYrfZTwmJcK+cszrr8Zpse1YUaB6RgMvj/0XFHRlbGVvUCXeYafxomtsAz4Ron
huz57a50lqXgOP0hQ4mYp3mCvPOJZQokTnNVJon5oifNbGf7+Ex/qW68B9/5aVoU
I7TCY3W2TT26RnKxIHMKOHMOkmidWt+DRxh7QCxS1OMkhf+4KxDGboyRRDUBGH1/
IJu7XQFCwQ+bbtWT2ZSRqxgnPxaPgjhIt3ypGOBiBOWDX/f8Wrdq0I+RsS/boIGS
A26CGs47NTEU/C4LActM3Sg+IvS7+r2LHr4USgw/Zxyn7lvO1EJ/332whA+ZAsvg
XXQOc1PznOrIovUZJsTVoReQbOPIS/p9W4CM0bBFCN0R/JiuT57eBKEzA8+/EKUE
T349zjsC
=a8Ly
-----END PGP SIGNATURE-----