<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="/assets/xslt/atom.xslt" ?>
<?xml-stylesheet type="text/css" href="/assets/css/atom.css" ?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<id>https://hollandvt.gov/</id>
	<title>Holland, VT</title>
	<updated>2026-04-07T18:41:44+00:00</updated>

	<subtitle>»Holland, VT« is ...</subtitle>

	
		
		<author>
			
				<name>Ed Brady</name>
			
			
			
				<uri>https://outsidethebox.bbbiz.us/</uri>
			
		</author>
	

	<link href="https://hollandvt.gov/atom.xml" rel="self" type="application/rss+xml" />
	<link href="https://hollandvt.gov/" rel="alternate" type="text/html" />

	<generator uri="http://jekyllrb.com" version="4.3.2">Jekyll</generator>

	
		<entry>
			<id>https://hollandvt.gov/community/open-source/</id>
			<title>Community-Driven Software</title>
			<link href="https://hollandvt.gov/community/open-source/" rel="alternate" type="text/html" title="Community-Driven Software" />
			<updated>2024-07-08T00:00:00+00:00</updated>

			
				
				<author>
					
						<name>Ed Brady</name>
					
					
					
						<uri>https://outsidethebox.bbbiz.us/</uri>
					
				</author>
			
			<summary>Open Source software is not only free to use and modify, it&apos;s community-driven.</summary>
			<content type="html" xml:base="https://hollandvt.gov/community/open-source/">&lt;h1 id=&quot;powered-by-open-source&quot;&gt;Powered By Open Source&lt;/h1&gt;

&lt;p&gt;You may be wondering what &lt;em&gt;“open source”&lt;/em&gt; is and how it’s relevant to this site. Generally speaking,
&lt;em&gt;open source&lt;/em&gt; can refer to any openly available information, but the term is commonly used to refer
specifically to &lt;em&gt;open source software&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Open source software is simply any software that makes the underlying code freely available and modifiable
by everyone. For example, you can see (and copy) all of the code that powers this website right &lt;a href=&quot;https://gitlab.com/website9940925/Website&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id=&quot;community-driven&quot;&gt;Community Driven&lt;/h2&gt;

&lt;p&gt;&lt;img src=&quot;/images/priscilla-du-preez-W3SEyZODn8U-unsplash.jpg&quot; alt=&quot;community&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Since anyone can view and modify open source code, the number of people contributing to a given project can quickly
surpass the number of contributors to a closed source counterpart. People contribute to open source software in various ways.&lt;/p&gt;

&lt;h4 id=&quot;common-contributions-can-come-in-the-form-of&quot;&gt;Common contributions can come in the form of:&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Reporting issues, ideas, and feature requests.&lt;/li&gt;
  &lt;li&gt;Writing code to address issues, features, and new ideas.&lt;/li&gt;
  &lt;li&gt;Testing and reviewing software/code.&lt;/li&gt;
  &lt;li&gt;Documenting and writing how-to guides.&lt;/li&gt;
  &lt;li&gt;Being an active user and sharing your experiences with given software.&lt;/li&gt;
  &lt;li&gt;Donating to help support the continued development of projects.&lt;/li&gt;
  &lt;li&gt;Many other forms…&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;From these various contributors, an open community is formed to collaborate toward common goals which result in free and open
technologies which are accessible to everyone.&lt;/p&gt;

&lt;h2 id=&quot;security&quot;&gt;Security&lt;/h2&gt;

&lt;p&gt;Despite common misconceptions in both directions, open source software isn’t inherently more or less secure than closed source software.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/john-salvino-bqGBbLq_yfc-unsplash.jpg&quot; alt=&quot;security&quot; /&gt;&lt;/p&gt;

&lt;p&gt;One commonly held belief by proponents of closed source software is that if anyone can read your code then “the cat’s out of the bag”, so to speak,
and any potential hacker could find the vulnerabilities and quickly exploit them. There is some truth in this, however this belief is based on the
concept of “security through obscurity” which is effectively the idea that if vulnerabilities are not “known” or obvious that things are secure.
This seems reasonable until you account for human ingenuity; people are clever and direct access to code is far from the only way to discover flaws
in various technologies. Vulnerabilities can go undiscovered for years by the companies who own the closed-source software, while potential bad actors
may quietly be discovering and taking advantage of those vulnerabilities long before they are ever fixed.&lt;/p&gt;

