Today a friend of mine (meow if you want to be identified¹) mentioned that it would be nice to have a name like campingpunk for a look with less brass than steampunk and more anodized aluminum and paracord. Also a bit like crazy survivalists with less camo and more colors.
I like the idea.
¹ no, that doesn't uniquely identify them: I tend to have many friends with feline tendencies.
2. Coding in the open is great for international relationsThe government National Technology Advisor Liam Maxwell, talked about the non-technical advantages of coding in the open and how the UK is a leader in the field.Liam said that the nature of the public sector means that sharing code is actually an advantage. Governments are not competing with each other and they can work together to make public services better. When it comes to providing driving licence services, for example, the UK can work with a country like Norway not just to share code but combine methodologies and standards to improve the experience for citizens across both countries.
Maybe above seems trite, but in my estimation, it's maybe the most important feature of commons-based production. The world war in progress may end the world, and it wouldn't be too surprising for the major part of it to be triggered by an "IP" dispute. Knowledge should be an opportunity to build collaboration capabilities, not provide reason for conflict.
Conservancy Applauds Linux Community's Promotion of Principled Copyleft Enforcement
October 16, 2017
Software Freedom Conservancy congratulates the Linux community for taking steps today to promote principled, community-minded copyleft enforcement by publishing the Linux Kernel Enforcement Statement. The Statement includes an additional permission under Linux's license, the GNU General Public License (GPL) version 2 (GPLv2). The additional permission, to which copyright holders may voluntarily opt-in, changes the license of their copyrights to allow reliance on the copyright license termination provisions from the GNU General Public License version 3 (GPLv3) for some cases 1.
Conservancy also commends the Linux community's Statement for reaffirming that legal action should be last resort for resolving a GPL violation, and for inviting noncompliant companies who work their way back into compliance to become active participants in the community. By bringing clarity to GPLv2 enforcement efforts, companies can adopt software with the assurance that these parties will work in a reasonable, community-centric way to resolve compliance issues.
Conservancy believes that free and open source software communities can use copyleft licenses to establish a healthy framework for collaboration and cooperation. We also believe that, when seeking compliance with such licenses, it is in the community and in the public's interest to bring people and companies into the community rather than to alienate them or seek monetary gain. That's the fundamental premise of our Principles of Community-Oriented GPL Enforcement: yesterday's violator can be tomorrow's valued contributor.
We co-authored and published the Principles with the FSF in 2015 to engage the broader free and open source software community in a dialogue about how to best achieve community-minded copyleft compliance. We believe that GPLv3's termination provisions better reflect the collaborative and friendly process of GPL enforcement that Conservancy, FSF, and gpl-violations.org have historically employed. Accordingly, we've encouraged copyright holders in GPLv2-licensed projects to forgive violators who cure violations in a timely manner in accordance with GPLv3§8, despite the stricter terms found in GPLv2§4. We are glad to see the Linux community express their formal alignment with this position.
Some Linux sub-projects — such as Netfilter — have wholly endorsed and adopted the Principles, and we continue to encourage the entire Linux community to adopt all of the Principles fully. We want to continue the conversation about how to best promote, encourage, and enforce compliance, and we invite members from the Linux community to join our ongoing forum for public discussion on the principles-discuss mailing list. Conservancy has suggested to all Linux copyright holders participating in our GPL Compliance Project for Linux Developers) that they sign this new Linux Kernel Enforcement Statement to grant the additional permission.
In addition to coordinating a coalition of copyright holders, Conservancy itself is a copyright holder in Linux, as developers have also assigned Linux copyrights to our organization. As a copyright holder in Linux, Software Freedom Conservancy signs onto the Linux Kernel Enforcement Statement. We plan to continue our work enforcing GPLv2 for our own copyrights (and those of our coalition), and will always afford violators — as we have since our inception — the 60- and 30-day periods for violation cure in GPLv3, even though Linux's default GPLv2 termination is much stricter and always permanent. We will continue to do this, even in defensive actions.
1. The additional permission in the Statement does not apply when a company is defending itself from any legal claim, even one unrelated to GPL.
processing my sumac harvest
After drying my sumac harvest and rubbing the berries off the clusters, I ground it by hand with mortar and pestle.
Passed through a sieve to remove the seeds and stems, an amazing spice emerged.
This is the first time I've processed a spice. It reminds me of processing tobacco in the barn as a kid. So tactile, hands become sticky with dry sap, and it smells amazing.
- "Effective today, @EFF is resigning from the W3C." - https://www.eff.org/deeplinks/2017/09/open-letter-w3c-director-ceo-team-and-membership good to see someone has principles #DRM; time to boycott @W3C?
- I don't want credit monitoring from these companies. The companies that expose all our data are the same companies trying to sell us a service to protect that data. If they get something wrong or somebody
"steals our identity", we're responsible for correcting it. What a racket. It seems this "industry" externalizes all the costs to people whose information it collects and then exposes. They win no matter what happens.
I want them to pay for credit freezes. (I want them to do some other things too, but it wouldn't be polite to express those things aloud.)
Here's a link to Equifax's own page on the matter (in case it is useful): https://www.equifaxsecurity2017.com/
der.hans likes this.
Public Money? Public Code!
31 organisations ask to improve public procurement of software: https://fsfe.org/news/2017/news-20170913-01
Sign the Open Letter now: https://publiccode.eu/#action
#publiccode #openletter #freesoftware #opensource #linux
- Best campaign ever https://publiccode.eu
Very happy to learn of this, more so that the Software Liberty Association of Taiwan (SLAT, slat.org) is one of the organizations supporting the campaign. I think SLAT also helps translate the campaign website and the video into Traditional Chinese. Press release from SLAT: https://slat-tw.blogspot.tw/2017/09/public-money-public-code.html .
Mike Linksvayer likes this.My congressional representation is going to be cross with me writing to them yet again. I might get added to the "Crank Index". There is a minor issue with just plopping an open source license in a code release by the federal government based upon something odd a Treasury bureau did in a legal position it took about FAQs on the bureau's home page. The odd thing is that it disavowed the FAQs another part of the bureau wrote, said they were invalid, said they could not be relied on by people with business before the bureau, and that they could not be used by people with business before the bureau to back any legal position. Only matters gazetted appropriately could be used. An appropriate statement may be needed for licenses in the Federal Register just to avoid an about-face maneuvers by later bureaucrats.
- California Proves That Environmental Regulations Don't Kill Profits - https://www.wired.com/story/california-proves-that-environmental-regulations-dont-kill-profits/ so there you go
der.hans likes this.
"DebCamp/DebConf17: reports on sprints and BoFs" by Sean Whitton
"DebCamp/DebConf17: reports on sprints and BoFs" by Sean Whitton https://spwhitton.name//blog/entry/debconf17_reports/
der.hans likes this.
- http://blog.jonasoberg.net/where-does-our-money-go/ a post about the FSFE budget, where I am very happy to read:And so we then come to our policy work, where I feel we need to elaborate a bit on what has changed in 2017. Our budget for 2016 was 4k for policy work (most of the work on policy is staff time). You will see that when we publish the results for 2017, the costs for policy has shot up remarkably. We have increased the budget to 29k for 2017 to be able to invest in our Public Money - Public Code campaign, which we hope will be a major driver for our work in 2018.
"20170812-reproducible-policy (packages should build reproducibly - after 4 years this work of many is in debian-policy now)" by Holger Levsen
"20170812-reproducible-policy (packages should build reproducibly - after 4 years this work of many is in debian-policy now)" by Holger Levsen http://layer-acht.org/thinking/blog/20170812-reproducible-policy/
der.hans likes this.