Can this please be fixed, or is it intentional for some reason?

https://github.com/armbian/armbian.github.io/actions/workflows/generate-keyring-data.yaml

ERROR: Unable to find debian-archive-keyring package URL from https://packages.debian.org/sid/all/debian-archive-keyring/download

Thanks for all you do!

Edit

With the limited understanding I have of this, I extracted relevant code and just ran a check on my local machine, and it returned:

  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
100   3012 100   3012   0      0    509      0   00:05   00:05            509
Debian debian-archive-keyring URL: http://ftp.debian.org/debian/pool/main/d/debian-archive-keyring/debian-archive-keyring_2025.1_all.deb
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
100   3021 100   3021   0      0    532      0   00:05   00:05            532
Debian debian-ports-archive-keyring URL: http://ftp.debian.org/debian/pool/main/d/debian-ports-archive-keyring/debian-ports-archive-keyring_2026.02.04_all.deb

(the reason it took 5s was due to the time it took me to press "allow" on the outgoing curl connection in my firewall)

So maybe it was just a fluke, and it was just really unlucky failing resolving to packages.debian.org instead of ftp.debian.org those two times.

Idk, just wanted to make sure everything was correctly configured.

Ignore this if all is ok.

 ./compile.sh BOARD=espressobin CLEAN_LEVEL=make-kernel RELEASE=trixie

.....

-rwxrwxr-x   1 root  root  296665952 Apr  7 16:47 vmlinux.unstripped
-rw-rw-r--   1 root  root     220926 Apr  7 16:47 modules.builtin.modinfo
-rw-rw-r--   1 root  root      16667 Apr  7 16:47 modules.builtin
-rwxrwxr-x   1 root  root  296215160 Apr  7 16:47 vmlinux
drwxrwxr-x  23 root  root     12288 Apr  7 16:47 kernel/
drwxrwxr-x  79 root  root     12288 Apr  7 16:47 fs/
drwxrwxr-x   5 root  root     36864 Apr  7 16:47 crypto/
drwxrwxr-x  22 root  root     20480 Apr  7 16:47 lib/
drwxrwxr-x  27 root  root      4096 Apr  7 16:47 sound/
drwxrwxr-x  23 root  root     12288 Apr  7 16:47 scripts/

$ armbian-imager

# installed the new image...

16:55:21 ● custom_image: Check decompression for /srv/development/espressobin-ultra/armbian-build/build/output/images/Armbian-unofficial_26.05.0-trunk_Espressobin_trixie_edge_6.18.21.img: false
16:55:21 ● operations: Starting flash: /srv/development/espressobin-ultra/armbian-build/build/output/images/Armbian-unofficial_26.05.0-trunk_Espressobin_trixie_edge_6.18.21.img -> /dev/sdb (verify: true)
16:55:21 ● flash::linux::writer: Starting flash: /srv/development/espressobin-ultra/armbian-build/build/output/images/Armbian-unofficial_26.05.0-trunk_Espressobin_trixie_edge_6.18.21.img -> /dev/sdb
16:55:21 ● flash::linux::writer: Image size: 2252341248 bytes (2.10 GB)
16:55:21 ● flash::linux::writer: Unmounting device partitions...
16:55:21 ● flash::linux::writer: Writing image...
16:55:27 ● flash::linux::writer: Write complete: 2148.0 MB in 5.4s (avg 398.9 MB/s)
16:55:27 ● flash::linux::writer: Starting verification...
16:55:27 ● flash::verify: Starting verification of 2252341248 bytes (2.10 GB)
16:55:32 ● flash::verify: Verify complete: 2148.0 MB in 4.9s (avg 441.9 MB/s)
16:55:32 ● flash::linux::writer: Flash complete!
16:55:32 ● operations: Flash completed successfully
16:55:32 ● custom_image: Deleting decompressed custom image: /srv/development/espressobin-ultra/armbian-build/build/output/images/Armbian-unofficial_26.05.0-trunk_Espressobin_trixie_edge_6.18.21.img
16:55:32 ● custom_image: Attempted to delete file outside custom-decompress cache: /srv/development/espressobin-ultra/armbian-build/build/output/images/Armbian-unofficial_26.05.0-trunk_Espressobin_trixie_edge_6.18.21.img
 

$ sudo mount /dev/sdb1 /mnt/
$> ls -ltr /mnt/boot/vmlinux-6.18.21-edge-mvebu64 
-rw-r--r-- 1 root root 36108800 Apr  3 18:36 /mnt/boot/vmlinux-6.18.21-edge-mvebu64

