Search the Community
Showing results for tags 'development' in content posted in Community Calendar.
Found 16 results
-
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
-
https://docs.armbian.com/Process_Release-Model/#agenda Is this list still valid? Supported: WIP Community supported where we could also look for re-enabling supported status. Criteria for Supported must be beneficial to the Armbian project Armbian team must confirm and agree upon all supported boards statuses a named individual as “maintainer” with GitHub ID must be preset in the BOARD_MAINTAINER within Board Configuration File a named individual must commit to providing “best effort” support for their SBC on the Armbian forums maintainer must participate in the Release Process maintainer must sign-off that device has been tested, is stable, and ready for release during release process maintainer must have physical access to the SBC they are supporting maintainer can operate under pseudonym but must reveal his identity to Armbian management maintainer should attend developers meetings held every Wednesday 7:00 PM CET when whole support burden is carried by maintainer and Armbian team, it will be labelled as “Pro bono” More here: https://docs.armbian.com/User-Guide_Board-Support-Rules/#criteria-for-supported Example of maintainer proposal: - add or remove board X from supported. Reason: its broken and I don't have time / I confirm it works, will monitor and collaborate ... - upgrade board X from WIP to supported. It works decently / well, I steal dealing with it, there is upstream support ... or remove as there is no progress, too many issues - board X from community section should become supported because ...
-
This week's meeting topics: 1. Check remaining 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 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.
-
This week's meeting topics: 1. Check remaining 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 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.
-
This week's meeting topics: 1. Check remaining 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 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.
-
This week's meeting topics: 1. Check remaining 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 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
-
This week's meeting topics: 1. Check remaining 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 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.
-
This week's meeting topics: 1. Check remaining 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 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
-
This week meeting topics: 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 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 The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. 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 you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
-
This week meeting topics: 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 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 The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. 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 you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
-
This week meeting topics: 1. Pre-release CI status check 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 The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. 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 you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
-
This week meeting topics: 1. Upcoming release 2. Security in GitHub actions 3. CI support 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 The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. 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 you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
-
This week meeting topics: 1. Progress of CI support 2. Security in GitHub actions 3. 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 The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. 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 you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
-
This week meeting topics: 1. Progress of CI support 2. Mechanism for rebuilding packages from sources 3. Misc 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 The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. 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 you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
-
This week meeting topics: 1. XML / JSON generation to support CI 2. Compilation of legacy configurations (Opi Zero2 legacy does not build) 3. Re-organise forums - Maintained / Unmaintained hardware 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 The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. 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 you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
-
This week meeting topics: 1. Redesign board support packages CLI & desktop 2. XML / JSON generation to support CI 3. Build framework 1st run configuration 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 The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. 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 you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