&lt;p&gt;A commonly held belief by proponents of open source software is that due to the fact the code can be thoroughly understood and scrutinized by anyone,
any potential vulnerabilities will be discovered and fixed quickly resulting in software that is difficult to exploit even if you understand exactly how it works.
There is also some truth in this, but this idea is based on a best case scenario. While many prominent open source software projects with big communities have positive security
track records, there are many projects which exist with only a small number of contributors. If there aren’t enough people consistently discovering and helping to
fix issues, they may never get resolved.&lt;/p&gt;

&lt;h2 id=&quot;closed-source-vs-open-source&quot;&gt;Closed Source Vs. Open Source&lt;/h2&gt;

&lt;p&gt;Closed source code is owned/developed by a company and more and more commonly are being provided as a service in the modern era of “cloud computing”.&lt;/p&gt;

&lt;h4 id=&quot;examples-of-closed-source-software&quot;&gt;Examples of closed source software:&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Microsoft Windows&lt;/li&gt;
  &lt;li&gt;Adobe Photoshop&lt;/li&gt;
  &lt;li&gt;Popular social media websites&lt;/li&gt;
  &lt;li&gt;Your banking website&lt;/li&gt;
  &lt;li&gt;Tractor ECU’s&lt;/li&gt;
  &lt;li&gt;Electronic voting machines&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Open source software may or may not be sponsored and primarily developed by a company, but the nature of it being open and free means it is typically community-driven. Despite
its often humble nature, open source software powers a significant portion of the internet and is even embedded inside many unsuspecting devices like your wireless router
or “smart” appliances.&lt;/p&gt;

&lt;h4 id=&quot;examples-of-open-source-software&quot;&gt;Examples of open source software:&lt;/h4&gt;

&lt;ul&gt;
  &lt;li&gt;Linux (Ubuntu/Red Hat/Android/embedded/etc.)&lt;/li&gt;
  &lt;li&gt;Wordpress&lt;/li&gt;
  &lt;li&gt;Apple’s underlying operating system (Darwin Unix)&lt;/li&gt;
  &lt;li&gt;Browsers like Firefox, Chromium (core of Chrome), Brave, etc.&lt;/li&gt;
  &lt;li&gt;The vast majority of programming languages everything else is developed on top of (C/Python/PHP/GO/Javascript/HTML/etc.)&lt;/li&gt;
  &lt;li&gt;This &lt;a href=&quot;https://gitlab.com/website9940925/Website&quot;&gt;website&lt;/a&gt;!&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;br /&gt;&lt;/p&gt;

&lt;p&gt;One is not objectively better than the other; they can both have their place. But when it comes to community, open source has a clear advantage.&lt;/p&gt;
</content>

			
				<category term="community" />
			
			
				<category term="open source" />
			
				<category term="software" />
			
				<category term="how it&apos;s made" />
			
				<category term="community" />
			

			<published>2024-07-08T00:00:00+00:00</published>
		</entry>
	
		<entry>
			<id>https://hollandvt.gov/info/about-posts/</id>
			<title>About Posts</title>
			<link href="https://hollandvt.gov/info/about-posts/" rel="alternate" type="text/html" title="About Posts" />
			<updated>2024-07-01T00:00:00+00:00</updated>

			
				
				<author>
					
						<name>Ed Brady</name>
					
					
					
						<uri>https://outsidethebox.bbbiz.us/</uri>
					
				</author>
			
			<summary>The purpose of posts vs regular pages</summary>
			<content type="html" xml:base="https://hollandvt.gov/info/about-posts/">&lt;p&gt;Most content on this website is organized in pages and accessible directly from the top navigation bar.
Content that is event-specific or a longer read typically lives in a blog style post (such as this) and
is accessible by following links to the blog section of this site which can be found at the bottom of the &lt;a href=&quot;/&quot;&gt;homepage&lt;/a&gt;.&lt;/p&gt;
</content>

			
				<category term="info" />
			
			
				<category term="info" />
			
				<category term="how it&apos;s made" />
			

			<published>2024-07-01T00:00:00+00:00</published>
		</entry>
	
</feed>