Site updated at 2017-01-28 23:55:35 UTC
This commit is contained in:
Travis CI
parent
017e728923
commit
f772530e97
28 changed files with 65 additions and 171 deletions
|
|
@ -111,6 +111,7 @@
|
|||
|
||||
<p>On Saturday, we released <a href="/blog/2016/10/22/flash-briefing-updater-hacktoberfest/#comment-2965607849">Home Assistant 0.31</a> which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.</p>
|
||||
|
||||
<a name="read-more"></a>
|
||||
<h2><a class="title-link" name="why-we-changed-the-updater" href="#why-we-changed-the-updater"></a> Why we changed the updater</h2>
|
||||
<p>This change was driven by two important factors.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -122,6 +122,7 @@
|
|||
The Christmas tree in action.
|
||||
</p>
|
||||
|
||||
<a name="read-more"></a>
|
||||
<p>During the time by tree was set up, I had 7,366 visitors from 88 countries connect to my Home Assistant instance. This generated an estimated 100,000 clicks on the switches in my Home Assistant instance - thanks in part to some folks who posted up with macros for 6-8 hour stretches.</p>
|
||||
|
||||
<p class="img">
|
||||
|
|
|
|||
|
|
@ -121,6 +121,7 @@
|
|||
|
||||
<p>Starting today we are announcing a few initiatives to help protect our users, contributors and community members.</p>
|
||||
|
||||
<a name="read-more"></a>
|
||||
<h2><a class="title-link" name="code-of-conduct" href="#code-of-conduct"></a> Code of Conduct</h2>
|
||||
|
||||
<p>More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we’re introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.</p>
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@
|
|||
<div class="meta clearfix">
|
||||
<time datetime="2017-01-28T08:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> January 28, 2017</time>
|
||||
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter et al.</span>
|
||||
<span><i class='icon-time'></i> eight minutes reading time</span>
|
||||
<span><i class='icon-time'></i> nine minutes reading time</span>
|
||||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
|
|
@ -125,6 +125,9 @@
|
|||
|
||||
<p>Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.</p>
|
||||
|
||||
<h3><a class="title-link" name="new-customization-options" href="#new-customization-options"></a> New customization options</h3>
|
||||
<p><a href="https://github.com/andrey-git">@Andrey-git</a> has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.</p>
|
||||
|
||||
<h3><a class="title-link" name="major-wink-and-hdmi-cec-improvements" href="#major-wink-and-hdmi-cec-improvements"></a> Major Wink and HDMI CEC improvements</h3>
|
||||
<p><a href="https://github.com/w1ll1am23">@w1ll1am23</a> did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your <code class="highlighter-rouge">configuration.yaml</code> file, no <code class="highlighter-rouge">client_id</code> and <code class="highlighter-rouge">client_secret</code> are needed, and token which was generated with the generator located in the <a href="https://home-assistant.io/components/wink/">Wink</a> documentation.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: community | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/community/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -31,6 +31,7 @@ I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Sw
|
|||
The Christmas tree in action.
|
||||
</p>
|
||||
|
||||
<!--more-->
|
||||
During the time by tree was set up, I had 7,366 visitors from 88 countries connect to my Home Assistant instance. This generated an estimated 100,000 clicks on the switches in my Home Assistant instance - thanks in part to some folks who posted up with macros for 6-8 hour stretches.
|
||||
|
||||
<p class='img'>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Device-Tracking | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/device-tracking/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: ESP8266 | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/esp8266/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: How-To | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/how-to/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: iBeacons | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/ibeacons/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Internet-of-Things | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/internet-of-things/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: IoT-Data | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/iot-data/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Micropython | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/micropython/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: MQTT | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/mqtt/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Organisation | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/organisation/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -30,6 +30,7 @@ The Home Assistant project and community has seen enormous growth in the last th
|
|||
|
||||
Starting today we are announcing a few initiatives to help protect our users, contributors and community members.
|
||||
|
||||
<!--more-->
|
||||
## <a class='title-link' name='code-of-conduct' href='#code-of-conduct'></a> Code of Conduct
|
||||
|
||||
More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we're introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.
|
||||
|
|
@ -118,6 +119,7 @@ We hope you understand that our desire with these changes is only to help protec
|
|||
<id>https://home-assistant.io/blog/2016/10/25/explaining-the-updater</id>
|
||||
<content type="html"><![CDATA[On Saturday, we released [Home Assistant 0.31][0.31] which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
|
||||
|
||||
<!--more-->
|
||||
## <a class='title-link' name='why-we-changed-the-updater' href='#why-we-changed-the-updater'></a> Why we changed the updater
|
||||
This change was driven by two important factors.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: OwnTracks | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/owntracks/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Presence-Detection | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/presence-detection/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Public-Service-Announcement | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/public-service-announcement/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Release-Notes | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/release-notes/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -34,6 +34,9 @@ After a security audit by Stephen O'Conner, he found that our source for randoml
|
|||
|
||||
Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.
|
||||
|
||||
### <a class='title-link' name='new-customization-options' href='#new-customization-options'></a> New customization options
|
||||
[@Andrey-git] has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.
|
||||
|
||||
### <a class='title-link' name='major-wink-and-hdmi-cec-improvements' href='#major-wink-and-hdmi-cec-improvements'></a> Major Wink and HDMI CEC improvements
|
||||
[@w1ll1am23] did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your `configuration.yaml` file, no `client_id` and `client_secret` are needed, and token which was generated with the generator located in the [Wink][wink] documentation.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Survey | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/survey/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Talks | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/talks/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Technology | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/technology/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: User-Stories | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/user-stories/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Video | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/video/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Website | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/website/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-01-28T23:48:44+00:00</updated>
|
||||
<updated>2017-01-28T23:52:58+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
102
blog/index.html
102
blog/index.html
|
|
@ -91,7 +91,7 @@
|
|||
<div class="meta clearfix">
|
||||
<time datetime="2017-01-28T08:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> January 28, 2017</time>
|
||||
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter et al.</span>
|
||||
<span><i class='icon-time'></i> eight minutes reading time</span>
|
||||
<span><i class='icon-time'></i> nine minutes reading time</span>
|
||||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
|
|
@ -129,6 +129,9 @@
|
|||
|
||||
<p>Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.</p>
|
||||
|
||||
<h3><a class="title-link" name="new-customization-options" href="#new-customization-options"></a> New customization options</h3>
|
||||
<p><a href="https://github.com/andrey-git">@Andrey-git</a> has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.</p>
|
||||
|
||||
<h3><a class="title-link" name="major-wink-and-hdmi-cec-improvements" href="#major-wink-and-hdmi-cec-improvements"></a> Major Wink and HDMI CEC improvements</h3>
|
||||
<p><a href="https://github.com/w1ll1am23">@w1ll1am23</a> did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your <code class="highlighter-rouge">configuration.yaml</code> file, no <code class="highlighter-rouge">client_id</code> and <code class="highlighter-rouge">client_secret</code> are needed, and token which was generated with the generator located in the <a href="https://home-assistant.io/components/wink/">Wink</a> documentation.</p>
|
||||
|
||||
|
|
@ -297,84 +300,10 @@ Climate - EQ3 BT smart: Add reporting for availability (<a href="https://github.
|
|||
|
||||
<p>Starting today we are announcing a few initiatives to help protect our users, contributors and community members.</p>
|
||||
|
||||
<h2><a class="title-link" name="code-of-conduct" href="#code-of-conduct"></a> Code of Conduct</h2>
|
||||
|
||||
<p>More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we’re introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.</p>
|
||||
|
||||
<p>Moving forward this Code of Conduct will be active for all projects within the Home Assistant organisation.</p>
|
||||
|
||||
<p><a href="/developers/code_of_conduct/">Read the Code of Conduct</a></p>
|
||||
|
||||
<h2><a class="title-link" name="contributor-license-agreement" href="#contributor-license-agreement"></a> Contributor License Agreement</h2>
|
||||
|
||||
<p>Moving forward we will also require that all contributors to any project have electronically signed our <a href="/developers/cla/">contributor license agreement (CLA)</a>. <del>We have adopted the CLA that GitHub uses for their projects</del> (see update at the top). Currently we have no plans to retroactively require a CLA for previous contributions, only those going forward.</p>
|
||||
|
||||
<p>Until a signed CLA is on file your pull request will not be reviewed or accepted. When you open a new pull request, if you do not have a CLA on file, our helpful bot will walk you through the steps to complete the process.</p>
|
||||
|
||||
<p><strong>We intend to require an electronically signed contributor licensing agreement for all contributors beginning with our next release (0.37), currently scheduled for release on Saturday, January 28th, 2017 (one week from today).</strong> The CLA is being added to all repositories today.</p>
|
||||
|
||||
<p>A CLA is difficult to describe but GitHub did an excellent job so this next section is taken from <a href="https://cla.github.com/">https://cla.github.com</a>:</p>
|
||||
|
||||
<h3><a class="title-link" name="what-is-a-contributor-license-agreement" href="#what-is-a-contributor-license-agreement"></a> What is a Contributor License Agreement?</h3>
|
||||
|
||||
<p>A Contributor License Agreement, known as a CLA, asks contributors to confirm that:</p>
|
||||
|
||||
<ol>
|
||||
<li>Anyone can use your contributions anywhere, for free, forever.</li>
|
||||
<li>Your contributions do not infringe on anyone else’s rights.</li>
|
||||
</ol>
|
||||
|
||||
<p>The GitHub CLA helps ensure the smooth operation and usability of the open source projects that we maintain.</p>
|
||||
|
||||
<h3><a class="title-link" name="why-is-a-cla-necessary" href="#why-is-a-cla-necessary"></a> Why is a CLA necessary?</h3>
|
||||
|
||||
<p>It depends on the jurisdiction, but in the United States, contributions are owned by the author or their employer. When the contribution is accepted, the project becomes a bundle of derivative works. The agreement of all contributors are necessary to maintain distribution of the complete project and to any licensing agreement.</p>
|
||||
|
||||
<h3><a class="title-link" name="isnt-that-the-purpose-of-an-open-source-license" href="#isnt-that-the-purpose-of-an-open-source-license"></a> Isn’t that the purpose of an open source license?</h3>
|
||||
|
||||
<p>Most open source licenses deal with use of the original code, and don’t refer to contributions, or derivatives of the original.</p>
|
||||
|
||||
<h3><a class="title-link" name="how-does-a-cla-protect-a-project" href="#how-does-a-cla-protect-a-project"></a> How does a CLA protect a project?</h3>
|
||||
|
||||
<p>If the owner of a contribution decides that they don’t want the contribution to be part of the project or in any given distribution, the law is on their side. The project, contributors, and users may be subject to legal action. This may require payment of damages and could prevent further usage or contributions until the matter is resolved.</p>
|
||||
|
||||
<p>Even when there is no legal pursuit, too much ambiguity can jeopardize or doom a project by preventing those that can’t risk legal action from getting involved.</p>
|
||||
|
||||
<h3><a class="title-link" name="why-does-it-seem-like-only-corporate-projects-have-a-cla" href="#why-does-it-seem-like-only-corporate-projects-have-a-cla"></a> Why does it seem like only “corporate” projects have a CLA?</h3>
|
||||
|
||||
<p>There are many projects without corporate ownership that use a CLA or even a copyright assignment: jQuery and Eclipse, for example. However, it is true that projects with financial backing tend to be at a higher risk of becoming a target, so they may have a lower tolerance for legal ambiguity.</p>
|
||||
|
||||
<h2><a class="title-link" name="security-requirements" href="#security-requirements"></a> Security requirements</h2>
|
||||
|
||||
<p>With more collaborators involved with Home Assistant we are also exposing ourselves to more risk as more people have write access. As such we taking the following steps.</p>
|
||||
|
||||
<ol>
|
||||
<li>As of November 3rd, 2016, all collaborators have been required to have 2 factor authentication (2FA) enabled on their GitHub account.</li>
|
||||
<li>Going forward, we will do an audit from time to time and strip collaborators from write access if they haven’t contributed for a while. This is in no sense meant to boot people, and you are absolutely eligible to get it back in the future when you wish start contributing again.</li>
|
||||
</ol>
|
||||
|
||||
<h2><a class="title-link" name="licensing" href="#licensing"></a> Licensing</h2>
|
||||
|
||||
<p>We will now ensure that a <code class="highlighter-rouge">LICENSE.md</code> file exists in all projects under the Home Assistant organization and is an <a href="https://opensource.org/licenses">OSI approved open source license</a> or a <a href="https://creativecommons.org">Creative Commons</a> license.</p>
|
||||
|
||||
<h3><a class="title-link" name="code-license" href="#code-license"></a> Code License</h3>
|
||||
|
||||
<p>The chosen license for all code projects under the Home Assistant organization is <a href="/developers/license/">the Apache 2.0 license</a>.</p>
|
||||
|
||||
<h3><a class="title-link" name="documentation-license" href="#documentation-license"></a> Documentation License</h3>
|
||||
|
||||
<p>All content on home-assistant.io and all other documentation/asset projects under the Home Assistant organization will be licensed under the Creative Commons License, specifically the <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">Attribution-NonCommercial-ShareAlike 4.0 International</a> license.</p>
|
||||
|
||||
<h2><a class="title-link" name="crediting-contributors" href="#crediting-contributors"></a> Crediting contributors</h2>
|
||||
|
||||
<p>We have now mostly automated updating the <a href="/developers/credits/">Credits</a> page so that contributors get their attribution more quickly.</p>
|
||||
|
||||
<h2><a class="title-link" name="in-closing" href="#in-closing"></a> In closing</h2>
|
||||
|
||||
<p>We hope you understand that our desire with these changes is only to help protect the amazing community that has been built around Home Assistant. If you have any questions, please contact us via email, Twitter or Gitter.</p>
|
||||
|
||||
|
||||
|
||||
<a class="btn pull-right" href="/blog/2017/01/21/home-assistant-governance/#read-more">Read on →</a>
|
||||
|
||||
</div>
|
||||
</article>
|
||||
<hr>
|
||||
|
|
@ -624,25 +553,10 @@ You have to note:
|
|||
The Christmas tree in action.
|
||||
</p>
|
||||
|
||||
<p>During the time by tree was set up, I had 7,366 visitors from 88 countries connect to my Home Assistant instance. This generated an estimated 100,000 clicks on the switches in my Home Assistant instance - thanks in part to some folks who posted up with macros for 6-8 hour stretches.</p>
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/blog/2017-01-bruh-christmas/stats.png" />
|
||||
View counts of the video.
|
||||
</p>
|
||||
|
||||
<p>I’m very excited to report that Home Assistant didn’t crash a single time. In fact, it didn’t even bog down or need to be restarted. The Wemo Insight and Sonoff relays were incredibly resilient, as well. I only had one Sonoff failure and two Wemo Insight failures both of which were resolved by power cycling them. The digital LED strips also fared pretty well, hanging up only twice, aside from a loose connector.</p>
|
||||
|
||||
<p>I would like to send a big thank you to the Home Assistant developers who have worked so hard on making Home Assistant run so well. This project is a testament to your hard work on making Home Assistant one of the best home automation platforms out there. Thank you!</p>
|
||||
|
||||
<p>I’m looking forward to continuing my home automation adventures with Home Assistant and I can’t wait for next Christmas with an even bigger and badder tree. :)</p>
|
||||
|
||||
<p>Wishing everyone the best in 2017!</p>
|
||||
|
||||
<p>Cheers! -Ben</p>
|
||||
|
||||
|
||||
|
||||
<a class="btn pull-right" href="/blog/2017/01/03/control-my-christmas-tree-stats/#read-more">Read on →</a>
|
||||
|
||||
</div>
|
||||
</article>
|
||||
<hr>
|
||||
|
|
|
|||
|
|
@ -115,48 +115,10 @@
|
|||
<div class="entry-content clearfix">
|
||||
<p>On Saturday, we released <a href="/blog/2016/10/22/flash-briefing-updater-hacktoberfest/#comment-2965607849">Home Assistant 0.31</a> which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.</p>
|
||||
|
||||
<h2><a class="title-link" name="why-we-changed-the-updater" href="#why-we-changed-the-updater"></a> Why we changed the updater</h2>
|
||||
<p>This change was driven by two important factors.</p>
|
||||
|
||||
<h3><a class="title-link" name="improving-the-security-of-the-users" href="#improving-the-security-of-the-users"></a> Improving the security of the users.</h3>
|
||||
|
||||
<p>As a user, you will be able to be notified if you are running a Home Assistant version that includes components that have known security flaws.</p>
|
||||
|
||||
<p>Although we hope to not have to use this feature often, it is important for us to be able to reach out to impacted users. We had the need for such a feature once in the past. Due to a bug the forecast.io sensor was making a huge amount of API requests causing some of our users to get charged because they went over the free quota.</p>
|
||||
|
||||
<p>Please note that this functionality is not done yet but will be available in a future release.</p>
|
||||
|
||||
<h3><a class="title-link" name="focusing-our-resources-where-it-matters" href="#focusing-our-resources-where-it-matters"></a> Focusing our resources where it matters</h3>
|
||||
|
||||
<p>As developers of Home Assistant, we will be able to see in what kind of environments Home Assistant is running. Here’s a few data points we didn’t have until now:</p>
|
||||
|
||||
<ul>
|
||||
<li>Total number of instances</li>
|
||||
<li>Which operating systems versions and flavors are in use</li>
|
||||
<li>Python version</li>
|
||||
<li>What option is more popular: Docker, Virtualenv or bare metal installs?</li>
|
||||
<li>How popular is our new <a href="/blog/2016/10/01/we-have-raspberry-image-now/">Raspberry Pi image</a>?</li>
|
||||
</ul>
|
||||
|
||||
<h2><a class="title-link" name="why-we-look-up-your-ip-address-with-geoip" href="#why-we-look-up-your-ip-address-with-geoip"></a> Why we look up your IP address with GeoIP</h2>
|
||||
<p>We store the city so that we can see where our users are from. This information will be used to give us a better insight in where our users are from. This will help us gather data to see if we should for example prioritize internationalization. In addition, we previously had a nasty bug with the <code class="highlighter-rouge">sun</code> component in which users above a certain latitude were having crashes multiple times a day. Had the updater component been in place we could have targeted a special priority update notification only to them.</p>
|
||||
|
||||
<p>As stated in the release blog post, the location information is <em>not</em> provided by your local Home Assistant installation but is instead gathered by comparing your IP address against the <a href="https://dev.maxmind.com/geoip/geoip2/geolite2/">GeoLite2 data created by MaxMind</a>. From their documentation:</p>
|
||||
|
||||
<blockquote>
|
||||
<p>IP geolocation is inherently imprecise. Locations are often near the center of the population. Any location provided by a GeoIP database should not be used to identify a particular address or household.</p>
|
||||
</blockquote>
|
||||
|
||||
<h2><a class="title-link" name="why-is-it-enabled-by-default" href="#why-is-it-enabled-by-default"></a> Why is it enabled by default</h2>
|
||||
<p>We decided to have it enabled by default because we consider the information that is gathered not harmful. We understand that not everyone will agree with us and so we have provided <a href="/components/updater/">multiple ways to opt out</a>.</p>
|
||||
|
||||
<p>It is in our short-term planning to add an option to control this to our frontend.</p>
|
||||
|
||||
<h2><a class="title-link" name="source-code" href="#source-code"></a> Source Code</h2>
|
||||
<p>The source code of our updater AWS Lambda function is now available <a href="https://github.com/home-assistant/Analytics-Receiver">here</a>.</p>
|
||||
|
||||
|
||||
|
||||
<a class="btn pull-right" href="/blog/2016/10/25/explaining-the-updater/#read-more">Read on →</a>
|
||||
|
||||
</div>
|
||||
</article>
|
||||
<hr>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue