forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/CODEOWNERS

136 lines
6.2 KiB
Text
Raw Normal View History

CODEOWNERS: add initial file (MR 1783)
2020-12-04 04:17:36 +00:00
# https://docs.gitlab.com/ee/user/project/code_owners.html
CI: add more tests for CODEOWNERS (MR 4940) * Parse the file in python and ensure it is ordered alphabetically * Ensure that we have at least as many gitlab nicknames in CODEOWNERS, as there are listed maintainers in main and community devices. This should help with enforcing that every maintainer is also listed in CODEOWNERS, so they can be easily pinged via their gitlab nickname if something for the device they maintain is happening. [ci:skip-build]: already built successfully in CI
2024-03-17 20:45:36 +00:00
# Put groups like @sdm845-mainline into test_device.py:gitlab_groups.
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
# Order lines alphabetically!
CODEOWNERS: add initial file (MR 1783)
2020-12-04 04:17:36 +00:00
CODEOWNERS: use my new gitlab handle and add more files (MR 4983) Signed-off-by: Ferass El Hafidi <funderscore@postmarketos.org>
2024-03-31 12:19:53 +00:00
device/*/*-amlogic-s905*/ @funderscore
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-arrow-db410c/ @Minecrell
device/*/*-asus-me176c/ @Minecrell
CODEOWNERS: add ayn-odin maintainership (MR 4986) [ci:skip-build]: already built successfully in CI
2024-04-01 08:38:35 +00:00
device/*/*-ayn-odin/ @jenneron
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-bq-paella/ @Minecrell
bq-tenshi: new device (MR 4938) [ci:skip-build]: already built successfully in CI
2024-03-23 13:01:02 +00:00
device/*/*-bq-tenshi/ @fossdd
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-google-gru/ @jenneron
device/*/*-google-kukui/ @jenneron @binarycraft
device/*/*-google-oak/ @jenneron @adamthiede
device/*/*-google-trogdor/ @jenneron
device/*/*-google-veyron/ @jenneron
device/*/*-google-x64cros/ @jenneron @JustSoup321 @alpernebbi
CODEOWNERS: reformat (MR 3546) * Switch to tab indenting with tab size 8 to improve rendering * Fix my entries (missing trailing /)
2022-10-16 13:52:32 +00:00
device/*/*-htc-golfu/ @Newbyte
device/*/*-htc-m8qlul/ @Newbyte
CODEOWNERS: add myself for packages I maintain (MR 5165) [ci:skip-build]: already built successfully in CI
2024-05-21 15:26:45 +00:00
device/*/*-kobo-clara/ @akemnade
device-lenovo-21bx: Add Jane as co-maintainer (MR 5156)
2024-05-20 20:31:36 +00:00
device/*/*-lenovo-21bx/ @craftyguy @jane400
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-lenovo-a6000/ @jenneron @Minecrell
device/*/*-lenovo-a6010/ @jenneron @Minecrell
CODEOWNERS: use my new gitlab handle and add more files (MR 4983) Signed-off-by: Ferass El Hafidi <funderscore@postmarketos.org>
2024-03-31 12:19:53 +00:00
device/*/*-librecomputer-lafrite/ @funderscore
device/*/*-librecomputer-lepotato/ @funderscore
device/*/*-librecomputer-solitude/ @Newbyte @funderscore
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-motorola-harpia/ @Minecrell
device/*/*-nokia-n900/ @sicelo @Danct12
device/*/*-pine64-pinebookpro/ @QC8086
device/*/*-pine64-pinephone/ @craftyguy @milesalan @proycon @anjandev @StacyHarper @Arnavion @PsychoGame
device/*/*-pine64-pinephonepro/ @PsychoGame
device/*/*-pine64-rockpro64/ @PureTryOut
device/*/*-purism-librem5/ @craftyguy @alistair23 @Newbyte
device/*/*-qcom-msm8916/ @Minecrell @TravMurav
CODEOWNERS: sdm845 and axolotl (MR 3546) * Specify the whole sdm845-mainline group for *-qcom-sdm845 packages. * Add myself and Dylan for axolotl
2022-10-16 13:54:54 +00:00
device/*/*-qcom-sdm845/ @sdm845-mainline
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-qcom-sm6350/ @z3ntu
device/*/*-samsung-a3/ @Mis012 @TravMurav @Minecrell
device/*/*-samsung-a5/ @Minecrell @minlexx
device/*/*-samsung-e7/ @wonderfulShrineMaidenOfParadise
device/*/*-samsung-espresso10/ @MightyM17
device/*/*-samsung-espresso7/ @MightyM17 @antoni.aloytorrens
device/*/*-samsung-grandmax/ @wonderfulShrineMaidenOfParadise
device/*/*-samsung-gt510/ @TravMurav
device/*/*-samsung-gt58/ @TravMurav
samsung-j5(x): maintain devices (MR 5140) [ci:skip-build]: already built successfully in CI
2024-05-17 11:22:30 +00:00
device/*/*-samsung-j5/ @wonderfulShrineMaidenOfParadise
device/*/*-samsung-j5x/ @wonderfulShrineMaidenOfParadise
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-samsung-serranove/ @Minecrell
CODEOWNERS: add myself for packages I maintain (MR 5165) [ci:skip-build]: already built successfully in CI
2024-05-21 15:26:45 +00:00
device/*/*-tolino-shine2hd/ @akemnade
CODEOWNERS: use my new gitlab handle and add more files (MR 4983) Signed-off-by: Ferass El Hafidi <funderscore@postmarketos.org>
2024-03-31 12:19:53 +00:00
device/*/*-videostrong-kii-pro/ @funderscore
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-wileyfox-crackling/ @TravMurav @Minecrell
CODEOWNERS: fix typos, remove non-existing entries (MR 4662)
2023-12-28 15:06:13 +00:00
device/*/*-xiaomi-beryllium/ @joelselvaraj
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/*-xiaomi-daisy/ @joelselvaraj @alikates
device/*/*-xiaomi-markw/ @vipaoL
device/*/*-xiaomi-mido/ @barni2000
device/*/*-xiaomi-scorpio/ @Tooniis
device/*/*-xiaomi-tissot/ @jiaxyga @barni2000
device/*/*-xiaomi-vince/ @M0Rf30
device/*/*-xiaomi-wt88047/ @Minecrell
device/*/*-xiaomi-ysl/ @barni2000
alsa-ucm-conf-cros: new aport (MR 5020)
2024-04-09 16:22:54 +00:00
device/*/alsa-ucm-conf-cros/ @WeirdTreeThing
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/device-fairphone-*/ @z3ntu
device-generic-x86_64: add Ollie as maintainer (MR 5066)
2024-04-26 17:39:40 +00:00
device/*/device-generic-x86_64/ @craftyguy @ollieparanoid
CODEOWNERS: add myself for packages that I maintain (MR 3611)
2022-11-02 17:00:01 +00:00
device/*/device-google-nyan-big/ @jenneron
device/*/device-google-nyan-blaze/ @jenneron
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/device-google-peach-pi/ @jenneron
CODEOWNERS: add myself for packages that I maintain (MR 3611)
2022-11-02 17:00:01 +00:00
device/*/device-google-peach-pit/ @jenneron
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/device-google-snow/ @jenneron
device/*/device-huawei-plank/ @gtrxAC
device/*/device-lg-judyln/ @Newbyte
CODEOWNERS: add myself for packages that I maintain (MR 3611)
2022-11-02 17:00:01 +00:00
device/*/device-lg-judyp/ @jenneron
device-microsoft-surface-rt: take co-maintainership (MR 4948)
2024-03-19 20:31:09 +00:00
device/*/device-microsoft-surface-rt/ @jenneron @jethrob
CODEOWNERS: update clamor-s nickname (MR 5155) > User 'clamor95' was moved to 'clamor-s'. Please update any links and > bookmarks that may still have the old path. [ci:skip-build]: already built successfully in CI
2024-05-19 22:34:24 +00:00
device/*/device-nvidia-tegra-armv7/ @clamor-s @okias @mschwalm @nokun
CODEOWNERS: clean up formatting (MR 4662) Make sure all directories end with a slash, replace spaces with tabs
2023-12-28 15:00:05 +00:00
device/*/device-odroid-xu4/ @Grimler
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/device-oneplus-enchilada/ @calebccff
device/*/device-oneplus-fajita/ @calebccff
testing/device-postmarketos-trailblazer (MR 4967) trailblazer is a bleeding edge, unstable target for EFI capable ARM64 devices. It runs linux-next and should otherwise be adjusted to support as many devices as possible. The goal of trailblazer is to motivate more upstream kernel development by providing a tighter feedback loop (patches land in -next weeks before they make it into mainline or stable), as well as encouraging more generic solutions to the device specific hacks we have in userspace. On supported devices, trailblazer should reflect the current state of upstream. It allows users to easily appreciate what feature are unavailable, and more importantly appreciate when a new feature does get added upstream. Due to the instability of linux-next, the plan is to have BPO build trailblazer images nightly, so if next breaks then the images should only be broken for a day. Signed-off-by: Caleb Connolly <caleb@postmarketos.org>
2024-03-21 22:12:13 +00:00
device/*/device-postmarketos-trailblazer/ @calebccff
qcom-msm8909: new device (MR 5222) With the new changes in lk2nd that allow us to support extlinux.conf, we can now generate image that would be generic to these devices. [ci:skip-build]: already built successfully in CI
2024-06-10 12:52:31 +00:00
device/*/device-qcom-msm8909/ @wonderfulShrineMaidenOfParadise
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/device-qemu-aarch64/ @Minecrell @ollieparanoid
device/*/device-qemu-amd64/ @Minecrell @ollieparanoid
device/*/device-qemu-riscv64/ @Minecrell @z3ntu
device-qualcomm-sdm845: new aport (MR 4599) Signed-off-by: Caleb Connolly <caleb@connolly.tech>
2023-12-05 15:38:08 +00:00
device/*/device-qualcomm-sdm845/ @calebccff
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/device-samsung-chagallwifi/ @Grimler
device/*/device-samsung-coreprimevelte/ @legolivesmatter @balejk
device/*/device-samsung-j5y17lte/ @andrisas
CODEOWNERS: clean up formatting (MR 4662) Make sure all directories end with a slash, replace spaces with tabs
2023-12-28 15:00:05 +00:00
device/*/device-samsung-klimtlte/ @Grimler
CODEOWNERS: add entry for samsung-lt01 (MR 5154) [ci:skip-build]: already built successfully in CI
2024-05-19 08:33:34 +00:00
device/*/device-samsung-lt01/ @knuxify
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/device-samsung-m0/ @Newbyte
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/device-samsung-manta/ @jenneron @alexmrqt
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/device-shift-axolotl/ @amartinz @calebccff @dylanvanassche
device/*/firmware-google-veyron-brcm/ @jenneron
CODEOWNERS: clean up formatting (MR 4662) Make sure all directories end with a slash, replace spaces with tabs
2023-12-28 15:00:05 +00:00
device/*/firmware-odroid-xu4/ @Grimler
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/firmware-oneplus-sdm845/ @calebccff
device/*/firmware-powervr-gx6250/ @jenneron
CODEOWNERS: add myself for packages I maintain (MR 5165) [ci:skip-build]: already built successfully in CI
2024-05-21 15:26:45 +00:00
device/*/kobo-epdc-extractor/ @akemnade
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/linux-google-nyan/ @jenneron
device/*/linux-google-veyron/ @jenneron
CODEOWNERS: clean up formatting (MR 4662) Make sure all directories end with a slash, replace spaces with tabs
2023-12-28 15:00:05 +00:00
device/*/linux-huawei-plank/ @gtrxAC
testing/linux-next: new aport (MR 4967) Introduce a linux-next kernel with postmarketOS configs and some additional device specific configs enabled. This kernel package will be updated daily to the latest -next tag. breakages expected. It is designed to be used in tandem with a generic ARM64 device package to provide a bleeding edge option for those with EFI capable bootloaders. Signed-off-by: Caleb Connolly <caleb@postmarketos.org>
2024-03-21 22:06:43 +00:00
device/*/linux-next/ @calebccff
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/linux-postmarketos-allwinner/ @Arnavion @PsychoGame
CODEOWNERS: use my new gitlab handle and add more files (MR 4983) Signed-off-by: Ferass El Hafidi <funderscore@postmarketos.org>
2024-03-31 12:19:53 +00:00
device/*/linux-postmarketos-amlogic/ @funderscore @exkc
linux-postmarketos-exynos4: remove inactive maintainer (MR 5433) Thiago Foganholi (@ThiagaoPlusPlus on GitLab.com) hasn't been active for over three years by now. Remove his maintainership as such.
2024-07-31 08:08:07 +00:00
device/*/linux-postmarketos-exynos4/ @Newbyte
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/linux-postmarketos-exynos5/ @jenneron @Grimler
CODEOWNERS: update clamor-s nickname (MR 5155) > User 'clamor95' was moved to 'clamor-s'. Please update any links and > bookmarks that may still have the old path. [ci:skip-build]: already built successfully in CI
2024-05-19 22:34:24 +00:00
device/*/linux-postmarketos-grate/ @clamor-s @jenneron @jethrob
CODEOWNERS: add myself for packages I maintain (MR 5165) [ci:skip-build]: already built successfully in CI
2024-05-21 15:26:45 +00:00
device/*/linux-postmarketos-imx-ereader/ @akemnade
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/linux-postmarketos-mediatek-mt8173/ @jenneron @adamthiede
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/linux-postmarketos-mediatek-mt8183/ @jenneron @binarycraft
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/linux-postmarketos-omap/ @MightyM17 @Sicelo
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/linux-postmarketos-qcom-msm8939/ @Newbyte
linux-postmarketos-qcom-msm8953: upgrade to 6.9.1-r0 (MR 5132) [ci:skip-build]: already built successfully in CI
2024-05-14 19:25:48 +00:00
device/*/linux-postmarketos-qcom-msm8953/ @M0Rf30 @Ultra-azu @barni2000
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/linux-postmarketos-qcom-msm8996/ @Tooniis
device/*/linux-postmarketos-qcom-sc7180/ @jenneron
device/*/linux-postmarketos-rockchip/ @QC8086
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/linux-postmarketos-stericsson/ @Newbyte
device/*/linux-samsung-chagallwifi/ @Grimler
device/*/linux-samsung-coreprimevelte/ @legolivesmatter @balejk
samsung-j5y17lte: new device (MR 4797) [ci:skip-build]: Already built successfully in CI.
2024-02-07 19:43:03 +00:00
device/*/linux-samsung-j5y17lte/ @andrisas
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/linux-samsung-klimtlte/ @Grimler
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/oem-amd/ @craftyguy
device/*/oem-intel/ @craftyguy
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
device/*/soc-mediatek-mt8183/ @jenneron
CODEOWNERS: add maintainers from APKBUILDs (MR 4940) Sometimes we need to figure out the gitlab nicknames of maintainers and co-maintainers as listed in the APKBUILDs, e.g. when a specific issue appears that only happens with a given device. Or if we want to ping all device maintainers in the testing phase for the new release. So far it has been a very tiresome, manual process to figure out gitlab nicknames from the maintainers in the APKBUILDs (involving git log --follow and opening merge requests in browsers...). After some discussion we figured it would be good to store it in the CODEOWNERS file. This also has the nice side-effect that maintainers get notifications if the APKBUILDs they maintain get changed.
2024-03-17 22:02:54 +00:00
device/*/soc-qcom-msm8953/ @barni2000
device/*/soc-qcom-msm8996/ @Tooniis
device/*/soc-qcom-sc7180/ @jenneron
device/*/soc-rockchip-rk3399/ @jenneron
device/*/soc-samsung-exynos4412/ @Newbyte
device/*/u-boot-librem5/ @craftyguy @alistair23 @Newbyte
device/*/u-boot-pinebookpro/ @QC8086
device/*/u-boot-pinephone/ @Arnavion @PsychoGame
device/*/wl1251-cal/ @Danct12
CODEOWNERS: Add Pablo and Newbyte to GNOME stuff (MR 5208) [ci:skip-build]: already built successfully in CI
2024-06-05 21:10:23 +00:00
main/postmarketos*gnome*/ @pabloyoyoista @Newbyte
CODEOWNERS: add Caleb and Clayton as maintainers of the initramfs (MR 5208)
2024-06-05 21:08:20 +00:00
main/postmarketos-initramfs/ @calebccff @craftyguy
main/postmarketos-ui-i3wm: take over maintainership (MR 5309)
2024-07-02 10:57:11 +00:00
main/postmarketos-ui-i3wm/ @fossdd
CODEOWNERS: Add Pablo and Newbyte to GNOME stuff (MR 5208) [ci:skip-build]: already built successfully in CI
2024-06-05 21:10:23 +00:00
main/postmarketos-ui-phosh/ @pabloyoyoista @Newbyte
CODEOWNERS: update postmarketos-ui-plasma-mobile (MR 5155) This is maintained by Bart, see Maintainer line in the APKBUILD.
2024-05-19 19:17:25 +00:00
main/postmarketos-ui-plasma-mobile/ @PureTryOut
CODEOWNERS: add Arnavion for pine64-pinephone and shutdown-clear-rtc-wakealarm (MR 4709) [ci:skip-build]: Already built successfully in CI.
2024-01-11 00:41:44 +00:00
main/shutdown-clear-rtc-wakealarm/ @Arnavion
CODEOWNERS: order alphabetically (MR 4940)
2024-03-17 21:16:48 +00:00
main/ttyescape/ @calebccff
Reference in a new issue Copy permalink