Keeping open source projects - awesome-go

Beginning of any project (especially when we are talking about open source) is extremely entertaining for developer, over the years the fun passes and it is the responsibility to keep your “son” following the path of it. How did the starting awesome-go? All projects I started are out of necessity, the awesome-go was no different. After knowing the awesome-python and seeing other “awesomes” projects I searched for the awesome-go and did not get results.

avelino / awesome-go

A curated list of awesome Go frameworks, libraries and software

Awesome Go

We use the Golang Bridge community Slack for instant communication, follow the form here to join.

Sponsorships:

Special thanks to

Your app, enterprise-ready. Start selling to enterprise customers with just a few lines of code. Add Single Sign-On (and more) in minutes instead of months.	An open, source-available software licensing and distribution API. Securely license and distribute Go applications with a single API. Add auto updates with only a few lines of code.

Awesome Go has no monthly fee, but we have employees who work hard to keep it running. With money raised, we can repay the effort of each person involved! You can see how we calculate our billing and distribution as it is open to the entire community. Want to be a supporter of the project click here.

A curated list of awesome Go frameworks, libraries, and software. Inspired by awesome-python.

Contributing:

…

View on GitHub

How did the starting awesome-go?

All projects I started are out of necessity, the awesome-go was no different.
After knowing the awesome-python and seeing other “awesomes” projects I searched for the awesome-go and did not get results. Wanted to do a “simple” project where he had markdown code with a list of legal projects written in go, this in “Jul 6, 2014” with the commit “start environment Awesome for Go“
After many people help the project began to have access and receive contributions. That was the moment I realized I would have to write code to help revise the contributions (dubbed as pull request within GitHub). Maintainers have written test to validate the following patterns within the markdown:

• Test alphabetical order
• Test if exist duplicated links
• Test if an entry has description, it must be separated from link with -

Work that was done manually by the maintainers and the volume of contributions was virtually impossible to revise all.

Continue reading in avelino.run.