Future Directions - Revision history

Armin Kuster: /* Other future topics */

2022-02-15T21:06:28Z

2022-02-15T21:05:48Z

Support for multiple toolchains

← Older revision		Revision as of 21:05, 15 February 2022
Line 170:		Line 170:
	Other areas which need development:		Other areas which need development:
	=== Support for multiple toolchains ===		=== Support for multiple toolchains ===
	* clang		# clang
	* or arch specific e.g. intel or arm compilers) as not all recipes build with standard gcc any longer		# or arch specific e.g. intel or arm compilers) as not all recipes build with standard gcc any longer

	=== meta-gplv2 ===		=== meta-gplv2 ===

2022-02-15T21:05:37Z

meta-gplv2

2022-02-15T21:04:56Z

ABI/API compliance

← Older revision		Revision as of 21:04, 15 February 2022
Line 179:		Line 179:

	=== ABI/API compliance ===		=== ABI/API compliance ===
	* Best practices		# Best practices
	* Scanning tools		# Scanning tools
	* Auto scanning like cve-checker.		# Auto scanning like cve-checker.

2022-02-15T21:03:21Z

ABI/API compliance

← Older revision		Revision as of 21:03, 15 February 2022
Line 178:		Line 178:
	* Maintainer		* Maintainer

	=== ~~'''~~ABI/API~~'''~~ compliance ===		=== ABI/API compliance ===
	~~====~~ Best practices ~~====~~		* Best practices
	~~====~~ Scanning tools ~~====~~		* Scanning tools
	~~====~~ Auto scanning like cve-checker. ~~====~~		* Auto scanning like cve-checker.

2022-02-15T21:02:47Z

meta-gplv2

← Older revision		Revision as of 21:02, 15 February 2022
Line 173:		Line 173:
	* or arch specific e.g. intel or arm compilers) as not all recipes build with standard gcc any longer		* or arch specific e.g. intel or arm compilers) as not all recipes build with standard gcc any longer

	=== ~~'''~~meta-gplv2~~'''~~ ===		=== meta-gplv2 ===
	~~====~~ Remove from build ~~====~~		* Remove from build
	~~====~~ Migrate packages ~~====~~		* Migrate packages
	~~====~~ Maintainer ~~====~~		* Maintainer

	=== '''ABI/API''' compliance ===		=== '''ABI/API''' compliance ===

2022-02-15T21:02:10Z

Support for multiple toolchains

← Older revision		Revision as of 21:02, 15 February 2022
Line 170:		Line 170:
	Other areas which need development:		Other areas which need development:
	=== Support for multiple toolchains ===		=== Support for multiple toolchains ===
	~~====~~ clang ~~====~~		* clang
	~~====~~ or arch specific e.g. intel or arm compilers) as not all recipes build with standard gcc any longer ~~====~~		* or arch specific e.g. intel or arm compilers) as not all recipes build with standard gcc any longer

	=== '''meta-gplv2''' ===		=== '''meta-gplv2''' ===

2022-02-15T21:01:06Z

2021-07-05T18:03:18Z

Inclusive Language

← Older revision		Revision as of 18:03, 5 July 2021
Line 71:		Line 71:
	addressing these issues as well using the opportunity to improve in other areas such as usability. The plan that was agreed/proposed:		addressing these issues as well using the opportunity to improve in other areas such as usability. The plan that was agreed/proposed:

	https://lists.openembedded.org/g/openembedded-architecture/topic/~~inclusive_language_summary~~/75821819		https://lists.openembedded.org/g/openembedded-architecture/topic/_summary/75821819

	''Current status:'' Plan published, next step is to create a wiki page of problems areas		''Current status:'' Plan published, next step is to create a wiki page of problems areas

			https://wiki.yoctoproject.org/wiki/inclusive_language

	''Resourcing estimate:'' Needs someone with community collaboration skills to lead/organize and should be a fixed term effort for a release cycle (6 months) with limited time commitments once the plan is formed. Plan may take a few weeks to develop/discuss/finalize. Individual changes can be made different individuals without high skillset requirements in many cases.		''Resourcing estimate:'' Needs someone with community collaboration skills to lead/organize and should be a fixed term effort for a release cycle (6 months) with limited time commitments once the plan is formed. Plan may take a few weeks to develop/discuss/finalize. Individual changes can be made different individuals without high skillset requirements in many cases.

2021-07-05T18:01:08Z

Inclusive Language

← Older revision		Revision as of 18:01, 5 July 2021
Line 75:		Line 75:
	''Current status:'' Plan published, next step is to create a wiki page of problems areas		''Current status:'' Plan published, next step is to create a wiki page of problems areas

	''Resourcing estimate:'' Needs someone with community collaboration skills to lead/~~organise~~ and should be a fixed term effort for a release cycle (6 months) with limited time ~~commitements~~ once the plan is formed. Plan may take a few weeks to develop/discuss/~~finalise~~. Individual changes can be made different individuals without high skillset requirements in many cases.
			''Resourcing estimate:'' Needs someone with community collaboration skills to lead/organize and should be a fixed term effort for a release cycle (6 months) with limited time commitments once the plan is formed. Plan may take a few weeks to develop/discuss/finalize. Individual changes can be made different individuals without high skillset requirements in many cases.

	== Developer Tools and Processes ==		== Developer Tools and Processes ==

← Older revision		Revision as of 21:01, 15 February 2022
Line 169:		Line 169:

	Other areas which need development:		Other areas which need development:
	#Support for multiple toolchains (clang or arch specific e.g. intel or arm compilers) as not all recipes build with standard gcc any longer		=== Support for multiple toolchains ===
			==== clang ====
			==== or arch specific e.g. intel or arm compilers) as not all recipes build with standard gcc any longer ====

			=== '''meta-gplv2''' ===
			==== Remove from build ====
			==== Migrate packages ====
			==== Maintainer ====

			=== '''ABI/API''' compliance ===
			==== Best practices ====
			==== Scanning tools ====
			==== Auto scanning like cve-checker. ====

← Older revision		Revision as of 21:06, 15 February 2022
Line 169:		Line 169:

	Other areas which need development:		Other areas which need development:

	=== Support for multiple toolchains ===		=== Support for multiple toolchains ===
	# clang		# clang