Thanks Brian. :) Hooray!<br><br><div class="gmail_quote">On Fri, Jan 29, 2010 at 12:10 PM, Brian Lavender <span dir="ltr"><<a href="mailto:brian@brie.com">brian@brie.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I thought there would be a reply. Like, horay, or something like that.<br>
<div><div></div><div class="h5"><br>
On Fri, Jan 29, 2010 at 09:08:23AM -0800, Brian Lavender wrote:<br>
> I thought Vox would also be interested in this.<br>
><br>
> <a href="http://www.cio.ca.gov/Government/IT_Policy/pdf/IT_Policy_Letter_10-01_Open_Source_Software.pdf" target="_blank">http://www.cio.ca.gov/Government/IT_Policy/pdf/IT_Policy_Letter_10-01_Open_Source_Software.pdf</a><br>
><br>
> brian<br>
><br>
> ----- Forwarded message from Brian Lavender <<a href="mailto:brian@brie.com">brian@brie.com</a>> -----<br>
><br>
> Date: Thu, 28 Jan 2010 23:32:51 -0800<br>
> From: Brian Lavender <<a href="mailto:brian@brie.com">brian@brie.com</a>><br>
> Subject: Re: [Lug-nuts] State of CA endorses Open Source Software<br>
> To: General SacLUG discussing <<a href="mailto:lug-nuts@saclug.org">lug-nuts@saclug.org</a>><br>
> Reply-To: General SacLUG discussing <<a href="mailto:lug-nuts@saclug.org">lug-nuts@saclug.org</a>><br>
><br>
> Hmm, how about if I attach the text? I don't know if a PDF will go<br>
> through on the mailing list.<br>
><br>
><br>
> OFFICE OF THE STATE CIO<br>
><br>
> NUMBER:<br>
><br>
> IT POLICY LETTER<br>
> SUBJECT:<br>
><br>
> ITPL 10-01<br>
> DATE ISSUED:<br>
><br>
> OPEN SOURCE SOFTWARE POLICY<br>
><br>
> January 7, 2010<br>
> EXPIRES:<br>
><br>
> Until Rescinded<br>
> REFERENCES: ISSUING AGENCY: OFFICE OF THE STATE CHIEF INFORMATION OFFICER<br>
><br>
> Government Code Section 11545 State Administrative Manual Sections<br>
> 4819.2. 4846, 4846.1, 5310, and 5345.1 Statewide Information Management<br>
> Manual Section 120<br>
><br>
> DISTRIBUTION<br>
><br>
> Agency 1 Secretaries Department Directors Agency Chief Information<br>
> Officers Department Chief Information Officers The purpose of this<br>
> Information Technology Policy Letter (ITPL) is to: â<br>
><br>
> €¢ Formally establish the use of Open Source Software (OSS) in California<br>
> state government as an acceptable practice;<br>
><br>
> • Add the OSS definition to the State Administrative Manual (SAM)<br>
> Section 4819.2;<br>
><br>
> • Remind organizations of the existing SAM Sections pertaining to<br>
> software management and security; and<br>
><br>
> • Announce changes to the Software Management Plan Guidelines [Section<br>
> 120 of the Statewide Information Management Manual (SIMM)].<br>
><br>
> Within the authority of Government Code Section 11545, the Office<br>
> of the Chief Information Officer (OCIO) has responsibility and authority<br>
> for the establishment and enforcement of state Information Technology<br>
> (IT) in California State Government. This includes establishing and<br>
> enforcing state IT strategic plans, policies, standards and enterprise<br>
> architecture. This policy provides guidance on the use of Open Source<br>
> Software (OSS) and will be augmented in the future to address topics<br>
> of licensing,<br>
><br>
> PURPOSE<br>
><br>
> BACKGROUND<br>
><br>
> 1<br>
><br>
> When capitalized, the term “Agency†refers to one of the state’s<br>
> super Agencies such as the State and Consumer Services Agency or the<br>
> Health and Human Services Agency. When used in lower case, the term<br>
> “agency†refers to any office department, board, bureau, commission<br>
> or other organizational entity within state government. Within this ITPL,<br>
> “agency†and “department†are used interchangeably.<br>
><br>
> Page 1<br>
><br>
> procurement, and copyright.<br>
><br>
> POLICY The OCIO permits the use of OSS. Consistent with other software,<br>
> use of OSS is subject to the software management licensing and security<br>
> practices included in the SAM, Sections 4846, 4846.1, 5310–Item 2 and<br>
> Item 5 Subsection (f), and 5345.1.<br>
><br>
> Agencies and departments are required to develop and maintain a<br>
> Software Management Plan as described in the SAM Section 4846.1, and<br>
> are reminded to include OSS in their plans as appropriate. Guidelines<br>
> to assist organizations with the development of a Software Management<br>
> Plan are available in Section 120 of the SIMM. These guidelines have<br>
> been updated to include the use of OSS and to reflect changes in the<br>
> state IT organizational structure.<br>
><br>
> Use of the SIMM Section 120 Guidelines is not mandatory;<br>
> however, agencies are encouraged to utilize the Guidelines<br>
> for assistance or guidance. SIMM Section 120 is located at<br>
> <a href="http://www.cio.ca.gov/Government/IT_Policy/SIMM.html" target="_blank">http://www.cio.ca.gov/Government/IT_Policy/SIMM.html</a>. Changes to SIMM<br>
> Section 120 are identified on Attachment A.<br>
><br>
> DEFINITION<br>
><br>
> The definition of OSS has been added to Section 4819.2 of the SAM. OSS<br>
> is defined as 2 Software that includes distribution terms that comply<br>
> with the following criteria provided by the Open Source Initiative:<br>
><br>
> 1. Free Redistribution: The software can be given as part of a package<br>
> with other applications;<br>
><br>
> 2. Source Code: The code must either be distributed with the software<br>
> or easily accessible;<br>
><br>
> 3. Derived Works: The code can be altered and distributed by the new<br>
> author under the same license conditions as the product on which it<br>
> is based;<br>
><br>
> 4. Integrity of the author's source code: Derived works must not interfere<br>
> with the original author's intent or work;<br>
><br>
> 5. No discrimination against persons or groups;<br>
><br>
> 6. No discrimination against fields of endeavor: Distributed software<br>
> cannot be restricted in who can use it based on their intent;<br>
><br>
> 7. Distribution of license: The rights of the program must apply to all to<br>
> whom the program is re-distributed without need for an additional license;<br>
><br>
> 8. License must not be specific to a product; Meaning that an operating<br>
> system product cannot be restricted to be free only if used with another<br>
> specific product;<br>
><br>
> 9. License must not contaminate other software; and<br>
><br>
> 10. License must be technology-neutral.<br>
><br>
> 2<br>
><br>
> The open source definition used here is from the Open Source Initiative<br>
> and is licensed under a Creative Commons Attribution 2.5 License<br>
> (<a href="http://creativecommons.org/licenses/by/2.5/" target="_blank">http://creativecommons.org/licenses/by/2.5/</a>)<br>
><br>
> Page 2<br>
><br>
> CONTACT<br>
><br>
> Questions regarding this policy should be directed to Lee Mosbrucker,<br>
> Acting Enterprise Architect at (916) 403-9624, or by e-mail at<br>
> <a href="mailto:Lee.Mosbrucker@state.ca.gov">Lee.Mosbrucker@state.ca.gov</a>. /s/ ___________________________________<br>
> Teri Takai, Chief Information Officer State of California<br>
><br>
> SIGNATURE<br>
><br>
> Page 3<br>
><br>
><br>
><br>
> On Thu, Jan 28, 2010 at 03:13:28PM -0800, Christopher Schlacta wrote:<br>
> > that page 403'd for me, cna you attach a copy of it for us ?<br>
> > On Jan 28, 2010, at 14:14 , Brian Lavender wrote:<br>
> ><br>
> > > California has an expliciti policy on using Open Source Software. How<br>
> > > about that?<br>
> > ><br>
> > > Apparently, this is old news.<br>
> > > <a href="http://www.cio.ca.gov/Government/IT_Policy/pdf/IT_Policy_Letter_10-01_Open_Source_Software.pdf" target="_blank">http://www.cio.ca.gov/Government/IT_Policy/pdf/IT_Policy_Letter_10-01_Open_Source_Software.pdf</a><br>
> > ><br>
> > > brian<br>
> > > --<br>
> > > Brian Lavender<br>
> > > <a href="http://www.brie.com/brian/" target="_blank">http://www.brie.com/brian/</a><br>
> > > _______________________________________________<br>
> > > Lug-nuts mailing list<br>
> > > <a href="mailto:Lug-nuts@saclug.org">Lug-nuts@saclug.org</a><br>
> > > <a href="http://www.leibmanland.com/cgi-bin/mailman/listinfo/lug-nuts" target="_blank">http://www.leibmanland.com/cgi-bin/mailman/listinfo/lug-nuts</a><br>
> ><br>
> > _______________________________________________<br>
> > Lug-nuts mailing list<br>
> > <a href="mailto:Lug-nuts@saclug.org">Lug-nuts@saclug.org</a><br>
> > <a href="http://www.leibmanland.com/cgi-bin/mailman/listinfo/lug-nuts" target="_blank">http://www.leibmanland.com/cgi-bin/mailman/listinfo/lug-nuts</a><br>
><br>
><br>
><br>
> ----- End forwarded message -----<br>
><br>
> --<br>
> Brian Lavender<br>
> <a href="http://www.brie.com/brian/" target="_blank">http://www.brie.com/brian/</a><br>
><br>
> "About 3 million computers get sold every year in China, but people don't<br>
> pay for the software. Someday they will, though. As long as they are going<br>
> to steal it, we want them to steal ours. They'll get sort of addicted, and<br>
> then we'll somehow figure out how to collect sometime in the next decade."<br>
><br>
> -- Bill Gates (Microsoft) 1998<br>
> _______________________________________________<br>
> vox mailing list<br>
> <a href="mailto:vox@lists.lugod.org">vox@lists.lugod.org</a><br>
> <a href="http://lists.lugod.org/mailman/listinfo/vox" target="_blank">http://lists.lugod.org/mailman/listinfo/vox</a><br>
<br>
--<br>
Brian Lavender<br>
<a href="http://www.brie.com/brian/" target="_blank">http://www.brie.com/brian/</a><br>
<br>
"About 3 million computers get sold every year in China, but people don't<br>
pay for the software. Someday they will, though. As long as they are going<br>
to steal it, we want them to steal ours. They'll get sort of addicted, and<br>
then we'll somehow figure out how to collect sometime in the next decade."<br>
<br>
-- Bill Gates (Microsoft) 1998<br>
_______________________________________________<br>
vox mailing list<br>
<a href="mailto:vox@lists.lugod.org">vox@lists.lugod.org</a><br>
<a href="http://lists.lugod.org/mailman/listinfo/vox" target="_blank">http://lists.lugod.org/mailman/listinfo/vox</a><br>
</div></div></blockquote></div><br>