Hi Paweł, I would like to welcome yourself and SparkyLinux to the Debian derivatives census! Would you like to take this opportunity to introduce yourself and SparkyLinux to us all? https://wiki.debian.org/Derivatives/Census/SparkyLinux It would be great if you could join our mailing list and IRC channel: http://wiki.debian.org/DerivativesFrontDesk I would encourage you to look at Debian's guidelines for derivatives: http://wiki.debian.org/Derivatives/Guidelines You may want to look at our census QA page, some of the mails from there may apply to SparkyLinux. http://wiki.debian.org/Derivatives/CensusQA You don't appear to be subscribed to the SparkyLinux census page, I've made a few changes: http://wiki.debian.org/Derivatives/Census/SparkyLinux?action=info Some of the Release files in the apt repository for SparkyLinux are missing the Valid-Until header, which allows clients to find out when active network attackers are holding back newer Release files. At minimum, rolling releases and suites containing security updates should have this header. With reprepro you can use the ValidFor config option. https://wiki.debian.org/RepositoryFormat#Date.2CValid-Until The apt repository for SparkyLinux does not contain source packages, including for packages licensed under the GNU GPL. This may or may not be a copyright violation depending on whether our not you distribute those elsewhere. In any case, please add source packages to your repository so that Debian can automatically create patches to be presented to Debian package maintainers. https://wiki.debian.org/Derivatives/CensusQA#No_source_packages https://wiki.debian.org/Derivatives/Integration#Patches The page is missing a dpkg vendor field. It is important that Debian derivatives set this properly on installed systems and mention the value of the field in the derivatives census. https://wiki.debian.org/Derivatives/Guidelines#Vendor I've added the SparkyLinux blog to Planet Debian derivatives which helps the Debian community find out the things that are happening in the world of Debian derivatives. http://planet.debian.org/deriv/ SparkyLinux seems to be funded by donations, please also fill out the funding field. Since SparkyLinux seems to be based in Poland you might want to join the Debian Poland group. Please also fill out the location field. https://wiki.debian.org/LocalGroups#Poland Next year the annual Debian conference is in Heidelberg, Germany. It would be great if developers from SparkyLinux could attend DebConf. If this isn't possible, there is always next year :) http://debconf15.debconf.org/ I would encourage any attendees to volunteer to ensure the continued the success of the annual Debian conference, here are some examples of things that need helpers. https://wiki.debconf.org/wiki/DebConf13/VolunteerCoordination I note that SparkyLinux is based on Debian testing. A great way to help ensure that the next Debian release working well is to install and run the how-can-i-help tool and try to work on any issues that come up. http://www.lucas-nussbaum.net/blog/?p=837 https://packages.debian.org/unstable/how-can-i-help https://wiki.debian.org/how-can-i-help I note that SparkyLinux uses Enlightenment and other desktops, I encourage you to provide help to the relevant Debian teams: https://wiki.debian.org/PkgE https://wiki.debian.org/Teams/DebianXfceGroup http://lists.lxde.org/listinfo/lxde-debian http://www.mate-desktop.org/blog/2013-11-08-debian-mate-packaging-team/ You might want to consider adding DNSSEC to your domains, TLSA records, SSL and TSTS to some of your domains to increase security. Please feel free to circulate this mail within the SparkyLinux team. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part