[HTTPS-Everywhere] upstream source for https-everywhere?

[Daniel Kahn Gillmor]

hey folks--

i'm looking at the https-everywhere plugin, and considering packaging it
for debian (or helping out with the packaging at least). (see
http://bugs.debian.org/591579, where the debian packaging should be tracked)

i'd like to know if there's an upstream source that i can follow more
directly than just the published xpis.

So far i've found git://git.torproject.org/https-everywhere , which
appears to be a git clone of some svn repo (i don't know where that svn
repo is, if it's published).  unfortunately, it doesn't include any tags
(e.g. of the 0.2.2 release), and the re-merges from stable to unstable
(or vice versa) aren't explicitly represented (probably because svn
doesn't represent them).

Should i just treat the xpi as the "upstream source"?  (it's not quite
"the preferred form of modification" promised in the GPL, since it
doesn't include the build scripts).  Do you publish tarballs or release
tags someplace?

Also, i note that the git repo has a pkg/ directory that appears to
contain .xpi files themselves, but those files are out of sync with the
material in src/ (at least, the already-built xpis don't contain
anything in Changelog more recent than 0.2.0).  why include them in the
upstream repo at all, since one should be able to generate an xpi from
the src/ ?

i'm happy working with git, btw -- if i was to contribute changes, i'd
rather do it via git than via svn, if possible.

Thanks for offering https-everywhere!  sorry for the nit-picky questions...

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 892 bytes
Desc: OpenPGP digital signature
URL: <http://lists.eff.org/pipermail/https-everywhere/attachments/20100923/564a4d1b/attachment.sig>