Jump to content

Weekly developers meetup

Igor

Event created by Igor

Community Calendar

Event details

 Share

This week's meeting topics:

 

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

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

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

 

The general goal of weekly meetings:

 

- To discuss the three (3) issues of the week

- Discussions will be documented to respective Jira tickets so they can be tracked

- Three (3) new issues will be selected from Jira for the next meeting

 

A weekly developers' meeting aims to coordinate the development of the build engine, continuous integration, operating system features, and low-level support. Meetings are hosted on Jitsi (Video), IRC, and Discord (Text). While we would prefer you attend on Jitsi when possible, we will also monitor text chat during the call for those unable to join Jitsi.
Please RSVP either way.

 

Do you want to participate or help in some way?

Meetings are focused on developers' top-level topics, and it's expected that they understand embedded software development, software testing, or operating system management. Knowledge of at least BASH & Python is expected in terms of programming languages.


Since meetings are held in public, any registered community member can join and listen. If you want to suggest issues for the next week, you have to be recognized Armbian contributor. If you want to become one, resolve at least one intermediate-level issue and tell us something about yourself. This is needed to communicate efficiently and to give you access to our organization infrastructure Jira, Github, hardware lab, and servers.

 

@Contributor/Maintainer

 

0
 Share

Recommended Comments

Igor
On 11/16/2023 at 2:17 AM, schwar3kat said:

Winter, Spring, Summer, Autumn.
This can only apply in northern hemisphere countries.  Southern hemisphere is the opposite months.

First quarter, second quarter, third quarter, fourth quarter are possible alternate options.


We forgot on you guys down there :)  Good catch!

 

Also good task for those who complain they are not contribution as they are not software developers.
https://armbian.atlassian.net/browse/AR-1933 

Link to comment
schwar3kat
7 hours ago, Igor said:

https://us06web.zoom.us/rec/share/_KNgbricrEDvO4WdkZGrso82cCs7bUxb1uvaUOzni4zI1FELDBTVQ30d97Px7t1n.in4hFwQ6IQEu8pzf

I watched this week's video, and have a question about Joey's configng presentation.
 

If my understanding is correct then the directory/folder that contains the script function determines the menu group, and the script header description determines the menu item wording.

How can we include/exclude a script in the menu based on a runtime condition, like it is possible in armbian config?  E.g. depending on a file or executable existing.

How can we include/exclude a script group in the menu based on a runtime condition like it is possible in armbian config?

1
Link to comment
Tearran


:) , Great point,  @Igor  Pointed out a probable solution to the concept, &  https://github.com/armbian/configng/blob/main/bin/armbian-configng#L25

On 12/6/2023 at 9:02 PM, schwar3kat said:

How can we include/exclude a script in the menu based on a runtime condition, like it is possible in armbian config?  E.g. depending on a file or executable existing.

How can we include/exclude a script group in the menu based on a runtime condition like it is possible in armbian config?

community direction is needed. Such as use cases for what to show or hide, and what to checks to make the determination.  @Igor  Pointed out a probable solution to the concept, Basic consept logic https://github.com/armbian/configng/blob/main/bin/armbian-configng#L25  

 

The current armbian-config has much of the said "runtime conditions" covered, To progress development, a generalized approach has been taken, keeping current armbian-config compatibility has been a priority.


As for general condition checking. There are a some working examples of approach. With some limitations. Arguably $args. :D Sorry, I mean "options". 

To progress a more focused approach development. Community direction is needed.  GIven my choice alone I would continue Focus on Developing ... ,  More accurately playing with a text editor and flat file UI UX elements, svg, html etc. for the project   

Link to comment
schwar3kat
On 12/8/2023 at 10:44 PM, Tearran said:

@Igor  Pointed out a probable solution to the concept, Basic consept logic https://github.com/armbian/configng/blob/main/bin/armbian-configng#L25  

 
@Tearran Bear in mind I'm not experienced with bash, so expect some ignorance 😄

Perhaps some kind of standard initialization function if it exists, could be triggered first as each script is parsed,  setting initialization variables could be included as a standard part of any function script.  And a similar menu folder initialization script could be included in any folder.

One of those variables could set visibility.  Another could set menu text, allowing dynamic menu text based on runtime requirements and possibly other options could be added if required.

Any logic could be used to set those variables.

To illustrate with an example of what I am imagining.  Maybe something like this:
(excuse my bash if it is bad or not feasible)
  

# @description Do something useless.
#
# @exitcode 0  If successful.
#
# @options none

# menu_init function triggered first by menu creation routines if it exists
function menu_init(){
    #
    # Only display menu option if internet connection is available
    #
    wget -q -t 1 --timeout=5 --spider http://github.com
    if [[ $? -ne 0 ]]; then
        menu_item=false
    else
        menu_item=true
    fi

    menu_text='Do something useful' # this could override the description as the menu text if it exists
}

function group::string() {s
    echo "Doing something"
    return 0
}

 

Link to comment
Tearran

@schwar3kat  Bear in mind you have clearly the advantage of specialised knowledge here.:D
Clearly proven by that pattern  😅 , it is brilliant. For one its set context for🤯.... before I get distracted again 😅
This does not seem to be the place to continue expanding. I am unsure!  Do you have collaborative insight you could share? Could you suggest a better place to expand on this topic? 

 

Link to comment
Igor
On 12/8/2023 at 10:44 AM, Tearran said:

keeping current armbian-config compatibility


From user perspective - it should function approximately the same. We need to come up with better code (style) as existing one, then upgrade and move further.

 

On 12/8/2023 at 10:44 AM, Tearran said:

Community direction is needed. 


For now, this community its me and @schwar3kat I am sure more ideas will come on the way ...  Yeah, lets continue this directly at PR.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept