I want to help on the project. I really do.

[Igor]

Armbian is community driven open source project. To keep it relevant and up to date it needs maintenance round the clock. This work is done by a small amateur contributor force which was under-powered since early days and it still is. For most basic tasks!

Any help is more then welcome.

 

• https://forum.armbian.com/staffapplications/ (what do we need)
• https://docs.armbian.com/Quick_facts/ (overview)
• https://www.armbian.com/get-involved/ (how-to contribute)
• https://github.com/armbian (sources for build engine, documentation, scripts) <---- <---- <---- Also refactoring, better wording, code cleanup.

 

General tips:
 

• plan to do things you understand. 
• expect little to no guidance.
• focus on common needs and forget what is important only to you.
• start small.

If you still don't know how to start, attach your questions below in the topic.

[Igor]

3 hours ago, jata said:

Happy to help

You know how to edit documentation, bash scripting, moderating forum? Perhaps some organising skills? Talking to other newbies? If yes to any, just do it. If no, keep on looking. There is a lot of things to do which does not require any deep technical knowledge but save us precious time. Which we don't have. I have to choose between fixing RC car for my kid or helping you ... 

[jata]

I'm keen to help out with some scripting and get into more technical stuff. Can also edit docs etc. 

 

As a first step on the technical side, do I need to be able to compile a kernel/image myself?

[Igor]

26 minutes ago, jata said:

do I need to be able to compile a kernel/image myself?

No, unless you want to improve documentations for that part.

[jata]

That's great so what can I do to help with the latest rock64 kernel 5.4?

 

Should I get a setup with rock64 plugged into a monitor and then compare the boot info from Armbian_19.11.3_Rock64_buster_current_5.3.11 (working) vs Armbian_19.11.6_Rock64_buster_current_5.4.y (broken)

 

If this is a good starting point then happy to assist...

 

 

[Igor]

6 hours ago, jata said:

If this is a good starting point then happy to assist...

 

- do things you understand.

- forget what is important to you.

- start small.

[Shoka]

Igor, as far as I can tell your documentation omits mention of the SYNC_CLOCK parameter to the build scripts. 

If your build host is a system already synced to NTP, for example by systemd-timedated this fragment from general.sh

    895         # sync clock
    896         if [[ $SYNC_CLOCK != no ]]; then
    897                 display_alert "Syncing clock" "host" "info"
    898                 ntpdate -s ${NTP_SERVER:- pool.ntp.org}
    899         fi

seems to simply mess with the system clock to no purpose.

 

 

What is the objective? To force an NTP synch  or to force the time into the log?

 

timedatectl seems to give correct answers about NTP status even when chrony is managing the clock. I don't have a system to test if it works reasonably with NTPD handling the clock, but if it does, possibly preceding the ntpdate with a check using timedatectl to check if  we are already synched to NTP  and if so skip the ntpdate would be a good idea?

 

Document the parameter?  If we add the check for NTP synch, possibly remove the parameter?

 

Harry

 

[Igor]

2 hours ago, Shoka said:

What is the objective? To force an NTP synch

 

We want to make sure clock is correct on start, nothing else.

[Werner]

13 hours ago, dhanushx012 said:

I'm keen to help out with some scripting and get into more technical stuff. Can also edit docs etc. 

https://armbian.atlassian.net/projects/AR/issues/?filter=allissues&=

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

Feel free to dig through some open issues and address some

[qiurui]

I want to join

[Igor]

3 hours ago, qiurui said:

I want to join

 

Best way is to start here:
https://forum.armbian.com/staffapplications/

 

Welcome!