In a way, because the lion's share of our technologies, libraries, tools, and projects are open source, nearly everything qualified for this tag before. It was becoming our site's junk drawer as it were - lots of nifty and useful stuff, but no semblance of organization to any of it.
Since DEV.to rolled out Listings, I'm taking the opportunity to narrow the tag focus a bit. The goal is to give the #opensource tag clear topic boundaries, so Following it doesn't lead to a bunch of irrelevant posts leaking into your feed.
I've updated the tag guidelines, but I wanted to lay out the changes here.
Posts promoting a single project should go on Listings.
Posts using or mentioning one or more open source projects should go on the appropriate tags for the relevant languages and technologies. This includes tutorials, "round ups", guides, comparisons, reviews, and the like. These typically land in #opensource, and are the main reason for the tag clutter.
Announcements relating to your awesome project, including new features, releases, versions, and the like, should go on Listings, or should be expanded out into a proper article (tutorial, maybe?) and posted on the appropriate technology tags.
If you're just bursting with pride at something you built, use the
All this mainly means the
#opensource tag is no longer valid merely if the project(s) being discusses happen to be open source!
To put that another way, here's a few theoretical topics which would have been #opensource material before, but aren't now.
- "Top 10 Open Source Python Data Modules" (
- "My Awesome Data Visualizer in Go" (
- "Looking for contributors to Supercoolproject" (Listings or
- "What I did on my Perl project this week" (
- "Installing Epictool on Ubuntu" (
Articles in this tag should be about at least one of these three broad topics:
Organizing, managing, running, or working in an Open Source project.
Open Source philosophy, licensing, and/or practical and legal topics thereof.
Advocacy and adoption of Open Source technology.
#freesoftware have been aliased over to
#opensource (thanks @michaeltharrington
!) and the tag info updated to account for that. I know that Free Software is culturally distinct from Open Source, but as the former is always compliant to a subset of the latter, having one tag for all just makes sense.
I won't be applying this to any posts before July 17th (retroactive guidelines just aren't fair).
#opensource tag is used incorrectly in new posts, I'll remove it and provide a friendly reminder, along with suggestions on better tags to use. I know it'll take a while to get used to the updated rules, so don't worry if you miss it a few dozen times.
As software gets more and more integrated into our lives, the industrialization of its crafting process becomes inevitable. But the over-generalization of software engineering can be crushing the creative side of programming.