Seeeking new maintainers from gVavaSense

Showcase
1

Gvavasense Linux OS :rocket:

Gvavasense is an open-source, highly modular distribution architecture focused on absolute user autonomy, alternative initialization tracks, and long-term hardware preservation.

To achieve uncompromised user control, our build pipelines enforce a 100% strict block on Canonical’s closed-source snapd ecosystem across all targets. Rather than using standard Ubuntu Desktop, our modern profiles leverage an Ubuntu Server Base running pure Vanilla GNOME to bypass Canonical’s custom upstream software bundles, telemetry, and hidden package trackers. Furthermore, we provide dedicated sub-editions on both Debian and Ubuntu that completely isolate, strip, and exclude systemd components.

:card_index_dividers: 1. Core Architecture, Base OS & Era Layout

To support modern, high-performance workstations alongside vintage 32-bit hardware without sacrificing software stability, Gvavasense divides its codebase into two distinct target tracks across two major base distributions:

:floppy_disk: The Legacy Preservation Track (Debian Base)

  • Base OS: Debian 11 (Bullseye)
  • Target Architecture: 32-bit (i686) utilizing the linux-image-686-pae kernel.
  • Purpose: Extreme resource optimization for vintage laptops, notebook terminals, and legacy PCs.
  • Distribution Formats: Live bootable ISO files and minimal Rootfs Deployment Tarballs (.tar.gz).

:high_voltage: The Modern Workstation Track (Ubuntu Server & Debian Base)

  • Base OS: Ubuntu 26.04 LTS (Server Base with Vanilla GNOME) OR Debian 13 (Trixie) / Present Testing.
  • Target Architecture: 64-bit (amd64) utilizing the linux-image-amd64 or linux-image-gnu-amd64 (Libre) kernel tracks.
  • Purpose: Clean, high-efficiency execution on modern multi-core x86_64 machines.
  • Distribution Formats: High-efficiency zstd compressed Live Installer ISO files and production deployment scripts.

:package: 2. Production Edition Parameters

Every edition is maintained across our dual-OS hardware architecture:

:green_circle: A. Libre Free-Only Edition

  • Philosophy: 100% Free/Libre software matching strict FSF licensing guidelines.
  • Repositories: Pure main repository tracking on Debian and main/universe on Ubuntu (completely excluding contrib, restricted, multiverse, and non-free channels).
  • Kernel: GNU Linux-libre (completely stripped of proprietary firmware and binary blobs via the Freesh project track).
  • Init Systems: systemd or SysVinit.

:blue_circle: B. Non-Free Edition

  • Philosophy: Maximum hardware compatibility out-of-the-box.
  • Repositories: Full access to all official software channels, including proprietary firmware microcode and third-party driver paths.
  • Kernel: Upstream Debian/Ubuntu kernel with integrated proprietary firmware, proprietary wireless drivers, and legacy GPU blobs.
  • Init System: systemd.

:yellow_circle: C. Non-Systemd Edition

  • Philosophy: Traditional, lightweight Unix-style process initialization.
  • Init System Options: SysVinit, OpenRC, or Runit (strictly enforced via customized APT pinning preferences).
  • Sub-Flavors: Separated into independent Libre (Free-only) and Non-Free configuration layers.

:red_circle: D. Vava Rolling Edition

  • Philosophy: Bleeding-edge packages tracking continuous development upstream.
  • Repositories: Live synchronization tracking active Debian Testing branches.
  • Init System: systemd.

:purple_circle: E. Ports Edition

  • Philosophy: Out-of-the-box specialization for corporate productivity and diverse web environments.
  • Base Restrictions: Deployed strictly on Non-Free base configurations (systemd/Non-Systemd) due to external upstream software packaging.
  • Pre-configured Alternative Office Suites:
    • ONLYOFFICE Desktop Editors (Native real-time collaborative workspace)
    • WPS Office Suite (High MS Office XML file layout compatibility)
    • Apache OpenOffice (Classic, lightweight traditional fallback)
  • Pre-configured Web Browser Arsenal:
    • Chromium & Ungoogled Chromium (Privacy-focused pure Chromium baselines)
    • Microsoft Edge & Google Chrome (Enterprise runtime standards)
    • Opera & Vivaldi (Power-user custom navigation environments)

:artist_palette: 3. Graphical Interface Tier Layout (18 Total UIs)

Gvavasense organizes its 18 supported desktop environments and window managers into explicit resource usage tiers. LXDE and LXQt remain the primary baseline standards for lightweight graphical editions. On our Ubuntu Server base, the environment directly launches vanilla GNOME environments completely detached from Canonical’s Snap store layouts.

Tier Profile Supported Desktop Environments & Window Managers Formats Min RAM (32-bit / 64-bit)
Traditional Heavyweight GNOME, KDE Plasma, Cinnamon, Budgie, Deepin (DDE), Cosmic Live ISO 1.5 GB / 4 GB
Traditional Lightweight LXDE, LXQt, XFCE, MATE, Trinity (TDE), Pantheon ISO + Tarball 512 MB / 2 GB
Floating Window Managers Openbox, Fluxbox, IceWM, JWM, FVWM ISO + Tarball 256 MB / 1 GB
Tiling Window Managers Sway, i3wm, AwesomeWM Live ISO 512 MB / 2 GB

