[Replicant] [www.replicant.us] [PATCH 2/2] about.php: FAQ: Add an entry about where the origin of Replicant name
Denis 'GNUtoo' Carikli
GNUtoo at cyberdimension.org
Wed Apr 28 17:30:48 UTC 2021
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo at cyberdimension.org>
---
about.php | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/about.php b/about.php
index e3147f8..a13f833 100644
--- a/about.php
+++ b/about.php
@@ -264,6 +264,35 @@
</p>
</div>
</div>
+
+ <div class="panel panel-default" id="replicant-name">
+ <div class="panel-heading">
+ <h3 class="panel-title">
+ Where does the Replicant name comes from?
+ </h3>
+ </div>
+ <div class="panel-body">
+ <p>
+ One of the goals initial of projects like GNU or ReactOS was to
+ replace nonfree operating systems, like Unix and Microsoft Windows.
+ To do that they could not simply reuse the nonfree operating system
+ source code as it wasn't free software, so they had to write their
+ own code and reuse other available free software components.<br />
+ <br />
+ With Android the situation was much easier because even if many
+ drivers were not free software, most of the operating system source
+ code was available.<br />
+ <br />
+ So with way less effort, we could have an exact Replica of Android
+ with the same graphical interface and so on. We just had to replace
+ these nonfree drivers.<br />
+ <br />
+ When trying to find a project name, "Replicant" looked neat as not
+ only we were Replicating Android, but the name was also loosely
+ related to Android as in Blade Runner, Replicants are also Androids.
+ </p>
+ </div>
+ </div>
</div>
<div class="col-md-3">
@@ -301,6 +330,9 @@
Why doesn't Replicant guide users through installing complementary
proprietary components?
</a>
+ <a href="#replicant-name" class="list-group-item">
+ Where does the Replicant name comes from?
+ </a>
</div>
</div>
</div>
--
2.31.1
More information about the Replicant
mailing list