When booting:

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.18.21-edge-mvebu64 (build@armbian) (aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT Thu Apr  2 07:23:33 EDT 2026
[    0.000000] KASLR enabled
 

  I am receiving this error while building the image:

Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop0 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.

I am .

This happens in the partitioning phase (lib/functions/image/partitioning.sh line 229, using branch "v23.11" commit bba856bb57823556e12fa180284c7490fdd3708d😞

  run_host_command_logged partprobe "${LOOP}"

Investigated a lot, tried to unmont the image, losetup -d the loop device but nothing helped.

Can you please help me?

Kind regards,

   Andrea

Today I updated vbox, reinstalled ubuntu  git cloned master and tried again with the similar results (different loopx sometimes).

Any help would be greatly appreciated.

🔨]   The partition table has been altered.
[🔨]   Syncing disks.
[🌿] Allocated loop device [ LOOP=/dev/loop3 ]
[🔨]   Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop3 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.
[💥] Error 1 occurred in main shell [ at /home/sysadmin/build/lib/functions/logging/runners.sh:211
    run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211
        run_host_command_logged() --> lib/functions/logging/runners.sh:193
             prepare_partitions() --> lib/functions/image/partitioning.sh:230
                do_with_logging() --> lib/functions/logging/section-logging.sh:81
         build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:86
   full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36
          do_with_default_build() --> lib/functions/main/default-build.sh:42
         cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25
        armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
                 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176
                           main() --> compile.sh:50
 ]
[💥] Cleaning up [ please wait for cleanups to finish ]
[🌿] Unmounting recursively [ SDCARD - be patient ]
[🌿] Unmounting recursively [ MOUNT - be patient ]
[🚸] Freeing loop [ trap_handler_cleanup_rootfs_and_image /dev/loop3 ]
[🌿] Freeing loop device [ /dev/loop3 ]

I can see that 6.8-rc2 and 6.8-rc3 have been released. How do they get integrated into the edge builds?

I am eagerly waiting to see some patches to rk3588s.

Gullik

Desktop improvements really are another unique create.    As you know we don't provide supported desktops, but we do make a like of nightlies, and there are contributors like @Rich Neese that really do a ton of work to make this stuff better.   Another part of our improvement process is stronger peer review on pull requests before merging.

This means we really need to start testing desktop images at the pull requests level.... Which we can gladly build images for PRs, just need community members will to download image, install, test and provide feedback.

Idea is... get list of willing testers and their preferred devices.   We can then produce images and link inside Pull Requests Like This.  Then we can just @mention user to try and review within the github issue and comment.. Easy peasy. no git checkouts, building, etc.


if Interested please reply here with what you're willing to test, and github user id if you're comfortable.  if not we can DM. thank you!


 

• khadas edge 2, installed to eMMC, logs: https://paste.armbian.com/iviwutanag
• bananapi m2+, installed to eMMC, logs: 
• orangepi lite2, logs: https://paste.armbian.com/awicabotod
• khadas vim1, installed to eMMC, logs: https://paste.armbian.com/ulopiziseb , maintainer needed
• khadas vim2, installed to eMMC, logs: https://paste.armbian.com/editiyaziv
• orangepi2e, installed to eMMC, logs: https://paste.armbian.com/ekuyaporil

and some via auto-testing machinery. Most of images works:

We need to fix Rpi4, Jetson nano, perhaps other media?

1. Checking Jira and GitHub tickets

2. Warming up for Khadas support

3. Changes on Allwinner group management

Subtitles 

What we did? This:

1. Check remaining from Jira tickets https://www.armbian.com/participate/

2. Review issues https://github.com/armbian/build/issues

3. Review pull requests https://github.com/armbian/build/pulls

What we did? This:

1. Check remaining from Jira tickets https://www.armbian.com/participate/

2. Review issues https://github.com/armbian/build/issues

3. Review pull requests https://github.com/armbian/build/pulls

Summary: Just overview on the status of CI and discussion on known problems regarding upcoming release. We are pretty confident new build framework will be up to the job. On the board support level, still we need to do testing, try to bump boot loader on Allwinner devices, bump rockchip64 current to 6.1.y.

1. Reviewing where we are with CI support

2. Challenges of upcoming release

1. Progress of CI support
 

- build matrix almost work. It could be integrated into production code, but we will do another week of polishing.

- we have added on-demand cloud runners action to add additional 128 build runners when needed

2. Security concerns

We talked about potential issues and how to improve that. A dedicated person, a CSO volunteer for Armbian project is most welcomed. There are issues in general and GitHub CI specifics, so understanding of those process is needed to understand or learn.

@Contributor/Maintainer

1. Progress of CI support

https://github.com/armbian/os 
Changes: 
- release numbering changed from 23.05 -> 23.5

- we have two separate version configs. One for nightly, one for stable, so its easy to generate a new release. Full or partial - for a single board only. It automatically increment patch number when doing that.
- all images are rebuild every run / night on 8 build clusters.

- splitting testing related tasks from armbian/os to armbian/ci is planned for future

- all currently enabled 3rd party packages are syncing also to stable repository.

All those scripts needs to be feed with JSON which is still around a week or two before integration. We checked the progress.

2. Mechanism for rebuilding packages from sources 

We concluded its better to switch to some existing solution. As this is still a low priority and not needed for upcoming release, main development won't be touching with it within next two months.

@Contributor/Maintainer

1. Redesign board support packages CLI & desktop
   We focused great deal of time to debug and agree how to deal with board support packages. Changes will be added to this merge request
2. XML / JSON generation to support CI
   XML/JSON development is also progressing nicely. BASH part is done, while there is some work around Python assembly
3. Build framework 1st run configuration
   Ran out of time for this topic.

@Contributor/Maintainer

1. We have cycled issues that are opened and found out there is nothing super critical at this moment https://github.com/armbian/build/issues Most of are minor issues or small to mid feature requests. 

2. First run configuration topic was skipped as key people on the topic were not on the meeting

3. We focus great deal of time on idea how to improve interaction with community and how to motivate people that use build system to help arranging documentation. As this is more or less our only option. Another alternative is that someone dedicate his full focus and check all feature. We checked "developers section" of docs and identified sections which can be removed as they are deprecated. The same for build switch. We didn't go into specific switches, but decide to generate section "Deprecated" and moved all features that are not maintained or broken, there. To wait for maintainers. Also we would set a date when feature is going to be removed unless it will be covered by someone.

Summary:

1. Changes on "about Armbian"

An email will sent out to all people mentioned on new "about armbian" to confirm their presence as is, chose anonymization (forum nick instead of "first name l."ast name)

2. Armbian versioning and repository management

- we are temporally going back to original versioning (as known from master branch) as its one step to far

- repository management was already tested with previously mentioned revert. It is already done, but need cleaning and making PRs

- we will drop DTB package and move dtb blobs to the /boot/

Short term to do:

- matrix to generate JSON for images and packages generation

- add warnings and exists on deprecated functions such as KERNEL_CONFIGURE=yes which is causing users many problems

- prepare more design related documents and instructions for developers to join in easier

3. Build framework 1st run configuration

We ran out of time, next week.

@Contributor/Maintainer

I discovered today (using Banapi-M5) with apt-file search 01-armbian-defaults.conf that this file is part of
the deb https://imola.armbian.com/beta/pool/main/a/armbian-bsp-cli-bananapim5/

I tried to fetch the sources on bsp-cli on https://github.com/armbian/build/tree/main/packages/

It is indicated bsp-cli folder in the README but neither the directory exists

nor bsp/bananapim5 folder that may provide the sources for the debian packages.

I am a bit confuse how to contribute to add the headless support for example.

It there an other git repository? Thanks.

                                                                     SoSie

 

In order to get best possible support status, please help us with testings. This last testing phase is a final check to see if devices boots and if basic functions work. We can only fix minor issues, try to recreate or remove broken images, but its also good if we write down what is wrong https://www.armbian.com/bugs/

Deadline for submitting test report: February 24th

Armbian has its own infrastructure for automated testings. But its limited so we need additional help with manual testings. Results:

- release candidate testings. Images has been uploaded to: https://stpete-mirror.armbian.com/dl/ -> BOARD/rc/

Publish report to:

https://www.armbian.com/rc-testing/

or comment below.

(I have manually tested Odroid N2+, Rockpi 4 1Gb)

@Contributor/Maintainer

In order to get your work into the release log, add a title, URL to commit / PR and set "Fix version" to 23.02

Open issues:

https://armbian.atlassian.net/jira/dashboards/10103

Video:

https://us06web.zoom.us/rec/share/ly7gbgZBTY1M4eiumUk6Gp357Jl0RV0h7usdUEGN5WcNKXNIwsOoNHbtoLbBeEje.KCku4wdAigfEI7pB

Armbian Next Jira:

https://armbian.atlassian.net/browse/AR-1451

@Contributor/Maintainer

Video:

https://us06web.zoom.us/rec/share/vq04OFykxpw7nGp8wJxKME7w8uNf1kMrwHRLldQLTCLJCT-zsZY8KP76aCknhBfN.JyvzRmfR9qulexM2

Slides:
https://github.com/rpardini/armbian-build/blob/extensions/README.armbian-next.slides.md#update-feb-1st-armbian-next---general-changes

Armbian Next Jira:

https://armbian.atlassian.net/browse/AR-1451

2. Moving development related topics to GitHub

Summed here:

https://armbian.atlassian.net/browse/AR-1529

3. Questions around upcoming release

Today is the code freeze. Actions:

• notify maintainers and prepare them to be ready on testings in two weeks from now
• notify developers:
  • their code gets into release log only if exists in Jira. Minimum requirement is Jira issue or Jira story with Name, short description and field "Fix versions" set to 23.02
  • that code freeze is a milestone when we change our focus into code stabilisation and fixing bugs. It is not expected to drop existing work in progress at once but gradually close it.
  • in the code freeze period, there is additional restriction on code merge: pull requests approval from 1 person to 2 persons

@Contributor/Maintainer

1. Merging NEXT (Jira tickets)

2. CI overview

Summary: TBD

1. Merging NEXT (Jira tickets)

- many small fixes

- windows build support (WSL2)

- small machine support (smarter dependency handling)

- better patch logging and logs in general

- people contributing

Focus on:

- CI, aggregation, rootfs cache ( @Igor @rpardini)

- testing, testing, testing (anyone)

2. Providing stable builds for main TV box image?

We generally support this idea and builds can be enabled @SteeMan https://github.com/armbian/build/blob/master/config/targets.conf

3. None this week.

Comments on all topics are welcome!
 

@Contributor/Maintainer

1. Merging NEXT (Jira tickets / updated slides)

We discussed progress and problems. Help is needed with:

• enabling CI
• developer perspective testing -> test all boot loader, old boot loaders, especially armhf images: cubox-i, odroids, clearfog, ...
• user perspective testing
• desktop (currently is broken?)

2. Encourage end-users to open bugs to Jira?

Replacing https://www.armbian.com/bugs/ with instructions how to add a bug to Jira seems like a good idea. But this will be community managed without any obligation from Armbian team. Basically introducing a proper bug tracker. Existing AR-XXXX issues that are hardware specific should be moved there. If we have a consensus on that, we have to make a plan, write proper instructions and launch it ... or forget about.

3. Move developers forums to GitHub

We were weighting idea to try to encourage more discussion on GitHub and have forum more users oriented. For start, we can try to enable Action - if label discussion is raised, it automatically creates a topic on GitHub discussions. Or similar. If we do that, we should first deal with hardware related bugs. 

For 2 and 3 we didn't come to any common conclusions except that communication is fragmented around forum, git, irc / discord, emails, PMs ...

Comments on all topics are welcome!
 

@Contributor/Maintainer

1. Checking the progress of Armbian-next. 

• most of open bugs has been fixed.

How to help?

• users? continue to test various variants -> open a ticket
• developers? focus on cleaning rockchip64 / media patches, focus into config/ section -> moving family and board hacks into extensions

2. Armbian short description

We are still not unified. Most sane idea is to better divide Armbian as OS for end users and Armbian as a build system for developers / integrator / business users and name those two more appropriate. We couldn't unite on a name to fit it all. 

3. Mainlining of patches

We generally agree and encourage this but we can deal with this gradually. Cleaning and squashing patches first, then move on. While doing this perhaps mark what could be good candidate to mainline so we don't press on people to proceed right on the spot.

1. Merging NEXT (updated slides)

We discussed progress made in past week (Jira Epic) and set limited expectations for following week due to holidays season. We will try to enable rootfs caching CI at first (which has to be compatible with master) and Docker image creation next (which probably isn't?) 

2. Unifying boot process

Most single board computers needs good overlay handling so moving them to complete generic image is likely / in short term not possible. We still can not count on DTBless or DT from u-boot only, well support from vendor SPI. If we want to move like everything to UEFI and keep things operation / loose no feature, its a lot of work. Sorting out u-boots and going extlinux way with support for multiple kernels (NEXT/CURRENT) might be the best mid-way. 

3. When 6.2 and 6.1, current / edge

Keeping and stabilising 6.1 at EDGE for few months, waiting that it will be tagged as LTS for sure. Keeping new things like 3588 / 3568 at their own kernel branches, CURRENT = 6.1, EDGE = 6.2 (at once)

@rpardini @JetHomeDid I forget to mention something important?

Event | Recording

This weeks meeting topics:

1. Merging of next generation build framework Primary goal is to understand benefits it is bringing as we all will need to sacrifice some time in order to review it, then merge and fix remaining bug. Despite our current system produces images, we have many bugs and dirty workarounds that this upgrade is addressing.
2. The future of rockchip64 family Main goal is to make it maintainable again.
3. GitHub development and review process Main goal is to motivate people to take more responsibility for reviewing and merging. Define clear rules.

    

Conclusions:

Everyone interested should watch a recording (~1h) and place a comment below. Comments will be discussed here and / or at next meeting. Before we can do anything in real regarding merging NEXT, we need to clean patches but also address several things, starting with those:

• Making a tool / module for patch generation (@rpardini)

• Preparing guidelines for review and contribution (@giddy)

• Move repo management from the build system (@igor)

How to help? Cleaning the patches! (helper is here)

armbian-next_-_meeting_21.dec.2022.pdf

https://armbian.atlassian.net/projects/AR/issues/AR-497

Description:

While it is possible to customize Armbian images at build time using the customize-image.sh script is not as comfortable as a chroot shell inside the image would be.

Destination:

https://github.com/armbian/build

Skills required:

Bash

[ error ] ERROR in function install_deb_chroot [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:285 -> functions/main/build-tasks.sh:208 -> functions/main/rootfs-image.sh:77 -> functions/rootfs/distro-agnostic.sh:282 -> functions/rootfs/apt-install.sh:22 -> functions/logging/traps.sh:0 ]
[ error ] Installation of linux-u-boot-nanopiduo-current failed [ nanopiduo jammy no sunxi ]
[ o.k. ] Process terminated 

Board maintainers @Contributor/Maintainer please check status of your board. Report a bug or try to fix it by the final release date.

Developers, check if your contribution is recorded in Jira as otherwise it won't fit into the release log:
https://armbian.atlassian.net/projects/AR/versions/10012/tab/release-report-all-issues

64 Issues in version

61 Issues done

0 Issues in progress

3 Issues to do

This release should be in bug fix mud as we stay at 5.15.y / 5.19.y for CURRENT kernel branches.

Aside from all the unheard user wishes we decided to create a new dedicated room for specific tasks with defined clear goals.

Topic creation is limited to collaborators.

I am creating my own Kernel configurations with Armbian, for example I want to observe the effect of 100Hz/250Hz/1000Hz on the timer on osnoise etc.

Currently ./ compile.sh can result in two outputs:

- Either a SD-Card-Image with one Kernel configuration

- or some Kernel-files in "Output" I dont yet understand in their structure or what to do to activate them on an already created running System making it bootable

I saw that Armbian-Config offers to switch Kernels, but this loooks more like a long list of standard-kernels from somewhere...how can I use this or a different technique like uboot to set my SD-card up like:

Three custom Kernels stored e.g. for the three frequencies switchable for the next boot.

Board maintainers:

@Contributor/Maintainer

• Open / close bugs related to your board  in Jira for your board and close them if they are resolved before release date.
• Record also bugs that were closed but they were not recorded to Jira (to have this info in release documentation)
• Bugs that are resolved change field "Fix versions" to "22.05". Optional select board and SOC.

Everyone with Jira access:

@private/contributor

• claim ownership of closed tasks (Assignee)
• close issues if they are done (change field "Fix versions" to "22.05")
• move issues to next release cycle (this needs to be done) or backlog (one day)

Anyone that wants to join:

• we are fairly good in maintain hardware, a little less in tweaking OS and desktops, ... We are good with infrastructure, except forums. Here we need help in moderating and reorganising. We also need help in leading projects. Like this release cycle and many small projects. If you wanna join coordinating release, read this ...

Meeting preface:

Clubs themselves can be confusing. They work similar to forums but have different arrangement of things. Also they partially lack of moderating options that common forums provide.

Thoughts?

anyway all supported boards got their individual tag. in bug tracker forums only those must be chosen, for some other forums tags are open but supported board tags are marked as recommended.

Therefore I propose to enable additional conditions applied to the build framework master branch:

- code must be submitted via a pull request
- pull requests require at least one review and approval from another individual

- all changes open requests resolved before merge.

- in-line conversation on merge request has to be resolved before merge
- commits pushed to master must have verified signatures,
- conversation on merge request has to be resolved before merging.

@private/contributor

Most of the things we already use, so new thing is mandatory review - counts from anyone except from the one that is sending a pull request.
 

Speak up if you find those measures too draconian.

Also I would like to point out another change related to our label system. It seems too complicated, some tags were never used and not many people are using them. So limiting them down significantly - comments are welcome here https://armbian.atlassian.net/browse/AR-959

So I double checked the job description, and that's not on there now.

Was that a simple oversight?  Or maybe we changed policy about handing out WordPress access to all these new people to the project?

Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 

Release Planning Meeting Location: Armbian IRC
Release Date: 2022-02-28

Release Branch Link: https://github.com/armbian/build/tree/v22.02

Release Changelog:

Release Coordinator: @Heisath and hopefully some new person on the team

Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.

Current steps:

- Refine supported/WIP/CSC/etc. board status

- Update maintainer list

- Onboard new maintainers / contributors

- Move Jira issues to new release

- Select release name 

@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini

Pls. ping developers I forgot  

https://github.com/armbian/autotests

Description:

Having a reliable automated testing for boards is absolutely mandatory. While the tests working most of the time the reports are not as reliable as they should. Also the code could need some refactoring and cleaning.

Destination:

https://github.com/armbian/autotests

Skills required:

Bash

https://forum.armbian.com/topic/16933-armbian-config-rfc-ideas/?do=findComment&comment=119703

https://armbian.atlassian.net/browse/AR-638

Description:

Our armbian-config tool shall be refactored or as a modular framework rewritten from scratch.

We are looking for both experienced bash scriptwriters as well as somebody who takes a overall look at task execution.

Destination:

https://github.com/armbian/config

Skills required:

Bash

* revise "invalid label"

* focus on moving messages

Came across https://en.wikipedia.org/wiki/Invision_Community.

The first thing I noticed is that it is proprietary software. Which I think is very out of character for a F/LOSS project at least alluding to the name Debian. Which carries a number of connotations, at least in my mind... Which is a whole another discussion, however...

Secondly, a quick read through that Wikipedia article quickly reveals a number of documented cases of changing things on their users, going back on their word, etc. I see red flags all over the place. Not the sort of software I feel inclined to invest a lot of time into learning. But I am the new guy here, so...

Has there ever been any discussion of perhaps changing forum software? Or why this one was even picked in the first place (familiarity, Jira or other integration, or...)? I did a few different searches (internally and externally) but couldn't come up with anything.

https://github.com/lanefu/sbc-gpio-pcf857x/blob/main/lib/gpio.sh

It would be great to convert this in to a simple python3 class.    Given we use this with various SBCs, I would recommend using https://docs.python.org/3/library/subprocess.html#module-subprocess to continue to exec via the gpio shell command other than a native python gpio library.

extra credit: create a REST API via flask

extra extra credit: Add Swagger interface to REST API

extra extra extra credit: react interface to REST API  

https://armbian.atlassian.net/browse/AR-315

Description:

A while ago general GPT support has been added. Though it is not possible yet to use it within nand-sata-install.

Destination:

https://github.com/armbian/build/blob/master/packages/bsp/common/usr/sbin/nand-sata-install

Skills required:

Bash

https://github.com/armbian/config/issues/120

Description:

Recently our download mirrors were regrouped into continents.

An option to select the best matching mirror group via armbian-config would make it perfect.

Destination:

https://github.com/armbian/config

Skills required:

Bash

@balbes150is making some accusations and I would like to see some more evidence. He is a moderator and I assume he understands that writing such things require some sort of proof.

Or maybe he can write anything he want and mudslinging is ok at this forum?

I am going to ping everyone I can think of (actually, I simply use the list here) below, but please add anyone else who I miss.

@Igor @lanefu @Werner @TonyMac32 @SteeMan @soerenderfor @pfeerick @NicoD @JMCC @balbes150 @_r9

https://github.com/armbian/dl-router/issues/12

The forum appears to be directed at hardware, but there may be potential for service. I for one am hitting a brick wall with coding some audio control hw and would like to hire someone to help. This seems like a place that might work for that.

I originally signed up for the 5 Euro auto pay. The 5 Euro auto pay works fine, then I get an invoice for the 15 balance ... humorous but tedious. I know you guys are working on such things so I thought I would report, hope this is the appropriate place to do so.  But I get these emails saying I've paid but Igor hasn't picked it up yet. I gave it to ya, use it ;]

So it looks like you still have something to adjust, it would be nice to just have the 20 come out of my account automagicly in one charge.

With other systems where I have like issues I usually cancel all of them then resubscribe with the correct one. Would this be the course or is there a better way...

Thanks and keep it up!!

Without proper common project tracking, one need a day or a week to sit down, scrap all this, think, make a visual, think again. And perception is still too narrow. What is important, what shell anyone work on if he wants to? Where we go next? When to finish this, that we are able to do that?

Recently we did some changes to upgrade organisational levels by starting to track changes via Github kanban project management system. We made groups and few tasks went along smoothly this way. It is probably good enough solo for build script but to manage the project as a whole, we need something (much) better than this.

There were several mentioning and ideas related to Jira. I use Jira on a separate project for several months now. Playground is around 50 active users separated in multiple teams doing software development. I am delighted how Jira helps in this process. There is surely some efforts to get this implemented and shift your MO to work the SCRUM way.

Do we want that? Which are pros and cons? Is is worth going this way?

If we go this way, we need and should find assistance. Perhaps there are people here which have (much) longer experiences running software project this way and can show us what is the best way? Dedicated project manager or just an Jira geek, which, in theory, does not need coding skills and can scan and move ideas from forum/GitHub/personal chat. Those which we are happy to deal with, to this central project manager tool. This should be rather a support for development process, not an additional boring unnecessary work.

There are videos for quick start and some additional resources can be added if needed. I saw those/recommend at least this few times:

• Using Jira (22m)
• Software development best practices (40m)

Primary purpose of project management tools is to cope with a complexity. Jira was designed and it is used by many software development projects. Bigger and smaller than ours. We need better organisation and we need to save time!

What shell we do with current Github issues and effort? IMO simply move already created teams and project structure to Jira while leave everything as is. And with help from someone that master Jira. The unstructured part of the development remains as is, while it could and can be linked with Jira.

I already sent a request to get a free Jira licence for open source projects. It was granted at once. Shall we proceed? In case we do, I need help, and help to get help. In case not, what then?

I sort of got into the habit of welcoming new people (in other places where that's encouraged) as I have always felt that the idea of "Community" is very important in F/LOSS. I even did it here, but only couple times so far. Just to try and make new people feel welcome. If we are lucky, maybe they will stick around, and eventually, contribute...

However I get the sense that may be going against the existing culture here, which seems to be more serious. I feel like doing such things would be viewed as "polluting" a thread or going "off topic" etc. But my perception could of course be wrong, so I wanted to discuss the issue. Especially with @Igor and @balbes150 who already expressed their dislike of forum signatures.

Also perhaps others? Please tag any such cranky minimalist people here (especially devs or other respected community members) so as to get their opinion on this.

As you can see it will

• add reply as above
• lock topic
• add topic prefix "[Invalid] - "
• (if hidden) unhides topic

Jira is designed for that. We have far greater problem - who will deal with bugs?

Description:

Aptly tool for creating apt repositories has been unmaintained since 2019 and that the original maintainers are now looking for new people to replace them. We encourage everyone to read the issue below and consider if you can allocate time to maintaining aptly (processing pull requests, issues and so on) and if so offer to join the aptly-dev organisation on github.

Destination:

https://github.com/aptly-dev/aptly/issues/920

https://armbian.atlassian.net/projects/AR/issues/AR-235

Description:

Add an option to armbian-config to allow editing the device tree

Destination:

https://github.com/armbian/config

Skills required:

Bash

I strip it down to a few notes:

• create a new sub-forums trade/marketplace where people
  • can offer spare SBCs for trade or sale and
  • can create requests if somebody is willing to sell his board XY
• To participate users need to fulfill TBD requirements like number of days registered, posts, reputation...
• User must agree to rules in order to create topics which will state that
  • Armbian staff does not and will not be involved in any way into trades. Armbian takes no responsibility for whatever may go wrong whatsoever
  • and user shall use PM, email or any 3rd party messenger to exchange private details
  • commercial sales will be forbidden. private trades/offers only

What do you think? Waste of time or an idea worth a try? Let me know!

https://armbian.atlassian.net/browse/AR-200

Description:

SBCs become more and more powerful and one of our long term goals is to enhance the desktop experience with Armbian.

At the moment we only have @Rich Neese who spends a crazy amount of time to push this forward.

Destination:

https://github.com/armbian/build/tree/desktop

Skills required:

Bash, dealing with configuration files of various desktop environments

• move topics related to p2p or
• create a new forum that collects all unsupported topics

I had donated to the server fund, did that mess up the auto? I noticed there is a recent charge so I assumed it is still working?

BTW, I think there should be an intermediate step between individual and corporate ... 5 Euros is nothing but 50 is more than I can do monthly.  Can you add a 10 Euros / mo?

LOL did I break something? Did I subscribe? ;]

Just as an experiment.

Since latter also includes - besides adding a post reply - the option to hide/unhide/move/lock threads as well as manipulate the topic title by adding a pre- or suffix I suggest to get rid of canned replies.

The downside of this change is that it is no longer possible for anybody, who has permission to do so, to create their own canned replies. However I barely notice anyone using this feature and the most common used canned reply is "missing armbianmonitor -u". Therefore not a big loss. This can easily be implemented as saved action as well.

Have there been some recent changes?  It seems only 1-2 days ago I could mark any post as the solution, but this seems to have gone away?

This is what I came up with

In first place I though about some transparency but since there are multiple themes including a dark one available it needs to look decent on both.

Also thinking about adding some further icons in the same design but they are not to be revealed to the public yet

I just dropped over this page by accident and I think this is the first time I have seen this since I registered

I have my doubts that many actually reading those, last but not least it is a lot of text and most is already spreat around to places where it is actually important.

So I suggest to simply remove the page due to lack of value.

https://docs.armbian.com/User-Guide_Getting-Started/

Since we have now this nice quick start video I was thinking about making more videos in the future. Kind a video series "How to Armbian" which cover various topics around basic stuff.

One idea that came to my mind to cover were serial consoles since they are in most cases the best way to debug and get an idea what is actually happen "inside".

Another one was about going real quick about the different ways how to contribute (time, money, knowledge)

Ideas for now:

• How to contribute?
• Using serial console for debugging
• Build script for advanced users

@lanefu @NicoD

dl.armbian.com is redirecting me to https://minio.k-space.ee/armbian/dl/espressobin/u-boot/

which is throwing an error: NoSuchKeyThe specified key does not exist.dl/espressobin/u-boot/armbian/armbian/dl/espressobin/u-boot/163FA81E77EC23A1394e75a7-0234-4f85-9911-0a00ffd23a46

Humor

But first, some humor. Does anyone remember this guy? Anyway, that old infomercial kept playing over and over in my head today while I was working on this. I think we stumbled across some of his students! OK, carrying on...

What Not To Do

First thing to probably point out, let's not simply edit out these links one by one as we come across them. That doesn't really solve the problem. In fact it makes it worse by eliminating the "trail of bread crumbs" so to speak, the easiest way we have to "get them all" (which is by recursive searching). Allow me to explain...

These links seem to be posted in groups, by a small number of spammers. Once you catch on to one part of a cluster of them, it is actually pretty easy to methodically work your way through and find quite a few more, and "get them all" (within a given cluster).

Modus Operandi

But let me back up even more, for those who are totally unaware of this issue. What these people (we think they are human) are doing, is to register, and then post some at least seemingly relevant information in some topic, at least enough to get their post(s) approved. Then they come back some days or even weeks (!) later, and edit their post(s) to insert spam links. To see some actual examples, have a look at the Announcement post linked in the beginning.

1. Check Profile

So, once I found one such post / Member, the first thing I would do is look at their profile. Typically they will have from 1-5 posts or so. I would right click, and open each new post in another tab. Sometimes you will have to search then in the thread (using your browser search function, Ctrl-F in Firefox) to find the post. You will quickly be able to determine whether they are a spammer or not (you will see all the spam links in all their few handful of posts).

2. Flag as Spammer

Once you are certain they are a spammer, there are a couple ways you can "Flag as Spammer." Since you already have their profile open, you can click that button in there. Other way is to mouse over their avatar, and then the gear at bottom right opens another little menu that gives you the same option. This should be the first real action you take, because it does a couple things all at once (which will save you some time):

• it Hides (not Deletes) all their posts, and
• Bans them from the site (permanently)

Note that the above are subject to Admin settings, and these are the current settings as of this writing.

3. Being Thorough

Now, if you like to be thorough (I do) I will also kind of go through the threads that contain their spam posts (especially after their post(s)) and look for the following:

• did any other user (usually unintentionally, or on accident) quote the spam links?
  • if so, edit out those spam links by hand and leave a note what you did
• make sure no actually useful content was hidden (I have yet to find this in even one case)

4. What Must Be Done (at Minimum)

However at a very minimum, you should be taking down a list of all these spam links you come across. This is key to the whole process. Methodically complete all of the above for each spammer and each of his posts. When you are done you should have a list of spam links, and one or more Banned spammers, with all their posts Hidden.

5. Working our URL List of Spam Links

Next step, we do a regular search on the forums for each of the spam links in turn. I like to leave this search window up, and again right click and open each result in a new tab, do whatever I need to do, and then come back to the main search result list, and keep going. Some pointers for this phase:

• Some results will be ones you already discovered
• Other results will lead you to additional spam posts and/or users. Take care of each of them in turn (as above) and continue to add to your URL list.
• Scratch each spam URL off your list once you have worked your way through all the results for that particular spam URL.
• Some times you may have to "massage" the URL a bit if it is too close to common search terms
  • shorten to base URL
  • add quotes around it
  • prepend "https://www."
  • etc...

6. The End

Get yourself a cold, tasty, delicious adult beverage of your choosing. You earned it. You have made the world a slightly better place than it was this morning. You have Maintained Civilization. Etc. 

I think that just about covers it. Any questions, comments are welcomed.

One thing I would like to re-iterate, if you don't have the time / patience for this, just Flag the post(s) and leave it for someone else who does. I think it's better to handle these properly and thoroughly than to half-arse it, deleting few links and then handicapping our ability to "get them all" later on.

Thanks!

EDIT: As an example, I will include my working list, below. This is what I came up with in a couple of hours this afternoon, all starting from one link that @Igor sent me in IRC (this is a bulleted checklist and table from org-mode; names of non spammers vindicated in my search have been removed):

** Spam Links

   - [X] showbox.run
     - [X] 192168ll.onl
     - [X] 7zip.vip
     - [X] 9apps.ooo
     - [X] apkals.com
     - [X] apkals.com/veteran-mode-dual-apps-apk
     - [X] applock.ooo
     - [X] appsync.biz/dafont
     - [X] bluestacks.vip
     - [X] dataguru.in/company/search-list/list-of-companies-in-gurgaon-dlf-cyber-city
     - [X] kodi.software
     - [X] luckypatcher.pro
       - [X] downloadnox.onl
       - [X] vidmate.vet
       - [X] vlc.onl
       - [X] user: haileykhysen
     - [X] minimilitia.mobi
     - [X] mxplayer.pro
     - [X] notesandprojects.com
     - [X] notesandprojects.com/kiran-news-agency
     - [X] oovoo.onl/adam4adam
     - [X] pnrstatus.vip
     - [X] salezshark.com/sales-automation
     - [X] sarkariresult.onl
     - [X] shareit.onl
     - [X] showbox.bio
     - [X] showbox.kim
     - [X] tutuapp.uno
     - [X] ucbrowser.vip
     - [X] webmentorz.com
     - [X] webmentorz.com/bank/wren-and-martin-book-pdf

|--------------+----------|
| User         | Spammer? |
|--------------+----------|
| Bï Ĺý        | yes      |
| jhoney       | yes      |
| klimbo       | yes      |
| nour         | yes      |
| haileykhysen | yes      |
|--------------+----------|

• Users with moderator privileges are now displayed correctly
• Started to move Announcements forums from tags to prefixes, also added a new one there

Showing pending approvals which have been dealt with an hour before.

Also color adjustments to themes are not being adopted.

memcached is not the cause.

Prefixes are gone for the moment and are replaced with traditional tags since the used addon is most likely abandoned by the author.

Certain plugins break acp entirely when trying to upgrade them.

@balbes150

As a new Mod I often feel like a Level 1 Tech Support. Or perhaps better stated, "triage." Which I figure is our purpose, to "take care of" as many low hanging fruit as possible (or at least sort to correct place, maybe adjust title, tag, ask OP for further info, etc.), in order to free up time/attention of Devs and more experienced users. I try to take on as much as I can, but there are simply things I am unsure about (and from private discussions, I know other new Mods feel same). As our knowledge grows over time, we will be able to take on more and more. But I think we can slightly better use the tools this software already provides to help with this (IMO, some times necessary) mentoring process. I realize you guys are busy (hence need for Mods in first place) however...

Give a man a fish, and he will eat for a day,

Teach a man to fish, and ...

So I request to the more experienced Mods and Admins, please take few moments here and there to help teach us newer guys (when we need help) how to fish...

But this post will also be for my fellow new Mods, as well ( @soerenderfor @Vanitarium @_r9 @jsfrederick , I went through Mod sign up thread already, but please tag any others I may have missed) so please, read on...

Newer Mod (or even regular user) can click on little Flag at bottom of any post:

And then enter some question what they need guidance about:

Now this will show up to all other Moderators and site level Admin as little triangle in upper right corner:

So far pretty simple, I am sure most of you are aware of this functionality already. Now this is what I propose to codify into some kind SOP:

If we still require attention / advice of someone "higher up" then we leave Status as "New Report" (Flag logo):

Once someone "higher up" replies, then they/we can change Status to "Under Review" (Triangle ! logo):

Where we leave it until person originally raising the flag either:

• gets their answer, at which point they can Close the Report,
• requires further clarification, in which case they can change back to Flag to raise more attention

I think this is a good way of fast, easy triage and sorting, because:

• it does not pollute IRC or forum threads (and less airing of potentially "dirty laundry")
• relevant discussion is attached directly to the thread in question
• "higher experience level" (Mods, site level Admin) can immediately see filtered view of what might need their attention (Flag logo), without having to read all of forums, or even pay attention to Moderation discussions, where they are not needed. However at same time should they want, can also get quick overview of moderation advice being given by Mods to each other, and could add their 2 cents if disagree.
• "medium experience level" Mods can help mentor lower level, to extent they are able, already relieving some load off "higher level" people, while still asking some questions themselves
• "lower experience level" Mods (and even regular users for that matter, although unable to see discussion on the Mod side) can get their questions answered, receive mentoring from "medium and higher" level people, and thereby eventually progress upward
• Over time, this will also build a body of knowledge which new Mods can look through when they have time to get up to speed (similar to reviewing past Bans, etc.)

Do note that this entire proposal is only for the meta of Moderation questions themselves, i.e.:

• should this be moved to x sub-forum
• I am not sure this qualifies as violating rule # x
• etc.

If you think this is a good idea, please say so here, and/or just start fulfilling one of the roles "low, medium, high" as outlined above, befitting your experience level.

I encourage any and all Mods to communicate with each other in this way, adding your $0.02 to whatever Mod discussion, where you feel it adds some value.

Feedback on this idea also welcomed, of course.

Those forums obviously do not receive much attention and the reason might be they are not that present like other forums (and surely new tutorials are not that often posted like issue complains ).

Anyway I was thinking about how to bring more attention to these topics and reduce the amount of sub-forums the same time. What I came up with was the following idea:

1. All topics within those forums will be marked with an appropriate prefix, mostly like the forums were called at the moment (so Review, Research/Tutorial and Hardware hack). This can be done in batch in no time.
2. Then the three forums are being merged into one and moved as a unified forum from sub-forums status to a full forum right between Common issues and Feature Requests.
3. New topics
   1. MUST be approved to make sure no BS or requests are posted there (latter should be done anywhere else). Based on the average activity there this should not lead into a significant amount of additional work (if any). And
   2. MUST have a prefix like described above. Choosing a prefix on topic creation can be enforced by forums software.

Please let me know what do you think.

PS: Yeah I know I should do other stuff in vacation than this

https://github.com/armbian/documentation/blob/master/docs/Governance_Maintainers_TBD.md

From time to time I already adjusted the list to what I believe fits the current situation but I wanted to hear from you all what you think about it or maybe even why it should not receive attention/maintenance.

It is possible to add explanations to certain expression or acronyms.

The example above shows the (in this case case-sensitive) expression OOB (you see it is "underdot'ed") with the explanation "out of the box" while pointing with the cursor on it.

Do you think this is a useful feature and if so what acronyms could/should be added to be automatically highlighted?

Ideas:

• dtc - device tree compiler
• dtb - device tree blob
• dts - device tree source
• IRC - internet relay chat
• sunxi - board family of Allwinner 32bit ARM SoCs
• sunxi64 - board family of Allwinner 64bit ARM SoCs
• XU4 - Odroid XU4
• OPi - Orange Pi
• N2 - Odroid N2
• C2 - Odroid C2
• C4 - Odroid C4
• RK - Rockchip
• AML - Amlogic
• AW - Allwinner
• M4 - NanoPi M4
• M4V2 - NanoPi M4V2
• P2P - peer to peer
• eMMC - embeeded MultiMediaCard
• OS - operating system
• VPU - video processing unit
• panfrost - driver for Mali Midgard and Bifrost GPUs
• cedrus - driver for hardware accelerated video de-/encoding
• PSU - power supply unit
• RC - release candidate
• WG - Wireguard

I suggest to merge those to one standardized reply that covers missing data and armbianmonitor -u as well as tips.

Something like this (with a bit of additional formatting):

Quote

Your support topic is lacking of important debugging information. Please edit and fix!

 

Please describe your setup as best as possible so we know what your operating environment is like.

 

• Name of your board with all details, version number, take a picture if you are not sure what you have
• Name of the image you installed or logs if you can boot the board: armbianmonitor -u (paste URL to your forum post)
• If your board does not boot, provide a log from serial console (UART) or at least make and attach a picture, where it stops.
• Describe the problem the best you can and provide all necessary info that we can reproduce the problem.
• If anything is attached to the board, supply all details

 

Tips:

 

• use spoiler  when adding a long text,
• use  when adding a code,
• be concise.

Will unhide and add this reply.

Quote

Users with moderator rights:

 

enforce users policy.

move threads to the correct sub forum

cut and move off topic sections from one thread to another,

merge more topics under one if that gives better topic overview,

can edit posts for a purpose of:

moving code under code,

moving text under spoilers,

if author explicitly asked for,

breaking the rules will result in a warning. Multiple warnings will result in revoking moderator rights

While the regulation as it is makes sense it does not being in the registration notes since the chance that a users registierung him-/herself just to become a moderator is decently low.

These should be more kind of rules that members have to agree which are elected to become a forums moderator.

Therefore I suggest to either remove those entirely or rewrite them to descripe what the rights and duties of moderators are and integrate this information into the common terms.

Not much to say about that. Do some of these mostly proprietary IM even still exist?

I suggest to replace a few of those with more adequate solutions like IRC, Matrix or Mastodon and threw out AIM, MSN, ICQ and Yahoo.

Opinions?

Tell me what you think,

Granted! Thank you.
 

1 hour ago, Werner said:

Maybe I find some time to take a look into that.

Great!

Forum is our common problem and it should be moderated according to that. We created some https://forum.armbian.com/terms and https://forum.armbian.com/guidelines. Read and use them, change if needed and keep in mind that people usually don't read them ... remember when you read the small print last time?

I have no intention to lead forum moderation - tell you what to do, but I will tell you if you went to far ... I expect the same treatment - I am just a forum user. (even I do have the same power and more as you do). There are topics which need to be sorted out - merge or move - and there are important topics which are floating in the see of banal - I work on this when I find some time which is less and less. Important stuff should be pinned and some, that are there are not relevant anymore, unpinned. If you can not decide on a specific case, but its important, speak up here, publicly. Only if there is a special need for privacy, in private. Administrator rights - for changing more critical things on the forum - contact @lanefu and me. We are both quite busy, so perhaps we shell also expand this role later on if you will come up with lots of ideas for changes.

Can't believe how quick we sorted this out.  And as a side effect, perhaps an IRC channel might get live soon. Thank you!

I couldn't help but wonder however, how much the PayPal fees and exchange rate were eating into my little contribution each month? And if it's significant, maybe we can figure out a better way to transfer funds. I have a strong dislike for middle men taking a cut anyway. Parasites.

Could I add a Reply to the drop down menu? If not, could somebody put this in there for everybody else, please...

Quote

 

1. Provide quality information for us to work with.

2. Use the forum search to find a solution. Make sure you've read the Armbian documentation. 

3. Include Logs: armbianmonitor -u (paste URL in your forum post) 

4. If your board does not boot, provide a log from serial console or take a screenshot

 

Thank you so much....

1. Hardware

                  1.1 Supported SBCs.

                       >> 1.11 ARMvX >> etc.

                   1.2 Unsupported SBC

                          >> 1.21 TV Boxes
                                              >> 1.21.1 TV1 >>. etc.

                   1.3 etc.

2. Software

                  2.1 User Manual & Wiki

                                 >> 2.11 Install

                                            >> 2.12 Post-Install >> etc.

2.2 Apps and Desktops >> 2.21 Install Desktops >> 2.22 Package Management >> 2.23 SDK >> 2.24 Development >> etc.

2.3 etc

3. Projects and SBC Uses

3.1 A.I. >> 3.11 Clever Home >>3.12 Hardware Linear Programmable Controls >> 3.13 Automation >> 3.14 Robotics >>etc.

3.2 Educational Projects >> 3.21 etc.

3.3 etc.

This schematic allows adding subjects ad infinitum but well located inside the big headings and sub-headings. It also permits coding and maybe creating a database for faster searching.

Your comments are welcome!

I also like to keep things in order, but forum and this project is too big for me since a long time ago. Keeping this thing organised can only be done together. I appreciate your willingness to do your share!

9 hours ago, TRS-80 said:

Incidentally, I tend to idle in IRC when online, I know the #armbian channel is not official, but I could also help with our presence there.

#armbian channel is unofficial for one very banal reason  It doesn't have a recording device -> irclogs.armbian.com I tried to fix this once - by reaching out to IRC server staff to acquire OP status which is needed to install a bot, now its years ago, but failed. Then this task simply faded off the radar. It has been more than 25 years since I was installing IRC bots so I also feel a bit rusted doing that ... if you can fix this, #armbian can become official at once and I will also be there more often.

Herzlich willkommen!