DEV Went Open Source One Year Ago Today, And We Have So Much More Planned!

Ben Halpern on August 08, 2019

Today marks one full year since DEV went open source. Operating out in the open has become such a core value and entrenched principle of how we bui... [Read Full]
markdown guide
 

I can't believe it's been one year. It feels like we open-sourced just yesterday, and also like it's already been ages.

Being able to collaborate directly alongside the community is the most special part of this entire project and company. A platform where the community members can be content-authors, bug-fixers, features-builders, and feedback-providers is truly a powerful and amazing thing.

It's been wonderful growing alongside all of you, and I can't wait for this next phase of the shared journey.

 

A quick trip down memory lane:

I remember how happy I was when DEV announced they had opened up their source code last August, I immediately jumped at the opportunity to collaborate. I just checked on GitHub and my first PR is dated exactly one day after that 😅

Automatically check vulnerabilities before deployment #303

rhymes avatar
rhymes commented on Aug 09, 2018

What type of PR is this? (check all applicable)

  • [ ] Refactor
  • [X] Feature
  • [ ] Bug Fix

Description

bundler-audit is a well known tool that helps keeping an eye on known vulnerabilities.

I think passing its check should be a pre-requisite for each build.

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

  • [ ] docs.dev.to
  • [ ] readme
  • [X] no documentation needed

A few months passed and they had graciously accepted in the code the 50th PR:

Around a couple of months later I ended up joining the team.

I can't thank enough the DEV team and their core values. This website I'm writing this comment on being open is a part of those values.

If you're in doubt, know that any contribution is welcome: ideas, bug reports, frontend and backend code, documentation, point of views on existing features and even "moonshots"

Don't hold back 😅

 

Around a couple of months later I ended up joining the team.

With about 75 PRs under your belt by then, safe to say we felt pretty good about your ability to contribute. 😄

 

We all thought you were in the core team long before you got the offer 😉

 

Some additional thoughts that I didn't want to try and cram into the post:

Alongside the work that goes into the community kernel which is this codebase, we look forward to improving the resources and tooling for use of our API to extend what we can all do together.

We have had some really interesting projects crop up and I can't wait to see what's next!

For an eye on some of the off-platform development we are trying to enable, check out this post:

And for some more reading on where our head is at with the health of the developer ecosystem and online publishing, check out this post:

 

A whole year, wow, doesn't time fly!

EDIT:

I like @rhymes idea of showing first pull requests!

My first pull request was to move the menu down by 8 pixels, just to test the waters.

Move menu background down 8 pixels #1227

Description

Move menu background down 8 pixels to prevent seemingly random bumps.

I probably ought to have left this for someone as a first PR but it bugs me 😉

Related Tickets & Documents

#1160 #1213

Added to documentation?

  • [ ] docs.dev.to
  • [ ] readme
  • [x] no documentation needed

But I'm most proud of implementing CSS variables, something @ben took a chance on and let me implement.

The wonder of having a community like this is how quickly the CSS variables evolved, thanks to people adding to them and finding places I'd missed.
This allowed for multiple themes to be created.

Beginning of css variable implementation (--theme-background) #1306

What type of PR is this? (check all applicable)

  • [ ] Refactor
  • [x] Feature
  • [ ] Bug Fix
  • [ ] Documentation Update

Description

Added --theme-background leaving the default the same. This will make no, visible, change to the styles currently.

Adding CSS variables means loading a CSS file containing overrides means you can change the whole sites theme.

:root {
  --theme-background: #303030
}

Related Tickets & Documents

#1104 and #1377

Added to documentation?

  • [ ] docs.dev.to
  • [ ] readme
  • [x] no documentation needed

❤️🧡💛💚💙💜🤎🤍

 
 

Yes! And thank goodness for your awesome ideas and contributions in getting themes going with variables, among other great CSS contributions. It's been such a boon to our frontend efforts.

 

Proud of what you have accomplished. Definitely love what you are doing. Hoping i can be a major contributor in the coming years. I moved from Medium paid membership to Dev and i have not regretted it. Keep winning! We are by your side.

 

Congrats to the entire team! I've loved this project/community since the first day I joined. 🔥

Awesome team

 

And here's my first PR. It was when the repository was private, so I can't link the PR as the number is no longer the same in the public repo, github.com/thepracticaldev/dev.to/...

My First PR to dev.to

 

Congrats team! Thanks for building this amazing platform and community!

 

Thanks Desi! We couldn't do it without folks like you who bring such a positive, constructive presence.

 

Congratulations! There is something about DEV.to that is unique and stands out alongside other developer communities. It is definitely one of the most welcoming communities I have seen. Keep up the great work!

 

One word guyz. AMAAAAZINGGG Community. I am really loving the experience over here at dev.to and cant wait to contribute back, yesterday i did fork the code and was struggling to get things running, will eventually.

I was really thinking that the whole app experience can be simplistically and smoothing made using ionic as a framework with all the push notifications and stuff, one of the possibility.

Well let time pass and surely with patience great minds meet.

I am going through the docs, and do hope for me to bug you again and again and again on email for things i mught need to understand.

Born to learn till i die. Cheers Guyz!

 

While there are plenty of open-source projects, really few websites have made the move. I would guess the main reasons are security (easier to find a breach) and website stability (keeping a good UX could be difficult with tons of contribution).

I hope to see more and more websites taking this path in the future.

Could you share with us the key to make an open-source website project successful, and how is it different from a normal open-source project?

Have you experienced things like bug-bounty or "feature-bounty"?

Do you think this would be possible if your community wasn't a developers community? Let say that instead of dev.to you started by building community.nba.com. What would have been different?

 

Want to say thanks for creating Dev.to.

Not being a Ruby dev (or web frontend) I probably won't be creating any PRs soon, but I surely benefit from the community it creates by being opensource and applaud the move. But given all the other languages I've learned over the years, who knows what the future might bring.

Year 2 looks like it will be a good one!

 

Great job! I have some questions for you.

  1. How many people work on the platform for dev.to?
  2. Let's say I would like to start a dev community (for example, embedded.dev), what would it looks like for a person to handle it (time, money, resources, knowledge)?

As of right now, except on Reddit, embedded system communities are built around manufacturers. I don't know if you visited some lately, but the majority of them (NXP, STMicro, Mbed) are slow (I mean, 15-20 seconds latency slow) in navigating on their systems and are not community-friendly.

Again, thanks for the platform. Very great job.

 

I can help you with that. I have done 4 years in electrical engineering, so buzz me up. Surely things can come up to mark.

 

Congrats team for this milestone. Really excited to see how phase two unfolds. Kudos to all that ya'll have achieved so far.

 

Another comparable community to dev.to I can find is hashnode.com. Features parity, I like it similar to how I like dev.to in term of easy publishing. But recently they launched DevBlog where you can point your domain to their server and enjoy publishing under your own domain with all the hashnode tools. Your own domain's blog post also get post to the main feed on hashnode.com (configurable) so you will not miss all the potential audiences of your posts.

If you don't use custom domain, by default you'll get yourname.hashnode.com for your blog. Since you can exempt certain posts from being pushed to the main feed, you're free to post non-dev stuff on your blog without cluttering the main feed on hashnode.com.

 

I am very happy with this website as I always read. It sucks when you want to read and there is a quota, especially in Medium.

code of conduct - report abuse