[Patchwork-maintainers] Patchwork project consolidation
Daniel Golle
daniel at makrotopia.org
Mon Feb 15 09:26:50 EST 2021
Hi Jeremy,
thank you for reaching out to us and thank you for providing the
patchwork instance!
This is the status of the projects where I'm listed as maintainer:
lede - C) projects no-longer consuming patches
openwrt - A) projects consuming patches and tracking states
Thank you!
Best regards
Daniel
On Mon, Feb 15, 2021 at 08:28:50PM +0800, Jeremy Kerr wrote:
> Hi all,
>
> [I'm sending this to all 221 maintainers of projects hosted on
> patchwork.ozlabs.org; through a private, moderated, mailing list. If
> you have comments you want to share with everyone, feel free to reply -
> but to prevent masses of unsolicited email, responses will be modreated
> before distributing. I suspect there won't be much whole-group chatter,
> but if you'd prefer not to hear anything else about this again, let me
> know, or unsubscribe at [1].]
>
> We're looking in to some changes in the hosting arrangements for the
> ozlabs.org servers, with one of the objectives to move from dedicated
> servers to cloud hosting. Part of this is rationalising what is
> currently used (by both ozlabs.org users, and the wider community), and
> what isn't, so we're not paying for what isn't being used.
>
> Patchwork is the main workload on ozlabs.org; we're tracking 1.3
> million patches, 1.7 million comments on those patches, totalling about
> 6.8GB of mail data.
>
> Since patchwork is one of main loads on ozlabs.org, I'd like to do some
> clean-up in cases where projects are no longer making use of their
> patchwork project instance.
>
> This doesn't mean patchwork is going away! If you're actively using
> patchwork, nothing needs to change.
>
> There seems to be a few usage patterns of patchwork at the moment:
>
> A) projects consuming patches and tracking states
>
> B) projects consuming patches but not tracking states; using the
> patchwork list as more of an list-archive
>
> C) projects no-longer consuming patches
>
> In case it helps categorising your usage, I've included a table with a
> few stats below[2].
>
> If your usage falls into (A), nothing needs to change. Do let me know
> though!
>
> For (B) and (C), I have a couple of plans on how we can reduce the
> requirements on our server for those:
>
> 1) If you have moved to an archive elsewhere, we can set up a redirect
> based on message ID. Since we started patchwork, there have been a
> few great mail-archive tools appear, which may better suit your
> usage model.
>
> 2) If you're no longer feeding patches in to patchwork, but still need
> an archive, we can do a static render of all of the projects'
> patches, which should reduce the load on our systems a little.
>
> - but if there's another option that would suit you better, I'm open
> for other feedback too.
>
> Let me know how you'd like to proceed. If you'd prefer to keep going
> as-is, that's fine - we more want to find out which projects don't need
> to keep their instance in its current form.
>
> Cheers,
>
>
> Jeremy
>
> 1: https://lists.ozlabs.org/listinfo/patchwork-maintainers/
>
> 2: Project stats on patchwork.ozlabs.org, as of yesterday. Note that
> these aren't supposed to represent any sort of metric about your
> project! Projects' usage models may differ, and that's perfectly fine.
>
> | total | new | percent | days since
> project | patches | patches | new | last patch
> ---------------------+---------+---------+---------+------------
> buildroot | 69820 | 368 | 0.53 | 0
> cbe-oss-dev | 345 | 153 | 44.35 | 4237
> crosstool-ng | 327 | 49 | 14.98 | 1219
> devicetree-bindings | 43522 | 944 | 2.17 | 0
> fedfs-utils | 438 | 0 | 0.00 | 1404
> flashrom | 102 | 102 | 100.00 | 8
> fwts | 3836 | 8 | 0.21 | 1
> gcc | 95190 | 94992 | 99.79 | 0
> glibc | 17985 | 17934 | 99.72 | 0
> hostap | 5779 | 34 | 0.59 | 1
> intel-wired-lan | 8526 | 4 | 0.05 | 0
> kvm-ppc | 6165 | 3009 | 48.81 | 1
> lede | 3515 | 20 | 0.57 | 1002
> linux-arc | 2804 | 2599 | 92.69 | 1
> linux-aspeed | 1834 | 86 | 4.69 | 1
> linux-cifs-client | 3034 | 3034 | 100.00 | 1
> linux-ext4 | 20347 | 1398 | 6.87 | 0
> linux-fsi | 59 | 30 | 50.85 | 1
> linux-gpio | 19597 | 19039 | 97.15 | 0
> linux-i2c | 12102 | 254 | 2.10 | 1
> linux-ide | 7987 | 170 | 2.13 | 0
> linux-imx | 20378 | 20352 | 99.87 | 1
> linux-mtd | 26326 | 4658 | 17.69 | 0
> linux-pci | 29531 | 5089 | 17.23 | 1
> linux-pwm | 5064 | 55 | 1.09 | 5
> linux-tegra | 19718 | 1270 | 6.44 | 0
> linux-um | 1919 | 67 | 3.49 | 3
> linuxppc-dev | 60292 | 835 | 1.38 | 0
> linuxppc-embedded | 8 | 1 | 12.50 | 4489
> ltp | 4095 | 80 | 1.95 | 1
> mptcp | 2097 | 9 | 0.43 | 0
> netdev | 234331 | 1 | 0.00 | 63
> netfilter-devel | 22025 | 1 | 0.00 | 2
> oe-lite | 975 | 43 | 4.41 | 2229
> openbmc | 4169 | 271 | 6.50 | 1
> openbsc | 1297 | 489 | 37.70 | 110
> opensbi | 193 | 6 | 3.11 | 25
> openvswitch | 21527 | 213 | 0.99 | 1
> openwrt | 10887 | 139 | 1.28 | 0
> osmocom-bb | 60 | 31 | 51.67 | 1164
> ovn | 822 | 16 | 1.95 | 0
> patchwork | 2337 | 16 | 0.68 | 76
> pdbg | 1231 | 12 | 0.97 | 30
> petitboot | 659 | 53 | 8.04 | 22
> qemu-devel | 311002 | 306571 | 98.58 | 0
> rtc-linux | 8459 | 22 | 0.26 | 1
> skiboot | 8681 | 157 | 1.81 | 3
> skiboot-stable | 105 | 7 | 6.67 | 3
> slof | 535 | 38 | 7.10 | 3
> snowpatch | 156 | 2 | 1.28 | 221
> sparclinux | 7414 | 216 | 2.91 | 2
> swupdate | 1604 | 16 | 1.00 | 1
> tpmdd | 1398 | 984 | 70.39 | 1308
> uboot | 133639 | 1206 | 0.90 | 0
> ubuntu-kernel | 59202 | 57181 | 96.59 | 0
> uclibc | 331 | 106 | 32.02 | 474
> uclibc-ng | 339 | 1 | 0.29 | 36
> yaboot | 88 | 16 | 18.18 | 2259
> (58 rows)
>
More information about the openwrt-adm
mailing list