* Introduce the `BOARD_MAINTAINER` in board config
Yes, we have documented the maintainers in `armbian/documentation`.
But it seem like that some of them don't maintain anymore.
Use a separated repos make us forget to update it.
So let's document here.
What's more, defining this make us easier to update `.github/CODEOWNERS`
* Set `BOARD_MAINTAINER` accroding to `armbian/documentation`
* Guess `BOARD_MAINTAINER`
Set he/she as board maintiner if he/she:
1. Create the board config
3. Commit at lease 3 times for the board config
3. Commit most for the board config
* Guess `BOARD_MAINTAINER`
Set he/she as board maintiner if he/she:
1. Create the board config
2. The only one to commit for the board config
* Set `BOARD_MAINTAINER` to empty for other boards
* AR-1712 fixing PR from wrong DB
* Fixing maintainers
Signed-off-by: Igor <igor@armbian.com>
* Add variable to missing ones
---------
Signed-off-by: Igor <igor@armbian.com>
Co-authored-by: Rafal-Hacus <68160861+Rafal-Hacus@users.noreply.github.com>
Co-authored-by: Igor <igor@armbian.com>
* [ rockchip64] second round config migration
Recommend all @armbian/boards-rockchip maintainers double check the resulting configurations, as stated in the PR the level of confusion in the family config logic likely means some boards have unnecessary extra stuff.
* Update targets.conf
* Update targets-desktop-beta.conf
* Update targets-cli-beta.conf
* Update targets.conf
Update targets according ot current status of maintainer list
reduce userspaces to Focal
reduce to xfce default desktop
keep one minimal and one edge to check if they build at least.
* adjust support status according current maintainer sheet
* Readd pbp
* Readd pbp
* Readd C2
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
