Hi Ted,

I read this a couple of days ago, and looked at the whole bill.

There seems to be a disconnect between what I read as the meaning of the bill:

AN ACT prohibiting, with limited exceptions, state agencies from requiring use 
of proprietary software in interactions with the public.

and what is described in the FISCAL IMPACT Statement:

AN ACT prohibiting, with limited exceptions, state agencies from using 
proprietary software in interactions with the public

Note that the first one is simply saying that citizens should be able to use 
Open Source software in interacting with the state.

The second one assumes that the state can not use any proprietary software in 
dealing with the public.

This is a HUGE difference.

In addition, the FISCAL IMPACT statement talks as if every system needs a 
massive update just to meet the requirements of the bill, and that this will 
cost 1.4 Billion dollars over five years, ignoring that existing systems have 
to be updated and replaced, and ignoring that new systems should be following 
these guidelines.

I have written to Eric (who I know and have worked with in the past) pointing 
out these issues, but I have not heard back from him.

I will be going to the meeting tomorrow, but I am very short on time tomorrow, 
so unless I get a chance to talk by 1400, I may have to leave.

md


> On 02/15/2023 6:46 PM Ted Roche <tedro...@gmail.com> wrote:
> 
>  
> I'm not sure this is the most current version of the bill, but there's
> some interesting discussion at the bottom.
> 
> https://www.gencourt.state.nh.us/bill_status/legacy/bs2016/billText.aspx?sy=2023&id=188&txtFormat=html
> 
> On Wed, Feb 15, 2023 at 5:48 PM Ted Roche <tedro...@gmail.com> wrote:
> >
> > If you are unable to testify in person (a much more effective option,
> > I've been told), you can post your (optional) testimony and/or your
> > position in favor or against the bill by navigating to:
> >
> > https://www.gencourt.state.nh.us/
> >
> > selecting the link labeled, "House Sign-in Form and Online Testimony 
> > Submission"
> >
> > registering your name, location and email, and selecting the bill you
> > wish to comment on:
> > Date: February 16, 2023
> > Committee: House Executive Departments and Administration
> > Choose the hearing time and bill: 1:00 - HB617
> > Representing: yourself or others
> >
> > and post whether you are in favor, opposed or neutral and optionally
> > upload or enter text testimony.
> >
> > Submit, review and post.
> >
> >
> > On Wed, Feb 15, 2023 at 4:58 PM Joshua Judson Rosen
> > <roz...@hackerposse.com> wrote:
> > >
> > > There will be a hearing mid-day tomorrow (Thursday) in Concord
> > > regarding House Bill 617-FN, "AN ACT prohibiting, with limited exceptions,
> > > state agencies from requiring use of proprietary software in interactions 
> > > with the public."
> > >
> > > Unfortunately I have no transportation tomorrow, but maybe you'd be able 
> > > to go and show your support?
> > >
> > > More details at 
> > > <https://www.fsf.org/blogs/community/new-hampshire-residents-voice-your-support-for-software-freedom-on-feb-16>
> > >
> > > If you were on this list around this time last year, you may remember 
> > > that there was a similar bill put forward then,
> > > which failed to become law.
> > > This version has apparently been trimmed to hopefully give it a better 
> > > chance at doing so.
> > >
> > > --
> > > Connect with me on the GNU social network: 
> > > <https://status.hackerposse.com/rozzin>
> > > Not on the network? Ask me for an invitation to a social hub!
> > > _______________________________________________
> > > gnhlug-discuss mailing list
> > > gnhlug-discuss@mail.gnhlug.org
> > > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss@mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Reply via email to