[tahoe-lafs-trac-stream] [tahoe-lafs] #2072: decide whether to enable Travis-CI for the main Tahoe-LAFS repo

[tahoe-lafs]

#2072: decide whether to enable Travis-CI for the main Tahoe-LAFS repo
------------------------------------+---------------------------
 Reporter:  daira                   |          Owner:
     Type:  defect                  |         Status:  new
 Priority:  normal                  |      Milestone:  undecided
Component:  dev-infrastructure      |        Version:  1.10.0
 Keywords:  security travis github  |  Launchpad Bug:
------------------------------------+---------------------------
 [https://travis-ci.com Travis-CI] is a virtual-machine-based continuous
 integration system, which does various neat things like [http://about
 .travis-ci.org/blog/2012-09-04-pull-requests-just-got-even-more-awesome/
 annotating pull requests with the results of testing a build].

 I've added a single-purpose [https://github.com/travis-tahoe travis-tahoe]
 github user to confirm that this works with Tahoe-LAFS. Here are the
 successful results for [https://github.com/travis-tahoe/tahoe-lafs that
 user's fork] of the tahoe-lafs repo: [https://travis-ci.org/travis-tahoe
 /tahoe-lafs]

 Unfortunately [https://github.com/travis-ci/travis-ci/issues/1390 Travis
 requires a github user with admin rights over the repo it is reporting
 on]. We need to decide whether to grant those rights for the main
 [https://github.com/tahoe-lafs/tahoe-lafs tahoe-lafs/tahoe-lafs] repo.

 (The Tahoe-LAFS commit to add the configuration file for Travis build
 testing [changeset:b8322c9c53710fb2d82da2d2ab9c9a9df45f0e24/trunk is on
 master already]. By itself it has no security consequences.)

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2072>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage