dev.to is now open source
Tags: meta, opensource
Published: 2018-08-08 17:01:59

---
title: dev.to is now open source
published: true
description: Let's do this together now :)
tags: meta, opensource
cover_image: https://thepracticaldev.s3.amazonaws.com/i/p5514uxlvliyevlpttun.png
---
 
Even though this release has been the culmination of a lot of hard work and hard thinking, this is not a finish line. It's a starting line.
 
{% github thepracticaldev/dev.to %}
 
Every time we've had the opportunity to let the community contribute in new ways, we have been surprised and amazed. I've seen this happen over and over again since the start of the project a few years ago. This is not a library, this is the codebase that runs this platform. And it's a lot of fun to share!
 
This new chapter is part of an ongoing effort to maintain and improve the transparency we strive for, and of course, an opportunity to improve and grow our lovely pile of code. As I mentioned in [my last post on the topic](https://dev.to/ben/the-devto-codebase-will-go-open-source-on-august-8-2kia), we are very excited about the possibility that, with your contributions, this platform can eventually be re-purposed for communities and ecosystems outside of our scope.
 
We will continue to maintain and grow our developer community, but as a strong open source project.  We imagine that this approach may lead to a lot of interesting and valuable use cases. We hope that some contributors come in with the goal of bolstering and improving [dev.to](/) itself, while others come to the project thinking about possible use cases as separate entities.
 
As this is the starting line, contributing guidelines and the open-source developer experience will need some ongoing improvements from us. So if you hit a stumbling block, we are here to help you, but we will also certainly make things better over time.

A huge thank you to our early contributors ([@briankephart](/briankephart), [@tiffanywismer](/tiffanywismer), [@yechielk](/yechielk), [@nektro](/nektro), [@nickytonline](/nickytonline), [@edemca](/edemca), [@citizen428](/citizen428), [@sabatesduran](/sabatesduran), [@rhymes](/rhymes), [@auua](/auua), [@twhite](/twhite), [@niko](/niko), [@arakodesigner](/arakodesigner) and [@joshichinmay](/joshichinmay)) for not only committing code, but for providing us with lots of insight into their developer experiences while we prepared the repo and documentation.

An additional thank you to the companies [Stride Consulting](https://www.stridenyc.com/) and [Planet Argon](https://www.planetargon.com/). They each chipped in pro-bono time and effort, and we appreciate their contributions to this process. Stride was especially responsive and supportive as soon as we reached out to them. They sent @edemca to work with us for several days to help audit and take this over the finish line. We are incredibly grateful. I'd be remiss if I didn't also mention [Corgibytes](https://corgibytes.com/), who also helped us way back in the winter, but really helped guide us to get to that point. Corgibytes specializes in identifying and paying down technical debt, which we definitely needed at the time. All three of these shops definitely get the DEV seal of approval.

If you are coming from elsewhere on the web, and are not familiar with [dev.to](/), we are a large online community of software developers committed to teaching one another, building our careers, and generally making software development a more collaborative, humane endeavor. We host articles and discussions that span from beginner to advanced, and as we grow we always work to foster a constructive environment that supports diverse use cases. As long as it is about code or the developer experience/life, all forms of blog posts and discussions are welcome.
 
Our members write posts, start discussions, and build their professional profiles. As we open-source, I'll remind folks that we are a for-profit company, but I can assure you that we are driven primarily by the values of building an inclusive and awesome software ecosystem. I'm sure everyone says this, but I think we wear it on our sleeves — the added transparency of open-sourcing should only help improve that accountability as we grow.
 
We are a [Ruby on Rails](https://github.com/rails/rails) app, with [Preact](https://github.com/developit/preact) on the front-end. We also have native apps on the way ([🍏](https://github.com/thepracticaldev/DEV-ios),[🤖](https://github.com/thepracticaldev/DEV-Android)). The technology choices will evolve over time. We are far from devotees to any one style, and while we are not going to change too much over night, we will encourage healthy discussions and debates over the choices along the way. We also have hard dependencies on some of our external services, but it's all up for change as we grow. These discussions will be half the fun!

The core project is licensed under [Affero GPL 3.0](https://www.gnu.org/licenses/agpl-3.0.en.html), a copyleft license used by similar projects. Any libraries built or extracted at any point in our future will be made available under MIT.
 
I’ll finish up with a reminder that we are very serious about our [code of conduct](https://dev.to/code-of-conduct), and we expect everyone to behave with respect for all involved.
 
Happy coding ❤️