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: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: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 &amp\; 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
END:VCALENDAR