Code awesome Go libraries

To have a good idea won’t guarantee your project is succeed. You need to apply the best practices to make it well-known.

Docs

Code style

Testing

High test coverage for your project won’t guarantee a project without bugs. On the other hand, a high coverage makes your project easier to understand by other people.

Makefile

Thanks to Makefiles, your go development process is more effective and fluent. A nice example be found here.

Continuous Integration

Integrate a CI tool to your project and display the status in your README.md. Best known ci tools are Travis and Circle. Several examples can be found on the net.

Releases

Create new releases of your project as long as new functionality needs to be provided. bugs fixed for previous releases.

Semantic versioning is the way to name our releases. A nice article can be found here

Issues & Pull Requests

Badges

There’re many other sites in which you could obtain badges.

Announce your project

Let’s people know about your project

Be awesome!

When your project is mature enough and you went through the above steps, you should make your project part of awesome-go community.

https://github.com/avelino/awesome-go

wesovilabs

wesovilabs articles

wesovilabs

wesovilabs articles

Iván Corrales Solera

Written by

wesovilabs

wesovilabs articles