7 May

Weekly Update 100: Celebrating open source

This is a copy of our weekly newsletter for developers which you can subscribe to here.

Hello contributors,

As you may have seen, this week we had an article published on opensource.com that explains some of our experiences building up the DuckDuckHack community. It was 2012 when we first started receiving code contributions, and since then we've learned a lot about how to make contributing easier, and how to encourage more people to join in. We're still working on improvements and plans for the future, and of course welcome your comments and ideas.

We also support other open source communities and initiatives, as can be seen in our announcement of open source donations for 2016. These were based on your nominations for which we're very grateful, and we encourage everyone to learn more about the recipient projects.

In the meantime, here are some coding suggestions for this week...

5-minute Fixes

Weekend Warriors

IAs for Adoption

Quick Tip

It's easy to make spelling mistakes when typing commands, but did you know Git has a feature to automatically correct such mistakes (typos)? Autocorrect is one of Git's built-in options and can be enabled with this command:

git config --global help.autocorrect 1

Then you're ready to go! Let's see it in action with an incorrect spelling:

git chekout master

With autocorrect enabled, this incorrect command will still be recognized and executed. A handy option meaning less re-typing.

Have a nice weekend everyone!

  • The DuckDuckGo Staff
5 Tweet

This blog has been archived

Thank you for reading and contributing lively discussion to our blog! Read more posts about online privacy on our new blog at spreadprivacy.com.

That's good for the community !

posted by SamuelLauradou • 2 years and 4 months ago Link

Great news ! :)

posted by MathieuCaneau • 2 years and 5 months ago Link

Thank you for those news, that's great

posted by ChristanDuveau • 2 years and 5 months ago Link

You wrote:

Then you're ready to go! Let's see it in action:

git chekout master

I think it has to be:

git checkout master

posted by jumpball • 2 years and 5 months ago Link

Hi jumpball.

Thanks for pointing that out. Actually, the mistake was intentional to show how Git autocorrect can fix it automatically. I've updated the blog post to make this a bit clearer.

posted by tagawa Staff • 2 years and 5 months ago Link