Permalink
Browse files

Merge pull request #535 from chocolatey/Gui-Blog

Chocolatey GUI 0.15.0 Blog Post
  • Loading branch information...
ferventcoder committed Oct 18, 2017
2 parents 5aa15b5 + 77e40cc commit 692e26da869582d7e225b940c84991d1d5c42315
@@ -30,7 +30,7 @@ Let’s take a little stroll through some of the interesting parts of Chocolatey
- April 1, 2011 – [Chris Ortman](https://twitter.com/chriso) writes the [first public blog post](https://chrisortman.wordpress.com/2011/04/01/getting-started-with-chocolatey/) about Chocolatey.
- April 26, 2011 – I [put up a video](https://www.youtube.com/watch?v=N-hWOUL8roU) showing Chocolatey installing 11 pieces of software. Pardon the music, it was swapped out from my original track.
- September 2011 – Community Repository ([https://chocolatey.org](https://chocolatey.org/)) introduced.
- September 7, 2011 – [Christiaan Baes](https://twitter.com/chrissie1) writes a [post about a side project](https://web.archive.org/web/20110926191629/http://blogs.lessthandot.com/index.php/DesktopDev/MSTech/chocolatey-gui) that is known as [ChocolateyGUI](https://github.com/chocolatey/ChocolateyGUI#features).
- September 7, 2011 – [Christiaan Baes](https://twitter.com/chrissie1) writes a [post about a side project](https://web.archive.org/web/20110926191629/http://blogs.lessthandot.com/index.php/DesktopDev/MSTech/chocolatey-gui) that is known as [Chocolatey GUI](https://github.com/chocolatey/ChocolateyGUI#features).
- October 07, 2011 – A year after NuGet was introduced, I blog about [Chocolatey for the first time](http://ferventcoder.com/archive/2011/10/07/letrsquos-get-chocolatey-kind-of-like-apt-get-for-windows.aspx).
- December 22, 2011 – [Anthony Mastrean](https://twitter.com/anthonymastrean/) [introduces Pester](https://github.com/chocolatey/chocolatey/pull/43) (a [PowerShell BDD testing framework](https://github.com/Pester/Pester)) to Chocolatey.
- March 2012 – Chocolatey is featured in the [Pro Nuget Book](http://www.amazon.com/Pro-NuGet-Experts-Voice-Microsoft/dp/1430241918/).
@@ -41,11 +41,11 @@ Let’s take a little stroll through some of the interesting parts of Chocolatey
- October 4, 2012 – [Guilhem Lettron](https://twitter.com/guilhemlettron) starts working on [Chef integration](https://github.com/chocolatey/chocolatey-cookbook/commit/99e151ca271ba8bf0f1e200a363649ceebf66daa).
- October 19, 2012 – After [putting](https://github.com/pester/Pester/commit/84d5acbab1d809a121378048908dd2a8b2dfefc9) [proper](https://github.com/pester/Pester/commit/ec77ceab7ba99bec93376ad6ca1f6f2d5dfc9d22) [mocking](https://github.com/pester/Pester/commit/4178c343a6574a8a9521be8a77006572fc49e311) [support](https://github.com/pester/Pester/commit/dd7dca288bf5d7258532243687b3f6b6e4936af3) into [Pester](https://github.com/pester/Pester), Matt Wrock [retrofits Chocolatey](https://github.com/chocolatey/chocolatey/commit/654703b9d4388eb385776986ce6d0ee53485a146) to use that.
- January 2013 – [Automatic packaging](https://github.com/chocolatey/choco/wiki/AutomaticPackages) is introduced.
- February 13, 2013 – [Gary Ewan Park](https://twitter.com/gep13) gives [ChocolateyGUI](https://chocolatey.org/packages/ChocolateyGUI) a new home and [takes over project maintenance](https://github.com/chocolatey/ChocolateyGUI/commit/c722821573cafce6bfb50760618a8c1803e76e7f).
- February 13, 2013 – [Gary Ewan Park](https://twitter.com/gep13) gives [Chocolatey GUI](https://chocolatey.org/packages/ChocolateyGUI) a new home and [takes over project maintenance](https://github.com/chocolatey/ChocolateyGUI/commit/c722821573cafce6bfb50760618a8c1803e76e7f).
- June 2013 – Community repo reaches [1,000 stable packages](http://ferventcoder.com/archive/2013/06/01/chocolatey-official-public-feed-now-has-1000-stable-packages.aspx).
- October 2013 – Community repo surpasses 1 million downloads.
- December 13, 2013 – First lines of the C# Chocolatey rewrite are [committed](https://github.com/chocolatey/choco/commit/b3dbcb851d95e9c0bd7f9f0438b7b087405e7e12).
- February 6, 2014 – [Richard Simpson](https://twitter.com/RichardSimp) joins Gary on [ChocolateyGUI](https://chocolatey.org/packages/ChocolateyGUI) and [commits the initial changes](https://github.com/chocolatey/ChocolateyGUI/commit/2d9bab432f58230f6c15f387608d58657201e536) for the modern version and look.
- February 6, 2014 – [Richard Simpson](https://twitter.com/RichardSimp) joins Gary on [Chocolatey GUI](https://chocolatey.org/packages/ChocolateyGUI) and [commits the initial changes](https://github.com/chocolatey/ChocolateyGUI/commit/2d9bab432f58230f6c15f387608d58657201e536) for the modern version and look.
- March 2014 – Microsoft validates the idea of Chocolatey.
- July 2014 – The Chocolatey package itself surpasses [1 million downloads](https://twitter.com/ferventcoder/status/490992889036419072).
- Sep 2014 – [Introduced Chocolatey Newsletter](http://codebetter.com/robreynolds/2014/09/27/chocolatey-newsletter/).
@@ -0,0 +1,74 @@
Url: chocolatey-gui-0.15.0-released
Title: Chocolatey GUI 0.15.0 has just been released!
Author: Gary Ewan Park
Published: 20171014
Tags: chocolatey oss, chocolatey gui, news, press-release
Keywords: chocolatey oss, chocolatey gui, news, press-release, chocolatey, automate existing systems, dev ops, software deployment automation, software management automation
Summary: Chocolatey GUI 0.15.0, the graphical user interface for Chocolatey, has just been released. This is a major release of the application which brings with it a number of improvements and features, as well as fixing a number of bugs.
---
We are very happy to announce the release of version 0.15.0 of Chocolatey GUI! This is a major overhaul of the application including a huge number of bug fixes, as well as a number of features and improvements. This release has been a while in the making, but we hope that it will be worth the wait!
The following will highlight a number of the major changes that are included in this release, and you can also see a full set of [release notes](https://github.com/chocolatey/ChocolateyGUI/releases/tag/0.15.0).
## Chocolatey Lib
In previous versions of Chocolatey GUI, we shelled out directly to PowerShell to invoke the various commands that are available within Chocolatey. In this release, we are now using the official [chocolatey.lib](https://www.nuget.org/packages/chocolatey.lib), which means we now have a much better integration with the features that Chocolatey offers. In doing this refactoring, we have also eliminated a number of the bugs that were present in the previous release, as well as significally improving the overall performance of Chocolatey GUI.
## New Branding
When we switched to using WPF as the base framework for Chocolatey GUI, we introduced what we thought was a sensible colour scheme, emphasing on the "chocolatey" theme. Looking back, we think we went a little too far. In the 0.15.0 release, we have changed the branding again, which is more in-keeping with the overall Chocolatey branding.
As an example of this change, the main Chocolatey GUI application screen has gone from this:
![Old Chocolatey GUI](https://github.com/chocolatey/ChocolateyGUI/blob/1a0a249ebcee29af10c9a09660a40dd2c34b5eb9/docs/assets/img/Screenshots/Showing_Only_Packages_With_Updates.png?raw=true)
to this:
![New Chocolatey GUI](https://github.com/chocolatey/ChocolateyGUI/blob/c7a92e35a4b7e43cc611d7f8fd854ba8bb3171e2/docs/input/assets/img/Screenshots/Application_Loaded.png?raw=true)
If you are interested in seeing more of the evolution of the branding for this release, you can follow along in this [commit](https://github.com/chocolatey/ChocolateyGUI/commit/ed894cc4e16abe5d33de1275efae49803d8d1919) and then this [commit](https://github.com/chocolatey/ChocolateyGUI/commit/c7a92e35a4b7e43cc611d7f8fd854ba8bb3171e2#diff-bcb0247f0d40fae191239e76914070a0).
We would love to hear any feedback that you might have related to the new branding. Feel free to reach out in our [Gitter Room](https://gitter.im/chocolatey/ChocolateyGUI) or open an issue for discussion on the [Chocolatey GUI repository](https://github.com/chocolatey/ChocolateyGUI).
## Localization of Chocolatey GUI
We know that Chocolatey GUI is used across the world, by speakers of lots of different languages. With this in mind, the decision was taken to support translation of all the major parts of Chocolatey GUI. This will be an ongoing effort, however, in this release, there is now support for English, Norwegian, German and Swedish.
If you are interested in helping support your language in Chocolatey GUI, then please reach out via an [issue on the GitHub repository](https://github.com/chocolatey/ChocolateyGUI/issues/new).
We are going to start using the amazing [Transifex](https://www.transifex.com/) service to better support this effort going forward.
## Release Notes
To find out information about all the features, improvements and bugs that were included in this release, have a look at the [release notes](https://github.com/chocolatey/ChocolateyGUI/releases/tag/0.15.0).
## Going forward...
Looking ahead, we have a number of things that we are thinking about for upcoming releases of Chocolatey GUI. These include things like:
* Making Accessibility of the Chocolatey GUI application a first class citizen
* Allowing modification of Chocolatey GUI colours/fonts - i.e. branding
## Contributors
This release would not have been possible without the help of the amazing Chocolatey Community! We thank you all for your support!
The people who helped out with this release are:
- [RichiCoder1](https://github.com/RichiCoder1)
- [pascalberger](https://github.com/pascalberger)
- [gep13](https://github.com/gep13)
- [mwallner](https://github.com/mwallner)
- [AdmiringWorm](https://github.com/AdmiringWorm)
- [magol](https://github.com/magol)
- [cniweb](https://github.com/cniweb)
- [ferventcoder](https://github.com/ferventcoder)
- Magnus Österlund
- [punker76](https://github.com/punker76)
### Learn More
* Check out the [documentation](https://chocolatey.github.io/ChocolateyGUI/about).
* Learn about other features available in [Chocolatey for Business](https://chocolatey.org/compare).
* [Contact us](https://chocolatey.org/contact) to find out more and setup your evaluation of Chocolatey for Business today.
@@ -36,7 +36,7 @@ Using a [local folder](https://chocolatey.org/docs/how-to-host-feed#local-folde
As your needs increase, you can easily move your local folder to a [CIFS (UNC) share](https://chocolatey.org/docs/how-to-host-feed#local-folder-unc-share-cifs). Both local folder and CIFS are quick to set up. It’s as easy as putting packages in a location and pointing to that location as the source. Permissions are based on what is already there — if you can get to the packages, you can install from there, and if you can put packages in the location, you have push permission.
A [Simple Server](https://chocolatey.org/docs/how-to-host-feed#simple-server) is ideal when you need more control over pushing packages or reaching a CIFS share is not easily possible. A simple server allows you to push and install from HTTP/HTTPS. The disadvantage here is that there is one shared key for pushing packages, so anyone that has push access can push any package. There is no fancy web site to view packages. All querying is done through choco.exe (or ChocolateyGUI). Most options for hosting packages are based on the simple server setup, including non-Windows options like [Sonatype Nexus](http://www.sonatype.org/nexus/go/) and [JFrog’s Artifactory](https://www.jfrog.com/artifactory/).
A [Simple Server](https://chocolatey.org/docs/how-to-host-feed#simple-server) is ideal when you need more control over pushing packages or reaching a CIFS share is not easily possible. A simple server allows you to push and install from HTTP/HTTPS. The disadvantage here is that there is one shared key for pushing packages, so anyone that has push access can push any package. There is no fancy web site to view packages. All querying is done through choco.exe (or Chocolatey GUI). Most options for hosting packages are based on the simple server setup, including non-Windows options like [Sonatype Nexus](http://www.sonatype.org/nexus/go/) and [JFrog’s Artifactory](https://www.jfrog.com/artifactory/).
The final option for the most complex scenarios is the [Package Gallery](https://chocolatey.org/docs/how-to-host-feed#package-gallery). A couple of examples are[Chocolatey.org](https://chocolatey.org/) and [NuGet.org](https://www.nuget.org/). You can have multiple types of package store, from file system to Azure blobs, and AWS S3. It has a database, indexing, and caching backing the package information, so it is super performant. And it has the idea of multiple users and rights assigned for each user to packages they maintain. Some disadvantages are that currently it only hosts on Windows and it requires more setup time.
@@ -29,7 +29,7 @@
<li>Packages can embed software, use UNC paths or download software from another location (like the official distribution locations).</li>
<li>Allows for community contributions.</li>
<li>Allows for pay for apps to be included as packages.</li>
<li>CLI focused, although there is a GUI (ChocolateyGUI).</li>
<li>CLI focused, although there is a GUI (Chocolatey GUI).</li>
<li>Easily scriptable which allows for adding setup scripts to things like source control.</li>
<li>Update apps simply by running <code>cup packagename</code> or <code>choco upgrade all</code>.</li>
<li>Integration with other package managers (Ruby Gems, Python PIP, WebPI, Windows Features, CygWin, etc).</li>
@@ -134,7 +134,7 @@
<li>Starts to affect performance once the source has over 2,000 packages for some sources. It depends on how they keep that information (in a db or file scans).</li>
<li>Authentication is typically limited to Basic Auth.</li>
<li>No moderation.</li>
<li>May not have a website for viewing package information. Use ChocolateyGUI for seeing package information.</li>
<li>May not have a website for viewing package information. Use Chocolatey GUI for seeing package information.</li>
<li>No package statistics for most of the simple server sources.</li>
<li>Package size may be limited to 28.61MB by default on some simple servers. Depending on your simple server - For IIS simple servers package size can be controlled through <a href="https://msdn.microsoft.com/en-us/library/ms689462(v=vs.90).aspx">maxAllowedContentLength</a> and <a href="https://msdn.microsoft.com/en-us/library/e1f13641(v=vs.100).aspx">maxRequestLength</a>. For others like Nexus, it may already be set very high. You can host the installer internally somewhere and access it through packaging though.</li>
</ul>
@@ -104,7 +104,7 @@
<p>Among the bug fixes, we&#39;ve brought Package Internalizer to the MSP edition of Chocolatey.</p>
<h3 id="bug-fixes-4">BUG FIXES</h3>
<ul>
<li>Fix - Configuration item is not serialized, causing issues with installs with packages.config and ChocolateyGUI.</li>
<li>Fix - Configuration item is not serialized, causing issues with installs with packages.config and Chocolatey GUI.</li>
<li>Package Synchronizer (Choco Sync):
<ul>
<li>Fix - syncing new items should capture audit information for Package Audit.</li>
@@ -28,7 +28,7 @@
</ul>
<!-- /TOC -->
<h2 id="summary">Summary</h2>
<p>We take security issues very seriously. Security falls into a few areas of the Chocolatey framework - the clients (choco.exe and ChocolateyGUI), and the community repository (aka <a href="https://chocolatey.org/packages" class="uri">https://chocolatey.org/packages</a>). While no one can give you a guarantee of complete security, we can provide information here for you to make the best decision for your use of Chocolatey. The most secure use of Chocolatey is when you use Chocolatey with packages that use embedded or local software resources. If you are super security conscious, you should understand the tradeoffs prior to using the community repository.</p>
<p>We take security issues very seriously. Security falls into a few areas of the Chocolatey framework - the clients (choco.exe and Chocolatey GUI), and the community repository (aka <a href="https://chocolatey.org/packages" class="uri">https://chocolatey.org/packages</a>). While no one can give you a guarantee of complete security, we can provide information here for you to make the best decision for your use of Chocolatey. The most secure use of Chocolatey is when you use Chocolatey with packages that use embedded or local software resources. If you are super security conscious, you should understand the tradeoffs prior to using the community repository.</p>
<ul>
<li>If you are an organization and you are using Chocolatey in the recommended way (internal repositories using packages that use internal resources only), Chocolatey is secure and reliable.</li>
<li>Using the community repository (<a href="https://chocolatey.org/packages" class="uri">https://chocolatey.org/packages</a>) is only as secure as the packages that you are using. While Chocolatey provides security features like checksumming, verification against VirusTotal (for packages and any binaries they contain or download), and moderation to be sure packages are using official binaries, there is no guarantee for what may be in the official distributions.</li>
@@ -83,7 +83,7 @@
<h2 class="text-center m-b">About the Official Chocolatey Client</h2>
<p>
The official Chocolatey client is the one you get from chocolatey.org on the <a href="https://chocolatey.org/packages/chocolatey">
package page</a>. This is the only official client. ChocolateyGUI is a recognized
package page</a>. This is the only official client. Chocolatey GUI is a recognized
client that is an extension of the official client. It is recommended you use the
official client as it has the latest security fixes, the latest features, and is
supported by the Chocolatey team.
@@ -129,7 +129,7 @@
<ul class="check-list m-t">
<li>The CLI client, choco.exe, was designed with security in mind. Know you are using Chocolatey from a trusted source when you are using the official Chocolatey clients.</li>
<li>Use choco.exe to install, upgrade, uninstall, publish and search for packages (and much more).</li>
<li>Use <a href="@Url.Package("ChocolateyGUI")" title="A visual of ChocolateyGUI">Chocolatey GUI</a> when you need a visual representation of packages.</li>
<li>Use <a href="@Url.Package("ChocolateyGUI")" title="A visual of Chocolatey GUI">Chocolatey GUI</a> when you need a visual representation of packages.</li>
<li>There is an <a href="@Url.RouteUrl(RouteName.Docs, new { docName = "features-infrastructure-automation" })#powershell-packagemanagement">official provider</a> for Windows 10/Windows Server 2016's built-in package manager (PowerShell PackageManagement) coming soon.</li>
</ul>
</div>
Oops, something went wrong.

0 comments on commit 692e26d

Please sign in to comment.