DevOps Zone is brought to you in partnership with:

I am the API Evangelist. Not in the sense that I’m evangelizing a single API to you--In the sense that APIs are important for everyone to be aware of. I’m paying attention to not just the technical, but the business and politics of the web API movement. I share my insights by blogging on the business of APIs at apievangelist.com, politics of APIs at apivoice.com and you can find more information about me at kinlane.com. Kin is a DZone MVB and is not an employee of DZone and has posted 91 posts at DZone. You can read more from them at their website. View Full User Profile

Creating Two Levels of Open Engagement with Github Pages and Disqus

03.06.2013
| 2349 views |
  • submit to reddit

I’m moving all my side projects to run on GitHub as open source repositories. One of my goals in doing this, is to facilitate engagement around my projects, as opposed to developing them in isolation.

My projects all start as a public GitHub repository, equipped a subdomain pointed at a GitHub Pages and a Jekyll site template--allowing me to add pages and give the project its own blog.

By default all pages and blog entries will have Disqus enabled for conversation around all aspects of the project.  

This approach to project management will open up two levels of engagement from users:

  1. Casual - Quick comments and feedback via Disqus as users come across a project
  2. Deep - Fork a project and commit back blog posts, pages or other more structured data as JSON files

In 2013 my goal is to make sure all projects use this format by default. It really isn’t any more work than what I’m doing now--with a huge amount of benefits.

Hopefully more of my work will see the light of day, and it will encourage casual and deeper engagement from anyone with the interest.

Published at DZone with permission of Kin Lane, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)