Note: Cosmic and Deepin environments are restricted to the 64-bit amd64 track due to modern upstream compilation toolchain requirements.

:hammer_and_wrench: 4. Core Maintainer Build Pipeline (Ubuntu Server + Vanilla GNOME Focus)

To customize Ubuntu 26.04 Server safely, maintainers must aggressively pin against snapd and inject alternative desktop environment hooks before the main environment triggers system dependencies.

Step 1: Initialize Your Host Workspace

Prepare your compilation machine with cross-architecture compilation utilities and directory trees:

sudo apt update
sudo apt install debootstrap live-build xz-utils tar -y
mkdir -p ~/gvavasense-core/config
mkdir -p ~/gvavasense-core/rootfs
cd ~/gvavasense-core

Step 2: Inject the Absolute Block Configuration

Create a global preference restriction file at config/preferences. This configuration enforces an aggressive priority blockade against snapd and systemd packages across your target build roots:

Package: snapd
Pin: release *
Pin-Priority: -1

Package: ubuntu-core-launcher
Pin: release *
Pin-Priority: -1

Package: systemd
Pin: release *
Pin-Priority: -1

Package: systemd-sysv
Pin: release *
Pin-Priority: -1

Package: *systemd*
Pin: release *
Pin-Priority: -1

Step 3: Run the Base System Extraction

Execute debootstrap to pull a minimal, clean directory tree base without system components.

  • For Modern amd64 (Ubuntu 26.04 Server Minimal Base):

    sudo debootstrap --arch=amd64 --variant=minbase \
  --include=sysvinit-core,elogind,libpam-elogind,initramfs-tools \
  resolute ./rootfs http://ubuntu.com

  • For Legacy i686 (Debian 11 Bullseye Base):

    sudo debootstrap --arch=i686 --variant=minbase \
  --include=sysvinit-core,elogind,libpam-elogind,initramfs-tools,linux-image-686-pae \
  bullseye ./rootfs http://debian.org

  • For Modern amd64 (Debian 13 Trixie Base):

    sudo debootstrap --arch=amd64 --variant=minbase \
  --include=sysvinit-core,elogind,libpam-elogind,initramfs-tools,linux-image-amd64 \
  trixie ./rootfs http://debian.org

Step 4: Chroot Environment Isolation & UI Layering

Bind the system logs, copy your package restrictions directly into the chroot’s configuration pathways, and swap roots:

sudo mount --bind /dev ./rootfs/dev
sudo mount --bind /proc ./rootfs/proc
sudo mount --bind /sys ./rootfs/sys
sudo cp config/preferences ./rootfs/etc/apt/preferences.d/gvavasense.pref
sudo chroot ./rootfs /bin/bash

Inside the Chroot terminal, update repositories and install a clean, pure Vanilla GNOME stack without any canonical tracking modifications:

apt update
# Enforce native pure desktop configurations
apt install xserver-xorg-core gdm3 gnome-session gnome-terminal --no-install-recommends -y
apt clean
exit

Unmount virtual directories when finishing operations inside the environment:

sudo umount ./rootfs/dev ./rootfs/proc ./rootfs/sys

Step 5: Exporting the Deployments

  • To extract the direct Rootfs Deployment Tarball:
    sudo tar --one-file-system -zcpf ./gvavasense-gnome-sysvinit.tar.gz -C ./rootfs .
  • To compile a Bootable Installer ISO via Penguins-Eggs:
    sudo eggs produce --output-dir ~/gvavasense-core/ --max

:handshake: Active Volunteer Teams Needed

We are organizing our community layout into focused ownership brackets. Open an issue or drop a line in our development channel to claim your specialization track:

  • Infrastructure Lead: Automating the debootstrap extraction loops via central GitHub Actions or GitLab CI tracking templates.
  • Init System Leads: Writing customized service automation scripts for OpenRC and Runit process management layers on both Debian and Ubuntu.
  • Ports Edition Lead: Managing external non-free web engine tracking repos, setting up independent application keyrings, and verifying flatpak packaging wrappers.
  • Desktop Caretakers: Tweaking interface configuration layers, refining desktop panels, and optimizing theme styling sheets for lightweight systems.
  • Web Developers: Constructing our static site documentation matrix and building front-end browser-based SHA256 image checksum verification modules.

:speech_balloon: Communication

  • Development Chat: Join our central workspace channel on Matrix at #gvavasense:matrix.org
    We need opition for us im not a spammer
2 Likes
2

ugnvs why you fire emoij me

3

I am sorry for possible misinterpretation of fire emoji. I believe that fire emoji is a positive one and literary means “nice and strong as a fire” or that the subject is excellent, impressive, or exciting in other words.

4 Likes
4

Absolutely positive! No negative intended!

My own interpretation of the “flame” is “Hot Stuff”, or “You are so good, you are on fire!” That should convey the gist of it!

It is very unfortunate that you couldn’t get it recognized as an Ubuntu Flavour, because many Ubuntu Users would likely “pounce” at the opportunity to use an Ubuntu installer and configuration the way you have outlined the above. Pity!

1 Like