If you missed the inaugural meeting of the Knoxville BSD User Group, you definitely don’t want to miss this one. Lead Documentation Expert and author for the PC-BSD and FreeNAS projects Dru Lavigne will be giving a talk: “You Too Can Doc Like an Egyptian”. For more information on meeting times and venue, please visit the Knoxville Tennessee BSD User Group’s web page. We hope to see you there!
Source: Call For Artists: New Icon Theme
Since the founding of the Lumina desktop project, one of the most common questions I get asked is: “I am not a programmer, but how can I help out?” Well today I would like to open up a new method of contributing for those of you that are graphically-inclined: the creation of a brand new icon theme for the Lumina desktop!
This new icon theme will adhere to the FreeDesktop specifications for registering an icon theme, and the good news is that I have already handled all the administrative setup/framework for you so that all you need to do to contribute is basically just send in icon files!
Here are the highlights for the new theme:
- Included within the main Lumina source repository
- All icons will be licensed under the Creative Commons Attribution 4.0 International Public License. This is comparable to the 3-clause BSD license, but specifically for static images/files (whereas the BSD license is for source code).
- This will be a high-contrast, high-resolution, fully-scalable (SVG) theme.
- The general concept is a white foreground, with a black outline/shadow around the icon, and colorized emblems/overlays for distinguishing between similar icons (“folder” vs “folder-network” for instance). We are going for a more professional/simple look to the icons since tiny image details generally do not scale as well across the range we are looking at.
The details on how to contribute an icon to the theme are listed on the repository page as well, but here is the summary:
- Icons which are still needed are listed in the TODO.txt files within each directory.
- Submit the icon file via git pull request
- Add an entry for your icon/submission to the AUTHORS file (to ensure each contributor gets proper credit for their work)
- Remove the icon from the appropriate TODO.txt file/list
If you are not familiar with git or how to send git pull requests, feel free to email me the icon file(s) you want to contribute and I can add them to the source tree for you (and update the AUTHORS/TODO files as necessary). Just be sure to include your full name/email so we can give you the proper credit for your work (if you care about that).
As an added bonus since we don’t have any actual icons yet (just the general guidelines), the first contributor to send in some icons will get to help decide the overall look-n-feel of the icon theme!
 FreeDesktop Specifications
- Theme Registration: https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html
- Icon Names: https://specifications.freedesktop.org/icon-naming-spec/latest/ar01s04.html
We recently looked at the pipelight port that recently received a patch in the ports tree and made a video for you guys.
I’ll just leave this here…
Joshua Allen Holm of opensource.com gave PC-BSD an awesome review on their web blog! Head on over and check it out! Make sure to comment on their blog to show your thanks for supporting PC-BSD.
The PC-BSD team has always been dedicated to bringing you the best graphical BSD desktop possible. We received some great feedback after our last release cycle that made us rethink our release schedule.
In the past, we tracked FreeBSD major releases, and also added our own quarterly updates that tended to add in a good bit of code for new features and utilities. Going forward, PC-BSD releases will track FreeBSD releases only, such as 10.2 -> 11.0 -> 11.1. Once the code base is frozen for a major release, an update can be pushed out to EDGE users who wish to act as advanced users and beta testers for the updates. During that several week testing period, if something goes wrong we’ll count on EDGE users to help report issues so that we can
quickly get those bugs fixed during the code freeze. After the several week testing period, we can release the update for PRODUCTION users, once we are confident that the kinks are worked out and EDGE users are happy.
We’re also changing the way the EDGE and PRODUCTION branches work a little bit. EDGE packages will now only be built with the ‘stable’ branch of PC-BSD code, to avoid radical changes that could break functionality to the PC-BSD tool-chain. This also allows us to focus our QA and testing on the new 3rd party packages themselves.
However, all packages that are built on FreeBSD -CURRENT will include PC-BSD’s ‘master’ branch, and are considered bleeding edge. These images will continue to be rolled monthly and are only intended for advanced users or developers who can debug and otherwise help fix issues as they arise.
The PRODUCTION package branch will be switching to a monthly update schedule instead of quarterly. The PC-BSD tool-chain will also be based upon “stable”, which will not radically change between releases. We are hoping this change will balance between the need for stability and bringing in the latest packages / security updates to end users in a timely manner.