DEV Community

Cover image for Keeping open source projects - awesome-go
Thiago Avelino
Thiago Avelino

Posted on • Originally published at avelino.run on

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.

GitHub logo avelino / awesome-go

A curated list of awesome Go frameworks, libraries and software

awesome-go Awesome Go

Build Status Awesome Slack Widget Netlify Status Track Awesome List

awesome-go - Curated list awesome Go frameworks, libraries and software | Product Hunt

Sponsorships

Doppler

Digital Ocean

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.

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

Contributing

Please take a quick gander at the contribution guidelines first. Thanks to all contributors; you rock!

If you see a package or project here that is no longer maintained or is not a good fit, please submit a pull request to improve this file. Thank you!

Contents

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.

Discussion (0)