BEGIN:VCALENDAR VERSION:2.0 PRODID:-//InvisionCommunity Events 4.7.23//EN METHOD:PUBLISH CALSCALE:GREGORIAN REFRESH-INTERVAL:PT15M X-PUBLISHED-TTL:PT15M X-WR-CALNAME:Community Calendar NAME:Community Calendar BEGIN:VTIMEZONE TZID:Europe/London TZURL:http://tzurl.org/zoneinfo/Europe/London X-LIC-LOCATION:Europe/London BEGIN:DAYLIGHT TZOFFSETFROM:+0000 TZOFFSETTO:+0100 TZNAME:BST DTSTART:20250330T020000Z RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0100 TZOFFSETTO:+0000 TZNAME:GMT DTSTART:20251026T020000Z RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU END:STANDARD END:VTIMEZONE BEGIN:VTIMEZONE TZID:Europe/London TZURL:http://tzurl.org/zoneinfo/Europe/London X-LIC-LOCATION:Europe/London BEGIN:DAYLIGHT TZOFFSETFROM:+0000 TZOFFSETTO:+0100 TZNAME:BST DTSTART:20240331T020000Z RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0100 TZOFFSETTO:+0000 TZNAME:GMT DTSTART:20241027T020000Z RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU END:STANDARD END:VTIMEZONE BEGIN:VTIMEZONE TZID:Europe/London TZURL:http://tzurl.org/zoneinfo/Europe/London X-LIC-LOCATION:Europe/London BEGIN:DAYLIGHT TZOFFSETFROM:+0000 TZOFFSETTO:+0100 TZNAME:BST DTSTART:20230326T020000Z RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0100 TZOFFSETTO:+0000 TZNAME:GMT DTSTART:20231029T020000Z RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU END:STANDARD END:VTIMEZONE BEGIN:VTIMEZONE TZID:Europe/London TZURL:http://tzurl.org/zoneinfo/Europe/London X-LIC-LOCATION:Europe/London BEGIN:DAYLIGHT TZOFFSETFROM:+0000 TZOFFSETTO:+0100 TZNAME:BST DTSTART:20220327T020000Z RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0100 TZOFFSETTO:+0000 TZNAME:GMT DTSTART:20221030T020000Z RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT SUMMARY:Release coordination DTSTAMP:20251103T172659Z SEQUENCE:0 UID:62-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n Agenda:\n\n\n\n  \n\n\n\n \n Review open blockers and c ritical priorities\n \n \n Maintainer status by board\n \n \n Label tria ge and deferrals to next release (26.02)\n \n \n Final checklist before f reeze\n \n\n\n\n  \n\n\n\n Meeting place: Discord ->\; Lounge\n\n DTSTART:20251108T150000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian Newsletter Coordination Meeting DTSTAMP:20250807T010633Z SEQUENCE:0 UID:59-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This meeting will be @ 11am EST\n\n\n\n All who want to c ontribute to the Newsletter are welcome.\n\n DTSTART:20250918T150000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian Newsletter Coordination Meeting #2 DTSTAMP:20250714T142602Z SEQUENCE:0 UID:58-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Michael Robinson":forums@mail.armbian.com DESCRIPTION:\n This meeting is open to anyone currently contributing or interested in helping shape the newsletter going forward.\n\n\n\n  \n\n\n \n Discussion Topics\n\n\n\n \n Strengthening the newsletter process and its impact  \n \n \n Expanding our contributor base (authors\, vendors\ , community voices)  \n \n \n Improving the flow of raw content from de velopers  \n \n \n Gathering better feedback from readers  \n \n \n Ensuring the publishing process runs smoothly\n \n\n\n\n  \n\n\n\n We're especially looking for:\n\n\n\n \n Fresh ideas to make the newsletter mo re useful and engaging  \n \n \n A volunteer to take on reviewing and approving the first draft before publication  \n \n\n\n\n  \n\n\n\n 📅 Meeting Details\n\n\n\n Location: Discord –>\; Armbian Server -&g t\; Lounge Channel\n\n Duration: ~45 minutes  \n\n  \n\n\n\n Looking fo rward to seeing you there!\n\n DTSTART:20250716T150000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian Newsletter Coordination Meeting DTSTAMP:20250624T181701Z SEQUENCE:0 UID:57-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Michael Robinson":forums@mail.armbian.com DESCRIPTION:\n This meeting is open to anyone currently contributing or interested in helping shape the newsletter going forward.\n\n\n\n  \n\n\n \n Discussion Topics\n\n\n\n \n Strengthening the newsletter process and its impact  \n \n \n Expanding our contributor base (authors\, vendors\ , community voices)  \n \n \n Improving the flow of raw content from de velopers  \n \n \n Gathering better feedback from readers  \n \n \n Ensuring the publishing process runs smoothly\n \n\n\n\n  \n\n\n\n We're especially looking for:\n\n\n\n \n Fresh ideas to make the newsletter mo re useful and engaging  \n \n \n A volunteer to take on reviewing and approving the first draft before publication  \n \n\n\n\n  \n\n\n\n 📅 Meeting Details\n\n\n\n Location: Discord –>\; Armbian Server -&g t\; Lounge Channel\n\n Duration: ~45 minutes  \n\n  \n\n\n\n Looking fo rward to seeing you there!\n\n DTSTART:20250702T150000Z END:VEVENT BEGIN:VEVENT SUMMARY:Release management DTSTAMP:20241019T171523Z SEQUENCE:0 UID:51-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n Armbian releases are complex problem and current ad-hoc r eleases are just a workaround. For doing it ideally we don't have resource and / or sufficient protocols.\n\n\n\n  \n\n\n\n https://us06web.zoom.us /j/85275202668\n\n DTSTART:20241109T150000Z DTEND:20241109T163000Z ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="SuperKali";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED: forums@mail.armbian.com ATTENDEE;CN="echatzip";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="katoomba";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian config development DTSTAMP:20241019T202606Z SEQUENCE:0 UID:53-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:For those that helps or wants to help here: https://github.c om/armbian/configng\n\n\n\nhttps://us06web.zoom.us/j/87331956802 DTSTART:20241024T180000Z DTEND:20241024T190000Z END:VEVENT BEGIN:VEVENT SUMMARY:QA DTSTAMP:20241009T083420Z SEQUENCE:0 UID:50-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:- forum reorganisation DTSTART:20241019T140000Z DTEND:20241019T150000Z ATTENDEE;CN="SuperKali";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED: forums@mail.armbian.com ATTENDEE;CN="33335";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:foru ms@mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="sfx2000";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian documentation follow-up DTSTAMP:20240106T043610Z SEQUENCE:0 UID:47-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="didierjoomun":forums@mail.armbian.com DESCRIPTION:\n Didier J. will be leading this meeting and sharing progre ss on the documentation tasks. Anyone interested in the documentation proc ess and content can join this meeting!\n\n DTSTART:20240410T073000Z DTEND:20240410T080000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="didierjoomun";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPT ED:forums@mail.armbian.com ATTENDEE;CN="brentr";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="Gunjan Gupta";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPT ED:forums@mail.armbian.com ATTENDEE;CN="Ragavendra Nagraj";CUTYPE=INDIVIDUAL;PARTSTAT=A CCEPTED:forums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230618T205615Z SEQUENCE:0 UID:46-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week's meeting topics:\n\n\n\n  \n\n\n\n - Check re maining Jira tickets https://www.armbian.com/participate/\n\n\n\n - Revie w issues https://github.com/armbian/build/issues\n\n\n\n - Review pull re quests https://github.com/armbian/build/pulls\n\n\n\n  \n\n\n\n The gene ral goal of weekly meetings:\n\n\n\n  \n\n\n\n - To discuss the three (3) issues of the week\n\n\n\n - Discussions will be documented to respecti ve Jira tickets so they can be tracked\n\n\n\n - Three (3) new issues will be selected from Jira for the next meeting\n\n\n\n  \n\n\n\n A weekly developers' meeting aims to coordinate the development of the build engine \, continuous integration\, operating system features\, and low-level supp ort. Meetings are hosted on Jitsi (Video)\, IRC\, and Discord (Text). Whi le we would prefer you attend on Jitsi when possible\, we will also monito r text chat during the call for those unable to join Jitsi.\n\n Please RSV P either way.\n\n\n\n  \n\n\n\n Do you want to participate or help in so me way?\n\n\n\n Meetings are focused on developers' top-level topics\, and it's expected that they understand embedded software development\, softwa re testing\, or operating system management. Knowledge of at least BASH &a mp\; Python is expected in terms of programming languages.\n\n\n\n \n\n Si nce meetings are held in public\, any registered community member can joi n 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\, reso lve at least one intermediate-level issue and tell us something about yo urself. This is needed to communicate efficiently and to give you access to our organization infrastructure Jira\, Github\, hardware lab\, and serv ers.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n\n\n  \n\n DTSTART:20230712T170000Z ATTENDEE;CN="Gunjan Gupta";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPT ED:forums@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="echatzip";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="pzc";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forums @mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 24.02 Kereru Release planning DTSTAMP:20240119T095828Z SEQUENCE:0 UID:48-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n https://docs.armbian.com/Process_Release-Model/#agenda\n\ n\n\n  \n\n\n\n Is this list still valid?\n\n \n\n Supported:\n\n\n\n  \ n\n\n\n \n Spoiler\n \n\n \n \"Banana Pi CM4IO\"\n\"Banana Pi M2Pro\"\n\ "Banana Pi M2S\"\n\"Banana Pi M5\"\n\"BigTreeTech CB1\"\n\"JetHub D1\"\n\" JetHub H1\"\n\"Khadas Edge2\"\n\"Khadas VIM1\"\n\"Khadas VIM1S\" # don't c onfuse with VIM1 (S905X)\n\"Khadas VIM2\"\n\"Khadas VIM3\"\n\"Khadas VIM3L \"\n\"Khadas VIM4\"\n\"La Frite\"\n\"Le potato\"\n\"NanoPi Duo2\"\n\"NanoP i Duo\"\n\"NanoPi R4S\"\n\"NanoPi R6S\"\n\"Odroid C2\"\n\"Odroid M1\"\n\"O droid N2\"\n\"Odroid XU4\"\n\"OLIMEX Teres A64\"\n\"OneCloud\"\n\"Orange P i 4 LTS\"\n\"Orange Pi 5\"\n\"Orange Pi 5 Plus\"\n\"Orange Pi One\"\n\"Ora nge Pi Prime\"\n\"Orange Pi R1\"\n\"Orange Pi R1 Plus LTS\"\n\"Orange Pi Z ero2\"\n\"Orange Pi Zero\"\n\"Orange Pi Zero Plus\"\n\"Pine64\"\n\"Pineboo k Pro\"\n\"Radxa Zero\"\n\"Renegade\"\n\"Rock 3A\"\n\"Rock 5B\"\n\"Rockpi 4A\"\n\"Rockpi E\"\n\"Rockpi S\"\n\"RockPro 64\"\n\"Raspberry Pi 4\"\n\"Ra spberry Pi 5\"\n\"SK-AM62B\"\n\"SK-AM64B\"\n\"SK-TDA4VM\"\n\"Tinker Board\ "\n\"Tritium\"\n\"Tritium\"\n\"UEFI arm64\"\n\"UEFI x86\"\n\"Xiaomi Elish\ "\n\n \n  \n \n \n\n\n\n  \n\n\n\n WIP\n\n\n\n  \n\n\n\n \n Spoile r\n \n\n \n \"FxBlox RK1\"\n\"Mekotronics R58 MiniPC\"\n\"Mekotronics R58 X-4G\"\n\"Mekotronics R58X\"\n\"Mixtile Blade 3\"\n\"NanoPC T6\"\n\"NanoPi R5S\"\n\"Orange Pi Zero3\"\n\"uefi-arm64\"\n\"uefi-x86\"\n\"Radxa E25\"\n \"Radxa Zero 2\"\n\"Rock 5A\"\n\"ThinkPad X13s\"\n\"Windows Dev Kit 2023\" \n\n \n  \n \n \n\n\n\n  \n\n\n\n Community supported where we could also look for re-enabling supported status.\n\n\n\n  \n\n\n\n \n Spoile r\n \n\n \n \"ArmSoM Sige7\"\n\"ArmSoM W3\"\n\"Banana Pi\"\n\"Banana Pi M 1+\"\n\"Banana Pi M2+\"\n\"Banana Pi M2 Ultra\"\n\"Banana Pi M2 Zero\"\n\" Banana Pi M3\"\n\"Banana Pi M64\"\n\"Banana Pi Pro\"\n\"Banana Pi R2\"\n\" Banana Pi R2 Pro\"\n\"BeagleV\"\n\"Clearfog Base\"\n\"Clearfog Pro\"\n\"Cl ockworkpi A06\"\n\"Cubieboard 2\"\n\"Cubieboard 4\"\n\"Cubieboard 1\"\n\"C ubietruck\"\n\"Cubietruck+\"\n\"Cubox i2eX/i4\"\n\"Espressobin\"\n\"Firefl y RK3399\"\n\"Helios4\"\n\"Helios64\"\n\"HiKey 960\"\n\"HinLink H28k\"\n\" Hinlink H88K\"\n\"HinLink HT2\"\n\"Indiedroid Nova\"\n\"Inovato Quadra\"\n \"Jetson Nano\"\n\"Khadas Edge\"\n\"LicheePi 4A\"\n\"A20 OLinuXino Lime 2\ "\n\"A33 OLinuXino\"\n\"A64 OLinuXino\"\n\"A20 OLinuXino Lime\"\n\"Macchia tobin DS\"\n\"Mangopi M28K\"\n\"Mekotronics R58X-Pro\"\n\"Mele A1000\"\n\" A20 OLinuXino Micro\"\n\"MK808C\"\n\"NanoPC T4\"\n\"NanoPi A64\"\n\"NanoPi Air\"\n\"NanoPi K1 Plus\"\n\"NanoPi K2\"\n\"NanoPi M4\"\n\"NanoPi M4V2\"\ n\"NanoPi Neo 2 Black\"\n\"NanoPi Neo 2\"\n\"NanoPi Neo 3\"\n\"NanoPi Neo 4\"\n\"NanoPi Neo Core 2\"\n\"NanoPi Neo\"\n\"NanoPi Neo Plus 2\"\n\"NanoP i R1\"\n\"NanoPi R1S H5\"\n\"Nanopi R2C\"\n\"Nanopi R2S\"\n\"NanoPi R4SE\" \n\"NanoPi R5C\"\n\"Odroid C4\"\n\"Odroid HC4\"\n\"Odroid N2L\"\n\"Olimex A13 SOM\"\n\"Orange Pi 2\"\n\"orangepi3b\"\n\"Orange Pi 3\"\n\"Orange Pi 3 LTS\"\n\"Orange Pi 4\"\n\"Orange Pi Lite 2\"\n\"Orange Pi Lite\"\n\"Orang e Pi One+\"\n\"Orange Pi PC2\"\n\"Orange Pi PC\"\n\"Orange Pi PC +\"\n\"Or ange Pi+ 2E\"\n\"Orange Pi+\"\n\"Orange Pi R1 Plus\"\n\"Orange Pi RK3399\" \n\"Orange Pi Win\"\n\"Orange Pi Zero Plus 2\"\n\"Orange Pi Zero Plus 2\"\ n\"panther-x2\"\n\"pcDuino 3\"\n\"SoPine A64\"\n\"Pinebook A64\"\n\"Pine C ube\"\n\"Pine H64 model B\"\n\"Pine H64\"\n\"Pine Quartz64 A\"\n\"Pine Qua rtz64 B\"\n\"Iagent Recore\"\n\"Rock 4SE\"\n\"Radxa CM5\"\n\"Rock 64\"\n\" Rockpi 4B\"\n\"Rockpi 4B+\"\n\"Rockpi 4C\"\n\"Rockpi 4C+\"\n\"Rockpi N10\" \n\"Renegade Elite\"\n\"Star64\"\n\"Station M1\"\n\"Station M2\"\n\"Statio n M3\"\n\"Station P1\"\n\"Station P2\"\n\"Tinker Board 2\"\n\"Tinker Edge R\"\n\"Udoo\"\n\"UEFI riscv64\"\n\"Unleashed\"\n\"Unmatched\"\n\"VisionFiv e2\"\n\"VisionFive\"\n\"WSL2 arm64\"\n\"WSL2 x86\"\n\"ZeroPi\"\n\"aml-s9xx -box\"\n\"Beelink X2\"\n\"JP-TVbox-3566\"\n\"rk322x-box\"\n\"RK3318 Box\"\ n\"Sunvell R69\"\n\"Tanix TX6\"\n\"XT Q8L V10\"\n\"Z28 PRO\"\n\n \n  \ n \n \n\n\n\n  \n\n\n\n Criteria for Supported\n\n\n\n  \n\n\n\n \n mu st be beneficial to the Armbian project\n \n \n Armbian team must confirm and agree upon all supported boards statuses\n \n \n a named individual as “maintainer” with GitHub ID must be preset in the BOARD_MAINTAINER within Board Configuration File\n \n \n a named individual must commit t o providing “best effort” support for their SBC on the Armbian forums\ n \n \n maintainer must participate in the Release Process\n \n \n main tainer must sign-off that device has been tested\, is stable\, and ready f or release during release process\n \n \n maintainer must have physical a ccess to the SBC they are supporting\n \n \n maintainer can operate under pseudonym but must reveal his identity to Armbian management\n \n \n m aintainer should attend developers meetings held every Wednesday 7:00 PM CET\n \n \n when whole support burden is carried by maintainer and Armbi an team\, it will be labelled as “Pro bono”\n \n\n\n\n  \n\n\n\n More here: https://docs.armbian.com/User-Guide_Board-Support-Rules/#criteria- for-supported\n\n\n\n  \n\n\n\n Example of maintainer proposal:\n\n\n\n - add or remove board X from supported. Reason:  its broken and I don't ha ve time / I confirm it works\, will monitor and collaborate ...\n\n\n\n - 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 p rogress\, too many issues\n\n\n\n - board X from community section should become supported because ...\n\n DTSTART:20240210T150000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="jock";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230618T205420Z SEQUENCE:0 UID:43-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="skorupion":forums@mail.armbian.com DESCRIPTION:\n  \n\n\n\n This week's meeting topics:\n\n\n\n  \n\n\n\n 1. Check remaining Jira tickets https://www.armbian.com/participate/\n\n \n\n 2. Review issues https://github.com/armbian/build/issues\n\n\n\n 3. Review pull requests https://github.com/armbian/build/pulls\n\n\n\n  \n\ n\n\n  \n\n\n\n The general goal of weekly meetings:\n\n\n\n  \n\n\n\n - To discuss the three (3) issues of the week\n\n\n\n - Discussions will b e documented to respective Jira tickets so they can be tracked\n\n\n\n - Three (3) new issues will be selected from Jira for the next meeting\n\n \n\n  \n\n\n\n A weekly developers' meeting aims to coordinate the develo pment of the build engine\, continuous integration\, operating system feat ures\, and low-level support. Meetings are hosted on Jitsi (Video)\, IRC\ , and Discord (Text). While we would prefer you attend on Jitsi when possi ble\, we will also monitor text chat during the call for those unable to j oin Jitsi.\n\n Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to p articipate or help in some way?\n\n\n\n Meetings are focused on developer s' top-level topics\, and it's expected that they understand embedded soft ware development\, software testing\, or operating system management. Know ledge of at least BASH &\; Python is expected in terms of programming l anguages.\n\n\n\n \n\n 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 w ant to become one\, resolve at least one intermediate-level issue and t ell 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.\n\n\n\n  \n\n DTSTART:20230621T160000Z ATTENDEE;CN="Gunjan Gupta";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPT ED:forums@mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230618T205510Z SEQUENCE:0 UID:45-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="skorupion":forums@mail.armbian.com DESCRIPTION:\n  \n\n\n\n This week's meeting topics:\n\n\n\n  \n\n\n\n 1. Check remaining Jira tickets https://www.armbian.com/participate/\n\n \n\n 2. Review issues https://github.com/armbian/build/issues\n\n\n\n 3. Review pull requests https://github.com/armbian/build/pulls\n\n\n\n  \n\ n\n\n  \n\n\n\n The general goal of weekly meetings:\n\n\n\n  \n\n\n\n - To discuss the three (3) issues of the week\n\n\n\n - Discussions will b e documented to respective Jira tickets so they can be tracked\n\n\n\n - Three (3) new issues will be selected from Jira for the next meeting\n\n \n\n  \n\n\n\n A weekly developers' meeting aims to coordinate the develo pment of the build engine\, continuous integration\, operating system feat ures\, and low-level support. Meetings are hosted on Jitsi (Video)\, IRC\ , and Discord (Text). While we would prefer you attend on Jitsi when possi ble\, we will also monitor text chat during the call for those unable to j oin Jitsi.\n\n Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to p articipate or help in some way?\n\n\n\n Meetings are focused on developer s' top-level topics\, and it's expected that they understand embedded soft ware development\, software testing\, or operating system management. Know ledge of at least BASH &\; Python is expected in terms of programming l anguages.\n\n\n\n \n\n 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 w ant to become one\, resolve at least one intermediate-level issue and t ell 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.\n\n\n\n  \n\n DTSTART:20230705T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230618T205452Z SEQUENCE:0 UID:44-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="skorupion":forums@mail.armbian.com DESCRIPTION:\n  \n\n\n\n This week's meeting topics:\n\n\n\n  \n\n\n\n 1. Check remaining Jira tickets https://www.armbian.com/participate/\n\n \n\n 2. Review issues https://github.com/armbian/build/issues\n\n\n\n 3. Review pull requests https://github.com/armbian/build/pulls\n\n\n\n  \n\ n\n\n  \n\n\n\n The general goal of weekly meetings:\n\n\n\n  \n\n\n\n - To discuss the three (3) issues of the week\n\n\n\n - Discussions will b e documented to respective Jira tickets so they can be tracked\n\n\n\n - Three (3) new issues will be selected from Jira for the next meeting\n\n \n\n  \n\n\n\n A weekly developers' meeting aims to coordinate the develo pment of the build engine\, continuous integration\, operating system feat ures\, and low-level support. Meetings are hosted on Jitsi (Video)\, IRC\ , and Discord (Text). While we would prefer you attend on Jitsi when possi ble\, we will also monitor text chat during the call for those unable to j oin Jitsi.\n\n Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to p articipate or help in some way?\n\n\n\n Meetings are focused on developer s' top-level topics\, and it's expected that they understand embedded soft ware development\, software testing\, or operating system management. Know ledge of at least BASH &\; Python is expected in terms of programming l anguages.\n\n\n\n \n\n 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 w ant to become one\, resolve at least one intermediate-level issue and t ell 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.\n\n\n\n  \n\n DTSTART:20230628T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="Julia Longtin";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEP TED:forums@mail.armbian.com ATTENDEE;CN="Gunjan Gupta";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPT ED:forums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230614T154852Z SEQUENCE:0 UID:42-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week's meeting topics:\n\n\n\n  \n\n\n\n 1. Check r emaining Jira tickets https://www.armbian.com/participate/\n\n\n\n 2. Rev iew issues https://github.com/armbian/build/issues\n\n\n\n 3. Review pull requests https://github.com/armbian/build/pulls\n\n\n\n  \n\n\n\n  \n\ n\n\n The general goal of weekly meetings:\n\n\n\n  \n\n\n\n - To discuss the three (3) issues of the week\n\n\n\n - Discussions will be documente d to respective Jira tickets so they can be tracked\n\n\n\n - Three (3) n ew issues will be selected from Jira for the next meeting\n\n\n\n  \n\n \n\n A weekly developers' meeting aims to coordinate the development of th e build engine\, continuous integration\, operating system features\, and low-level support. Meetings are hosted on Jitsi (Video)\, IRC\, and Disco rd (Text). While we would prefer you attend on Jitsi when possible\, we wi ll also monitor text chat during the call for those unable to join Jitsi.\ n\n Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n\n\n\n Meetings are focused on developers' top-leve l topics\, and it's expected that they understand embedded software develo pment\, software testing\, or operating system management. Knowledge of at least BASH &\; Python is expected in terms of programming languages.\n \n\n\n \n\n Since meetings are held in public\, any registered community member can join and listen. If you want to suggest issues for the next we ek\, you have to be recognized Armbian contributor. If you want to beco me one\, resolve at least one intermediate-level issue and tell us some thing about yourself. This is needed to communicate efficiently and to gi ve you access to our organization infrastructure Jira\, Github\, hardware lab\, and servers.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230614T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="Gunjan Gupta";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPT ED:forums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian infra meeting DTSTAMP:20230605T213819Z SEQUENCE:0 UID:41-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Determine infra related actions for next 6 to 12 months DTSTART:20230610T160000Z DTEND:20230610T170000Z END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230604T151344Z SEQUENCE:0 UID:40-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="skorupion":forums@mail.armbian.com DESCRIPTION:\n This week's meeting topics:\n\n\n\n  \n\n\n\n 1. Check r emaining Jira tickets https://www.armbian.com/participate/\n\n\n\n 2. Rev iew issues https://github.com/armbian/build/issues\n\n\n\n 3. Review pull requests https://github.com/armbian/build/pulls\n\n\n\n  \n\n\n\n  \n\ n\n\n The general goal of weekly meetings:\n\n\n\n  \n\n\n\n - To discuss the three (3) issues of the week\n\n\n\n - Discussions will be documente d to respective Jira tickets so they can be tracked\n\n\n\n - Three (3) n ew issues will be selected from Jira for the next meeting\n\n\n\n  \n\n \n\n A weekly developers' meeting aims to coordinate the development of th e build engine\, continuous integration\, operating system features\, and low-level support. Meetings are hosted on Jitsi (Video)\, IRC\, and Disco rd (Text). While we would prefer you attend on Jitsi when possible\, we wi ll also monitor text chat during the call for those unable to join Jitsi.\ n\n Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n\n\n\n Meetings are focused on developers' top-leve l topics\, and it's expected that they understand embedded software develo pment\, software testing\, or operating system management. Knowledge of at least BASH &\; Python is expected in terms of programming languages.\n \n\n\n \n\n Since meetings are held in public\, any registered community member can join and listen. If you want to suggest issues for the next we ek\, you have to be recognized Armbian contributor. If you want to beco me one\, resolve at least one intermediate-level issue and tell us some thing about yourself. This is needed to communicate efficiently and to gi ve you access to our organization infrastructure Jira\, Github\, hardware lab\, and servers.\n\n DTSTART:20230607T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="Gunjan Gupta";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPT ED:forums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230524T200357Z SEQUENCE:0 UID:39-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="skorupion":forums@mail.armbian.com DESCRIPTION:\n This week's meeting topics:\n\n\n\n  \n\n\n\n 1. Check r emaining Jira tickets https://www.armbian.com/participate/\n\n\n\n 2. Rev iew issues https://github.com/armbian/build/issues\n\n\n\n 3. Review pull requests https://github.com/armbian/build/pulls\n\n\n\n  \n\n\n\n  \n\ n\n\n The general goal of weekly meetings:\n\n\n\n  \n\n\n\n - To discuss the three (3) issues of the week\n\n\n\n - Discussions will be documente d to respective Jira tickets so they can be tracked\n\n\n\n - Three (3) n ew issues will be selected from Jira for the next meeting\n\n\n\n  \n\n\ n\n A weekly developers' meeting aims to coordinate the development of the build engine\, continuous integration\, operating system features\, and l ow-level support. Meetings are hosted on Jitsi (Video)\, IRC\, and Discor d (Text). While we would prefer you attend on Jitsi when possible\, we wil l also monitor text chat during the call for those unable to join Jitsi.\n \n Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to participate o r help in some way?\n\n\n\n Meetings are focused on developers' top-level topics\, and it's expected that they understand embedded software develop ment\, software testing\, or operating system management. Knowledge of at least BASH &\; Python is expected in terms of programming languages.\n\ n\n\n \n\n Since meetings are held in public\, any registered community me mber 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 o ne\, 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.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230531T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230523T112609Z SEQUENCE:0 UID:38-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="skorupion":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Check rem aining from Jira tickets https://www.armbian.com/participate/\n\n\n\n 2. Review issues https://github.com/armbian/build/issues\n\n\n\n 3. Review p ull requests https://github.com/armbian/build/pulls\n\n\n\n  \n\n\n\n   \n\n\n\n General goal of weekly meetings:\n\n\n\n  \n\n\n\n \n To discus s the three (3) issues of the week\n \n \n Discussions will be documente d to respective Jira tickets so they can be tracked\n \n \n Three (3) ne w issues will be selected from Jira for the next meeting\n \n\n\n\n  \n\ n\n\n The purpose of a weekly developers meeting is to coordinate developm ent of the build engine\, continuous integration\, operating system featur es 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 unab le to join Zoom.  Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n\n\n\n Meetings are focused in devel opers 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 expec ted.\n\n\n\n \n\n Since meetings are held in public\, any registered commu nity member can join and listen. If you want to suggest issues for the nex t week\, you have to be recognized Armbian contributor. If you want to b ecome one\, resolve at least one intermediate level issue and tell us som ething about you. This is needed to efficiently communicate and to give y ou access to our organisation infrastructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230524T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="skorupion";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED: forums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230514T115505Z SEQUENCE:0 UID:37-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Check rem aining from Jira tickets https://www.armbian.com/participate/\n\n\n\n 2. Review issues https://github.com/armbian/build/issues\n\n\n\n 3. Review p ull requests https://github.com/armbian/build/pulls\n\n\n\n  \n\n\n\n   \n\n\n\n General goal of weekly meetings:\n\n\n\n  \n\n\n\n \n To discus s the three (3) issues of the week\n \n \n Discussions will be documente d to respective Jira tickets so they can be tracked\n \n \n Three (3) ne w issues will be selected from Jira for the next meeting\n \n\n\n\n  \n\ n\n\n The purpose of a weekly developers meeting is to coordinate developm ent of the build engine\, continuous integration\, operating system featur es 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 unab le to join Zoom.  Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n\n\n\n Meetings are focused in devel opers 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 expec ted.\n\n\n\n \n\n Since meetings are held in public\, any registered commu nity member can join and listen. If you want to suggest issues for the nex t week\, you have to be recognized Armbian contributor. If you want to b ecome one\, resolve at least one intermediate level issue and tell us som ething about you. This is needed to efficiently communicate and to give y ou access to our organisation infrastructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230519T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230510T153553Z SEQUENCE:0 UID:36-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Pre-relea se CI status check\n\n\n\n  \n\n\n\n  \n\n\n\n General goal of weekly me etings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week \n \n \n Discussions will be documented to respective Jira tickets so t hey can be tracked\n \n \n Three (3) new issues will be selected from Jir a for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly deve lopers meeting is to coordinate development of the build engine\, continuo us integration\, operating system features and low level support. Meeting s 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 eit her way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some wa y?\n\n\n\n Meetings are focused in developers top level topics and its exp ected that understand embedded software development\, software testings or operating system management. In term of programming languages\, knowledge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings a re held in public\, any registered community member can join and listen. I f you want to suggest issues for the next week\, you have to be recognize d Armbian contributor. If you want to become one\, resolve at least one i ntermediate level issue and tell us something about you. This is needed t o efficiently communicate and to give you access to our organisation infr astructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @C ontributor/Maintainer\n\n DTSTART:20230510T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230425T175450Z SEQUENCE:0 UID:35-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Upcoming release\n\n\n\n 2. Security in GitHub actions\n\n\n\n 3. CI support\n\n\n\ n  \n\n\n\n  \n\n\n\n General goal of weekly meetings:\n\n\n\n  \n\n\n\ n \n To discuss the three (3) issues of the week\n \n \n Discussions wi ll be documented to respective Jira tickets so they can be tracked\n \n \ n Three (3) new issues will be selected from Jira for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly developers meeting is to coor dinate development of the build engine\, continuous integration\, operatin g system features and low level support. Meetings are hosted located on Z oom (Video) and IRC and Discord (Text). While  we would prefer you atten d on Zoom when possibly\, we  will also monitor text chat during the call for those unable to join Zoom.  Please RSVP either way.\n\n\n\n  \n\n\n \n Do you want to participate or help in some way?\n\n\n\n Meetings are f ocused in developers top level topics and its expected that understand emb edded software development\, software testings or operating system managem ent. In term of programming languages\, knowledge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings are held in public\, any r egistered community member can join and listen. If you want to suggest iss ues for the next week\, you have to be recognized Armbian contributor. I f 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.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230503T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="SteeMan";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230413T090522Z SEQUENCE:0 UID:34-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Progress of CI support\n\n\n\n 2. Security in GitHub actions\n\n\n\n 3. \n\n\n\n  \n\n\n\n  \n\n\n\n General goal of weekly meetings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions will be documented to respective Jira tickets so they can be tracked\n \n \n Three (3) new issues will be selected from Jira for the next meeting\n \ n\n\n\n  \n\n\n\n The purpose of a weekly developers meeting is to coordi nate development of the build engine\, continuous integration\, operating system features and low level support. Meetings are hosted located on Zoo m (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 f or those unable to join Zoom.  Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n\n\n\n Meetings are foc used in developers top level topics and its expected that understand embed ded software development\, software testings or operating system managemen t. In term of programming languages\, knowledge of at least BASH &\; Py thon is expected.\n\n\n\n \n\n Since meetings are held in public\, any reg istered community member can join and listen. If you want to suggest issue s for the next week\, you have to be recognized Armbian contributor. If you want to become one\, resolve at least one intermediate level issue an d tell us something about you. This is needed to efficiently communicate a nd to give you access to our organisation infrastructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230419T160000Z ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230405T194714Z SEQUENCE:0 UID:33-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Progress of CI support\n\n\n\n 2. Mechanism for rebuilding packages from sources  \n\n\n\n 3. Misc\n\n\n\n  \n\n\n\n  \n\n\n\n General goal of weekly meet ings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions will be documented to respective Jira tickets so the y can be tracked\n \n \n Three (3) new issues will be selected from Jira  for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly devel opers meeting is to coordinate development of the build engine\, continuou s integration\, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While  w e would prefer you attend on Zoom when possibly\, we  will also monitor t ext chat during the call for those unable to join Zoom.  Please RSVP eith er way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way ?\n\n\n\n Meetings are focused in developers top level topics and its expe cted that understand embedded software development\, software testings or operating system management. In term of programming languages\, knowledge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings ar e 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 recognize d Armbian contributor. If you want to become one\, resolve at least one i ntermediate level issue and tell us something about you. This is needed t o efficiently communicate and to give you access to our organisation infr astructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @C ontributor/Maintainer\n\n DTSTART:20230412T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230404T054646Z SEQUENCE:0 UID:32-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. XML / JS ON generation to support CI\n\n\n\n 2. Compilation of legacy configuration s (Opi Zero2 legacy does not build)\n\n\n\n 3. Re-organise forums - Maint ained / Unmaintained hardware\n\n\n\n  \n\n\n\n  \n\n\n\n General goal o f weekly meetings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions will be documented to respective Jira t ickets so they can be tracked\n \n \n Three (3) new issues will be select ed from Jira for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly developers meeting is to coordinate development of the build engine \, continuous integration\, operating system features and low level suppor t. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text ). While  we would prefer you attend on Zoom when possibly\, we  will al so monitor text chat during the call for those unable to join Zoom.  Plea se RSVP either way.\n\n\n\n  \n\n\n\n Do you want to participate or help  in some way?\n\n\n\n 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.\n\n\n\n \n\n Sinc e meetings are held in public\, any registered community member can join a nd listen. If you want to suggest issues for the next week\, you have to b e 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 organ isation infrastructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230405T170000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230328T180557Z SEQUENCE:0 UID:31-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Redesign board support packages CLI &\; desktop\n\n\n\n 2. XML / JSON generatio n to support CI\n\n\n\n 3. Build framework 1st run configuration\n\n\n\n  \n\n\n\n  \n\n\n\n General goal of weekly meetings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions wil l be documented to respective Jira tickets so they can be tracked\n \n \n Three (3) new issues will be selected from Jira for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly developers meeting is to coord inate development of the build engine\, continuous integration\, operating system features and low level support. Meetings are hosted located on Zo om (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.\n\n\n\n  \n\n\n\ n Do you want to participate or help in some way?\n\n\n\n Meetings are fo cused in developers top level topics and its expected that understand embe dded software development\, software testings or operating system manageme nt. In term of programming languages\, knowledge of at least BASH &\; P ython is expected.\n\n\n\n \n\n Since meetings are held in public\, any re gistered community member can join and listen. If you want to suggest issu es for the next week\, you have to be recognized Armbian contributor. If you want to become one\, resolve at least one intermediate level issue a nd 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.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230329T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230320T195632Z SEQUENCE:0 UID:30-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Identify critical problems\n\n\n\n \n finish caching for other packages\n \n\n\n\n 2. Build framework 1st run configuration\n\n\n\n 3. How to enable docume ntation updating?\n\n\n\n  \n\n\n\n  \n\n\n\n General goal of weekly mee tings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\ n \n \n Discussions will be documented to respective Jira tickets so th ey can be tracked\n \n \n Three (3) new issues will be selected from Jira  for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly devel opers meeting is to coordinate development of the build engine\, continuou s integration\, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While  w e would prefer you attend on Zoom when possibly\, we  will also monitor t ext chat during the call for those unable to join Zoom.  Please RSVP eith er way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way ?\n\n\n\n Meetings are focused in developers top level topics and its expe cted that understand embedded software development\, software testings or operating system management. In term of programming languages\, knowledge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings ar e 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 recognize d Armbian contributor. If you want to become one\, resolve at least one i ntermediate level issue and tell us something about you. This is needed t o efficiently communicate and to give you access to our organisation infr astructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @C ontributor/Maintainer\n\n DTSTART:20230322T170000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="Yakov";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:foru ms@mail.armbian.com ATTENDEE;CN="SteeMan";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Release Planning DTSTAMP:20221117T162934Z SEQUENCE:0 UID:6-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Release Planning\nIRC DTSTART:20230401T150000Z DTEND:20230401T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="Albert Xiao";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTE D:forums@mail.armbian.com ATTENDEE;CN="brentr";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="ALIGMSTEN";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED: forums@mail.armbian.com ATTENDEE;CN="joshaspinall";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPT ED:forums@mail.armbian.com ATTENDEE;CN="Heisath";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="jock";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230313T195725Z SEQUENCE:0 UID:29-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Changes o n \"about Armbian\"\n\n\n\n \n maintainers\, developers and support staff are in the database\n \n \n we have POC and scripts for pooling data\n \ n \n how / how much to present this data\, move tables from documentation \n \n\n\n\n  \n\n\n\n 2. Armbian versioning and repository management\n\n \n\n\n\n\n 3. Build framework 1st run configuration\n\n\n\n\n\n\n  \n\n\n \n Different starting hour!!!\n\n\n\n  \n\n\n\n General goal of weekly me etings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week \n \n \n Discussions will be documented to respective Jira tickets so t hey can be tracked\n \n \n Three (3) new issues will be selected from Jir a for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly deve lopers meeting is to coordinate development of the build engine\, continuo us integration\, operating system features and low level support. Meeting s 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 eit her way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some wa y?\n\n\n\n Meetings are focused in developers top level topics and its exp ected that understand embedded software development\, software testings or operating system management. In term of programming languages\, knowledge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings a re held in public\, any registered community member can join and listen. I f you want to suggest issues for the next week\, you have to be recognize d Armbian contributor. If you want to become one\, resolve at least one i ntermediate level issue and tell us something about you. This is needed t o efficiently communicate and to give you access to our organisation infr astructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @C ontributor/Maintainer\n\n DTSTART:20230315T170000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="Yakov";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:foru ms@mail.armbian.com ATTENDEE;CN="SteeMan";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230301T192242Z SEQUENCE:0 UID:28-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Armbian f ramework after the merge\n\n\n\n \n revisiting bugs\n \n \n identify lar ger chunks of work\n \n\n\n\n 2. Changes on \"about Armbian\"\n\n\n\n \n maintainers\, developers and support staff are in the database\n \n \n we have POC and scripts for pooling data\n \n \n how / how much to present this data\, move tables from documentation\n \n\n\n\n 3.\n\n\n\n\n\n\n  \ n\n\n\n Different starting hour!!!\n\n\n\n  \n\n\n\n General goal of week ly meetings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions will be documented to respective Jira tickets so they can be tracked\n \n \n Three (3) new issues will be selected fro m Jira for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly developers meeting is to coordinate development of the build engine\, con tinuous integration\, operating system features and low level support. Me etings are hosted located on Zoom (Video) and IRC and Discord (Text). Whi le  we would prefer you attend on Zoom when possibly\, we  will also mon itor text chat during the call for those unable to join Zoom.  Please RSV P either way.\n\n\n\n  \n\n\n\n Do you want to participate or help in so me way?\n\n\n\n Meetings are focused in developers top level topics and it s expected that understand embedded software development\, software testin gs or operating system management. In term of programming languages\, know ledge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meeti ngs are held in public\, any registered community member can join and list en. If you want to suggest issues for the next week\, you have to be reco gnized Armbian contributor. If you want to become one\, resolve at least one intermediate level issue and tell us something about you. This is nee ded to efficiently communicate and to give you access to our organisation infrastructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n \n @Contributor/Maintainer\n\n DTSTART:20230308T170000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="Yakov";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:foru ms@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230223T232103Z SEQUENCE:0 UID:27-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Armbian f ramework after the merge\n\n\n\n \n revisiting bugs\n \n \n identify lar ger chunks of work\n \n\n\n\n 2. Moving development related topics to GitH ub\n\n\n\n \n how to start?\n \n\n\n\n 3. Changes on \"about Armbian\"\n\ n\n\n \n maintainers\, developers and support staff are in the database\n \n \n we have POC and scripts for pooling data\n \n \n how / how much t o present this data\, move tables from documentation\n \n\n\n\n  \n\n\n\n Different starting hour!!!\n\n\n\n  \n\n\n\n General goal of weekly meet ings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions will be documented to respective Jira tickets so the y can be tracked\n \n \n Three (3) new issues will be selected from Jira  for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly devel opers meeting is to coordinate development of the build engine\, continuou s integration\, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While  w e would prefer you attend on Zoom when possibly\, we  will also monitor t ext chat during the call for those unable to join Zoom.  Please RSVP eith er way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way ?\n\n\n\n Meetings are focused in developers top level topics and its expe cted that understand embedded software development\, software testings or operating system management. In term of programming languages\, knowledge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings ar e 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 recognize d Armbian contributor. If you want to become one\, resolve at least one i ntermediate level issue and tell us something about you. This is needed t o efficiently communicate and to give you access to our organisation infr astructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @C ontributor/Maintainer\n\n DTSTART:20230301T170000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="RooopDooop";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED :forums@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="SteeMan";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian re-configurator DTSTAMP:20230213T123531Z SEQUENCE:0 UID:26-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n Meetings to support development of:\n\n\n\n https://githu b.com/armbian/configng\n\n\n\n  \n\n\n\n @sgjava @D-mo @joekhoobyar @A meer Dawood @esanya @TRS-80 @TheLinuxBug\n\n\n\n and anyone interested in some bash coding!\n\n  \n\n\n\n  \n\n DTSTART:20230217T190000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230207T115940Z SEQUENCE:0 UID:25-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Checking the progress of Armbian-next\n\n\n\n \n define upgrade path\n \n\n\n\n 2. Moving development related topics to GitHub\n\n\n\n \n ideas for moving comm\n \n\n\n\n 3. Questions around upcoming release\n\n\n\n  \n\n\n\n Di fferent starting hour!!!\n\n\n\n  \n\n\n\n General goal of weekly meeting s:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions will be documented to respective Jira tickets so they c an be tracked\n \n \n Three (3) new issues will be selected from Jira fo r the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly developer s meeting is to coordinate development of the build engine\, continuous in tegration\, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While  we wo uld 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 w ay.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n\ n\n\n Meetings are focused in developers top level topics and its expected that understand embedded software development\, software testings or oper ating system management. In term of programming languages\, knowledge of a t least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings are he ld 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 Ar mbian contributor. If you want to become one\, resolve at least one interm ediate level issue and tell us something about you. This is needed to eff iciently communicate and to give you access to our organisation infrastru cture Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contri butor/Maintainer\n\n DTSTART:20230208T160000Z DTEND:20230208T170000Z ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="TRS-80";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230131T115422Z SEQUENCE:0 UID:23-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Checking the progress of Armbian-next\n\n\n\n \n define upgrade path\n \n \n adju st communication strategy\n \n\n\n\n 2. Moving development related topics to GitHub\n\n\n\n \n how\, when\, how to communicate\n \n\n\n\n 3. Questi ons around upcoming release\n\n\n\n \n Today is the code freeze. Sent out  announcement\, asks for testing\n \n\n\n\n  \n\n\n\n Different starting hour!!!\n\n\n\n  \n\n\n\n General goal of weekly meetings:\n\n\n\n  \n\ n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions  will be documented to respective Jira tickets so they can be tracked\n \n \n Three (3) new issues will be selected from Jira for the next meeti ng\n \n\n\n\n  \n\n\n\n The purpose of a weekly developers meeting is to coordinate development of the build engine\, continuous integration\, oper ating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While  we would prefer you a ttend on Zoom when possibly\, we  will also monitor text chat during the call for those unable to join Zoom.  Please RSVP either way.\n\n\n\n  \n \n\n\n Do you want to participate or help in some way?\n\n\n\n Meetings a re focused in developers top level topics and its expected that understand embedded software development\, software testings or operating system man agement. In term of programming languages\, knowledge of at least BASH &am p\; Python is expected.\n\n\n\n \n\n Since meetings are held in public\, a ny registered community member can join and listen. If you want to suggest issues for the next week\, you have to be recognized Armbian contributo r. If you want to become one\, resolve at least one intermediate level iss ue and tell us something about you. This is needed to efficiently communi cate and to give you access to our organisation infrastructure Jira\, Git hub\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contributor/Maintainer \n\n DTSTART:20230201T150000Z DTEND:20230201T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="Werner";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian re-configurator DTSTAMP:20230131T144835Z SEQUENCE:0 UID:24-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n Meetings to support development of:\n\n\n\n https://githu b.com/armbian/configng\n\n\n\n  \n\n\n\n @sgjava\n\n\n\n @D-mo\n\n\n\n @j oekhoobyar\n\n\n\n @Ameer Dawood\n\n\n\n @esanya\n\n\n\n and anyone intere sted in some bash coding!\n\n  \n\n\n\n Lets move things further! Once we got it moving\, it will get a lot easier.\n\n DTSTART:20230203T190000Z DTEND:20230203T193000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="TRS-80";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian re-config meeting DTSTAMP:20221220T195926Z SEQUENCE:0 UID:17-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n Coordinating development of armbian-config refactoring:\n \n\n\n  \n\n\n\n https://github.com/armbian/configng\n\n\n\n  \n\n\n\n @ joekhoobyar\n\n DTSTART:20221223T190000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="D-mo";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 23.02 Quoll code freeze DTSTAMP:20221117T163628Z SEQUENCE:1 UID:11-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Code freeze is a milestone when we change our focus into cod e stabilisation\, fixing bugs. However it is not expected to drop existing work in progress at once but gradually close it.\n\n\n\nThis will be the last build from master branch\, before switicing to next generation build freamework(armbian-next).\n\n\n\nRelease is planned for February 25th. DTSTART:20230131T230000Z DTEND:20230201T223000Z END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230123T101354Z SEQUENCE:0 UID:22-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Checking the progress of Armbian-next\n\n\n\n 2. Continuous integration scripts us ed on the project\n\n\n\n 3. ??\n\n\n\n  \n\n\n\n General goal of weekly meetings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the we ek\n \n \n Discussions will be documented to respective Jira tickets so they can be tracked\n \n \n Three (3) new issues will be selected from J ira for the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly de velopers meeting is to coordinate development of the build engine\, contin uous integration\, operating system features and low level support. Meeti ngs are hosted located on Zoom (Video) and IRC and Discord (Text). While   we would prefer you attend on Zoom when possibly\, we  will also monit or text chat during the call for those unable to join Zoom.  Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n\n\n\n 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\, knowle dge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meeting s 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 recogn ized Armbian contributor. If you want to become one\, resolve at least on e intermediate level issue and tell us something about you. This is neede d to efficiently communicate and to give you access to our organisation i nfrastructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230125T120000Z DTEND:20230125T130000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="SteeMan";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230111T095846Z SEQUENCE:0 UID:21-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Checking the progress of Armbian-next\n\n\n\n 2. Providing stable builds for main T V box image?\n\n\n\n 3. \n\n\n\n  \n\n\n\n General goal of weekly meetin gs:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \ n \n Discussions will be documented to respective Jira tickets so they can be tracked\n \n \n Three (3) new issues will be selected from Jira f or the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly develope rs meeting is to coordinate development of the build engine\, continuous i ntegration\, operating system features and low level support. Meetings ar e hosted located on Zoom (Video) and IRC and Discord (Text). While  we w ould 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.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n \n\n\n Meetings are focused in developers top level topics and its expecte d that understand embedded software development\, software testings or ope rating system management. In term of programming languages\, knowledge of at least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings are h eld in public\, any registered community member can join and listen. If yo u want to suggest issues for the next week\, you have to be recognized A rmbian contributor. If you want to become one\, resolve at least one inter mediate level issue and tell us something about you. This is needed to ef ficiently communicate and to give you access to our organisation infrastr ucture Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contr ibutor/Maintainer @MattWestB @jock @SteeMan\n\n DTSTART:20230118T120000Z DTEND:20230118T130000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="SteeMan";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230107T121619Z SEQUENCE:0 UID:20-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Checking the progress of Armbian-next\n\n\n\n 2. Encourage end-users to open bugs t o Jira?\n\n\n\n 3. Move developers forums to GitHub?\n\n\n\n  \n\n\n\n Ge neral goal of weekly meetings:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions will be documented to respe ctive Jira tickets so they can be tracked\n \n \n Three (3) new issues wi ll be selected from Jira for the next meeting\n \n\n\n\n  \n\n\n\n The p urpose 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 D iscord (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.\n\n\n\n  \n\n\n\n Do you want to particip ate or help in some way?\n\n\n\n Meetings are focused in developers top l evel topics and its expected that understand embedded software development \, software testings or operating system management. In term of programmin g languages\, knowledge of at least BASH &\; Python is expected.\n\n\n\ n \n\n Since meetings are held in public\, any registered community member can join and listen. If you want to suggest issues for the next week\, yo u have to be recognized Armbian contributor. If you want to become one\, resolve at least one intermediate level issue and tell us something abou t you. This is needed to efficiently communicate and to give you access t o our organisation infrastructure Jira\, Github\, hardware lab and servers .\n\n\n\n  \n\n\n\n @Contributor/Maintainer\n\n DTSTART:20230111T120000Z DTEND:20230111T130000Z ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="ZazaBr";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:for ums@mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Release Planning DTSTAMP:20221117T162934Z SEQUENCE:0 UID:7-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Release Planning\nIRC DTSTART:20230107T150000Z DTEND:20230107T160000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="jock";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="Heisath";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20230103T123905Z SEQUENCE:0 UID:19-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This week meeting topics:\n\n\n\n  \n\n\n\n 1. Checking the progress of Armbian-next\n\n\n\n 2. Armbian short description\n\n\n\n 3. Mainlining of patches\n\n\n\n  \n\n\n\n General goal of weekly meeting s:\n\n\n\n  \n\n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions will be documented to respective Jira tickets so they c an be tracked\n \n \n Three (3) new issues will be selected from Jira fo r the next meeting\n \n\n\n\n  \n\n\n\n The purpose of a weekly developer s meeting is to coordinate development of the build engine\, continuous in tegration\, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While  we wo uld 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 w ay.\n\n\n\n  \n\n\n\n Do you want to participate or help in some way?\n\ n\n\n Meetings are focused in developers top level topics and its expected that understand embedded software development\, software testings or oper ating system management. In term of programming languages\, knowledge of a t least BASH &\; Python is expected.\n\n\n\n \n\n Since meetings are he ld 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 Ar mbian contributor. If you want to become one\, resolve at least one interm ediate level issue and tell us something about you. This is needed to eff iciently communicate and to give you access to our organisation infrastru cture Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n @Contri butor/Maintainer\n\n DTSTART:20230104T120000Z DTEND:20230104T130000Z ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="Heisath";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20221221T144005Z SEQUENCE:0 UID:18-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This weeks meeting topics:\n\n\n\n  \n\n\n\n \n Merging NEXT\n \n \n Unifying boot process\n \n \n When 6.2 and 6.1\, current / edge\n \n\n\n\n  \n\n\n\n General goal of weekly meetings:\n\n\n\n  \n\ n\n\n \n To discuss the three (3) issues of the week\n \n \n Discussions  will be documented to respective Jira tickets so they can be tracked\n \n \n Three (3) new issues will be selected from Jira for the next meeti ng\n \n\n\n\n  \n\n\n\n The purpose of a weekly developers meeting is to coordinate development of the build engine\, continuous integration\, oper ating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While  we would prefer you a ttend on Zoom when possibly\, we  will also monitor text chat during the call for those unable to join Zoom.  Please RSVP either way.\n\n\n\n  \n \n\n\n Do you want to participate or help in some way?\n\n\n\n Meetings a re focused in developers top level topics and its expected that understand embedded software development\, software testings or operating system man agement. In term of programming languages\, knowledge of at least BASH &am p\; Python is expected.\n\n\n\n \n\n Since meetings are held in public\, a ny registered community member can join and listen. If you want to suggest issues for the next week\, you have to be recognized Armbian contributo r. If you want to become one\, resolve at least one intermediate level iss ue and tell us something about you. This is needed to efficiently communi cate and to give you access to our organisation infrastructure Jira\, Git hub\, hardware lab and servers.\n\n DTSTART:20221228T120000Z ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="JetHome";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:fo rums@mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Weekly developers meetup DTSTAMP:20221210T125010Z SEQUENCE:0 UID:16-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="Igor":forums@mail.armbian.com DESCRIPTION:\n This weeks meeting topics:\n\n\n\n  \n\n\n\n \n Merging of next generation build framework Primary goal is to understand benefit s it is bringing as we all will need to sacrifice some time in order to re view it\, then merge and fix remaining bug. Despite our current system pro duces images\, we have many bugs and dirty workarounds that this upgrade i s addressing.\n \n \n The future of rockchip64 family Main goal is to ma ke it maintainable again.\n \n \n GitHub development and review process  Main goal is to motivate people to take more responsibility for reviewing and merging. Define clear rules.\n \n  \n \n \n\n\n\n  \n\n\n\n Goal of the weekly meetings:\n\n\n\n \n To discuss the three (3) issues of th e week\n \n \n Discussions will be documented to respective Jira ticket s so they can be tracked\n \n \n Three (3) new issues will be selected fr om Jira for the next meeting\n \n\n\n\n  \n\n\n\n Conclusions:\n\n\n\n  \n\n\n\n Everyone interested should watch a recording (~1h) and place a comment below. Comments will be discussed here or at next meeting. Before we can do anything in real regarding merging NEXT\, we need to clean patc hes but also address several things\, starting with those:\n\n\n\n  \n\n \n\n \n Making a tool / module for patch generation (@rpardini)\n \n \n \n Preparing guidelines for review and contribution (@giddy)\n \n \n \n \n Move repo management from the build system (@igor)\n \n \n\n\n\ n  \n\n\n\n How can anyone help? Cleaning the patches!\n\n\n\n  \n\n\n\n The purpose of a weekly developers meeting is to coordinate development o f the build engine\, continuous integration\, operating system features an d low level support. Meetings are hosted located on Zoom (Video) and IRC  and Discord (Text). While  we would prefer you attend on Zoom when poss ibly\, we  will also monitor text chat during the call for those unable t o join Zoom.  Please RSVP either way.\n\n\n\n  \n\n\n\n Do you want to p articipate or help in some way?\n\n\n\n Meetings are focused in developer s top level topics and its expected that understand embedded software deve lopment\, software testings or operating system management. In term of pro gramming languages\, knowledge of at least BASH &\; Python is expected. \n\n\n\n \n\n Since meetings are held in public\, any registered community member can join and listen. If you want to suggest issues for the next we ek\, you have to be recognized Armbian contributor. If you want to becom e one\, resolve at least one intermediate level issue and tell us somethi ng about you. This is needed to efficiently communicate and to give you a ccess to our organisation infrastructure Jira\, Github\, hardware lab and servers.\n\n\n\n  \n\n\n\n armbian-next_-_meeting_21.dec.2022.pdf\n\n DTSTART:20221221T120000Z ATTENDEE;CN="rpardini";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:f orums@mail.armbian.com ATTENDEE;CN="Igor";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:forum s@mail.armbian.com ATTENDEE;CN="TonyMac32";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED: forums@mail.armbian.com ATTENDEE;CN="giddy";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:foru ms@mail.armbian.com END:VEVENT BEGIN:VEVENT SUMMARY:Armbian config refactoring DTSTAMP:20221209T225030Z SEQUENCE:0 UID:15-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Armbian config refactoring\nOnline Meeting via Zoom Meeting DTSTART:20221216T190000Z DTEND:20221216T200000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 23.11 Topi code freeze DTSTAMP:20221117T180601Z SEQUENCE:0 UID:12-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Armbian 23.11 Topi code freeze DTSTART:20231101T150000Z DTEND:20231101T160000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 23.08 Colobus code freeze DTSTAMP:20221117T180601Z SEQUENCE:0 UID:13-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Armbian 23.08 Colobus code freeze DTSTART:20230801T180000Z DTEND:20230801T190000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 23.05 Suni code freeze DTSTAMP:20221117T180601Z SEQUENCE:0 UID:14-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Armbian 23.05 Suni code freeze DTSTART:20230501T180000Z DTEND:20230501T190000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 23.11 Topi release DTSTAMP:20221117T163207Z SEQUENCE:0 UID:8-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Armbian 23.11 Topi release DTSTART:20231130T180000Z DTEND:20231130T190000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 23.08 Colobus release DTSTAMP:20221117T163207Z SEQUENCE:0 UID:9-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Armbian 23.08 Colobus release DTSTART:20230831T180000Z DTEND:20230831T190000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 23.05 Suni release DTSTAMP:20221117T163207Z SEQUENCE:0 UID:10-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Armbian 23.05 Suni release DTSTART:20230531T180000Z DTEND:20230531T190000Z END:VEVENT BEGIN:VEVENT SUMMARY:Release Planning DTSTAMP:20221117T162934Z SEQUENCE:0 UID:4-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Release Planning\nIRC DTSTART:20231007T150000Z DTEND:20231007T160000Z END:VEVENT BEGIN:VEVENT SUMMARY:Release Planning DTSTAMP:20221117T162934Z SEQUENCE:4 UID:5-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Release Planning\nIRC DTSTART:20230715T150000Z DTEND:20230715T190000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 23.02 Quoll release DTSTAMP:20221116T130417Z SEQUENCE:0 UID:2-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Regular release DTSTART:20230225T140000Z DTEND:20230225T150000Z END:VEVENT BEGIN:VEVENT SUMMARY:Armbian 22.11 Goral release DTSTAMP:20221116T125341Z SEQUENCE:2 UID:1-1-ff57c068b0728da0c96d884045c87296@forum.armbian.com ORGANIZER;CN="admin":forums@mail.armbian.com DESCRIPTION:Regular release. \n\n\n\nhttps://www.armbian.com/download/ DTSTART:20221203T140000Z DTEND:20221203T150000Z END:VEVENT END:VCALENDAR