open-source

practice

access from corporate context

behind a proxy

Recommendation: use a local proxy (e.g. this one) and chain this to your corporate proxy.

Advantage: cross application, unified local proxy settings for in- and external traffic rules

Simply configure within all applications your local “ProxyChain”. For e.g. git you have to configure your git config --global -l .gitconfig like

[url "http://"]
	insteadOf = git://
[http]
	sslVerify = false
	proxy = "http://localhost:8888"
[https]
        sslVerify = false
	proxy = "http://localhost:8888"

e.g. by using the following commands

git config --global url."http://".insteadOf git://

// ProxyProxy setting(s)
git config --global http.sslVerify false
git config --global http.proxy "http://localhost:8888"

git config --global https.sslVerify false
git config --global https.proxy "http://localhost:8888"

release engineering

building

Travis-CI

releasing

Github Releases

Create releases to bundle and deliver iterations of a project to users.

Maven Release Plugin

A plugin to release a project with Maven, saving a lot of repetitive, manual work.

semantic-release

Fully automated version management and package publishing. Highlights:

publishing

Maven artifacts

project metrics

Such metrics may be related to your builds, chats, dependencies, sizes, downloads, funding, issue tracking, licenses, rating, social media, versioning, platform and version support, monitoring and more.

highlight important stats with badges from shields.io e.g. GitHub stars