antz

Posh Git uses a powershell session to host git and allows for a much better git experience on windows. As an example, my git prompt displays as follows: First part is the current path, master is the branch that i'm on. Green shows files are added, modified or removed in the current commit, Red shows files are added, modified or removed which are not part of the current commit, How to install Posh-Git 1) Open powershell 2) Enter the following: Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Confirm Answer Yes to any prompts that appear. 3) Enter the following to install NuGet (if you haven't already): PowerShellGet\Install-Module NuGet -Scope CurrentUser -Force 4) Enter the following to install Posh-Git: PowerShellGet\Install-Module posh-git -Scope CurrentUser -Force 5) Import Posh-Git into powershell: Import-Module posh-git 6) Set powershell to import Posh-Git by default: Add-PoshGitToProfile -AllHosts That's it, navigate to a folder containing a git repo to discover the magic. Original Articles: Dahlbyk - Posh-Git Computering For Geeks - Posh-Git

In previous years we had a roadmap of changes we wanted to implement. However, we are a small team and it seemed silly to specify a set of things to do on a time scale. If you think you can help us do any of these, please contact @antz or @madmax and we can discuss things in more detail. MaNGOS (C++) Build System B1) When selecting only to build extraction tools, the build fails. B2) Modify the build system on Mangos Three & Four to match that of Mangos Zero-Two. B3) Apply updates from Mangos Zero-Two into Three/Four. Extraction Tools E1) Modify the Unified Extractors to support the changes in Mangos Three & Four. E2) Add functionality to load DBC data into a database (along with the core code to read from Database rather than DBC files) and change the extraction process to include importing into a DB for use by the core. Including Multiple locale support. Database changes D1) Apply changes to standardise the Databases across the cores. D2) Merge all the different xxx_loot_template tables into a single table with a Loot Type Field (along with the core changes to support this). D3) Extract the character table data field (all the character stat data) into a table containing the required named fields. Including Item_Instance. D4) Modify the EventAI Database (and Core) to support the TC style handling (SAI). D5) Complete the Command Help localisation for Mangos One, Two, Three and Four. D6) Complete the Achievement localisation for Mangos Two, Three and Four. D7) Move some hardcoded values from the core into the DB, possibly some enums as well. D8) Change defaults in DB table in order to fit latests MYSQL standards. D9) Add support for Broadcast text table and move all text tables to use that. Core C1) Standardise the naming of functions across the cores. C2) Implement standard account handling across the cores (Mangos Zero is the odd one out with reduced functionality). C3) Implement Playerbot functionality to Mangos One and above. C4) Add Cinematic Manager to the cores - Based on the work of TC/Cmangos. C5) Redo the server commands to make them a bit more standard and obvious. C6) Break out AHBot into its own daemon process. C7) Develop a mangos update daemon, which allows the ability to apply DB content and minor updates automatically. C8) Apply useful updates from other cores into Mangos cores. Other R1) Reorganise the core into a 'mangos core' set of files functions which are shared by all the cores and a module for each core which contains the code just for that core. MangosSharp (C#) Core C1) Modify the extraction tools / Core to use the same .map files as main MaNGOS C2) Fix up the many current issues with this young core Database D1) Adapt the current databases to match the standard MaNGOS ones