[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3633: Use forked txi2p

[Tahoe-LAFS]

#3633: Use forked txi2p
------------------------------------+-----------------------
     Reporter:  sajith              |      Owner:  sajith
         Type:  defect              |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by maylee):

 == Background

 `txi2p` has been forked and lives at https://github.com/sajith/txi2p

 Sajith has done cleanup and added testing on the fork.

 '''A few considerations at this time'''

 * Not known how important i2p is, and therefore whether integration tests
 are needed.
 * Testing currently takes 15 minutes
 * We would like some reviewers from Tahoe for this package

 jaraco recommends that we keep the fork in tahoe-lafs (presumably GitHub
 or GitLab) and that we point PyPI to that repo.

 We might be eligible to take over the project as maintainers.
 We would need to show that we tried to contact Str4d and
 we would need to show that we couldn't just use the name `txi2p-tahoe`.

 '''Attempts to contact Str4d'''

 * Open issue on project repo https://github.com/str4d/txi2p/issues/10,
 beginning July 1, 2020
 * Email sent to a private address on March 1, 2021
 * Email sent after the fork to the public address on the project's page
 (PEP's official requirement) March 13, 2021

 == Need for A Plan

 The fork will require long-term maintenance.

       - Str4d also owns the documentation
 https://readthedocs.org/projects/txi2p/
         Do we want to do anything here?

       - What about the foolscap?  Do we need txi2p back in foolscap?

       - Who will take up maintenance?  Who will do code reviews?

       - CI configuration is for Travis. Seems that travis-ci.com (not
 travis-ci.org) works just fine, for now anyway. Should we move it
 elsewhere?

       - Should we expand the CI test matrix to include more platforms?
         (Currently it's just Linux on Travis.)

       - Should we continue to test with unsupported Python (3.5) and
         really old Twisted (< 20.3 for Python 2.7) versions?  (In
         tox.ini, there's Twisted 10.2 through 21.2, and current, and
         trunk.)

       - Some dependencies are in pyproject.toml, some are in
         setup.py.  What to do about that?

       - Probably should switch CI badge, coverage badge (uses
         coveralls), project homepage, etc.

       - Other minor issues: Travis CI does not catch some errors
         (failures with old versions of Twisted); pypy2 needs cleanup;
         plugins module is under-tested, etc.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3633#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage