[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2049: Decide where "packaging tests" should live.

[Tahoe-LAFS]

#2049: Decide where "packaging tests" should live.
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  nejucomo
  nejucomo               |     Status:  new
         Type:  task     |  Milestone:  soon (release n/a)
     Priority:  normal   |    Version:  1.10.0
    Component:  dev-     |   Keywords:  packaging dev-infrastructure
  infrastructure         |  buildbot pypi openitp-packaging
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by daira):

 Replying to [comment:22 nejucomo]:
 > Replying to [comment:19 Zancas]:
 > > Should nejucomo be given commit access to:
 > >
 > > https://github.com/tahoe-lafs/packaging-tests
 > >
 > > and/or:
 > >
 > > https://github.com/tahoe-lafs/buildbot-config-tahoe
 > >
 > > ?
 >
 > I'll just do the simple non-blocking github flow: fork and make a pull
 request.  I think I prefer that to having commit access anyway.  The main
 reason I would want commit access is if we frequently block on the
 existing set of people with access.

 I see no reason why the permissions for those two repos shouldn't be
 identical to those for tahoe-lafs/tahoe-lafs.

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