From c4a0214d36e5ec5d109a07d7df50e659aa4bb656 Mon Sep 17 00:00:00 2001 From: Petr Bokoc Date: May 29 2026 09:04:33 +0000 Subject: Migrate to Forgejo and archive --- diff --git a/.gitignore b/.gitignore deleted file mode 100644 index 9f3ebf5..0000000 --- a/.gitignore +++ /dev/null @@ -1,3 +0,0 @@ -build -cache -public diff --git a/README.md b/README.md index be47a7e..c264f3f 100644 --- a/README.md +++ b/README.md @@ -1,17 +1,3 @@ -# Fedora Minimization Objective +This repository has been migrated to https://forge.fedoraproject.org/docs-archive/minimization. -This repo is used for **tickets** regarding the objective, and to store the **documentation** source. - -See the [**Fedora Minimization Documentation**](https://docs.fedoraproject.org/en-US/minimization/) for more information. - -## Documentation source - -All content is in an [AsciiDoc format](https://asciidoctor.org/docs/asciidoc-writers-guide/), stored in the `modules/ROOT/pages` directory. When adding a new page, make sure to add it to the menu definition in `modules/ROOT/nav.adoc` so it shows up. - -### Local preview - -``` -$ ./build.sh && ./preview.sh -``` - -On Fedora, all you need is to have [Podman](https://podman.io/) installed. \ No newline at end of file +It has also been archived due to the contents being out of date. If you'd like to revive this documentation, come talk to us on Matrix: https://matrix.to/#/#docs:fedoraproject.org. diff --git a/antora.yml b/antora.yml deleted file mode 100644 index 4994cea..0000000 --- a/antora.yml +++ /dev/null @@ -1,16 +0,0 @@ -# Name will be mostly visible in the URL. Treat it as an indentifier. -# Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page) -name: minimization # <---- PLEASE MODIFY - -# Title will be visible on the page. -title: Minimization # <---- PLEASE MODIFY - -# If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version. -version: master - -# We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise. -start_page: ROOT:index - -# This lists all the menu definitions of your component. -nav: -- modules/ROOT/nav.adoc diff --git a/build.sh b/build.sh deleted file mode 100755 index 1e4db2d..0000000 --- a/build.sh +++ /dev/null @@ -1,46 +0,0 @@ -#!/bin/sh - -image="docker.io/antora/antora" -cmd="--html-url-extension-style=indexify site.yml" - -if [ "$(uname)" == "Darwin" ]; then - # Running on macOS. - # Let's assume that the user has the Docker CE installed - # which doesn't require a root password. - echo "" - echo "This build script is using Docker container runtime to run the build in an isolated environment." - echo "" - docker run --rm -it -v $(pwd):/antora $image $cmd - -elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then - # Running on Linux. - # Check whether podman is available, else faill back to docker - # which requires root. - - if [ -f /usr/bin/podman ]; then - echo "" - echo "This build script is using Podman to run the build in an isolated environment." - echo "" - podman run --rm -it -v $(pwd):/antora:z $image $cmd - - elif [ -f /usr/bin/docker ]; then - echo "" - echo "This build script is using Docker to run the build in an isolated environment." - echo "" - - if groups | grep -wq "docker"; then - docker run --rm -it -v $(pwd):/antora:z $image $cmd - else - echo "" - echo "This build script is using $runtime to run the build in an isolated environment. You might be asked for your password." - echo "You can avoid this by adding your user to the 'docker' group, but be aware of the security implications. See https://docs.docker.com/install/linux/linux-postinstall/." - echo "" - sudo docker run --rm -it -v $(pwd):/antora:z $image $cmd - fi - else - echo "" - echo "Error: Container runtime haven't been found on your system. Fix it by:" - echo "$ sudo dnf install podman" - exit 1 - fi -fi diff --git a/modules/ROOT/assets/images/green.jpg b/modules/ROOT/assets/images/green.jpg deleted file mode 100644 index 8b0b412..0000000 Binary files a/modules/ROOT/assets/images/green.jpg and /dev/null differ diff --git a/modules/ROOT/assets/images/red.png b/modules/ROOT/assets/images/red.png deleted file mode 100644 index 2fc31e5..0000000 Binary files a/modules/ROOT/assets/images/red.png and /dev/null differ diff --git a/modules/ROOT/assets/images/yellow.jpg b/modules/ROOT/assets/images/yellow.jpg deleted file mode 100644 index 6a0f3f9..0000000 Binary files a/modules/ROOT/assets/images/yellow.jpg and /dev/null differ diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc deleted file mode 100644 index 02e89b5..0000000 --- a/modules/ROOT/nav.adoc +++ /dev/null @@ -1,13 +0,0 @@ - -* **Objective** -* xref:index.adoc[Fedora Minimization Objective] - -* **Community** -* xref:team.adoc[Contribute] -* xref:communication.adoc[Discuss & Track] - -* **Progress** -* xref:action-plan.adoc[Action Plan] -* xref:tools.adoc[Tools & Services] -* xref:discoveries.adoc[Packaging Discoveries] -* xref:status.adoc[Status Updates] diff --git a/modules/ROOT/pages/action-plan.adoc b/modules/ROOT/pages/action-plan.adoc deleted file mode 100644 index 8b5ddef..0000000 --- a/modules/ROOT/pages/action-plan.adoc +++ /dev/null @@ -1,56 +0,0 @@ -= Action Plan for Minimization - -This is a short-term action plan for the Minimization effort. The objective is in an early stage and doesn’t have a proper tracker, yet. At this time, everything is tracked at and reported back to this space in Fedora Docs. - -There are four main focus areas at this moment: - -1. **Prototyping tools** -** Developing (or documenting existing) tools that help with exploration and analysis. - -2. **Ecosystems exploration** -** Identifying specific use cases (specific package installations) to optimize. Comparing Fedora with other ecosystems for reference. - -3. **Use case analysis** -** Digging into dependency trees of specific use cases (specific package installations), and finding ways for potential minimization. - -4. **Content strategy** -** Defining an effective way to let the world know about the cool things we do! - -== Prototyping tools - -https://pagure.io/minimization/issues?status=Open&tags=Focus+Area%3A+Prototyping+Tools&close_status=[**Issue tracker: Prototyping Tools**] - -Developing (or documenting existing) tools that help with exploration and analysis. - -Two main classes: - -* **Use case analysis** — Tools that help with looking at specific use cases installed in various context such as an empty root, the Fedora base container image, or the "Fedora Minimal" installation, and finding ways how to optimize the size. Visualising the dependency tree, showing sizes of various parts, offering alternative packages as dependencies from the Fedora repos and showing the impact of choosing an alternative, potentially even showing dependencies on the file level and suggesting package splits in cases a tiny portion of an otherwise large package is used as a dependency, etc. -* **Monitoring and feedback** — Monitoring the sizes of relevant use cases over time as new versions of packages are built, reporting potential size increases. Also monitoring for specific dependencies that have been removed in the past but could come back, and reporting those. - - -== Ecosystems exploration - -https://pagure.io/minimization/issues?status=Open&tags=Focus+Area%3A+Ecosystems+Exploration&close_status=[**Issue Tracker: Ecosystems Exploration**] - -Identifying specific use cases (specific package installations) to optimize. Comparing Fedora with other ecosystems for reference. - -Talking to other groups in Fedora such as https://docs.fedoraproject.org/en-US/iot/[IoT] and finding what use cases are relevant for them to minimize, what their goals are, and helping them with minimization. - -There are also many different ecosystems other than Fedora — other linux distributions, various container images, etc. We’ll look at those to compare what sizes and features are available in the universe. This will help us get a better idea about where we stand, and what our goal should be. - - -== Use case analysis - -https://pagure.io/minimization/issues?status=Open&tags=Focus+Area%3A+Use+Case+Analysis&close_status=[**Issue Tracker: Use Case Analysis**] - -Digging into dependency trees of specific use cases (specific package installations), and finding ways for potential minimization. - -Important part of this will be working closely together with the maintainers as they are the subject matter experts. - -== Content strategy - -https://pagure.io/minimization/issues?status=Open&tags=Focus+Area%3A+Content+Strategy&close_status=[**Issue Tracker: Content Strategy**] - -Keeping the world up-to-date about our efforts is an essential part of this objective. We need to have a simple content strategy to make sure that there is information flowing consistently. - -We need to consider readers with various amouts of time and levels of interest. \ No newline at end of file diff --git a/modules/ROOT/pages/communication.adoc b/modules/ROOT/pages/communication.adoc deleted file mode 100644 index 5d3dcae..0000000 --- a/modules/ROOT/pages/communication.adoc +++ /dev/null @@ -1,15 +0,0 @@ -= Discussing & Tracking Minimization - -**Instant messaging**:: - IRC #fedora-devel at FreeNode is the default channel to discuss things live. - -**Mailing list**:: - https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org/[Fedora Devel mailing list]. This list is used to discuss many other technical topic in Fedora, and therefore has a large audience. That's why we use it to discuss larger topics that require broader attention. - -**Issue tracker**:: - https://pagure.io/minimization/issues[Minimization issue tracker] on Pagure. The idea behind this tracker is to keep track of things we're looking at or want to look at. - -**Fedora package changes**:: - https://bugzilla.redhat.com/show_bug.cgi?id=1734342[Tracker bug 1734342] in Bugzilla. We block this bug with other bugs that are relevant to the effort. That way we can see what's going on. - -Minimization is not completely centralized effort — work is happening (and is discussed and tracked) at many different places such as upstream issue trackers, mailing lists, forums, meetings, etc. Many of those referenced in in our Minimization issue tracker. \ No newline at end of file diff --git a/modules/ROOT/pages/discoveries.adoc b/modules/ROOT/pages/discoveries.adoc deleted file mode 100644 index 0f880bf..0000000 --- a/modules/ROOT/pages/discoveries.adoc +++ /dev/null @@ -1,64 +0,0 @@ -= Discoveries - -This page contains random discoveries that we make. We'll bring some structure to this page as we go. - -== Techniques - -=== dnf - -* --nodocs or --setopt=tsflags=nodocs -** Average shrink is 5 to 10M -* --setopt=install_weak_deps=false -** Depending on the package could shrink alot, could shrink nothing -** Can remove some functionality -* install glibc-minimal-langpack -** Average shrink is 200M -** Can remove some language based functionality - -== Packages - -These headings can/should be changed. They are what they currently are just for placeholders. - -=== Investigating Minimization - -* httpd -** Remove systemd from main package -** https://src.fedoraproject.org/rpms/httpd/pull-request/7 -*** /usr/sbin/apachectl requires /usr/bin/systemctl so this will require some package/subpackage shuffling. -* nginx -** Remove systemd from main package -** https://src.fedoraproject.org/rpms/httpd/pull-request/5 -* mariadb -** Drop perl ? -*** The two perl scripts in mariadb (mysqlaccess and mysql_find_rows) and might be considered being moved to a sub-package -client-utils, similiar to the perl scripts in -server-utils. -** Drop systemd ? -*** The mariadb containers start with run-mysqld. systemd is not involved at all. -** https://bugzilla.redhat.com/show_bug.cgi?id=1753696 -* postgresql -** Drop systemd ? -* systemd -** Can we pull it out of more package dependencies -** https://pagure.io/minimization/issue/2 -** Systemd is in all Fedora containers due to a bug in anaconda. Although the bug has been fixed, updating the koji image builders still hasn't happened. -* polkit -** Currently depends on mozjs60 -*** It's rather large, (25M - 30M) can it be removed from some package dependencies ? -*** Possibly use duktape instead of mozjs -*** Request for information has been sent out, no replies yet. -* perl -** It's rather large, can it be removed from some package dependencies ? - -=== Finished Investigation - -* dnf [changed] -** removed systemd as a dependency. Dropped container size by 30M. -* anaconda-core [not-changed] -** Can we shift flatpack-libs dependency to anaconda-gui ? -** https://src.fedoraproject.org/rpms/anaconda/pull-request/5 -*** No, it needs to be where it is. - -== External Articles - -* Building tiny container images: https://opensource.com/article/18/7/building-container-images -* Creating small containers with Buildah: https://opensource.com/article/18/5/containers-buildah -* Buildah images not so small?: https://github.com/containers/buildah/issues/532 diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc deleted file mode 100644 index f53b812..0000000 --- a/modules/ROOT/pages/index.adoc +++ /dev/null @@ -1,96 +0,0 @@ -= Fedora Minimization Objective - -While Fedora is well suited for traditional physical/virtual workstations and servers, it is often overlooked for use cases beyond traditional installs. - -Some modern types of deployments — such as IoT and containers — are quite sensitive to size. For IoT that's usually slow data connections (for updates/management) and for cloud and containers it's the massive scale. - -A specific example is Systemd — while being very useful (everybody loves Systemd) and is always present on physical systems, it is rarely needed in containers. So it wasn't a problem for packages to require Systemd just for __systemd-sysusers__ to create users. However, in containers, that means a significant size increase. - -Besides that, basically all types of deployments benefit from a reduced size, as there is a direct relationship between the installation footprint and attacks surface & relevant CVEs. - -=== Vision - -Thousands of individual and corporate contributors collaborate in the Fedora community to explore new problems and to build a fast-moving modern OS with a rich ecosystem allowing them to experiment on modernising their infrastructure. - -=== Mission - -Helping open source developers, sysadmins, and Linux distribution maintainers to focus on what's relevant for them. - -=== Outcomes - -Fedora is a popular platform because its ecosystem is both cutting-edge and well optimized for modern deployments such as IoT and containers. That makes many people use Fedora rather than to build and assemble their own artifacts directly from upstream projects. And that relieves the pressure on open source developers caused by users who would otherwise ask for their specific security and other issues to be fixed quickly. - -So: - -* Open source developers can focus on feature development -* Sysadmins can easily consume pre-built bits that also get regular updates -* Fedora contributors (vendors and individuals) can collaborate within the Fedora community on exploring and developing open source solutions to problems of the future - -=== Outputs - -Specific use cases are defined in Fedora. The community then focuses on those use cases with development and maintenance, optimisation (like minimisation), and testing (like CI and gating). These use cases can be transparently prioritized for infrastructure resources based on community interests. - -Feedback Pipeline actively monitors each use case and records the size and the dependencies required for it to run. Data history is kept and shown to see changes over time. And to keep things small over time, Feedback Pipeline also automatically detects size increases and potentially automatically opens Bugzilla bugs to track/fix/justify such increases transparently. - -An active focus on minimization means that our maintainers produce size-optimised content with the same or lower amount of effort. Tooling, services, and data help them to make the right decision about dependencies easily, and to keep things smaller over time. - -=== Actions - -**Identify relevant use cases** and allow the community (meaning not just the Minimization Team) to define their own. We think of a use case as a set of packages installed in a specific context, having a specific purpouse — such as __Apache HTTP Server Container__. Define use cases at least for: - -* __httpd__ -* __nginx__ -* __MariaDB__ -* __PostgreSQL__ -* __Fedora IoT__ -* __Python 3__ - -Also, consider looking at container-native use cases, such as: - -* __GO for container apps__ -* __Rust for container apps__ -* __Quarkus__ - -Collect specific use cases by talking to people at tech events, internet forums, and any other viable venues. - -**Extend monitoring services** (Feedback Pipeline) that: - -* Visualize dependencies and a total size for each use case -* Monitor size changes over time -* Auto-detect large size changes -* Notifies maintainers about unexpected size increases - -Other than features, we also need to: - -* write tests to significantly simplify contribution -* do performance optimizations for the service to scale well -* explore the use of CI and Rawhide Gating - -Being able to see what's going on is a prerequisite of implementing any changes. Seeing all the relevant opportunities helps us to focus on the ones having the most impact, and a transparent tracking helps us prove the usefulnes of our work, and to further focus on the most impactful activities. - -**Minimize** the installation size of the use cases by optimizing RPM dependencies, features, software architecture, and other factors. Specifically, look for: - -* Unnecessary RPM dependencies (although there probably won't be many) -* Multiple implementations of the same functionality required by various packages — try to make them use the same one -* Context-specific requirements — such as requiring Systemd on traditional deployments being fine vs. requiring it in containers means significant size increases. Leverage weak dependencies in those cases (that might require code changes). -* Dependnecies on large things while only using a fraction of the functionality — such as requiring the whole Perl stack to run a single script — such script can be rewritten to Python which is everywhere mostly because of DNF - -**Engage with upstream developers** regarding bigger changes in packaging and architecture. An example is Systemd and splitting the __systemd-sysuser__ package. - -**Implement process and policy changes** reflecting bigger, more general changes. Again, a good example is using Systemd in containers, or the general issue of creating users in containers. - -**Provide guidance** for the Fedora community in form of blog posts, videos, and conference talks. Even though we might have guidelines and policies in place, spreading the word is always important. - -=== Resources and Inputs - -Cloud resources to prototype services. We are not going to change the existing Fedora infrastructure in any way before whatever we develop proves useful and worth the hustle of stabilization and changing production. - -No existing Fedora Infra or Release Engineering resources are needed at the moment. However, we might need help with setting up (or getting access to) the cloud resources. - -Active support from our maintainers, the FPC, and other community members is definitely needed. This is obviously not something we can "request", but it's still a necessary input. - -=== Guiding Principles - -**Usefulness over size**: There is a balance between the usefulness and size. We take that in mind and will not implement drastic changes that would prevent our users from using Fedora. However, nothing prevents us from producing additional very specific and mininal artifacts. - -**Using RPM**: We're doing this with RPM. We're not achieving minimization by deleting files after installation. This might be obvious, but still worth mentioning. diff --git a/modules/ROOT/pages/status.adoc b/modules/ROOT/pages/status.adoc deleted file mode 100644 index 154150f..0000000 --- a/modules/ROOT/pages/status.adoc +++ /dev/null @@ -1,50 +0,0 @@ -= Minimization Objective Status - -include::project:dashboard:page$objectives/minimization.adoc[] - -== Updates on the Devel list - -Regular updates are posted to the https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[Fedora Devel mailing list]: - -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/N6LGANSTRGWU5I7NDDRFAEBDTDEL32A3/[Friday, 15 November 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/SRNQMG2XCXXPEYGZ3QUDS6UF67T2ZLJU/[Wednesday, 30 October 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/DBLD5XO52YVEYRLZR6NQJHTMCNO5GGN2/[Thursday, 3 October 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/DNGGW7QCWXQACVTJDMLHTQRR53LXRROX/[Wednesday, 25 September 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/74RI2KYXCPS7GU52GPZDSNRQ535QLFNC/[Wednesday, 18 September 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ANW4DMWWDH3XKBQYAAQ34GVH6IKACZQZ/[Wednesday, 11 September 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/N34HGDSMQWNTXOJVDT7CPNCNKONQNZ74/[Wednesday, 4 September 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WSIWZOAOY5QM23G4AP5ITIIA7I7I3Q5M/[Wednesday, 28 August 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/2QB42MDK354LWI44BRCQHRXUB6B6QCNX/[Wednesday, 21 August 2019] -* https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/QIX5LJJF4X6HKZXOQMKEIORRTK7ZIAN7/[Friday, 2 August 2019] - -== First Phase Accomplishments - -See the https://docs.fedoraproject.org/en-US/minimization/status/[status page] for detailed info and historic weekly updates. Summary below. - -**Better understanding** — Yes, we now have much better understanding of the problem and a better, more specific idea about the next steps. - -https://minimization.github.io/reports/[**Feedback Pipeline**] — A service that monitors use cases for size and dependencies. Includes various views in tables and interactive dependency graphs. - -**Systemd and containers** — We dag into the issue of Systemd vs. containers, especially for packages requiring it just to create users in containers using __systemd-sysuser__. Working with upstream on splitting the package out. Thought about, but not yet proposed, a wider policy around this. - -* Mailing list discussion: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/6YX6CEFBPU3XVZZEHTN6CBH2F7JDF35N/#EJD4BNBE52JTEOPKAT6HFOO4HVUPBTCH -* Ticket: https://pagure.io/minimization/issue/13 - -Policy thinking: - -* A - If systemd is only needed to start services, a package should only -"Recommend" systemd. This will allow containers to install the -package without systemd. -* B - If a program is just using a library of systemd, only require -systemd-libs. Example: libusb -* C - If a package wants to use systemd-sysusers to create users/groups, -only require systemd-sysusers. (NOTE: This subpackage isn't -implemented yet) - -**initial-setup** — If an image is built without users, there needs to be some way to add a user at startup. initial-setup does a good job of that, but at the expense of size. It pulls in anaconda-tui and anaconda-core. Those two packages then commence to pull in alot of other, rather large, packages. This is for the IoT images, as well as others. -We currently do not have a recommendation, but it is being worked on. - -**Use pcre2 instead of pcre** — The minimization effort is trying to trim -things down to just one pcre, and that is pcre2. - -**Polkit and mozjs60** — Let's expain this one with a terrible analogy! Polkit is this lovely person (.5M) that rings your doorbell and says they will wash the windows of your house. After you agree, they bring out their elephant (mozjs60 30M) and use it to spray your windows with water. Polkit pulls in mozjs60, which is a rather large package. So, we're trying to sort this one out, too. \ No newline at end of file diff --git a/modules/ROOT/pages/team.adoc b/modules/ROOT/pages/team.adoc deleted file mode 100644 index 1340549..0000000 --- a/modules/ROOT/pages/team.adoc +++ /dev/null @@ -1,60 +0,0 @@ -= Contributing to Minimization - -Are you interested in minimizing the installation footprint various Fedora bits and pieces? Are you interested in contributing? Or perhaps already working on something and want to make it more visible? Then you're at the right place! - -== What to contribute - -The main areas of contribution include: - -=== Collecting use cases and problems - -Help us make sure we work on stuff that's relevant to people. Both Fedora users and others who might become Fedora users. Talk to people at events, online forums, or anywhere, really. Ask them on how they run stuff, what pain points they experience, or what would they like to see. - -=== Optimizing Fedora packaging - -Look at the use cases and problems we've collected and see if there are ways to minimize them by optimizing the packaging. That might include cutting off unnecessary dependencies, switching common dependencies to a single implementation, or even proposing policy changes about packaging. - -=== Working with upstream communities - -Many changes go beyond Fedora. Are there any potential code changes that could help us? Or anything that requires coordination upstream? Reach out to upstream communities, offer help, build connections with the members, and help make bigger changes. - -=== Developing tools and services - -Ask our maintainers and developers if there's anything in their minimization-related workflows that could use some automation or a tool, and help develop that. That goes for both making things smaller, as well as keeping them small over time. - -=== Looking at alternative approaches - -Look at other Linux distributions, repositories, container images, and other solutions, and compare them with Fedora. Anything they do differently? Maybe even better? What could we experiment with and learn about? - -=== Promoting Minimization and Fedora - -Being visible helps us get more feedback, more contributors, and to do a better overall progress. Write blog posts about cool things that are happening, about interesting problems we're solving, or about examples of using Fedora in various use cases. Submit talks at events, write on social media, make videos, etc. - - -== How to join - -If you want to be a listed member of this group, please https://pagure.io/minimization/new_issue[open an issue], introduce yourself, and tell us how you want to help. - -But you don't need to be a formal team member to contribute. We also welcome ocasional contributions from the whole Fedora community. Just reach out through one of the xref:communication.adoc[communication channels]. - -== Current members - -Adam Samalik (asamalik) — objective lead - -Peter Robinson (pbrobinson) - -Zbigniew Jędrzejewski-Szmek (zbyszek) - -Felipe Borges (feborges) - -Neal Gompa (ngompa) - -Christian Glombek (lorbus) - -Michel Alexandre Salim (salimma) - -Troy Dawson (tdawson) - -Igor Gnatenko (ignatenkobrain) - -Jun Aruga (jaruga) diff --git a/modules/ROOT/pages/tools.adoc b/modules/ROOT/pages/tools.adoc deleted file mode 100644 index bbaa6d0..0000000 --- a/modules/ROOT/pages/tools.adoc +++ /dev/null @@ -1,18 +0,0 @@ -= Tools & Services for Minimization - -== Feedback Pipeline service - -Reporting and notifications regarding dependencies and sizes of defined RPM installations. - -https://minimization.github.io/reports/[**minimization.github.io/reports**] - -== rpm-showme tool - -Dependency visualisation of an RPM-based installation (a system, an image, etc.) - -Source: https://pagure.io/minimization/rpm-showme - -The script takes a file path or a container image name as an input, and generates a graph of packages and their relations including sizes of all individual packages and some basic clustering. Clicking on a package highlights its relations to other packages. - - - diff --git a/nginx.conf b/nginx.conf deleted file mode 100644 index f7093b3..0000000 --- a/nginx.conf +++ /dev/null @@ -1,14 +0,0 @@ -server { - listen 80; - server_name localhost; - - location / { - root /antora/public; - index index.html index.htm; - } - - error_page 500 502 503 504 /50x.html; - location = /50x.html { - root /usr/share/nginx/html; - } -} diff --git a/preview.sh b/preview.sh deleted file mode 100755 index acc52af..0000000 --- a/preview.sh +++ /dev/null @@ -1,18 +0,0 @@ -#!/bin/sh - -if [ "$(uname)" == "Darwin" ]; then - # Running on macOS. - # Let's assume that the user has the Docker CE installed - # which doesn't require a root password. - echo "The preview will be available at http://localhost:8080/" - docker run --rm -v $(pwd):/antora:ro -v $(pwd)/nginx.conf:/etc/nginx/conf.d/default.conf:ro -p 8080:80 nginx - -elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then - # Running on Linux. - # Fedora Workstation has python3 installed as a default, so using that - echo "" - echo "The preview is available at http://localhost:8080" - echo "" - cd ./public - python3 -m http.server 8080 -fi diff --git a/site.yml b/site.yml deleted file mode 100644 index b6d6557..0000000 --- a/site.yml +++ /dev/null @@ -1,21 +0,0 @@ -site: - title: Local Preview - start_page: minimization::index -content: - sources: - - url: . - branches: HEAD -ui: - bundle: - url: https://asamalik.fedorapeople.org/ui-bundle.zip - snapshot: true - default_layout: with_menu - #supplemental_files: ./supplemental-ui -output: - clean: true - dir: ./public - destinations: - - provider: archive -runtime: - pull: true - cache_dir: ./cache