Relationship With Upstream

From Kicksecure
< Dev
Revision as of 15:13, 19 February 2022 by Nurmagoz (talk | contribs)
Jump to navigation Jump to search

Summary

For various reasons Kicksecure tries to diverge by the smallest possible amount from its upstream projects, and especially from Debian:

  • wants to share his work with the rest of the Free Software community.
  • values maintainability very much: believe users are best served if keep the amount of work needed to maintain Kicksecure the smallest possible.
  • Focus on low-effort maintainabilityarchive.org iconarchive.today icon

How

Debian specific

Derivatives Census

Kicksecure participates in the Derivatives Census.archive.org iconarchive.today icon

Infrastructure

Debian Derivatives Guidelines recommends "We encourage derivative distributions to use Debian infrastructure and the software that powers Debian infrastructure where possible.".

Kicksecure makes heavy use of that. Only official Debian repositories are used. Kicksecure is very thankful, that Debian derivatives are allowed to do so. The Kicksecure project has neither the infrastructure, the founding nor the manpower to run its own repositories.

Debian packages

Neither binary nor source packages are modified.

Any configuration file modifications of any packages sourced from packages.debian.org which derivate from the default package configuration is implemented through Kicksecure packages.

Keyrings

Kicksecure does not modify keyrings.

Patrick's OpenPGP key is copied into Kicksecure virtual machines at build time. It is only used to ensure authenticity of Kicksecure APT repository.

Releases

See About Debian for reasons to choose stable.

Trademark

Kicksecure is and will never be called Debian. It must always be clear that Kicksecure is a Debian derivative or based on Debian.

Patrick Schleizer e-mailed trademark at debian.org and briefly explained Kicksecure. Debian Leader Stefano Zacchiroli said, there will be no trademark issues as long as Kicksecure will not claim to be Debian, which will of course never happen.

See also Kicksecure Trademark Policy.

De-/Re-branding

Not necessary. See Trademark above.

Bug reports

Reportbug is unchanged. No Debian packages are modified.

Popularity Contest

Not installed in Kicksecure. Reasons are in the Popularity Contest chapter.

General

Upstream software

When technical skills and time allows, changes are pushed upstream when we need to modify software shipped. Only package selection, configuration files and scripts are modified.

Upstream Bug tracking systems

All bugs found in Kicksecure, will be checked, if they also apply to upstream. If that is the case, the plan is to check if bug has already been reported. If there is something constructive to contribute, it will be done. In case there is not yet a bug report, one will be submitted.

The same goes for wishlist/enhancement requests.

Why this document?

The Debian Derivatives Guidelinesarchive.org iconarchive.today icon encourages "derivative distributions to mention and define their relationship with Debian". Because this seems like a great idea, this statement that not only covers Kicksecure relationship with Debian, but also Kicksecure relationship with any one of its upstream projects.

License

Kicksecure Dev/Relationship With Upstream wiki page Copyright (C) Amnesia <amnesia at boum dot org>
Kicksecure Dev/Relationship With Upstream wiki page Copyright (C) 2012 - 2025 ENCRYPTED SUPPORT LLC <

This program comes with ABSOLUTELY NO WARRANTY; for details see the wiki source code.
This is free software, and you are welcome to redistribute it under certain conditions; see the wiki source code for details.

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!