Add files via upload
This commit is contained in:
parent
0bc9c68664
commit
3047d3d440
7 changed files with 358 additions and 0 deletions
45
content/about.md
Normal file
45
content/about.md
Normal file
|
|
@ -0,0 +1,45 @@
|
|||
---
|
||||
title: About
|
||||
date: "2025-01-08T20:00:00+09:00"
|
||||
draft: false
|
||||
---
|
||||
|
||||
# About Dragon Linux
|
||||
|
||||
Dragon Linux is a project with the goal of making a simple and easy to use Linux experience with support for various hardware from all kinds of life.
|
||||
|
||||
Dragon Linux is developed by a thriving community of free and open source software developers.
|
||||
|
||||
## The name
|
||||
|
||||
Theming around the mystical world of dragons 日本の龍 (*nihon no ryu*) is something new, and not seen before in the world of Linux.
|
||||
|
||||
## The logo
|
||||
|
||||
<img src="/img/merge/dragon1.png" alt="Dragon Linux logo" width="100">
|
||||
|
||||
The Dragon Linux logo is a modified work of a clipart designed by [ClipArtBest](https://www.clipartbest.com/clipart-7cao4M6gi). The Dragon Linux website is based on the Asahi Linux website designed by [soundflora*](https://soundflora.tokyo).
|
||||
|
||||
<img src="/img/AsahiLinux_kawaii_logo.png" alt="Kawaii Asahi Linux logo" width="100">
|
||||
|
||||
# FAQ
|
||||
|
||||
## What devices are/will be supported?
|
||||
|
||||
All AMD, and Intel devices are in scope, as well as future generations as development time permits. We currently have support for most machines and some legacy machines. Check out our [feature support page](/ubuntu/#device-support) for the most up-to-date information.
|
||||
|
||||
## Is this a Linux distribution?
|
||||
|
||||
Dragon Linux is a [unoffical remix of Ubuntu Linux](/ubuntu), and serves as both a polished end-user distribution and a reference for other distributions who wish to incorporate our work.
|
||||
|
||||
## How will this be released?
|
||||
|
||||
All development takes place on GitHub, [github.com/VenithNET](https://github.com/VenithNET). We write our contributions with the intent to upstream them into the respective upstream projects. Code will be dual-licensed as the upstream license (e.g. GPL) and a permissive license (e.g. MIT), to ensure that the work can be reused in other OSes where possible.
|
||||
|
||||
## Who is working on Dragon Linux?
|
||||
|
||||
Dragon Linux is a community, and everyone is invited to contribute. If you are interested in contributing, check out our [contribute page](/contribute)!
|
||||
|
||||
Current major contributors are:
|
||||
|
||||
* [Matthew Pitsicalis](https://home.venith.net/), the founder of Dragon Linux. Matthew is a Linux nerd known for his work on various projects.
|
||||
16
content/blog/2025/09/the-dragons-have-arisen.md
Normal file
16
content/blog/2025/09/the-dragons-have-arisen.md
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
+++
|
||||
date = "2025-09-06T09:00:00+10:00"
|
||||
draft = false
|
||||
title = "Progress Report: Dragon Linux [6.1]"
|
||||
slug = "the-dragons-have-arisen"
|
||||
author = "Matthew Pitsicalis"
|
||||
+++
|
||||
|
||||
## The Dragons have arisen!
|
||||
|
||||
Dragon Linux 6.1 is now released!
|
||||
|
||||
## Release Notes
|
||||
|
||||
We plan to make new releases of Dragon Linux on every new Ubuntu release.<br> Example [Ubuntu 25.04 -> 25.10]<br>
|
||||
While we do NOT have a built in updater to go between versions like Mint does, you can always apt upgrade.
|
||||
51
content/code-of-conduct.md
Normal file
51
content/code-of-conduct.md
Normal file
|
|
@ -0,0 +1,51 @@
|
|||
---
|
||||
title: Code of Conduct
|
||||
date: "2021-01-05T20:00:00+09:00"
|
||||
draft: false
|
||||
---
|
||||
|
||||
# Dragon Linux Code of Conduct
|
||||
|
||||
Like many Open Source projects and the greater FLOSS community, Dragon Linux is a collaborative open source community comprised of a diverse group of contributors and users from around the globe. We find the contributions, collaborations, and mentorships within our community to be the essential lifeblood of our project and appreciate the efforts of those who participate to nurture and grow those, and all other aspects of our community.
|
||||
|
||||
However, when a large and sufficiently diverse group of people work together, there are often cultural, communication, and compatibility issues. In order to minimize conflict, and provide a framework for resolution, we have a brief code of conduct that we ask all participants in the Dragon Linux community adhere to. These rules should apply to everyone, regardless of station within the community, and anyone can serve to remind, or ask the board to help resolve issues.
|
||||
|
||||
No list is ever exhaustive, so we encourage members of the Dragon Linux community to adhere to the spirit, rather than the letter, of this code, as that is how it will be enforced. Places where this code may be particularly applicable are GitHub issues and pull requests, IRC, Matrix, mailing lists, Fediverse discussions broadly directed at or between members of the community, and other direct interactions within the community. Any violations, especially continued or flagrant offenses, may affect an individual’s (or organization’s) ability to participate within the Dragon Linux community.
|
||||
|
||||
If you feel that someone is in violation of the code of conduct, whether in letter or in spirit, we request that you email as detailed a description as possible of the offense and offending party/parties to [the board](mailto:mattthetekie@venith.net). If you have questions, concerns, or any other inquiries please feel free to contact the board.
|
||||
|
||||
A large fraction of Dragon Linux consists of contributions to upstream projects. All Dragon Linux contributors are expected to adhere to the respective upstream Codes of Conduct when interacting with such projects, or developing code intended for upstreaming.
|
||||
|
||||
## Rules
|
||||
|
||||
1. **Be friendly and patient.** We were all new or suffered from a lack of knowledge at one point in time. Please try to remember what it felt like to be on that end, and treat people accordingly.
|
||||
|
||||
2. **Be welcoming.** We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
|
||||
|
||||
3. **Be helpful.** By helping others to learn our entire ecosystem is enriched. We encourage members of the Dragon Linux community to mentor each other and help to raise the general level of knowledge in the community whenever possible.
|
||||
|
||||
4. **Be considerate.** Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we’re a world-wide community, so you might not be communicating in someone else’s primary language.
|
||||
|
||||
5. **Be respectful.** Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the Dragon Linux community should be respectful when dealing with other members as well as with people outside the Dragon Linux community.
|
||||
|
||||
6. **Be careful in the words that you choose.** We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behavior aren’t acceptable. This includes, but is not limited to:
|
||||
* Violent threats or language directed against another person.
|
||||
* Discriminatory jokes and language.
|
||||
* Posting sexually explicit or violent material.
|
||||
* Posting (or threatening to post) other people’s personally identifying information (“doxing”), regardless of whether it is publicly available.
|
||||
* Personal insults, especially those using racist, sexist, or otherwise discriminatory terms.
|
||||
* Deliberately referring to others by names or pronouns counter to their identity.
|
||||
* Unwelcome sexual attention.
|
||||
* Advocating for, or encouraging, any of the above behavior.
|
||||
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
|
||||
|
||||
7. **When we disagree, try to understand why.** Disagreements, both social and technical, happen all the time and Dragon Linux is no exception. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of Dragon Linux comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.
|
||||
|
||||
## Consequences
|
||||
|
||||
1. Except in flagrant or otherwise egregious cases, the first infraction will result in a verbal warning. Everyone slips up or acts out of frustration at times, we just ask that you work to not repeat the behavior.
|
||||
2. A second infraction (or more flagrant first offense, as determined by the board) will have an anonymized summary of the interaction published as a way to educate the community and serve as a reminder that adverse behavior will not be tolerated.
|
||||
3. A third infraction (or especially egregious first offense, as determined by the board) will result in temporary suspension from all avenues of Dragon Linux community participation for 4 weeks. This will include, but is not limited to, Discord, and GitHub issues/PRs.
|
||||
4. Continued infractions will be dealt with on a case-by-case basis, but could result in permanent suspension from the Dragon Linux community.
|
||||
|
||||
This text is adapted from the [Ceph Code of Conduct](https://ceph.io/community/code-of-conduct/), which itself credits [Django Project](https://www.djangoproject.com/conduct/) for the original inspiration of this document and the [Ada Initiative](https://adainitiative.org/) for expanding the fight for equality and civility within FLOSS communities and beyond.
|
||||
25
content/community.md
Normal file
25
content/community.md
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
---
|
||||
title: Community
|
||||
date: "2025-01-08T20:00:00+09:00"
|
||||
draft: false
|
||||
---
|
||||
|
||||
# Community
|
||||
|
||||
If you're interested in the project, you're welcome to drop by! Check out [ways in which you can contribute](/contribute).
|
||||
|
||||
Please remember that all community members are expected to abide by our [Code of Conduct](/code-of-conduct).
|
||||
|
||||
## Discord
|
||||
|
||||
Most development and project discussion takes place on Discord. We have several channels on our Discord:
|
||||
|
||||
* #dragon-linux [[chat](https://discord.gg/ZTd5JEcaMz)] - General project discussion
|
||||
* #dragon-dev [[chat](https://discord.gg/ZTd5JEcaMz)] - Development discussion
|
||||
* #dragon-stream [[watch](https://www.twitch.tv/astafathersatan666_)] - Chatroom for people to talk during the devs' video streams
|
||||
|
||||
Even if you don't plan to speak, feel free to join and idle in the above channels if you'd like to follow the discussion.
|
||||
|
||||
## Mastodon (Fediverse)
|
||||
|
||||
You will also find official announcements and information on the [Dragon Linux Mastodon account](https://nerdculture.de/@astafathersatan).
|
||||
26
content/contribute.md
Normal file
26
content/contribute.md
Normal file
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
title: Contribute
|
||||
date: "2021-01-05T20:00:00+09:00"
|
||||
draft: false
|
||||
---
|
||||
|
||||
# Contribute
|
||||
|
||||
Dragon Linux is an open source project, and it would not be possible without the support of the community. We encourage contributors of all skill sets and backgrounds!
|
||||
|
||||
All contributors are expected to abide by our [Code of Conduct](/code-of-conduct) and our [Copyright policy](/copyright).
|
||||
|
||||
## New to this kind of thing?
|
||||
|
||||
Are you interested in this kind of project, but you've never worked on something like this before? We were all like that at one point! The best way to learn how a project like this works is to get involved. It might be intimidating at first, but don't worry. Join the [community channels](/community) and watch to see how things work. If you find an area which you find interesting, you can poke around yourself! If you feel like you can contribute to anything, just say so!
|
||||
|
||||
Here are some suggestions to get you started:
|
||||
|
||||
* Documentation: Reverse engineering often results in ugly brain-dump text files full of information, but we don't always have the time to clean things up into a nice wiki page. Helping out here is a good opportunity to get familiar with the subject, and you can ask questions to help shape the documentation and ensure it is accurate.
|
||||
* Verification: Notes and documentation may have mistakes or be hastily written! It is always useful to have a second set of eyes go over the information, then try things out on the operating system and see if it is correct. This is a good way to play around with the operating system and understand how things work, and help find problems along the way!
|
||||
* Testing: Does the code actually work? We need you to find out if it's broken in some way :-)
|
||||
* Completeness: There are often gaps in what we find out - what does this bit do? What happens if you do more than one thing at once? You can look at cases we haven't tested yet and help complete the documentation and code.
|
||||
|
||||
## Already been here before?
|
||||
|
||||
Feel free to jump right and help us out - there is lots of work to do. A brief introduction would be helpful so that we can get to know you better. Let us know what you are experienced with and we can point you at specific areas you can help with.
|
||||
52
content/copyright.md
Normal file
52
content/copyright.md
Normal file
|
|
@ -0,0 +1,52 @@
|
|||
---
|
||||
title: Copyright
|
||||
date: "2021-01-05T20:00:00+09:00"
|
||||
draft: false
|
||||
---
|
||||
|
||||
# Copyright policy
|
||||
|
||||
Dragon Linux is an open source project, and all contributions must follow the appropriate open source licenses.
|
||||
|
||||
These contribution rules are particularly important for code that is to be upstreamed into other projects, to maintain a clean paper trail of the licensing.
|
||||
|
||||
## Licensing
|
||||
|
||||
Code developed for Dragon Linux itself should be licensed under a permissive license that allows other projects to take advantage of the code without running into license compatibility problems. The specific licenses are subject to being decided on a case-by-case basis, but we will usually use a permissive license such as the MIT license.
|
||||
|
||||
Code developed for other open source projects must be licensed under that same project's license, and follow licensing/header/authorship conventions appropriate for that project. However, specific modules developed by Dragon Linux contributors (such as entire drivers or submodules) should be dual-licensed under a permissive license such as MIT, to ensure that they can be ported or reused within other projects.
|
||||
|
||||
For original code, we use [SPDX license identifiers](https://spdx.github.io/spdx-spec/v2.3/using-SPDX-short-identifiers-in-source-files/) to record the license of individual files in a concise way. Files should have header of this form (with whatever license information is appropriate):
|
||||
|
||||
```// SPDX-License-Identifier: GPL-2.0+ OR MIT```
|
||||
|
||||
No specific authors should be listed in source code files themselves, as this is hard to maintain and unlikely to remain accurate. For top-level and informational places where a copyright statement is needed, such as the MIT license text or "about" style dialogs, the code should be attributed to "The Dragon Linux Contributors".
|
||||
|
||||
We do not require contributors to accept any kind of CLA, nor do we require any kind of copyright assignment. You retain all copyright ownership of any code you write. These are merely conventions about how the origin of the code should be documented in version control and files.
|
||||
|
||||
## Attribution
|
||||
|
||||
Dragon Linux uses Git for managing source code, and the Git history serves as a record of authorship. The Git "Author" field should reflect the primary author of a change - if you commit a change authored by another person, you should ensure they are listed as the author. If a change is authored by multiple people, you should add one or more `Co-Developed-by: Foo Bar <foo@bar.com>` lines at the end of the commit message.
|
||||
|
||||
Non-Git releases of the software will be arranged to have an automatically generated authorship file containing a list of all Git contributors.
|
||||
|
||||
In order to certify the origin of contributions, all contributors are required to accept the Developer's Certificate of Origin 1.1:
|
||||
|
||||
> ## Developer’s Certificate of Origin 1.1
|
||||
>
|
||||
> By making a contribution to this project, I certify that:
|
||||
>
|
||||
> * The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
|
||||
> * The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
|
||||
> * The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
|
||||
> * I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
|
||||
|
||||
To certify this, add a line to the end of your Git commit message as follows:
|
||||
|
||||
```
|
||||
Signed-off-by: Random J Developer <random@developer.example.org>
|
||||
```
|
||||
|
||||
This can be automated by simply using `git commit -s`.
|
||||
|
||||
Real names are not required for authorship or sign-off info. We encourage people to use a name they are commonly known by (e.g. a name you commonly use to interact in similar spaces), as that helps establish trust.
|
||||
143
content/ubuntu.md
Normal file
143
content/ubuntu.md
Normal file
|
|
@ -0,0 +1,143 @@
|
|||
---
|
||||
title: Dragon Linux
|
||||
date: "2025-01-08T20:00:00+09:00"
|
||||
draft: false
|
||||
body_class: "landing dragon"
|
||||
layout: landing
|
||||
---
|
||||
<section id="eye-catch">
|
||||
<div>
|
||||
<div>
|
||||
<p>Introducing</p>
|
||||
<h1>Dragon Linux</h1>
|
||||
<p>The most Dragonified Linux® to exist.</p>
|
||||
<pre><a href="https://sourceforge.net/projects/sujix-linux/files/latest/download"><code id="curl">Download</code></a></pre>
|
||||
</div>
|
||||
<div>
|
||||
<img src="/img/merge/desktop.png" alt="Dragon Linux on a laptop">
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<section class="topic">
|
||||
|
||||
## <div>Ubuntu Linux 25 + Dragons = Dragon Linux</div>
|
||||
|
||||
<img width="200" class="w-200" src="/img/far_landing/ubuntu_remix.png">Dragon Linux started out as a simple hobby project to bring Linux to the masses during an era of Linux not becoming mainstream. A time where software was NOT supported across the board like it is now. Now in the modern era of Linux development we came back to revive the project. We've worked hard in order to bring you a fully integrated distro, cooperating closely to get improvements and bug fixes to users as quickly as possible.
|
||||
|
||||
With Ubuntu's excellent software and hardware support, you can expect a solid and high-quality experience without any unwanted surprises. Dragon Linux is based on Ubuntu Linux 25, the latest Ubuntu Linux release with the newest software versions across the board. We support most AMD and Intel CPU's.
|
||||
|
||||
</section>
|
||||
<section class="topic">
|
||||
|
||||
## <div>Dragon Linux ❤️ KDE Plasma</div>
|
||||
|
||||
<img width="150" class="w-150" src="/img/far_landing/kde-logo-white-blue-rounded-source.svg">We are proud to offer [KDE Plasma](https://kde.org/plasma-desktop/) as our flagship desktop environment. With leading edge Wayland support and a highly customizable experience plus wide support for many hardware features, KDE Plasma is a joy to use on systems.
|
||||
|
||||
Want to use Night Color to keep your screen from disrupting your sleep cycle? No worries, it just works. Tweak your trackpad settings for a more comfortable experience? Everything's right there in System Settings. Are things on screen too big or too small? Just adjust the display scale to your heart's content, even in 5% increments. We've worked with the KDE project to bring you bug fixes and improvements to improve platform support, and we've also built a custom Calamares-based initial setup wizard so you can be up and running in no time with minimal fuss.
|
||||
|
||||
Dragon Linux 6.1 comes with [KDE Plasma 6.3](https://kde.org/announcements/plasma/6/6.3.0/), with the latest patches and improvements to provide *the* premier desktop experience.
|
||||
|
||||
</section>
|
||||
<section class="topic">
|
||||
|
||||
## <div>Even Dragons can use it!</div>
|
||||
<img width="150" class="w-150" src="/img/merge/dragon.jpeg">Dragon Linux comes out of the box with all of the essentials like Firefox, LibreOffice, Educational Apps, Video Games, Freetube, Spotify, and a whole LOT more! Dragon Linux offers a seamless and carefree expierence. Dragon Linux also comes with offline apps such as locally hostable AI options, offline wiki's, and a whole ton more!
|
||||
|
||||
</section>
|
||||
<section id="device-support">
|
||||
<div class="center-title">
|
||||
<h1 id="device-support">Device support</h1>
|
||||
</div>
|
||||
<div class="devices">
|
||||
<a href="#" id="dev1" class="device dev-selected">
|
||||
<img src="/img/devices/macbook_air.svg">
|
||||
<p>Laptop</p>
|
||||
</a>
|
||||
<a href="#" id="dev2" class="device">
|
||||
<img src="/img/devices/imac.svg">
|
||||
<p>PC</p>
|
||||
</a>
|
||||
</div>
|
||||
<div class="device-infos">
|
||||
<div id="info-dev1" class="device-info dev-selected"><div>
|
||||
<h3>Chips</h3>
|
||||
<div class="features">
|
||||
<div class="sup">AMD</div>
|
||||
<div class="sup">Intel</div>
|
||||
<div class="unsup">ARM</div>
|
||||
<div class="unsup">RISC-V</div>
|
||||
</div>
|
||||
<h3>Features</h3>
|
||||
<div class="features">
|
||||
<div class="sup">Display</div>
|
||||
<div class="sup">Keyboard (+ Backlight)</div>
|
||||
<div class="sup">Trackpad</div>
|
||||
<div class="sup">Headset Jack</div>
|
||||
<div class="sup">Speakers</div>
|
||||
<div class="sup">Microphone</div>
|
||||
<div class="sup">Camera</div>
|
||||
<div class="sup">USB Type C</div>
|
||||
<div class="sup">Wi-Fi</div>
|
||||
<div class="sup">Bluetooth</div>
|
||||
<div class="sup">USB-C Displays</div>
|
||||
<div class="sup">Thunderbolt / USB4</div>
|
||||
</div>
|
||||
</div></div>
|
||||
<div id="info-dev2" class="device-info"><div>
|
||||
<h3>Chips</h3>
|
||||
<div class="features">
|
||||
<div class="sup">AMD</div>
|
||||
<div class="sup">Intel</div>
|
||||
<div class="unsup">ARM</div>
|
||||
<div class="unsup">RISC-V</div>
|
||||
</div>
|
||||
<h3>Features</h3>
|
||||
<div class="features">
|
||||
<div class="sup">Display</div>
|
||||
<div class="sup">Keyboard (+ Backlight)</div>
|
||||
<div class="sup">Trackpad</div>
|
||||
<div class="sup">Headset Jack</div>
|
||||
<div class="sup">Speakers</div>
|
||||
<div class="sup">Microphone</div>
|
||||
<div class="sup">Camera</div>
|
||||
<div class="sup">USB Type C</div>
|
||||
<div class="sup">Wi-Fi</div>
|
||||
<div class="sup">Bluetooth</div>
|
||||
<div class="sup">USB-C Displays</div>
|
||||
<div class="sup">Thunderbolt / USB4</div>
|
||||
</div>
|
||||
</div></div>
|
||||
</div>
|
||||
</section>
|
||||
<script>
|
||||
document.addEventListener("DOMContentLoaded", function() {
|
||||
var devs = ["dev1", "dev2", "dev3", "dev4", "dev5"];
|
||||
devs.forEach(function(dev) {
|
||||
document.getElementById(dev).onclick = function(e) {
|
||||
var el = Array.from(document.getElementsByClassName("dev-selected"));
|
||||
el.forEach(function(e) {
|
||||
if (!e.id.endsWith(dev)) {
|
||||
console.log(e.id, dev);
|
||||
e.classList.remove("dev-selected");
|
||||
}
|
||||
})
|
||||
document.getElementById(dev).classList.toggle("dev-selected");
|
||||
document.getElementById("info-" + dev).classList.toggle("dev-selected");
|
||||
e.preventDefault();
|
||||
};
|
||||
});
|
||||
var btn = document.getElementById("copy-button");
|
||||
btn.onmouseover = function(e) {
|
||||
btn.firstChild.classList.remove("fa-check");
|
||||
btn.firstChild.classList.add("fa-clipboard");
|
||||
}
|
||||
btn.onclick = function(e) {
|
||||
var text = document.getElementById("curl");
|
||||
window.getSelection().selectAllChildren(text);
|
||||
navigator.clipboard.writeText(text.textContent);
|
||||
btn.firstChild.classList.add("fa-check");
|
||||
btn.firstChild.classList.remove("fa-clipboard");
|
||||
e.preventDefault();
|
||||
};
|
||||
});
|
||||
</script>
|
||||
Loading…
Add table
Add a link
Reference in a new issue