[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4142: Review and make sure all 3rd party services are owned by active members

[Tahoe-LAFS]

#4142: Review and make sure all 3rd party services are owned by active members
------------------------------------+-----------------------
     Reporter:  btlogy              |      Owner:  btlogy
         Type:  task                |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:
Launchpad Bug:                      |
------------------------------------+-----------------------
Description changed by btlogy:

Old description:

> The project does rely on 3rd party services and some might no longer be
> controlled by enough active member of the community (e.g.: Cachix is
> currently blocking CI).
>
> This means those services can break PRs or prevent/delay a release w/o
> enough contributors having access to the relevant 3rd party provider to
> fix the problem (e.g.: expired token).
>
> Let's review them all and maybe ensure at least 2 active members are in
> control.
>
> == Tahoe LAFS - https://github.com/tahoe-lafs/tahoe-lafs
>
> ||= Provider =||= Account =||= Owner/Admin =||= Status =||
> || Github.com || org: Tahoe-LAFS || brian, exarkun, meejah || maybe
> enough active maintainers? ||
> || CirclCI.com || org: Tahoe-LAFS  || same as Github || maybe enough
> active maintainers? ||
> || Cachix.org || org: tahoe-lafs-opensource || exarkun || no active
> maintainers and blocking (see #4134) ||
> || !PyPi.org || project: tahoe-lafs || brian, exarkun, meejah || maybe
> enough active maintainers? ||
> || test.!PyPi.org || project: tahoe-lafs || meejah || only one active
> maintainers ||
>
> In addition, the same problem can arise in some other projects related to
> Tahoe-LAFS:
>
> == ZFEC - https://github.com/tahoe-lafs/zfec
>
> ||= Provider =||= Account/!Org. =||= Owner/Admin =||= Status =||
> || !GitHub.com || org: Tahoe-LAFS || brian, exarkun, meejah || maybe
> enough active maintainers? ||
> || CirclCI.com || org: Tahoe-LAFS || same as !GitHub || maybe enough
> active maintainers but likely broken (same as #4098) ||
> || Cachix.org || org: tahoe-lafs-opensource || exarkun || no active
> maintainers and likely broken (like #4134) ||
> || !PyPi.org || project: zfec || exarkun, meejah, sajith, vu3rdd, brian,
> zooko || maybe enough active maintainers? ||
> || test.!PyPi.org || project: zfec || exarkun, meejah, sajith ||
> supposedly working ||
>
> == Magic Folder - https://github.com/tahoe-lafs/magic-folder
> ||= Provider =||= Account/!Org. =||= Owner/Admin =||= Status =||
> || !GitHub.com || Tahoe-LAFS || brian, exarkun, meejah || maybe enough
> active maintainers? ||
> || !PyPi.org || project: magic-folder || meejah || only one active
> maintainers ||
> || test.!PyPi.org || project: magic-folder || meejah || only one active
> maintainers ||
>
> == Tahoe Capabilities - https://github.com/tahoe-lafs/tahoe-capabilities
>
> ||= Provider =||= Account/!Org. =||= Owner/Admin =||= Status =||
> || !GitHub.com || Tahoe-LAFS || brian, exarkun, meejah || maybe enough
> active maintainers? ||
> || CircleCI.com || Tahoe-LAFS || same as !GitHub || maybe enough active
> maintainers? ||
> || Cachix.org || tahoe-lafs-opensource || exarkun || no active
> maintainers and likely broken (like #4134) ||
> || !PyPi.org || project: tahoe-capabilities || exarkun, meejah || only
> one active maintainers ||
> || test.!PyPi.org || project: tahoe-capabilities || exarkun || no active
> maintainers ||
>
> Alternatively, if one of those related projects is inactive and/or not
> required for Tahoe-LAFS, maybe we should properly archive them (there
> might be more than those 3).

New description:

 The project does rely on 3rd party services and some might no longer be
 controlled by enough active member of the community (e.g.: Cachix is
 currently blocking CI).

 This means those services can break PRs or prevent/delay a release w/o
 enough contributors having access to the relevant 3rd party provider to
 fix the problem (e.g.: expired token).

 Let's review them all and maybe ensure at least 2 active members are in
 control.

 == Tahoe LAFS - https://github.com/tahoe-lafs/tahoe-lafs

 ||= Provider =||= Account =||= Owner(s) =||= Status =||
 || Github.com || org: Tahoe-LAFS || brian, exarkun, meejah || maybe enough
 active maintainers? ||
 || CirclCI.com || org: Tahoe-LAFS  || same as Github || maybe enough
 active maintainers? ||
 || Cachix.org || org: tahoe-lafs-opensource || exarkun || no active
 maintainers and blocking (see #4134) ||
 || hub.Docker.com || org: Tahoe-LAFS? || unknown || unknown ||
 || !PyPi.org || project: tahoe-lafs || brian, exarkun, meejah || maybe
 enough active maintainers? ||
 || test.!PyPi.org || project: tahoe-lafs || meejah || only one active
 maintainers ||

 In addition, the same problem can arise in some other projects related to
 Tahoe-LAFS:

 == ZFEC - https://github.com/tahoe-lafs/zfec

 ||= Provider =||= Account/!Org. =||= Owner(s) =||= Status =||
 || !GitHub.com || org: Tahoe-LAFS || brian, exarkun, meejah || maybe
 enough active maintainers? ||
 || CirclCI.com || org: Tahoe-LAFS || same as !GitHub || maybe enough
 active maintainers but likely broken (same as #4098) ||
 || Cachix.org || org: tahoe-lafs-opensource || exarkun || no active
 maintainers and likely broken (like #4134) ||
 || !PyPi.org || project: zfec || exarkun, meejah, sajith, vu3rdd, brian,
 zooko || maybe enough active maintainers? ||
 || test.!PyPi.org || project: zfec || exarkun, meejah, sajith ||
 supposedly working ||

 == Magic Folder - https://github.com/tahoe-lafs/magic-folder
 ||= Provider =||= Account/!Org. =||= Owner(s) =||= Status =||
 || !GitHub.com || Tahoe-LAFS || brian, exarkun, meejah || maybe enough
 active maintainers? ||
 || !PyPi.org || project: magic-folder || meejah || only one active
 maintainers ||
 || test.!PyPi.org || project: magic-folder || meejah || only one active
 maintainers ||

 == Tahoe Capabilities - https://github.com/tahoe-lafs/tahoe-capabilities

 ||= Provider =||= Account/!Org. =||= Owner(s) =||= Status =||
 || !GitHub.com || Tahoe-LAFS || brian, exarkun, meejah || maybe enough
 active maintainers? ||
 || CircleCI.com || Tahoe-LAFS || same as !GitHub || maybe enough active
 maintainers? ||
 || Cachix.org || tahoe-lafs-opensource || exarkun || no active maintainers
 and likely broken (like #4134) ||
 || !PyPi.org || project: tahoe-capabilities || exarkun, meejah || only one
 active maintainers ||
 || test.!PyPi.org || project: tahoe-capabilities || exarkun || no active
 maintainers ||

 Alternatively, if one of those related projects is inactive and/or not
 required for Tahoe-LAFS, maybe we should properly archive them (there
 might be more than those 3).

--

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