From: Leah Rowe via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
Cc: news@phoronix.com, media@technologyadvice.com,
info@linux-magazine.com, edit@linux-magazine.com,
doug_dineley@idg.com, marc_ferranti@idg.com, vaggarwal@idg.com,
press@WIRED.com, tim_greene@idg.com,
maggie.holland@futurenet.com, dale.walker@futurenet.com,
adam.shepherd@futurenet.com, bobby.hellard@futurenet.com,
connor.jones@futurenet.com, help@rossmanngroup.com, info@fsf.org,
info@eff.org, info@sfconservancy.org, press@spi-inc.org,
spi-general@lists.spi-inc.org, apache@apache.org,
info@wikimedia.org, feedback@masslive.com,
customerservice@cmonitor.com, newstips@whdh.com,
press@debian.org, linuxgizmos@gmail.com, editors@lxer.com,
info@linux-magazine.com, info@linuxiac.com,
libreplanet-discuss@libreplanet.org
Subject: New Hampshire software freedom bill on 21 February 2023
Date: Mon, 20 Feb 2023 10:37:17 +0000 [thread overview]
Message-ID: <20230220103717.894bcab58615d391131651dc@minifree.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2013 bytes --]
Hello everyone,
I'm CC'ing this to several organisations. I ask that you all please
spread the news about this, in whatever way you can:
On 21 February 2023, there is a hearing for a bill in the New Hampshire
Legislative Office Building in Concord, New Hampshire, named House Bill
556-FN that would greatly advance the cause of free and open source
software everywhere.
The text of the bill is here:
https://gencourt.state.nh.us/lsr_search/billText.aspx?id=193&type=4
If passed, the New Hampshire Information Technology Council would then
be required, by law, to promote software freedom to the Department of
Information Technology Commissioner. This would include analysis of
practical issues such as cost, and deployment strategies for libre
systems to replace current proprietary systems; more importantly, it
would require them to study ways of reducing (or eliminating) the need
for citizens to use proprietary software for interactions with the
state. The bill also promotes the principle of copyleft licensing, such
as GNU GPL; regardless of how you feel about copyleft versus permissive
(BSD-style) licensing, the advancement of any libre software on such
massive scale will help the entire movement.
I wrote about this on the Libreboot website, today:
https://libreboot.org/news/usa-libre-part3.html
The Free Software Foundation (FSF) also published their own article, on
Friday last week:
https://www.fsf.org/blogs/community/new-hampshire-residents-support-another-software-freedom-initiative-on-tuesday-february-21
The bill hearing is *tomorrow*. It is critical that as many supporters
of software freedom show up as possible, to testify in favour of it,
and to advance the cause of our movement.
Thank you for reading!
--
Leah Rowe,
Company Director,
Minifree Ltd
Registered in England, registration No. 9361826
VAT Registration No. GB202190462
Minifree Ltd, 19 Hilton Road, Canvey Island
Essex SS8 9QA, United Kingdom
United Kingdom
[-- Attachment #1.2: Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 184 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
reply other threads:[~2023-02-21 2:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230220103717.894bcab58615d391131651dc@minifree.org \
--to=libreplanet-discuss@libreplanet.org \
--cc=adam.shepherd@futurenet.com \
--cc=apache@apache.org \
--cc=bobby.hellard@futurenet.com \
--cc=connor.jones@futurenet.com \
--cc=customerservice@cmonitor.com \
--cc=dale.walker@futurenet.com \
--cc=doug_dineley@idg.com \
--cc=edit@linux-magazine.com \
--cc=editors@lxer.com \
--cc=feedback@masslive.com \
--cc=help@rossmanngroup.com \
--cc=info@eff.org \
--cc=info@fsf.org \
--cc=info@linux-magazine.com \
--cc=info@linuxiac.com \
--cc=info@minifree.org \
--cc=info@sfconservancy.org \
--cc=info@wikimedia.org \
--cc=linuxgizmos@gmail.com \
--cc=maggie.holland@futurenet.com \
--cc=marc_ferranti@idg.com \
--cc=media@technologyadvice.com \
--cc=news@phoronix.com \
--cc=newstips@whdh.com \
--cc=press@WIRED.com \
--cc=press@debian.org \
--cc=press@spi-inc.org \
--cc=spi-general@lists.spi-inc.org \
--cc=tim_greene@idg.com \
--cc=vaggarwal@idg.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).