-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 02/03/2014 01:21 PM, [email protected] wrote: > On 02/03/2014 04:17 PM, Yan Zhu wrote: >> [1] Github: https://github.com/EFForg/https-everywhere/issues/ > >> [2] Trac: >> https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&groupdesc=1&group=type&max=200&component=EFF-HTTPS+Everywhere&component=HTTPS+Everywhere%3A+Chrome&order=priority&col=id&col=summary&col=component&col=status&col=owner&col=type&col=priority&col=milestone&report=19 > >> Thanks for all your help in making the web a safer place! -Yan > > Are there any thoughts on using one issue/bug tracker for the > ruleset lists? > > Wouldn't this help in reducing the the overhead, work, and time > needed for future tasks of compiling the rules together? The question would then be which one to get rid of. trac.torproject.org gets points because we've used it historically, it hosts all the other Tor Browser Bundle tickets as well, and it allows you to post bugs anonymously without making an account. Github gets points because it has a friendlier user interface, lets you link issues to pull requests and vice versa, and has encouraged new contributors to HTTPS Everywhere. Hard call, but luckily keeping both around hasn't incurred much extra work if any. Open to suggestions though. - -Yan - -- Yan Zhu [email protected] Technologist Tel +1 415 436 9333 x134 Electronic Frontier Foundation Fax +1 415 436 9993 -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJS8AskAAoJENC7YDZD/dns9toH/3ogm2JbTZNxJrd9Yk6f8epG 5eY5g9BzRaZt1pYealKbmBmc0H76jpz/Eq8RFBzEcOoGlPvfv17u/J6Sh8OQ1dZq Zkk/THDNaUlj/PwqhAgJW7ndOaAQ6CBfqPC7AgdST3CIjoZQ6Snq6QKGq7kNg8/L P6MQhBSK4rw25ETxr95qhuVKwPS690tZx0jHUrW4tkhQedytQwwm33u8pZf1vvCq PJ+UlUtjkoC/UvLSF+OIJfIbcgeVvEfvYoMqaeyVkMo3oL4KsM8dBoEcVaBO+sA1 DOv6zAOrkkyRVPpy5x0wonP4lWm6rDclef1ADsLh/zwcvxZ+lFw7CukNAFdrg38= =NNI1 -----END PGP SIGNATURE-----
