1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
|
#use wml::debian::template title="Debian derivatives"
<p>
There are a <a href="#list">number of distributions</a> based on Debian.
Some people might want to take a look at these distributions <em>in addition to</em> the official Debian releases.
</p>
<p>
A Debian derivative is a distribution that
is based on the work done in Debian but
has its own identity, goals and audience and
is created by an entity that is independent from Debian.
Derivatives modify Debian to achieve the goals they set for themselves.
</p>
<p>
Debian welcomes and encourages organisations that want to develop new distributions based on Debian.
In the spirit of Debian's <a href="$(HOME)/social_contract">social contract</a>,
we hope derivatives will contribute their work to Debian and upstream projects,
so that everyone can benefit from their improvements.
</p>
<h2 id="list">Which derivatives are available?</h2>
<p>
We would like to highlight the following Debian derivatives:
</p>
## Please keep this list sorted alphabetically
## Please only add derivatives that meet the criteria below
<ul>
<li>
<a href="https://grml.org/">Grml</a>:
live system for system administrators.
<a href="https://wiki.debian.org/Derivatives/Census/Grml">More info</a>.
</li>
<li>
<a href="https://www.kali.org/">Kali Linux</a>:
security auditing and penetration testing.
<a href="https://wiki.debian.org/Derivatives/Census/Kali">More info</a>.
</li>
<li>
<a href="https://pureos.net/">Purism PureOS</a>:
<a href="https://www.fsf.org/news/fsf-adds-pureos-to-list-of-endorsed-gnu-linux-distributions-1">FSF-endorsed</a>
rolling release, focused on privacy, security and convenience.
<a href="https://wiki.debian.org/Derivatives/Census/Purism">More info</a>.
</li>
<li>
<a href="https://tails.boum.org/">Tails</a>:
preserve privacy and anonymity.
<a href="https://wiki.debian.org/Derivatives/Census/Tails">More info</a>.
</li>
<li>
<a href="https://www.ubuntu.com/">Ubuntu</a>:
popularising Linux around the world.
<a href="https://wiki.debian.org/Derivatives/Census/Ubuntu">More info</a>.
</li>
</ul>
<p>
In addition, distributions based on Debian are listed in the
<a href="https://wiki.debian.org/Derivatives/Census">Debian derivatives census</a>
as well as in <a href="https://wiki.debian.org/Derivatives#Lists">other places</a>.
</p>
<h2>Why use a derivative instead of Debian?</h2>
<p>
If you have a specific need which is better served by a derivative,
you might prefer using it instead of Debian.
</p>
<p>
If you are part of a specific community or group of people and
there is a derivative for that group of people,
you might prefer using it instead of Debian.
</p>
<h2>Why is Debian interested in derivatives?</h2>
<p>
Derivatives bring Debian to a larger number of people with more diverse
experiences and requirements than the audience we currently reach.
By developing relationships with derivatives,
<a href="https://wiki.debian.org/Derivatives/Integration">integrating</a>
information about them into Debian infrastructure and
merging changes they have made back into Debian, we
share our experience with our derivatives,
expand our understanding of our derivatives and their audiences,
potentially expand the Debian community,
improve Debian for our existing audience and
make Debian suitable for a more diverse audience.
</p>
<h2>Which derivatives will Debian highlight?</h2>
## Examples of these criteria are in the accompanying README.txt
<p>
The derivatives highlighted above have each met most of these criteria:
</p>
<ul>
<li>actively cooperate with Debian</li>
<li>are actively maintained</li>
<li>have a team of people involved, including at least one Debian member</li>
<li>have joined the Debian derivatives census and included a sources.list in their census page</li>
<li>have a distinguishing feature or focus</li>
<li>are notable and established distributions</li>
</ul>
<h2>Why derive from Debian?</h2>
<p>
It can be faster to modify an existing distribution like Debian than starting from scratch since
a packaging format, repositories, base packages and other things are specified and usable.
A lot of software is packaged so there is no need to spend time packaging most things.
This allows derivatives to focus on the needs of a specific audience.
</p>
<p>
Debian ensures that what we distribute is <a href="$(HOME)/intro/free">free</a>
for derivatives to modify and redistribute to their audience.
We do this by checking the licenses of software we distribute
against the <a href="$(HOME)/social_contract#guidelines">Debian Free Software Guidelines (DFSG)</a>.
</p>
<p>
Debian has a number of different <a href="$(HOME)/releases/">release</a> cycles
available for derivatives to base their distribution on.
This allows derivatives to
try <a href="https://wiki.debian.org/DebianExperimental">experimental</a> software,
move really <a href="$(HOME)/releases/unstable/">fast</a>,
update <a href="$(HOME)/releases/testing/">often</a> with quality assurance,
have a <a href="$(HOME)/releases/stable/">solid base</a> for their work,
use <a href="https://backports.debian.org/">newer</a>
software on top of a solid base,
enjoy <a href="$(HOME)/security/">security</a> support and
<a href="https://wiki.debian.org/LTS">extend</a> that support.
</p>
<p>
Debian supports a number of different <a href="$(HOME)/ports/">architectures</a>
and contributors are <a href="https://wiki.debian.org/DebianBootstrap">working</a>
on methods of automatically creating new ones for new processor types.
This allows derivatives to use the hardware of their choice
or to support new processor designs.
</p>
<p>
The Debian community and people from existing derivatives are available
and willing to help guide new distributions in their work.
</p>
<p>
Derivatives are created for a number of reasons, such as
translation to new languages,
specific hardware support,
different installation mechanisms or
supporting a particular community or group of people.
</p>
<h2>How to derive from Debian?</h2>
<p>
Derivatives can use parts of Debian's infrastructure if needed (like repositories).
Derivatives should change references to Debian (like the logo, name, etc.)
and to Debian services (like the website and BTS).
</p>
<p>
If the goal is to define a set of packages to install,
creating a <a href="$(HOME)/blends/">Debian blend</a>
could be an interesting way to do that within Debian.
</p>
<p>
Detailed development information is available in the
<a href="https://wiki.debian.org/Derivatives/Guidelines">guidelines</a> and
guidance is available from the
<a href="https://wiki.debian.org/DerivativesFrontDesk">front desk</a>.
</p>
|
