[HTTPS-E Rulesets] How do you decide which rulesets to merge?

[michael at yanovich.net]

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

On 10/22/2014 07:31 AM, Kentrell Johnson wrote:
> Hello,
> 
> I submitted a ruleset in February but it was never merged.  It looks
> like the majority of rulesets posted to this list do not get merged.
> 
> How is it decided which rulesets to merge?  I have found several
> websites needing rulesets but do not want to post patches if they do not
> meet the standard for inclusion.
> 
> Thanks,
> Kentrell

I am not officially affiliated with HTTPS Everywhere nor the EFF, but
from my experience it seems that rules that are submitted to their
GitHub mirror[1] are more likely to be accepted into stable.

I have been submitting rules against the latest floating number branch.
(currently titled "4.0") I imagine that once 5.0 becomes the new stable
that one would need to submit rules to that branch. The list of "pending"
rulesets and other changes can be seen on the GitHub issues/pulls page
for the project[2].


[1]: https://github.com/EFForg/https-everywhere
[2]: https://github.com/EFForg/https-everywhere/pulls

- -- 
Michael Yanovich
What is all that gibberish at the end of this e-mail?
https://en.wikipedia.org/wiki/Pretty_Good_Privacy#Digital_signatures


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJUR8KHAAoJEKBpQL3CDq4daMcP/0P8Cf9vBBlXNBHp7t/Vi47/
NcsKL10PyLlq1y6x14n1TLDwBJg5TcoDxIw4ZEiUlV5ZAmqzJh5A9C3IsNqY7Cym
FRbEenpPWufUmTnB3bVIPPBXRgxbirVQzxZ0xQVi6kybTrwlVYJOjbvLp6WTdhPZ
RDyr435Oq8A1Kw8yG0URnNuc1Im0eyOTF3GLyG6bGXtY0a6IGV2lKpgn8kbmUOev
JsALPCkW/LQ87JQY+L9820QhYA4I6ykFT++sPYUXncyUu25RlNE9f2jbRO26Wwpx
QLHM/Hj7pPG9cAOKRSTd3BqLjSitj1ukMbAY7D6oxZ1GhG/PUtwwOlg+VjthvIFX
JfWt02YNmwlVlQR/KNiH7WPMYuXaqINZUclJnK0O7KiQG0lShoSiJzEiNpnvTQTG
CMrF1P5XgGNsOWi4TxQcFIR0kwjDG0BuHertYaZYRwbAyze+0cL3orpPbuSmJyQC
tnryVBw+Z+ilLArTCJLeYY562pXU7zKFxYuVu02wYMEnNYAj23PaczLzVrfJnBLE
to6SaHCSeb2kF1Ih2VBcfNNLhmZPw8kKwrz+FSIoLf7E6TAKgsDZywTwhpnnr1Xg
mv/a2CuBwWa1256iomDWg9ZFiF6Qe098AS+OHeL2DdlWisRmRcXY1jg0BZV5lOLR
eN0bSNBtJ+m1hR2feGKL
=iNLc
-----END PGP SIGNATURE-----