xcasex

Okay since i'm pretty much doing the same thing with my team at work,  I'll take on establishing clearer process / procedures for issue tracking.   Since both the forum and github support a concept of tagging there's some opportunities there for integration.    
 
We want to make issue/task creation is easy, but deliberate enough that we don't end up with having to filter a bunch of noise.

@all
 
I have had a go at what you suggested and i need to spend a LOT more time getting to grips with the fundamentals, so I wont be claiming any of the deb and packaging side.
 
I think that @Xer0 & @madilabs & @xcasex & @rella would be more suited to this task
 
I will resign myself to doing HOWTO's for armbian as and when i spot the need for one.

@Xer0
 
https://github.com/igorpecovnik/lib/blob/master/desktop.sh
 
We need implementation there, within build process. Current way is outdated, a bit dirty and need an upgrade. It looks like it's still working on H3 but failing on A20 since certain libs needs updated versions. We need a solution which is build from sources to get rid of outdated prepacked libs and pack output into .deb that we can provide an update. Only complete solution makes sense since we already have some temporally solution.
 
@madilabs
 
Check our way of packaging. It's fairly simple, no need for any extra tools.
https://github.com/igorpecovnik/lib/blob/master/extras/tools.sh#L33
 
Later tonight we will be selecting for the first batch - already moving tasks are having advantage.
 
add.
... and well designed and not yet working procedure is better than a quick fix.

i've succesfully compiled media_build drivers on/for Orange Pi
could share how to circumvent the caveats if someone needs

Don't know if you can call it "hidden", but you may want to read official Debian packaging documentation and tutorials (i.e. [1], [2], [3]) - this describes "proper" way - using debian/rules file instead of creating and populating directory structure manually (aka "quick&dirty" way of building packages).
 
Also you may check this (Note: fbturbo is beneficial for both legacy and mainline kernels!), this (pay attention to the warning about partially outdated instructions) and this. Also Rellla's wiki page about Armbian has tons of useful stuff.

Most of tasks benefit from team work - you are welcome to join / claim already claimed tasks. If you need anything special, just ask.

Like i mentioned to tkaiser on irc i'd be willing to take on packaging, seeing as how Gravelrash beat me to it I think we can tag-team it.
 
what i'll be looking into is reusable package templates, metapackages & taxonomy as per the list summarized by @rellla
 
ps. Gravelrash, hit me up in a dm if you're up for collaborating.