Update Readme (#16)

Author: thimmy687

Directory.Build.props

@@ -11,6 +11,7 @@
     <FileVersion>0.0.0.1</FileVersion>
     <InformationalVersion>0.0.0.1</InformationalVersion>
     <PackageVersion>0.0.0.1</PackageVersion>
+    <PackageTags>GitExtensions</PackageTags>
   </PropertyGroup>
 
   <PropertyGroup>

README.md

@@ -1,31 +1,20 @@
-# GitExtensions Plugin Template
-An example/empty repository for building a GitExtensions plugin that can be installed using [GitExtensions.PluginManager](https://github.com/gitextensions/gitextensions.pluginmanager).
-
-The package is going to be published on [NuGet.org](https://www.nuget.org/packages/GitExtensions.PluginTemplate) feed.
-
-## Files to keep an eye on
- - [Plugin.cs](src/GitExtensions.PluginTemplate/Plugin.cs)
- - [GitExtensions.PluginTemplate.csproj](src/GitExtensions.PluginTemplate/GitExtensions.PluginTemplate.csproj)
- - [GitExtensions.PluginTemplate.nuspec](src/GitExtensions.PluginTemplate/GitExtensions.PluginTemplate.nuspec)
- 
-### Nuspec
- - Place all content under lib folder. Custom nested folders are supported and path is preserved.
- - Add dependency on "virtual" package GitExtensions.Extensibility and target version `[3.0,3.1)` *.
- - Real package dependencies are not supported, so everything should be packed with the plugin.
- - Keep in mind that sharing common libraries can be cumbersome as these must match across all plugins and also Git Extensions itself. So my current recommendation is not to do so.
- 
-_* This is just my own eperience. Git Extensions follow SemVer, but it's public plugin API is not so rich that sometimes you need to kind a hack it using APIs that are not ment to be public. For these reasons its better to check compatibility with every single feature update._
-
-### Csproj
-
- - I'm using powershell script to download a selected version of Git Extensions from GitHub releases. This script runs before every build and checks if Git Extensions binaries are donwloaded.
- - CSproj references selected binaries from the downloaded Git Extensions.
- - After build a newly created binaries of the plugin is copied to Git Extensions plugins directory.
- - F5 is setup to start downloaded `GitExtensions.exe` for easy debugging.
- 
- ### Plugin.cs
-  - Nothing special, but ordinary Git Extensions plugin :-)
-
-## Icons
-
-Some icons by Yusuke [Kamiyamane](http://p.yusukekamiyamane.com).
+
+# GitExtensions.GerritPlugin
+
+GitExtensions.GerritPlugin is a plugin for GitExtensions to work with a [Gerrit](https://www.gerritcodereview.com/) as Git server.
+
+## Features
+
+* Gerrit hook installation
+* Patchset publish
+* Patchset download
+
+## Usage
+
+The cloned repository requires a `.gitreview` file, which is in use for the plugin to identify the gerrit server.
+This file must be located in root foilder of the repository.
+Get more information about this file [here](https://docs.openstack.org/infra/git-review/installation.html#gitreview-file-format)
+
+## GitExtensions Plugin Template infomration
+
+The [GitExtensions Plugin Template](https://github.com/gitextensions/gitextensions.plugintemplate) gives additional information about the pluign development.

contributors.txt

@@ -112,4 +112,5 @@ YYYY/MM/DD, github id, Full name, email
 2019/12/25, dfev77, Florin Daneliuc, [email protected]
 2020/01/02, c3er, Christian Dreier, flipper.x3r(at)googlemail.com
 2020/01/04, MarkJ74, Mark Jackson, markj74(at)outlook.com
-2020/01/07, asherber, Aaron Sherber, aaron(at)sherber.com
+2020/01/07, asherber, Aaron Sherber, aaron(at)sherber.com
+2021/01/17, thimmy687, Ricardo Krause, [email protected]

src/GitExtensions.GerritPlugin/GitExtensions.GerritPlugin.nuspec

@@ -5,6 +5,7 @@
     <version>$version$</version>
     <authors>$authors$</authors>
     <description>$description$</description>
+    <license type="file">LICENSE.md</license>
     <projectUrl>$projectUrl$</projectUrl>
     <tags>$tags$</tags>
     <dependencies>