Public Money, Public Code: Show Your Support For Free Software in Europe



  • The global movement for open access to publicly-funded research stems from the sensible proposition that if the government has used taxpayers’ money to fund research, the publication of the results of that research should be freely-licensed. Exactly the same rationale underpins the argument that software code that the government has funded to be written should be made available as Free and Open Source Software (FOSS). Public Money, Public Code is a campaign of the Free Software Foundation Europe (FSFE) that seeks to transform that ideal into European law.

    An open letter at the center of the campaign reads in part:

    Public bodies are financed through taxes. They must make sure they spend funds in the most efficient way possible. If it is public money, it should be public code as well!

    That is why we, the undersigned, call our representatives to:

    “Implement legislation requiring that publicly financed software developed for public sector must be made publicly available under a Free and Open Source Software licence.”

    The campaign has already collected over 13,000 signatures to the open letter, which has already been delivered to candidates for the German Federal election. But that’s not the end of it—the FSFE also plans to resubmit the letter during other European elections, including the 2018 election in Italy, culminating in a big handover for the 2019 election for the European Parliament. So there is plenty of time to add your voice to those who have already expressed their support.

    In the United States, under a Federal Source Code Policy that was introduced in 2016, agencies are required to release at least 20 percent of code developed by government employees and contractors as FOSS. But this isn’t enough, particularly when you consider that 100% of code written by government employees is, by law, already in the public domain and should be available to the public for free. We therefore recommend that the next revision of the Federal Source Code Policy reflect that, by creating an “open-by-default” rule in place of the current 20 percent rule. Since 2013 we have also supported a proposed Open Access law called the Fair Access to Science and Technology Research Act (S.1701, H.R.3427), or FASTR, that would require every federal agency that spends more than $100 million on grants for research to adopt an open access policy.

    On both sides of the Atlantic, the advantages of releasing publicly-funded code under a FOSS license are the same. For example, it saves money by allowing code to be reused in multiple public or private projects, it makes government more accountable to the people by allowing them to review the software used by public agencies, and it stimulates collaboration and innovation. If you are European or have European friends or colleagues, we recommend that you review the FSFE’s open letter and add your endorsement if you agree with it as strongly as we do.

    https://www.eff.org/deeplinks/2017/10/public-money-public-code-show-your-support-free-software-europe





Tmux Commands

screen and tmux

A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.

The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x

It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road.

Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here).

Action tmux screen
start a new session tmux OR
tmux new OR
tmux new-session
screen
re-attach a detached session tmux attach OR
tmux attach-session
screen-r
re-attach an attached session (detaching it from elsewhere) tmux attach -d OR
tmux attach-session -d
screen -dr
re-attach an attached session (keeping it attached elsewhere) tmux attach OR
tmux attach-session
screen -x
detach from currently attached session ^b d OR
^b :detach
^a ^d OR
^a :detach
rename-window to newname ^b , <newname> OR
^b :rename-window <newn>
^a A <newname>
list windows ^b w ^a w
list windows in chooseable menu ^a "
go to window # ^b # ^a #
go to last-active window ^b l ^a ^a
go to next window ^b n ^a n
go to previous window ^b p ^a p
see keybindings ^b ? ^a ?
list sessions ^b s OR
tmux ls OR
tmux list-sessions
screen -ls
toggle visual bell ^a ^g
create another window ^b c ^a c
exit current shell/window ^d ^d
split window/pane horizontally ^b " ^a S
split window/pane vertically ^b % ^a |
switch to other pane ^b o ^a <tab>
kill the current pane ^b x OR (logout/^D)
collapse the current pane/split (but leave processes running) ^a X
cycle location of panes ^b ^o
swap current pane with previous ^b {
swap current pane with next ^b }
show time ^b t
show numeric values of panes ^b q
toggle zoom-state of current pane (maximize/return current pane) ^b z
break the current pane out of its window (to form new window) ^b !
re-arrange current panels within same window (different layouts) ^b [space]
Kill the current window (and all panes within) ^b killw [target-window]
  • FYI for FreeBSD the driver only supports block size chunks, therefore:

    dd if=/dev/cd0 of=/name-the.iso bs=2048

    read more
  • sort -g /var/log/nginx/access.log | awk '{print $1}' | uniq

    read more
});