# Proposed SIG table of contents

**Legend**
:white_check_mark: Consolidation work complete
:curly_loop: Consolidation work in progress in current MR
:large_orange_diamond: Consolidation work not started

**Proposed structure**
- :white_check_mark: Welcome to the Automotive SIG
- :white_check_mark: About the Automotive SIG community
- :white_check_mark: Communication and meetings
- :white_check_mark: About AutoSD
- :white_check_mark: AutoSD key features
- :white_check_mark: AutoSD salient benefits
- :white_check_mark: Performance and security benefits
- :white_check_mark: SIG repos
- :white_check_mark: Contributing to GitLab
- :white_check_mark: Enabling CentOS Stream repositories
- :white_check_mark: Up/downstreams

- :white_check_mark: Features and Concepts
- :white_check_mark: Open source development
- :white_check_mark: Source and binary distributions
- :white_check_mark: RPM packages and the RPM package manager
- :white_check_mark: AutoSD image build mechanics
- :white_check_mark: Mixed criticality
- :white_check_mark: OSTree

- :white_check_mark: Getting started
- :white_check_mark: Setting up a Linux development environment
- :white_check_mark: Quick-start build an image
- :white_check_mark: Quick-start boot a nightly image with QEMU
- :white_check_mark: Quick-start QEMU development environment
- :white_check_mark: Setting up a MacOS development environment
- :white_check_mark: Quick-start build an image
- :white_check_mark: Quick-start boot a nightly image with QEMU
- :white_check_mark: Quick-start QEMU development environment
- :large_orange_diamond: Setting up a Windows development environment
- :large_orange_diamond: Quick-start build an image
- :large_orange_diamond: Quick-start boot a nightly image with QEMU
- :large_orange_diamond: Quick-start QEMU development environment
- :white_check_mark: Working with the sample manifests, sample images, aib/targets
- :white_check_mark: Sample manifests
- :white_check_mark: Sample images and non-sample images
- :white_check_mark: Targets
- :white_check_mark: Distros
- :white_check_mark: Exports
- :curly_loop: Deploying sample apps (radio, engine)

- :white_check_mark: Building and customizing images
- :white_check_mark: Working with RPM packages
- :white_check_mark: Packaging source code with RPM
- :white_check_mark: Embedding RPM packages in the OS image
- :white_check_mark: Containerizing applications
- :white_check_mark: Building container images
- :white_check_mark: Embedding containerized applications in the OS image
- :white_check_mark: Configuring quadlet
- :white_check_mark: Deploying QM applications
- :white_check_mark: Embedding RPM packages in QM
- :white_check_mark: Embedding containerized applications in QM
- :white_check_mark: Configuring QM-QM and ASIL-QM container communication
- :white_check_mark: Managing containers at scale
- :white_check_mark: Configuring BlueChi
- :large_orange_diamond: Deploying graphical QM applications
- :large_orange_diamond: Running Android virtual guests
- :large_orange_diamond: Configuring networking
- :white_check_mark: Building your custom image
- :curly_loop: Managing your images with OSTree
- :white_check_mark: Building an OS image with a custom AutoSD kernel

- :white_check_mark: Provisioning systems
- :white_check_mark: Building and booting virtual systems
- :white_check_mark: Flashing hardware
- :white_check_mark: Qualcomm
- :white_check_mark: Texas Instruments
- :white_check_mark: Renesas
- :white_check_mark: NXP

- :large_orange_diamond: Cross-compiling
- :large_orange_diamond: Cross-compilation asks and usage
- :large_orange_diamond: Available cross-compiler tools
- :large_orange_diamond: Cross-compilation limitations

- :large_orange_diamond: Security offerings
- :white_check_mark: Enabling hardware for AutoSD
- :white_check_mark: Hardware enablement program
- :white_check_mark: Advantages of upstreaming your drivers
- :white_check_mark: Ideal hardware
- :white_check_mark: Out-of-tree driver modules
- :white_check_mark: Upstreaming drivers

- :large_orange_diamond: Conducting performance tests
- :large_orange_diamond: FAQs
- :large_orange_diamond: Why is the RPi4 not supported?
- :large_orange_diamond: How do I get cross compilation up and running?
- :large_orange_diamond: Why can't I use a package manager on the system?

- :white_check_mark: Deprecated/superceded content
- :white_check_mark: Old(er) build mechanics
- :white_check_mark: Building an image manually or with makefile
- :white_check_mark: Building an image in a VM
- :white_check_mark: Containers in automotive images
- :white_check_mark: Customizing images
- :white_check_mark: Using make manifests
- :white_check_mark: Using non-containerized OSBuild

## Topics not included (yet)
- App store
- Monitoring and reporting
- Other Linux configs like user/group quotas, partitioning, etc.
- Configuring remote/cloud build systems
- Running AutoSD on AWS or other cloud providers
- POC-ready hardware definition/explanation
- HW watchdog
- Real time
- Optimizing boot time
- Demos
- Container demo
- Infotainment demo
- OTA demo