Protecting the security of the Internet requires everyone. We talked about this theme in a recent post, and in this post we’ll expand on the role Mozilla plays, and how our work supports and relies on the work of the other participants in the Web.
Now in its seventh year, MozFest is the world’s go-to event for the free and open Internet movement. Part meeting place for like-minded individuals keen to share ideas; part playground for Web enthusiasts, hobbyist netizens and seasoned open source technonauts alike, part hack-a-thon; part living breathing creative brainstorm; part speaker-series; MozFest is a buzzy hive of activity. It attracts thousands of visitors each year (1,800 in 2015) from as many as 50 countries around the world, making it the biggest unconference of its kind.
Tiny, open spec SBC offers wireless and 8GB eMMC
FriendlyElec’s $45, 75 x 40mm “NanoPi S2” SBC runs Debian or Android on a quad-core A9 SoC, and offers RPi expansion, WiFi, Bluetooth, and 8GB eMMC.
On Thursday, October 27, 2016, Eben Moglen stepped down as general counsel to the Free Software Foundation (FSF). Moglen, who in addition to being a professor of law and legal history at Columbia University, is the founder, president, and executive director of the Software Freedom Law Center (SFLC), and a former FSF board member, has generously served as the FSF's pro bono general counsel for the last 23 years.
We provide plenty of resources when it comes to picking a license. From our list of licenses to essays on copyleft, if you are looking to figure out what license is right for you there is plenty of information to rely upon. But this month's resource helps to pull that information together in one place to make selecting a license simple.
Our guide, "How to choose a license for your work" is one stop browsing for answering many of the questions you may have when it comes to finding the right license. It provides recommendations based on the state of the work, but also based on the type of work that it is. While the Affero GNU General Public License version 3 works great for server software, documentation would probably be better served with a license directed at such, like the GNU Free Documentation License version 1.3. Smaller works can often get away without a strong copyleft, but still need to address patents, and so Apache License version 2.0 might be appropriate. The guide explains the reasoning behind the different recommendation for these and more. It also links to all those other resources mentioned above in case you need to dive in deeper when picking out a license.