Hi H. Sumen, I've BCCed you on this mail because you didn't add your contact details under the "Debian derivatives census maintainer" field. Ideally every derivative in the census should have this field filled out so that Debian folks and people from other derivatives have an easy way to contact each of the derivatives. I would like to welcome yourself and BunsenLabs Linux to the Debian derivatives census! Would you like to take this opportunity to introduce yourself and BunsenLabs to us all? https://wiki.debian.org/Derivatives/Census/BunsenLabs It would be great if you could join our mailing list and IRC channel: https://wiki.debian.org/DerivativesFrontDesk I would encourage you to look at Debian's guidelines for derivatives: https://wiki.debian.org/Derivatives/Guidelines You may want to look at our census QA page, some of the mails from there may apply to BunsenLabs. https://wiki.debian.org/Derivatives/CensusQA You don't appear to be subscribed to the BunsenLabs census page, I've made a few changes to the BunsenLabs census page: https://wiki.debian.org/Derivatives/Census/BunsenLabs?action=info Please fill out as much of the BunsenLabs census page as you can. Some of the Release files in the apt repository for BunsenLabs 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 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 BunsenLabs news & announcements forum 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/ I noticed that Distrowatch says that BunsenLabs is based in Japan, if so, you might be interested in joining the Debian Japan groups. https://wiki.debian.org/LocalGroups/Debian-JP http://www.debian.or.jp/ https://tokyodebian.alioth.debian.org/ https://wiki.debian.org/KansaiDebianMeeting This year the annual Debian conference is in Cape Town, South Africa. It would be great if developers from BunsenLabs could attend DebConf. Unfortunately it is very very very close to the start of DebConf. If this isn't possible, next year DebConf will be in Montreal, Canada. https://debconf16.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 BunsenLabs is based on Debian stable. The Debian release team recently released a timeline for the freeze for the next Debian stable release. I would encourage you to review it and prepare your plans for rebasing on the next Debian release (stretch). https://lists.debian.org/debian-devel-announce/2016/03/msg00000.html 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 BunsenLabs does Debian jessie backports, you might also like to contribute your backporting efforts to Debian. http://backports.debian.org/Contribute/ I note that BunsenLabs uses openbox, I would encourage you to provide feedback and fixes to the maintainer. https://tracker.debian.org/pkg/openbox You might want to consider adding DNSSEC and TLSA records to your domains. Please feel free to circulate this mail within the BunsenLabs team. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part