rizkiv1

Coding Conventions

This file will cover important coding practices that are important to stress when coding this program. Listed below are some of the more important details that should be stressed. Each programmer has his/her own way to deliver code. The importance of having similar coding conventions throughout this program are listed below.

80% of the time spent on a piece of software goes to maintenance.
Hardly any software is maintained for its whole life by the original author.
Code conventions improve the readability of the software, allowing engineers to understand new code more quickly and thoroughly.
If you ship your source code as a product, you need to make sure it is as well packaged and clean as any other product you create.

	Here's what I ended up doing - it worked perfectly. Note that I was moving from my old host (Bitbucket) to my new one (Gitlab). My comments are above the commands:

	# First, shallow-clone the old repo to the depth we want to keep
	git clone --depth=50 https://[email protected]/....git

	# Go into the directory of the clone
	cd clonedrepo

	# Once in the clone's repo directory, remove the old origin
	git remote remove origin

	// ==UserScript==
	// @name YouTube Disable Normalization
	// @namespace http://tampermonkey.net/
	// @version 0.1
	// @description Allows true 100% volume on youtube videos.
	// @author Wouter Gerarts
	// @match https://www.youtube.com/*
	// @match https://youtube.com/*
	// @grant none
	// ==/UserScript==

	defaults
	timeout connect 5s
	timeout client 24h
	timeout server 24h

	global
	log /dev/log local0

	frontend ssl
	log global